On Sat, Sep 13, 2014 at 07:12:29PM +0100, Laurie Brown wrote:
On 13 September 2014 19:09:17 BST, Chris Green cl@isbd.net wrote:
If I have a wired connection to my LAN I can use 'arp-scan -l' to find the IP addresses of other systems on the LAN. However arp-scan only works if *I* have a hard-wired connection.
How can one find IP addresses on a LAN when connected by WiFi?
Try an Android device running fring...
Not a lot of help when I'm sitting here on a boat in France with two Beaglebone Black systems, an IBM Lenovo laptop, a Siemens Gigaset VOIP phone, an internet radio, but nothing running Android.
Does nmap -sL [lan.address.number.*] | grep lan do what you want?
It's how I search for anything on my home network - using 192.168.1.* it searches all ips on my network. The pipe to grep just saves you searching through a huge list of "None"
Paul
On 13 September 2014 19:26:38 GMT+01:00, Chris Green cl@isbd.net wrote:
On Sat, Sep 13, 2014 at 07:12:29PM +0100, Laurie Brown wrote:
On 13 September 2014 19:09:17 BST, Chris Green cl@isbd.net
wrote:
If I have a wired connection to my LAN I can use 'arp-scan -l' to
find
the IP addresses of other systems on the LAN. However arp-scan only works if *I* have a hard-wired connection.
How can one find IP addresses on a LAN when connected by WiFi?
Try an Android device running fring...
Not a lot of help when I'm sitting here on a boat in France with two Beaglebone Black systems, an IBM Lenovo laptop, a Siemens Gigaset VOIP phone, an internet radio, but nothing running Android.
On Sat, Sep 13, 2014 at 08:29:46PM +0100, Paul Lenton wrote:
Does nmap -sL [lan.address.number.*] | grep lan do what you want?
It's how I search for anything on my home network - using 192.168.1.* it searches all ips on my network. The pipe to grep just saves you searching through a huge list of "None"
Well, sort of, but none of my systems have names that appear on the LAN (crap modern routers don't seem to do names) so filtering using grep is a little difficult.
Doesn't nmap have an option to report only IPs that respond?
On 13/09/14 19:26, Chris Green wrote:
On Sat, Sep 13, 2014 at 07:12:29PM +0100, Laurie Brown wrote:
On 13 September 2014 19:09:17 BST, Chris Green <cl@isbd.net> wrote:If I have a wired connection to my LAN I can use 'arp-scan -l' to find the IP addresses of other systems on the LAN. However arp-scan only works if *I* have a hard-wired connection.
How can one find IP addresses on a LAN when connected by WiFi?
Try an Android device running fring...Not a lot of help when I'm sitting here on a boat in France with two Beaglebone Black systems, an IBM Lenovo laptop, a Siemens Gigaset VOIP phone, an internet radio, but nothing running Android.
It's possible my reply has sent twice, as I'm having some problems with K9 Mail on my phone but...
Does "nmap -sL 192.168.1.* (or whatever the LAN address is) | grep lan" do what you're after?
The -sL flag is the basic scan (you could use -pn for a ping scan, if everything had an open port to respond) and various others (check the manpage for a full list of scan types) and will return a list of IP addresses and device names for everything that matches the IP range and has a .lan network address.
Paul
-
Chris Green -
Paul -
Paul Lenton