If I want to know the Pi address by MAC address, use the command: sudo nmap -sP -n 192.168.100.100-254 Nmap scan report for 192.168.1.153 It will be easier to link to our own Pi through a shell connection. If each Pi has a unique name, it will be easier to identify which IP has been assigned by the DHCP process of the router. Nmap scan report for (192.168.1.153)Įverybody's out-of-the-box Pi has that same name, "raspberrypi". I should be able to pick it out more easily at the next meeting. My unmodified Pi shows up at home as: Nmap scan report for (192.168.1.153)Īfter making the changes recommended in the How-to-Geek article the Nmap scan shows this result for my Pi.
I didn't have this note figured out while at the meeting. (nmap is also available for Windows and Mac: ) You need to know the router's root password which Saman or anybody else hosting a meeting wouldn't want to share.Ĭombine that with the Linux command to list the network hosts: nmap -sP 192.168.100.100-254 (This is the range at Saman's place.) and we would have a list of the IP numbers for every connected "host" on the local network. At home, I could use my laptop browser to see the list on my router, but that option isn't good with somebody else's router.
#ANGRY IP SCANNER NOT SHOWING MAC HOSTNAME HOW TO#
One link that I found useful told me how to set each Pi's name instead of the default "raspberrypi". There was an (expectable) issue with finding our IP number for our own Pi on the network. Raspberry Pi comes with a secure shell server running. While many were connected using keyboards and monitors, some of us were trying to access our Pi through a shell (SSH/Putty) connection. At the recent Raspberry Pi meeting run by Saman (great job) at Framigham Makerspace had 15 of us working.
0 kommentar(er)
