From owner-freebsd-security@FreeBSD.ORG Wed Jul 7 19:46:31 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 DDB4716A4CE for ; Wed, 7 Jul 2004 19:46:31 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFC3F43D39 for ; Wed, 7 Jul 2004 19:46:31 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (8.12.6/MantshX 2.0) with ESMTP id i67JkRn6021160; Wed, 7 Jul 2004 12:46:27 -0700 (PDT) Received: from [10.1.1.193] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i67JkNkI006732; Wed, 7 Jul 2004 12:46:26 -0700 (PDT) In-Reply-To: <16595.567.380998.969679@canoe.dclg.ca> References: <20040617120329.8AA7216A4D5@hub.freebsd.org> <20040618062557.GA616@kolic.net> <16595.567.380998.969679@canoe.dclg.ca> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <504FDE20-D04E-11D8-9FB6-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 7 Jul 2004 15:46:18 -0400 To: David Gilbert X-Mailer: Apple Mail (2.618) cc: freebsd-security@freebsd.org cc: Zoran Kolic 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: Wed, 07 Jul 2004 19:46:32 -0000 On Jun 18, 2004, at 10:54 AM, David Gilbert wrote: > Zoran> Have you tried without "'"? Or 172.19.17.1-254? Nmap works > Zoran> for me. Maybe port 21? > > I've noticed that nmap on FreeBSD is particularly lame at scanning the > local network. If the majority of the addresses on the local network > are unoccupied, then it will pause with a 'no buffer space available' > message and pause for 15 or 20 seconds each. I believe Oliver (the port's maintainter) looked into this issue and found a fix, try updating to the latest nmap port and see whether it does better now... -- -Chuck