1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Kismet on the wrt54gs

Discussion in 'Cisco/Linksys Wireless Routers' started by troycicle, Jul 18, 2004.

  1. troycicle

    troycicle Network Guru Member

  2. lud

    lud Network Guru Member

    I have a wrt54gs and used kismet-feb.04.01-wrt54.tar.gz I got somewhere i can't remember...

    It nearly works on my HyperWRT firmware !

    I use this source for the drone: source=WRT54G,prism0,WRT54G

    I needed to run 'wl ap 0', and 'wl scan; wl scanresults' and found some APs, but I have some bugs:
    1- SNR levels are not reported
    2- channels can't be changed (and no channel hopping of course).

    So I need to:
    1- run 'wl scan...'
    2- set the channel manually with 'wl channel X'
    3- run kismet-drone.

    Maybe I should try a more recent kismet ?
     
  3. suid

    suid Network Guru Member

  4. jlw

    jlw Network Guru Member

    GAH.. I cant get my wrt54gs to run kismet under hyperwrt... getting this error:

    # ./kismet_drone -f kismet_drone.conf
    Using alternate config file: kismet_drone.conf
    Suid priv-dropping disabled. This may not be secure.
    No specific sources given to be enabled, all will be enabled.
    Disabling channel hopping.
    ): Enabling monitor mode for WRT54G source interface eth1 channel 6...
    ): Opening WRT54G source interface eth1...
    FATAL: pcap reported netlink type 1 (EN10MB) for eth1. This probably means you're not in RFMON mode or your drivers are reporting a bad value. Make sure you have the correct drivers and that entering monitor mode succeeded.


    Have tryd eth0 and eth1 and br0
     
  5. suid

    suid Network Guru Member


    I'm running Alchemy-6.0-RC5a v3.01.3.8sv, duno if this will help you but it works for me and with how i have everything situated at the time being.

    Wget the kismetdrone tarball into the /tmp directory on the WRG54GS , then extract the archive files and rename the kismetdrone folder to kismet. Once thats done you can edit the correct paramters on the drone config file by using vi /tmp/kismet/etc/kismet_drone.conf, or whatever text editor you have compiled on the router.
    Make sure your interface is available, ifconfig -a should show you what ifaces are up and which ones are available just like a nix box.

    BusyBox v1.00 (2004.12.04-16:43+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    ~ # ifconfig
    br0 Link encap:Ethernet HWaddr 00:12:17:40:ED:CE
    inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:84669 errors:0 dropped:0 overruns:0 frame:0
    TX packets:63564 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:8465693 (8.0 MiB) TX bytes:56767706 (54.1 MiB)

    br1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.255.255.0
    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)

    eth0 Link encap:Ethernet HWaddr 00:12:17:40:ED:CE
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:3377757 errors:4 dropped:0 overruns:4 frame:4
    TX packets:710356 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:494302265 (471.4 MiB) TX bytes:351777140 (335.4 MiB)
    Interrupt:5 Base address:0x2000

    eth1 Link encap:Ethernet HWaddr 00:12:17:40:ED:D0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:72583
    TX packets:18233 errors:8597 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:0 (0.0 B) TX bytes:2206193 (2.1 MiB)
    Interrupt:4 Base address:0x1000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
    RX packets:1278 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1278 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:79360 (77.5 KiB) TX bytes:79360 (77.5 KiB)

    vlan0 Link encap:Ethernet HWaddr 00:12:17:40:ED:CE
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:505152 errors:0 dropped:0 overruns:0 frame:0
    TX packets:466218 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:49677415 (47.3 MiB) TX bytes:314620331 (300.0 MiB)

    vlan1 Link encap:Ethernet HWaddr 00:12:17:40:ED:CF
    inet addr:69.169.18.52 Bcast:69.169.31.255 Mask:255.255.240.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2872601 errors:0 dropped:0 overruns:0 frame:0
    TX packets:244138 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:383825024 (366.0 MiB) TX bytes:37156809 (35.4 MiB)



    that out put there from ifconfig is with the sniffing interface down.

    Follow the same instructions given on the http://toys.lerdorf.com site with

    wl disassoc
    wl passive
    wl scan
    wl scanresults

    after that you should be able to lunch /tmp/kismet/bin/kismet_drone &

    What i usually like to do is check my ifaces after the disassoc and scanresullt to see what iface is up and if its the same one thats on the /tmp/kismet/etc/kismet_drone.conf. If all good then it should all work out. The configs for drone is calling for eth1 but if that fails try

    wl prism0 monitor 1

    then

    ifconfig prism0 up

    and it should all go from there. Lot of it is pretty self explanitory just a little bit of editing configs and just like a computer poke around and see what your options are. Good Luck
     
  6. jlw

    jlw Network Guru Member

    kismet on my wrt54gs makes my network sloooooow
     

Share This Page