![]() |
|
|||||||
| Register | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Registered Member
Join Date: Aug 2004
Posts: 16
|
Trouble throwing Senao NL-2511CD plus ext2 card into monitor mode
I'm currently using this card with hostap driver on a hard drive installed copy of Auditor.
I can't seem to throw the card into monitor mode manually with iwconfig. I'm getting "not supported" errors. Kismet is also complaining about same thing. Below is the supporting info for the investigation I've done. Now the thing is, the hostap driver works fine for connecting to my cheapo linksys wap. I can connect fine.(but cannot set a WEP key, but that's a seperate issue. The question I have is should I be using the wlan_ng driver instead of the hostap driver? Might this be a firmware issue? I've searched these forums and haven't seen any closely related posts. I've searched the kismet docs and have my capture source set to: source=hostap,wlan0,6 Can anyone who uses this card point me in the right direction? ---------------------------supporting info------------------------------- Ok here's my card: ############################################## Socket 0: no product info available Socket 1: product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", "" manfid: 0x0156, 0x0002 function: 6 (network) ############################################## Translation: It's a Senao NL-2511CD plus ext2 card ##############################################Scri pt started on Sat May 13 23:30:24 2006 root@auditor:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:04:76:40:B0:54 BROADCAST 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:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xe800 eth1 Link encap:UNSPEC HWaddr 44-4F-C0-00-11-95-54-01-00-00-00-00-00-00-00-00 BROADCAST 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:1000 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:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:400 (400.0 b) TX bytes:400 (400.0 b) wlan0 Link encap:Ethernet HWaddr 00:02:6F:35:3B:EB 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:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:3 Base address:0x100 root@auditor:~# iwconfig lo no wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. wlan0 IEEE 802.11-b ESSID:"nixyes" Nickname:"nixyes" Mode:Managed Frequency:2.462 GHz Access Point: 00:0C:41:68:BA:46 Bit Rate:11 Mb/s Tx-Power:2346 dBm Retry min limit:8 RTS thr ff Fragment thr ffEncryption key ffLink Quality=92/92 Signal level=-40 dBm Noise level=-100 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 root@auditor:~# iwconfig wlan0 mode monitor Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not supported. root@auditor:~# iwconfig wlan0 mode monitor wlan0 mode monitor Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not supported. root@auditor:~# iwconfig wlano mode monitor Error for wireless request "Set Mode" (8B06) : SET failed on device wlano ; No such device. root@auditor:~# monitor .wlan wlan0 11 message=lnxreq_wlansniff enable=true channel=11 prismheader=false wlanheader=false keepwepflags=true stripfcs=true packet_trunc=no_value resultcode=success root@auditor:~# iwconfig wlan0 wlan0 IEEE 802.11-DS ESSID:"nixyes" Nickname:"nixyes" Mode:Managed Frequency:2.462 GHz Access Point: 00:0C:41:68:BA:46 Bit Rate:2 Mb/s Tx-Power:2346 dBm Retry min limit:8 RTS thr ff Fragment thr ffEncryption key ffLink Quality=0/92 Signal level=-69 dBm Noise level=-90 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ########################################### Kismet config: source=hostap,wlan0,6 ################### kismet error root@auditor:~# kismet Server options: none Client options: none Starting server... Waiting for server to start before starting UI... Suid priv-dropping disabled. This may not be secure. No specific sources given to be enabled, all will be enabled. Enabling channel hopping. Enabling channel splitting. Source 0 (6): Enabling monitor mode for hostap source interface wlan0 channel 6... FATAL: Failed to retrieve list of private ioctls 95:Operation not supported |
|
|
|
|
|
#2 (permalink) | |
|
I amuse you?
Join Date: Dec 2003
Posts: 9,127
|
Quote:
http://www.remote-exploit.org/index.php/Auditor_main |
|
|
|
|
|
|
#3 (permalink) |
|
Registered Member
Join Date: Aug 2004
Posts: 16
|
Ok see if this makes sense
On a hunch I did the following:
switch-to-wlanng ran cardinfo and ejected and reinserted card state.wlan wlan0 enable;monitor.wlan wlan0 6 tail /var/log/messages and I saw: May 14 10:30:10 auditor kernel: linkstatus=CONNECTED May 14 10:30:41 auditor kernel: monitor mode enabled May 14 10:30:41 auditor kernel: device wlan0 entered promiscuous mode light on the card is now blinking. Am I correct here in saying that switching to the wlan_ng driver successfully threw the card in monitor mode? The thing is when I rerun iwconfig wlan0 it still indicates the Mode as Managed. ??? |
|
|
|
|
|
#4 (permalink) | |
|
I amuse you?
Join Date: Dec 2003
Posts: 9,127
|
Quote:
|
|
|
|
|