Re: nmap in netbsd-5

[Arnaud Lacombe <lacombar%gmail.com@localhost>]

Hi,

It still fails, but on another point:

# nmap -sS 10.0.0.1 -e ath0 -v
Starting Nmap 4.65 ( http://nmap.org ) at 2009-01-25 01:04 EST
I cannot figure out what source address to use for device ath0, does
it even exist?
QUITTING!
% ifconfig ath0
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
[...]
        inet 10.0.0.150 netmask 0xffffff00 broadcast 10.0.0.255

either nmap try to be too clever, or we are missing a bit somewhere.
I'll try to have a look at nmap code.

 - Arnaud

On Sat, Jan 24, 2009 at 3:16 PM, Rhialto <rhialto%falu.nl@localhost> wrote:
> On Sat 24 Jan 2009 at 02:14:01 +0100, Frederic Jaeckel wrote:
>> # nmap -sS 192.168.0.1 -v
>>
>> Starting Nmap 4.65 ( http://nmap.org ) at 2009-01-24 02:10 CET
>> WARNING: Unable to find appropriate interface for system route to 192.168.0.1
>> WARNING: Unable to find appropriate interface for system route to 127.0.0.1
>> WARNING: Unable to find appropriate interface for system route to 127.0.0.1
>> WARNING: Unable to find appropriate interface for system route to 127.0.0.1
>> Target* nexthost(HostGroupState*, TargetGroup*, scan_lists*, int): failed to 
>> determine route to 192.168.0.1
>> QUITTING!
>
> You can supply an explicit interface to use - see the nmap manual page.
>
> That nmap is trying too clever and thinks it is able to find out for
> itself, while it can't, can be called a bug.
>
> -Olaf.
> --
> ___ Olaf 'Rhialto' Seibert    -- You author it, and I'll reader it.
> \X/ rhialto/at/xs4all.nl      -- Cetero censeo "authored" delendum esse.
>