From owner-freebsd-questions@FreeBSD.ORG Tue Mar 24 10:11:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 809341065674 for ; Tue, 24 Mar 2009 10:11:38 +0000 (UTC) (envelope-from brucec@muon.cran.org.uk) Received: from muon.cran.org.uk (brucec-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:c09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 58E468FC13 for ; Tue, 24 Mar 2009 10:11:38 +0000 (UTC) (envelope-from brucec@muon.cran.org.uk) Received: by muon.cran.org.uk (Postfix, from userid 1000) id E3B451924A; Tue, 24 Mar 2009 10:11:37 +0000 (GMT) Date: Tue, 24 Mar 2009 10:11:37 +0000 From: Bruce Cran To: perryh@pluto.rain.com Message-ID: <20090324101137.GB451@muon.cran.org.uk> References: <200903232010.21179.mel.flynn+fbsd.questions@mailing.thruhere.net> <49c88f26.l1EpVEWeSl4QsOWV%perryh@pluto.rain.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49c88f26.l1EpVEWeSl4QsOWV%perryh@pluto.rain.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: jalmberg@identry.com, freebsd-questions@freebsd.org Subject: Re: utility that scans lan for client? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 10:11:38 -0000 On Tue, Mar 24, 2009 at 12:43:34AM -0700, perryh@pluto.rain.com wrote: > Mel Flynn wrote: > > On Monday 23 March 2009 19:59:36 John Almberg wrote: > > > What I'm looking for is a utility that can scan a LAN for attached > > > clients... i.e., computers that are attached to the LAN. > > > > > > I have one box (an appliance that I have no access to), that is on > > > the LAN but I don't know what IP address it's using. I'd like to > > > complete my network map, and that is the one empty box on my chart. > > > > security/nmap > > > > If the box pings, you can simply scan your LAN like: > > $ nmap -sP 192.168.2.0/24 > > Or, with no ports needed: > > $ ping -n -t 5 -i 10 192.168.200.255 > > Granted you need to know the broadcast address. If you know the > interface name, you can get the broadcast address from ifconfig: That only works if the OS is configured to reply to broadcast ping, which appears to be usually disabled nowadays. At least on FreeBSD 7.1 net.inet.icmp.bmcastecho defaults to 0. -- Bruce Cran