Nmap Development mailing list archives
Re: nmap 3.50 Oddity on FreeBSD 4.9-RELEASE
From: eric <eric-nmap () catastrophe net>
Date: Tue, 23 Mar 2004 22:43:19 -0600
On Tue, 2004-03-23 at 10:06:52 +0100, Weiersmüller Mathias (KPFN 1) proclaimed...
Is the network 10.51.55.0/25 directly connected, or is a entry in the routing table which has the address 10.51.55.0 as "first address" within the network? So this address is a "network number", and I suppose that FreeBSD 4.9 does not want to send packets towards the network number. What happens when trying to ping or open a telnet towards 10.51.55.0? Just my 5 cents...
It's a subnet about 4 hops away, routed through a core. subnet-zero is enabled in our environment, and 10.51.55.0 is seen as a host on the network. Note that if I try any other .0's around, I don't get the problem. Only this one .0. Also, I've tested a kernel change to no avail. kern.ipc.nmbclusters=32768 Any more words of wisdom are appreciated. --------------------------------------------------------------------- For help using this (nmap-dev) mailing list, send a blank email to nmap-dev-help () insecure org . List archive: http://seclists.org
Current thread:
- nmap 3.50 Oddity on FreeBSD 4.9-RELEASE eric (Mar 19)
- Re: nmap 3.50 Oddity on FreeBSD 4.9-RELEASE MadHat (Mar 22)
- Re: nmap 3.50 Oddity on FreeBSD 4.9-RELEASE MadHat (Mar 22)
- <Possible follow-ups>
- RE: nmap 3.50 Oddity on FreeBSD 4.9-RELEASE KPFN 1 (Mar 23)
- Re: nmap 3.50 Oddity on FreeBSD 4.9-RELEASE MadHat (Mar 23)
- Re: nmap 3.50 Oddity on FreeBSD 4.9-RELEASE eric (Mar 23)