Network is unreachable and other related errors

Jason Chambers jchambers at ucla.edu
Mon Jan 12 12:37:03 PST 2009


Hello all,

Wondering if anyone else experiences errors such as "Network is
unreachable" and the like when using security auditing tools like nmap,
nessus, etc.

I found a PR from a long time ago that appears relevant but it was
abandoned:

http://www.freebsd.org/cgi/query-pr.cgi?pr=102741&cat=



As a result of this condition some tools are completely unusable.  A
nessus scan returns all scanned hosts as dead seconds after starting a
scan.  Nmap is unable to scan a system because it immediately goes into
a loop of the following:

  sendto in send_ip_packet: sendto(4, packet, 44, 0,
   xxx.xxx.xxx.xxx, 16) => Network is unreachable

  Offending packet: TCP xxx.xxx.xxx.xxx:55555 > xxx.xxx.xxx.xxx:80
   S ttl=56 id=xxxx iplen=11264  seq=xxxx win=1024 <mss 1460>

  Sleeping 15 seconds then retrying

  sendto in send_ip_packet: sendto(4, packet, 44, 0,
   xxx.xxx.xxx.xxx, 16) => Network is unreachable

  Offending packet: TCP xxx.xxx.xxx.xxx:55555 > xxx.xxx.xxx.xxx:80
   S ttl=56 id=xxxx iplen=11264  seq=xxxx win=1024 <mss 1460>

  Sleeping 60 seconds then retrying


It's obviously related in part to the hardware configuration of a device
however I'm not sure where to look next.  The network controller does
not seem to make a difference.  So far I've not experienced anything
related to this issue when running Linux on the same hardware.


Any ideas where to look next ?


Regards,

--Jason



More information about the freebsd-net mailing list