From owner-freebsd-security@FreeBSD.ORG Fri Jun 18 14:16:12 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 61CB216A573 for ; Fri, 18 Jun 2004 14:16:12 +0000 (GMT) Received: from bm.netm.net.ru (bm.netm.net.ru [213.148.26.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4833D43D49 for ; Fri, 18 Jun 2004 14:16:11 +0000 (GMT) (envelope-from bm@netmaster.ru) Received: from bm.netm.net.ru (localhost [127.0.0.1]) by bm.netm.net.ru (8.12.11/8.12.11) with SMTP id i5IEGk7a040951 for ; Fri, 18 Jun 2004 18:16:47 +0400 (MSD) (envelope-from bm@netmaster.ru) Date: Fri, 18 Jun 2004 18:16:46 +0400 From: Alexey Karguine To: freebsd-security@freebsd.org Message-Id: <20040618181646.6468ba8f.bm@netmaster.ru> In-Reply-To: <40D093CE.6020603@mac.com> References: <20040616220533.2ec0bc9c@tarkhil.over.ru> <40D093CE.6020603@mac.com> Organization: ISP Netmaster.ru X-Mailer: Sylpheed version 0.9.11 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: nmap not scanning networks? X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2004 14:16:13 -0000 On Wed, 16 Jun 2004 14:39:10 -0400 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(). > nmap interprets the wildcard character in a network address to include the > all-zeros "base network address" and the all-ones "network broadcast address". > I seem to recall that some systems won't let you send traffic to the > all-zeros address which might explain the EADDRNOTAVAIL, although my > explanation is not entirely satisfactory as there are still problems: > Consider trying "nmap -sT -p 21 '172.19.17.1-255'", only it results in similar > behavior: > # nmap -sT -p 21 '10.1.1.1-10' > Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-06-16 14:29 EDT > sendto in send_ip_raw: sendto(4, packet, 28, 0, 10.1.1.1, 16) => Can't assign > requested address > Sleeping 15 seconds then retrying Try the 'su' command to became root. May be it helps you. --bm