Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Mar 2009 00:43:34 -0700
From:      perryh@pluto.rain.com
To:        mel.flynn+fbsd.questions@mailing.thruhere.net
Cc:        jalmberg@identry.com, freebsd-questions@freebsd.org
Subject:   Re: utility that scans lan for client?
Message-ID:  <49c88f26.l1EpVEWeSl4QsOWV%perryh@pluto.rain.com>
In-Reply-To: <200903232010.21179.mel.flynn+fbsd.questions@mailing.thruhere.net>
References:  <E4A3989A-982F-4B9D-971D-25C49A932EB7@identry.com> <200903232010.21179.mel.flynn+fbsd.questions@mailing.thruhere.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> 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:

$ ping -n -t 5 -i 10 ` ifconfig xl0 | sed -n -e 's/^.* broadcast //p' `

BTW both ping and ifconfig are in /sbin, which is perhaps somewhat
less likely to be in PATH than /bin and /usr/bin.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?49c88f26.l1EpVEWeSl4QsOWV%perryh>