PDA

View Full Version : [ubuntu] iwl3945 wireless monitor mode


Anomander
May 7th, 2008, 06:25 AM
I see that Hardy has switched to the iwl driver for intel wireless chips.
I'm having trouble switching the driver into monitor mode, something that used to work ok with the old ipw drivers.
I'm trying to use wireshark to do some wireless sniffing.

When I try to flip the iwl3945 driver into monitor mode with:
sudo iwconfig wlan0 mode monitor

I get:
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.

I know the driver is basically working because I can get it to scan with:
sudo iwlist wlan0 scanning.
That gives me results.

Anyone know anything about this driver and how to get it to sniff?

Cannaregio
May 7th, 2008, 09:44 AM
Same problem here.
iwl3945 on a Amilo Fujitsu Siemens on Hardy
Monitoring (and kismet) only work if I boot with previous kernel 2.6.22-14 generic instead of new kernel 2.6.24-17.

Didn't find a solution (yet).

Anyone can help?

chili555
May 7th, 2008, 09:55 AM
Anyone can help?Sure, chili can help. Please try:sudo ifdown wlan0
sudo iwconfig wlan0 mode monitorThen start up Kismet or whatever. When you are finished, do:sudo iwconfig wlan0 mode managed
sudo ifup wlan0

Anomander
May 7th, 2008, 10:17 AM
No, that didn't work.
Same problem.
I also tried killing NetworkManager, thinking that might get in the way, but still no luck.

Cannaregio
May 7th, 2008, 10:29 AM
Sure, chili can help. Please try:sudo ifdown eth1
sudo iwconfig eth1 mode monitorThen start up Kismet or whatever. When you are finished, do:sudo iwconfig eth1 mode managed
sudo ifup eth1


chili you'r da man !!
your solution works perfectly (with eth1 instead of wlan0 in my case)
still I would like to know why my card did work well in Gutsy (auto setting in monitor mode when starting kismet and automatically back to managed when exiting) and now does require such gimmicks in Hardy...

thanks again