From owner-freebsd-security@FreeBSD.ORG Thu Jun 17 11:23:11 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7394316A4CE for ; Thu, 17 Jun 2004 11:23:11 +0000 (GMT) Received: from mail.geocell.com.ge (mail.geocell.com.ge [212.72.145.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F9C443D54 for ; Thu, 17 Jun 2004 11:23:07 +0000 (GMT) (envelope-from FreeBSD@access.sanet.ge) Received: from prepaid1 (io.geocell.com.ge [212.72.145.14]) by mail.geocell.com.ge (8.11.6/8.11.6) with ESMTP id i5HBTOV02718; Thu, 17 Jun 2004 16:29:26 +0500 Date: Thu, 17 Jun 2004 16:22:07 +0500 From: FreeBSD User X-Mailer: The Bat! (v2.10.01) Personal X-Priority: 3 (Normal) Message-ID: <1426783068.20040617162207@access.sanet.ge> To: Oliver Eikemeier In-Reply-To: <9671B9BE-BFC7-11D8-9250-00039312D914@fillmore-labs.com> References: <40D093CE.6020603@mac.com> <9671B9BE-BFC7-11D8-9250-00039312D914@fillmore-labs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-security@freebsd.org Subject: Re[2]: nmap not scanning networks? X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD User List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 11:23:11 -0000 OE> Chuck Swiger wrote: >> Alex Povolotsky wrote: >>> Attempt to scan a network with any method except plain ping results in >>> an error: >>> truss nmap -sT -p 21 '172.19.17.*' >> >> I can confirm the problem, anyway, although I'm not sure it's germane >> to freebsd-security. :-) >> >>> [...] >>> sendto(0x4,0x8094200,0,0x0,{ AF_INET 172.19.17.0:0 },0x10) ERR#49 >>> 'Can't assign requested address' >>> [...] >>> What's strange that man on send(2) doesn't state that EADDRNOTAVAIL >>> can ever be returned from sendto(). OE> Have you checked the firewall rules and routing tables on your machines? OE> Do you have the same problems with non-private IP ranges? I had the same problem because my host IP address was inclusive in the IP range. Make sure your host IP is not inclusive and see the result. OE> -Oliver OE> _______________________________________________ OE> freebsd-security@freebsd.org mailing list OE> http://lists.freebsd.org/mailman/listinfo/freebsd-security OE> To unsubscribe, send any mail to OE> "freebsd-security-unsubscribe@freebsd.org" -- Best regards, FreeBSD mailto:FreeBSD@access.sanet.ge