From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Oct 22 10:50:05 2007 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2919516A41B for ; Mon, 22 Oct 2007 10:50:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F1D9813C4C5 for ; Mon, 22 Oct 2007 10:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l9MAo40e078611 for ; Mon, 22 Oct 2007 10:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l9MAo4ob078610; Mon, 22 Oct 2007 10:50:04 GMT (envelope-from gnats) Date: Mon, 22 Oct 2007 10:50:04 GMT Message-Id: <200710221050.l9MAo4ob078610@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Daniel Roethlisberger Cc: Subject: Re: ports/116778: security/nmap ping-scan misses some hosts X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Roethlisberger List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2007 10:50:05 -0000 The following reply was made to PR ports/116778; it has been noted by GNATS. From: Daniel Roethlisberger To: "Mark D. Foster" Cc: bug-followup@FreeBSD.org Subject: Re: ports/116778: security/nmap ping-scan misses some hosts Date: Mon, 22 Oct 2007 12:27:55 +0200 Sorry for the delay, been terribly busy at work. Mark D. Foster 2007-10-01: > It seems that despite specifying -PE nmap is solely relying on ARP to > determine who is up or not. Also it is not seeing the ARP replies when > a range is used. I can reproduce this, thanks for reporting. That it uses ARP instead of ICMP for directly connected nets is a documented feature. There seems to be some sort of off by one bug with some ranges, as you have reported, I can see the same here. I will try to produce a fix soon. If you have some spare time, you can help me by trying to build the latest development version of nmap from source and verifying that the bug has not been fixed yet. -- Daniel Roethlisberger