OpenWrt Forum Archive

Topic: Monitor mode on Asus WL-500GP V2 -> reboot

The content of this topic has been archived on 12 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
Cypher
31 May 2008, 22:45

Hi!

I have some strange problems and hope you can help me. sad

root@wBox:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:346 errors:0 dropped:0 overruns:0 frame:0
          TX packets:350 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:49574 (48.4 KiB)  TX bytes:44088 (43.0 KiB)

eth0      Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:345 errors:0 dropped:0 overruns:0 frame:0
          TX packets:348 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:56068 (54.7 KiB)  TX bytes:46960 (45.8 KiB)
          Interrupt:4

eth0.0    Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:346 errors:0 dropped:0 overruns:0 frame:0
          TX packets:350 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:50958 (49.7 KiB)  TX bytes:45488 (44.4 KiB)

eth0.1    Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          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
          UP LOOPBACK RUNNING  MTU:16436  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)

wl0       Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:284
          TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:20584 (20.1 KiB)
          Interrupt:2 Base address:0x2000

root@wBox:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      no wireless extensions.

eth0.0    no wireless extensions.

eth0.1    no wireless extensions.

br-lan    no wireless extensions.

wl0       IEEE 802.11-DS  ESSID:"OpenWrt"
          Mode:Master  Frequency:2.432 GHz  Access Point: 00:1F:C6:62:1B:64
          Bit Rate=54 Mb/s   Tx-Power:32 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Link Quality:5  Signal level:0  Noise level:169
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@wBox:~# wl down; wl up; wl monitor 1;
root@wBox:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:439 errors:0 dropped:0 overruns:0 frame:0
          TX packets:438 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:61817 (60.3 KiB)  TX bytes:63020 (61.5 KiB)

eth0      Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:438 errors:0 dropped:0 overruns:0 frame:0
          TX packets:436 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:71237 (69.5 KiB)  TX bytes:66636 (65.0 KiB)
          Interrupt:4

eth0.0    Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:439 errors:0 dropped:0 overruns:0 frame:0
          TX packets:438 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:63573 (62.0 KiB)  TX bytes:64772 (63.2 KiB)

eth0.1    Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          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
          UP LOOPBACK RUNNING  MTU:16436  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)

prism0    Link encap:UNSPEC  HWaddr 00-1F-C6-62-1B-64-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST MULTICAST  MTU:0  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)

wl0       Link encap:Ethernet  HWaddr 00:1F:C6:62:1B:64
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:350
          TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:25349 (24.7 KiB)
          Interrupt:2 Base address:0x2000
root@wBox:~# iwconfig
[CONNECTION TIMEOUT -> ROUTER REBOOT]

If I execute now (in monitor mode) "iwconfig", "kismet_server"(prism0) or anything else with wireless the router crashes and reboots.

Is it possible to solve that?
What must I do? sad

I compiled trunk r11269 with kernel 2.4 and as "WL-500gp" on "target profile".

BIG THX!

Cypher

//edit:
TCPDUMP with prism0 interface works fine...
But I need Kismet... :s

Kismet example:

root@wBox:~# wl down; wl up; wl monitor 1; sleep 1; /kismet.sh
Using alternate config file: /tmp/kismet/kismet.conf
Suid priv-dropping disabled.  This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Disabling channel splitting.
Source 0 (wl500gp): Enabling monitor mode for wrt54g source interface prism0 channel 0...
prism0    no private ioctls.

Source 0 (wl500gp): Opening wrt54g source interface prism0...
Allowing clients to fetch WEP keys.
WARNING:  Logging (gps coordinates) enabled but XML logging (networks) was not.
It will be enabled now.
SSID cloak file did not exist, it will be created.
IP track file did not exist, it will be created.
Logging networks in CSV format to /tmp/kismetrecs/1_Jan-01-2000.csv
Logging networks in XML format to /tmp/kismetrecs/1_Jan-01-2000.xml
Logging gps coordinates to /tmp/kismetrecs/1_Jan-01-2000.gps
Logging data to /tmp/kismetrecs/1_Jan-01-2000.dump
Writing data files to disk every 86400 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
WARNING:  Unable to open '/etc/ap_manuf' for reading (No such file or directory), AP manufacturers and defaults will not be detected.
WARNING:  Unable to open '/etc/client_manuf' for reading (No such file or directory), client manufacturers will not be detected.
Using network-classifier based data encryption detection
Not tracking duplicate IVs
Dump file format: wiretap (local code) dump
Kismet 2007.10.R1 (wBox)
Logging data CSV XML gps
GPSD unknown host 'localhost'
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Allowing connections from 192.168.0.0/255.255.255.0
Allowing connections from 192.168.1.0/255.255.255.0
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
[CONNECTION TIMEOUT -> ROUTER REBOOT]

thx a lot for every help smile

(Last edited by Cypher on 31 May 2008, 23:37)

Post #2
Cypher
5 Jun 2008, 16:20

Some users were talking about ioctl and that there would be an error in it.
Anyone know more or how to solve?
Thank you very much! smile

Post #3
Cypher
7 Jun 2008, 13:58

Problem solved!

Before starting Kismet:

wl down; wl up; wl monitor 1;

in kismet.conf:

source=wrt54g,wl0,wl500gp

//edit:
wl down; wl up; is important because without that before wl monitor 1; the router often dont switch to monitor mode.

(Last edited by Cypher on 7 Jun 2008, 14:00)

The discussion might have continued from here.