From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 20:37:01 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D9501065670 for ; Mon, 12 Jan 2009 20:37:01 +0000 (UTC) (envelope-from jchambers@ucla.edu) Received: from out-21.smtp.ucla.edu (out-21.smtp.ucla.edu [169.232.47.166]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2688FC1E for ; Mon, 12 Jan 2009 20:37:00 +0000 (UTC) (envelope-from jchambers@ucla.edu) Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.151]) by smtp-4.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id n0CKQ618008815 for ; Mon, 12 Jan 2009 12:26:06 -0800 Received: from computer.local ([149.142.36.207]) (authenticated bits=0) by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id n0CKQ6H4008054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 12 Jan 2009 12:26:06 -0800 Message-ID: <496BA75E.7020309@ucla.edu> Date: Mon, 12 Jan 2009 12:26:06 -0800 From: Jason Chambers Organization: UCLA User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Probable-Spam: no X-Scanned-By: smtp.ucla.edu on 169.232.47.244 Subject: Network is unreachable and other related errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 20:37:03 -0000 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 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 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