nmap: interfaces/route NONE FOUND

[4xh3ll]

Hi everyone,
i have a problem with nmap:

root@bt:~/nmap-5.61TEST2# nmap --iflist

Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-11-15 14:42 CET
INTERFACES: NONE FOUND(!)
ROUTES: NONE FOUND(!)

in fact with any command i get the error:

route_dst_netlink: can't find interface "eth0"

and if i specify the iface(-e eth0):

I cannot figure out what source address to use for device eth0, does it even exist?
QUITTING!

This happens with any ifaces.

Could someone help me, pls?

hi

EDIT
x86 permanent on usb

[4xh3ll]

Update:
disabling the monitor mode on wlanx, nmap work properly with all the iface.......why???
Please, let me know if this happens to you too. Probably i should contact nmap developers...

[scottm99]

Run ifconfig at the command line to show your available interfaces. That, and dmesg should give you some troubleshooting help. Are you running BT5 in a virtual machine? If so, you may need to connect/activate the network interface(s) in your VM software.

[thorin]

Does your system actually have a network connection? (Did you physically plug it in or have you configured a wireless connection that is actually working?)
Do you have an address? (ifconfig)
Did you try to get an address? (dhclient)
etc

[4xh3ll]

Run ifconfig at the command line to show your available interfaces. That, and dmesg should give you some troubleshooting help. Are you running BT5 in a virtual machine? If so, you may need to connect/activate the network interface(s) in your VM software.

i saw dmesg before and after enabling promiscuous mode on wlan iface and no error occured

Does your system actually have a network connection? (Did you physically plug it in or have you configured a wireless connection that is actually working?)
Do you have an address? (ifconfig)
Did you try to get an address? (dhclient)
etc

All work properly, dhclient or wicd for any ifaces(eth, wifi) and all programs (ettercap, tcpdump, wireshark, etc) work properly with all the ifaces, even in promiscuous mode. Only nmap doesn't work when promiscuous mode is enabled.

thanks

[thorin]

Only nmap dasen't work when promiscuous mode is enabled.

This would have been a good detail to include in the original post. Have you tried using nmap when you're not in promiscuous mode? Can you think of a reason why nmap wouldn't work when your NIC is in promiscuous mode?

http://en.wikipedia.org/wiki/Promiscuous_mode might help.

If it doesn't then please find some networking 101 tutorials and brush up.

PS > Yes I should have caught this from your second post, but for some reason promiscuous stood out more than monitor, and I also didn't pay close enough attention to realize that post 1 and post 2 were both you (I had been thinking that post 2 was an unhelpful post by someone else.....)

[4xh3ll]

This would have been a good detail to include in the original post. Have you tried using nmap when you're not in promiscuous mode? Can you think of a reason why nmap wouldn't work when your NIC is in promiscuous mode?

http://en.wikipedia.org/wiki/Promiscuous_mode might help.

If it doesn't then please find some networking 101 tutorials and brush up.

Well, i know how promiscuous mode work, i think! But i can't understand why, if wlan3 is in promiscuous mode, also the eth0 is not reachable from nmap. If only wlan3 is in promiscuous mode, eth0 should be still reachable from nmap....Am I missing something about how promiscuous mode works?

[Scamentology]

Depending on what scan you are doing you can try the "--unprivileged" switch when in monitor mode.

[4xh3ll]

Depending on what scan you are doing you can try the "--unprivileged" switch when in monitor mode.

Thanks for the tip! this work with my debian, and it must be the same with bt5.
I'll put SOLVED in the title, but, if someone wants to add something to the thread, I appreciate it very much!

[thorin]

Well, i know how promiscuous mode work, i think!

If nmap is receiving packets from everywhere on your network and not only those destined specifically to you (your NIC) then how does it know which packets are responses to the probes it's sending out? While your network may be small (or very small) on a medium or large network this could result in a huge drain on resources (on the nmap host), so I wouldn't be surprised at all if nmap simply refuses to try....

But i can't understand why, if wlan3 is in promiscuous mode, also the eth0 is not reachable from nmap. If only wlan3 is in promiscuous mode, eth0 should be still reachable from nmap....Am I missing something about how promiscuous mode works?

If eth0 is configured correctly and nmap is told to use it then it should work.

You could try using the -S switch which is actually "Spoof source address" but provide the actual address you want to use (whatever eth0 is supposed to be)....