Hello
I use PeasyPort Lan scanner to find IPs of anything conected to my home network but have difficulties with anything connected to the router by WiFi.
I am running xenial64 7.5 on various pcs, makes no difference.
I need to find the IP adress of two music servers, one Daphile, the other PiCoreplayer, both WiFi.
Is this the right program to use and am I doing something wrong.I always scan port 80 but not sure realy why.
Any help would be appreciated.
Thanks
number77
PeasyPort Lan scanner for WiFi connected devices.(solved)
PeasyPort Lan scanner for WiFi connected devices.(solved)
Last edited by number77 on Thu 02 Apr 2020, 07:52, edited 1 time in total.
The LAN scanner is looking for ports. So if you give the scanner the IP range and the port (in your case 80) it will return the sub-net IP of all the machines connected to the router with the port 80 open. Port 80 is default for http, most web servers use port 80 for http:// and use port 443 for https://.
This scan will return all the sub-net IP's of the machines on the LAN that have port 80 open. Most likely machines running some web server.
same range and port 443 will return the ip's of the machines that have web servers with open port 443 for https:// connections
To find out the ip's of the machines running Daphile, the other PiCoreplayer, you will need to identify what ports these streaming servers are using. Then give the LAN ip range you use and those ports and you will find Daphile and PiCoreplayer
otherwise login to the router admin GUI and use the option to see all attached devices.
Code: Select all
IP Range = 192.168.0.1-254
port 80same range and port 443 will return the ip's of the machines that have web servers with open port 443 for https:// connections
To find out the ip's of the machines running Daphile, the other PiCoreplayer, you will need to identify what ports these streaming servers are using. Then give the LAN ip range you use and those ports and you will find Daphile and PiCoreplayer
otherwise login to the router admin GUI and use the option to see all attached devices.
For what it's worth, here is a Down&Dirty ICMP (ping) scanner for your local network. It should detect everything that doesn't have ICMP turned off.
icmpscan
icmpscan
Code: Select all
#! /bin/bash
#
# icmpscan - ICMP (ping) scan local IP subnet
#
UpLink=`ip address show | grep "MULTICAST,UP" -A2 | grep inet`
LinkIP=`echo $UpLink | cut -d' ' -f2 | cut -d'/' -f1`
BaseIP=`echo $LinkIP | cut -d"." -f1-3`
NODE=1
echo "Starting ICMP (ping) scan .."
while ((NODE < 255))
do
RTN=$(ping -c 1 -n -W1 "$BaseIP.$NODE" | grep "from")
if [ ! -z "$RTN" ]; then
echo "$BaseIP.$NODE" "is active"
fi
((NODE++))
done
echo "Scan complete"
Last edited by jafadmin on Thu 02 Apr 2020, 10:03, edited 2 times in total.
I admire jafadmin, he always have this nice script.
@number77 and the rest. I do not have experience on any of the programs mention.
But I have a feeling that number77 have multiple networks cascaded. Like he uses if phone to provide internet to his router. Then some PC/Server are hook to the phone and some to the router. I bet you is on that line.
So the quick answer is they will not show as they are in different networks. And he will have to manipulate the net and or its scanning app to resolve the issue. But we need more info to help if that is the case.
Good luck my friend.
@number77 and the rest. I do not have experience on any of the programs mention.
But I have a feeling that number77 have multiple networks cascaded. Like he uses if phone to provide internet to his router. Then some PC/Server are hook to the phone and some to the router. I bet you is on that line.
So the quick answer is they will not show as they are in different networks. And he will have to manipulate the net and or its scanning app to resolve the issue. But we need more info to help if that is the case.
Good luck my friend.
Get it from the forum here.
Remove the fake .gz extension and left-click-install it. I have tested it in Bionic64.
Set it on Slow speed and do a MAC scan. It might take a second try to find all devices on the network.
Remove the fake .gz extension and left-click-install it. I have tested it in Bionic64.
Set it on Slow speed and do a MAC scan. It might take a second try to find all devices on the network.
Thanks rcrsn51, that installed on xenial64 7.5 without problems.rcrsn51 wrote:Get it from the forum here.
Remove the fake .gz extension and left-click-install it. I have tested it in Bionic64.
Set it on Slow speed and do a MAC scan. It might take a second try to find all devices on the network.
BionicPup64's arp_scan oui hardware list is about 7 years old.
/usr/sbin/get-oui is a perl script to update the oui list,
but it doesn't work because of a missing module.
This is a simple shell script that does about the same thing as the perl script.
To scan for devices on your network:
Attached script is gzipped, click it to unzip it.
/usr/sbin/get-oui is a perl script to update the oui list,
but it doesn't work because of a missing module.
This is a simple shell script that does about the same thing as the perl script.
To scan for devices on your network:
Code: Select all
arp-scan -lg- Attachments
-
- get-oui.sh.gz
- download and click to unzip
- (174 Bytes) Downloaded 56 times
@williams2: Your post completely misses the point.
1. On my network with a combination of wired and wireless hosts, "arp-scan -l" is unreliable, even when increasing the timeout. PeasyPort uses an alternate method. This is why I requested testing.
2. PeasyPort uses "arp-scan -q", so the oui list is irrelevant.
1. On my network with a combination of wired and wireless hosts, "arp-scan -l" is unreliable, even when increasing the timeout. PeasyPort uses an alternate method. This is why I requested testing.
2. PeasyPort uses "arp-scan -q", so the oui list is irrelevant.