Does this happen if you connect to your network via WICD or manual wireless connection setup ?
This is a new install of Backtrack 5.3 with nmap 6.01. From what I've read in these forums and on Google, this problem is being caused by monitor mode. My question is how to I end monitor mode, but keep connected to my network?
-The error happens on both eth0 and wlan0 interfaces.
-nmap starts to work, if I use the --unprivileged switch, but then complains that it can't run most scans that way.
-when I use 'airmon-ng stop wlan0' it shows "monitor mode disabled", but then I'm disconnected from my network.
So suggestions about how to get nmap started would be appreciated. This is most likely a user problem.
Monitor mode will only function on wlan0 as this is an 802.11 function and is not applicable to ethernet adaptors.
Monitor mode is not necessary to associate with a network, have you tried not entering monitor mode in the first place, associating with the network (ensure you have an IP address and can communicate with other hosts on the network) and then tried running the scan?
So far I have tried to connect using WiCd and manually for the wifi0 port. Presumably, when I use a manual connection, I'm not in monitor mode?
The 'nmap --iflist' command shows "INTERFACES: NONE FOUND!", but I can ping my local router and google, so I'm obviously connected.
Monitor mode seems to be the problem. What command tells me that I am or am not in monitor mode?
it should be airmon-ng stop mon0
SOLUTION...The problem was solved after reading the FAQ and then upgrading my software. Apparently, the problem is fixed by updates, and now NMAP works normally. Thanks to all who tried to help.