Hi guys, having issues with monitor mode using 0.15rc2, same behaviour as
previous versions of the driver, in that kismet seems to bomb after a few
seconds.. I dont think its a Kismet issue though...
-----------------------
On card insertion:
-----------------------
orinoco 0.15rc2STA (David Gibson
<hermes-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@xxxxxxxxxxxxxxxx>, Pavel Roskin
<proski-mXXj517/zsQ@xxxxxxxxxxxxxxxx>, et al)
orinoco_cs 0.15rc2STA (David Gibson
<hermes-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@xxxxxxxxxxxxxxxx>, Pavel Roskin
<proski-mXXj517/zsQ@xxxxxxxxxxxxxxxx>, et al)
eth1: Hardware identity 0001:0001:0004:0000
eth1: Station identity 001f:0001:0007:001c
eth1: Firmware determined as Lucent/Agere 7.28
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:2D:0F:D2:23
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 5.0, irq 10, io 0x0100-0x013f
eth1: New link status: Connected (0001)
-----------------------
Running kismet_server:
-----------------------
ballburner:/home/ewan/orinoco-0.15rc2# kismet_server
Will drop privs to ewan (1000) gid 1000
Enabling channel hopping.
Enabling channel splitting.
Source 0 (orinocosource): Enabling monitor mode for orinoco source interface
eth1 channel 6...
Source 0 (orinocosource): Opening orinoco source interface eth1...
Spawned channelc control process 4323
Dropped privs to ewan (1000) gid 1000
Allowing clients to fetch WEP keys.
Logging networks to Kismet-Nov-12-2004-3.network
Logging networks in CSV format to Kismet-Nov-12-2004-3.csv
Logging networks in XML format to Kismet-Nov-12-2004-3.xml
Logging cryptographically weak packets to Kismet-Nov-12-2004-3.weak
Logging cisco product information to Kismet-Nov-12-2004-3.cisco
Logging gps coordinates to Kismet-Nov-12-2004-3.gps
Logging data to Kismet-Nov-12-2004-3.dump
Writing data files to disk every 300 seconds.
Filtering PHY layer packets.
Mangling encrypted and fuzzy data packets.
Not tracking probe responses or associating probe networks.
Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
Dump file format: wiretap (ethereal libwiretap) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2004.04.devel (Kismet)
Logging data networks CSV XML weak cisco gps
GPSD cannot connect: Connection refused
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
Fri Nov 12 16:37:02 2004 Found new network "<no ssid>" bssid 00:0F:3D:A0:03:4A
WEP N Ch 0 @ 0.00 mbit
Fri Nov 12 16:37:02 2004 Found IP 136.201.99.21 for <no
ssid>::00:B0:D0:BE:F9:6F via ARP
Fri Nov 12 16:37:02 2004 Found IP 136.201.151.199 for <no
ssid>::00:30:05:28:CA:46 via ARP
Fri Nov 12 16:37:02 2004 Found SSID "BDS" for network BSSID 00:0F:3D:A0:03:4A
Fri Nov 12 16:37:02 2004 Found IP 136.201.107.125 for BDS::00:0A:95:D9:20:84
via UDP
Fri Nov 12 16:37:02 2004 Found new network "csis-wlan" bssid 00:0D:54:FC:15:C0
WEP N Ch 12 @ 36.00 mbit
Fri Nov 12 16:37:03 2004 Found new network "csis-wlan" bssid 00:0D:54:FC:15:69
WEP N Ch 12 @ 36.00 mbit
Fri Nov 12 16:37:03 2004 Found IP 136.201.10.95 for BDS::00:01:63:B0:34:00 via
ARP
Fri Nov 12 16:37:03 2004 Found IP 136.201.16.45 for BDS::00:30:05:03:B4:33 via
ARP
Fri Nov 12 16:37:03 2004 Found IP 136.201.157.242 for BDS::00:0B:CD:86:83:C9
via ARP
Fri Nov 12 16:37:03 2004 Found IP 136.201.1.45 for BDS::00:10:5A:36:E9:3F via
ARP
Fri Nov 12 16:37:06 2004 Found IP 136.201.132.215 for BDS::00:10:4B:59:BD:63
via TCP
Fri Nov 12 16:37:06 2004 Found IP 136.201.107.153 for BDS::00:0A:95:96:38:80
via UDP
Fri Nov 12 16:37:06 2004 Found IP 136.201.16.45 for BDS::00:30:05:03:B4:33 via
TCP
Fri Nov 12 16:37:09 2004 Found IP 136.201.1.49 for BDS::00:B0:D0:AA:1F:8F via
ARP
Fri Nov 12 16:37:09 2004 Found IP 136.201.149.47 for BDS::00:B0:D0:D5:3D:A4 via
ARP
Fri Nov 12 16:37:09 2004 Found IP 136.201.132.220 for BDS::00:10:4B:59:BF:9B
via ARP
Fri Nov 12 16:37:09 2004 Found IP 136.201.16.167 for BDS::00:0E:7F:23:D3:FB via
ARP
Fri Nov 12 16:37:09 2004 Found IP 136.201.152.18 for BDS::00:06:5B:C3:2A:7D via
ARP
Fri Nov 12 16:37:11 2004 Found IP 136.201.144.215 for BDS::00:80:AD:81:B9:C5
via TCP
Fri Nov 12 16:37:11 2004 Found IP 136.201.16.152 for BDS::00:30:05:1F:76:CD via
ARP
Fri Nov 12 16:37:11 2004 Found IP 136.201.16.154 for BDS::00:30:05:1D:5E:47 via
ARP
Fri Nov 12 16:37:11 2004 Found IP 136.201.16.143 for BDS::00:E0:18:46:20:00 via
ARP
Fri Nov 12 16:37:11 2004 Found IP 136.201.10.99 for BDS::00:D0:95:7C:2F:28 via
ARP
Fri Nov 12 16:37:11 2004 Found IP 136.201.16.151 for BDS::00:30:05:1B:D6:7C via
ARP
Fri Nov 12 16:37:11 2004 Found IP 136.201.16.35 for BDS::00:90:27:AC:8C:E7 via
ARP
Fri Nov 12 16:37:12 2004 Found IP 136.201.1.23 for BDS::00:04:76:21:79:F5 via
ARP
Fri Nov 12 16:37:14 2004 Found IP 136.201.146.164 for BDS::00:0B:5D:4E:EB:72
via ARP
Fri Nov 12 16:37:14 2004 Found IP 136.201.16.8 for BDS::00:A0:C9:EC:82:94 via
ARP
FATAL: Failed to set channel 3 16:Device or resource busy
Terminating.
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't see any weak encryption packets, unlinking weak file
Sending termination request to channel control child 4323...
Waiting for channel control child 4323 to exit...
Kismet exiting.
----------------------------
What comes up in the dmesg:
----------------------------
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
eth1: IRQ handler is looping too much! Resetting.
Any ideas? Im running kernel 2.6.7-mm6 on Debian Unstable. Card works fine
in Managed and Ad-Hoc modes.
Thanks
Ewan
--
Ewan Oughton [0143324]
4th Year B.Sc. Comp Sys
DB / AnonFTP / Orac Root Admin SkyNet
http://www.10xshot.com
ICQ: 57047095
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
|
