Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Jun 2004 12:49:59 -0400
From:      David Gilbert <freebsd-list@dclg.ca>
To:        Zoran Kolic <kolicz@eunet.yu>
Cc:        freebsd-security@freebsd.org
Subject:   Re: nmap not scanning networks?
Message-ID:  <16595.7479.439833.235009@canoe.dclg.ca>
In-Reply-To: <20040618062557.GA616@kolic.net>
References:  <20040617120329.8AA7216A4D5@hub.freebsd.org> <20040618062557.GA616@kolic.net>

next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Zoran" == Zoran Kolic <kolicz@eunet.yu> writes:

>> nmap -sT -p 21 '172.19.17.*'
Zoran> Have you tried without "'"?  Or 172.19.17.1-254?  Nmap works
Zoran> for me. Maybe port 21?

I've noticed that nmap on FreeBSD is particularly lame at scanning the
local network.  If the majority of the addresses on the local network
are unoccupied, then it will pause with a 'no buffer space available'
message and pause for 15 or 20 seconds each.  This seems to be due to
it wanting to send a number of packets to the same addresses and when
the arp is not resolved we're putting a negative entry in the routing
table.

... or at least that was the behaviour.  Recent -CURRENTS don't even
seem to try to send arp entries as the arp table isn't full of
incomplete entries as it was before.

Dave.

-- 
============================================================================
|David Gilbert, Independent Contractor.       | Two things can only be     |
|Mail:       dave@daveg.ca                    |  equal if and only if they |
|http://daveg.ca                              |   are precisely opposite.  |
=========================================================GLO================



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16595.7479.439833.235009>