atom feed11 messages in org.freebsd.freebsd-securitynmap not scanning networks?
FromSent OnAttachments
Alex PovolotskyJun 16, 2004 6:05 pm 
Per EngelbrechtJun 16, 2004 6:25 pm 
Chuck SwigerJun 16, 2004 6:39 pm 
Oliver EikemeierJun 16, 2004 7:01 pm 
Oliver EikemeierJun 17, 2004 4:58 am 
FreeBSD UserJun 17, 2004 11:22 am 
Zoran KolicJun 18, 2004 6:58 am 
David GilbertJun 18, 2004 7:55 am 
Alexey KarguineJun 18, 2004 2:16 pm 
David GilbertJun 18, 2004 4:50 pm 
Charles SwigerJul 7, 2004 12:46 pm 
Subject:nmap not scanning networks?
From:David Gilbert (free@dclg.ca)
Date:Jun 18, 2004 4:50:39 pm
List:org.freebsd.freebsd-security

"Zoran" == Zoran Kolic <kol@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: da@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================