LinuxQuestions.org - Need to list IP of all devices connected in LAN including wi-fi connected devices

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Need to list IP of all devices connected in LAN including wi-fi connected devices (https://www.linuxquestions.org/questions/linux-newbie-8/need-to-list-ip-of-all-devices-connected-in-lan-including-wi-fi-connected-devices-4175561113/)

Need to list IP of all devices connected in LAN including wi-fi connected devices

I use nmap command to detect the IP of connected devices in the LAN but if a hotspot is created on one of ubuntu machine of LAN and some of the devices are connected to internet using this hotspot, nmap command does not list these IPs. Devices which are connected to LAN whose IP is like 192.168.0.x and the devices those are connected using hotspot whose IP is like 10.0.xx.xx but nmap is not able to detect IP of these devices. As well as if virtual machine is installed on some of machine and they are using other OS like fedora and centos, these have also different IP than the sytem on which these are installed. These can not be detected too.

Is there any way so I can detect IP of each device either they are connected to hotspot or virtual machines?

Please help.

I assume you used the ping option of nmap. Why not use the 10.0.0.0/16 ip range and ping those?

Also have in mind if a machine would block ping nmap would not list it (not sure. nmap is really intelligent). You might want to use arpwatch on several points of the network to get a whole lot more ip. This one is also indepentend of ip ranges.

The virtual machine problem and the hotspot problem are two separate (but similar) issues. If the VM has an ip like 10.x.x.x this sounds to me like you are NATing in your virtualization software. So nmap cannot detect these ips because they are simply not visible on your LAN. It's like if you were trying to ping a machine that sits behind a router.
You could address this by changing the networking mode to something that I think is called "bridge" in e.g. VirtualBox. As a result, the VM would become a client of your LAN and receive an ip adress in the 192.168... range.

The hotspot thing is probably similar. The hotspot acts like a router. The clients connected to the hotspot are hidden via NAT just the same. This is more difficult to solve though, and very much depends on you are creating the hotspot and what configuration options you have in the process.