Results 1 to 5 of 5

Thread: wg511t wtf am i doing wrong here??

  1. #1
    Junior Member default's Avatar
    Join Date
    Nov 2007
    Posts
    87

    Default wg511t wtf am i doing wrong here??

    Ok, I'm tired and trying to figure out this foreign linux language.

    This is what i get when i type:

    "airmon-ng stop ath0"


    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    wifi1 Atheros madwifi-ng



    and this is what i think want to have (going by the tutorial video):

    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    ath0 Atheros madwifi-ng VAP (parent: wifi0) (VAP destroyed)


    What do i do?

    If i type iwconfig i get

    lo no wireless extension
    eth0 ''
    wifi0 ''
    wifi1 ''

    ?

    when i fire up kismet and it only works from wifi1? and makes an ath0, then every other time i fire up kismet it makes another ath# ? whaaaaaaaa? please explain



    I suspect, i may have screwed something up trying to get my orinoco and prism cards working, but now i have an atheros card. Another card another set of problems, sigh I'm so ****en tired and stressed right now

  2. #2
    Developer
    Join Date
    Mar 2007
    Posts
    6,126

    Default

    Ignore the first command because thats me loading my drivers which you should not have to do
    Code:
    purehate ~ # modprobe ath_pci
    purehate ~ # airmon-ng stop ath0
    
    
    Interface       Chipset         Driver
    
    wifi0           Atheros         madwifi-ng
    wlan0           RTL8187         r8187
    ath0            Atheros         madwifi-ng VAP (parent: wifi0) (VAP destroyed)
    
    purehate ~ # airmon-ng start wifi0
    
    
    Interface       Chipset         Driver
    
    wifi0           Atheros         madwifi-ng
    wlan0           RTL8187         r8187
    ath0            Atheros         madwifi-ng VAP (parent: wifi0) (monitor mode enabled)
    
    purehate ~ # ifconfig
    ath0      Link encap:UNSPEC  HWaddr 00-14-6C-FC-4B-68-04-00-00-00-00-00-00-00-00-00
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:164 errors:0 dropped:0 overruns:0 frame:0
              TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:218912 (213.7 KiB)  TX bytes:218912 (213.7 KiB)
    
    vmnet1    Link encap:Ethernet  HWaddr 00:50:56:C0:00:01
              inet addr:172.16.243.1  Bcast:172.16.243.255  Mask:255.255.255.0
              inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    
    vmnet8    Link encap:Ethernet  HWaddr 00:50:56:C0:00:08
              inet addr:192.168.81.1  Bcast:192.168.81.255  Mask:255.255.255.0
              inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    
    wifi0     Link encap:UNSPEC  HWaddr 00-14-6C-FC-4B-68-76-6D-00-00-00-00-00-00-00-00
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:1792 errors:0 dropped:0 overruns:0 frame:2751
              TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:199
              RX bytes:180 (180.0 b)  TX bytes:1794 (1.7 KiB)
              Interrupt:18
    
    wlan0     Link encap:Ethernet  HWaddr 00:C0:CA:19:AA:9B
              inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::2c0:caff:fe19:aa9b/64 Scope:Link
              UP BROADCAST NOTRAILERS RUNNING PROMISC ALLMULTI  MTU:1500  Metric:1
              RX packets:352794 errors:0 dropped:287786 overruns:0 frame:0
              TX packets:237309 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:487353053 (464.7 MiB)  TX bytes:58010171 (55.3 MiB)
    
    purehate ~ #
    Now you are in monitor mode as you can see with the iwconfig command

  3. #3
    Junior Member default's Avatar
    Join Date
    Nov 2007
    Posts
    87

    Default

    That made it start monitor mode on ath2 ? and there is an ath1 in managed mode ? and for some reason there's also an eth0? what's that doing there?

    airodump doesn't receive any data from ath2

    I tried booting from live and running but it must have read from the hdd config or something? maybe i should disable my hdd and see if that helps, or burn everything and give up

  4. #4
    Junior Member default's Avatar
    Join Date
    Nov 2007
    Posts
    87

    Default

    cool, got it sussed now. Ill Just use the wifi1 and it's parent ath1, have no idea why the ath0, wifi0, lo and eth0 are there but as long as they don't start any trouble they can stay where they want




    edit: further more, after 3 weeks of trying and 3 different cards i have finally managed to associate my mac with the damn router, yay, that's a good start

  5. #5
    Developer
    Join Date
    Mar 2007
    Posts
    6,126

    Default

    you can destroy all un needed interfaces with the airmon-ng stop command

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •