Have there been any news regarding this topic? I’m in the same situation, nmap cannot see the MAC adresses in another subnet, so it doesn’t list the devices on the tracker. Maybe there could be an option to use the hostname or ip instead?
“ARP generally won’t work outside the subnet you are scanning from. This is effectively an impossible feature request since it would require a fundamental change how IP networking works.”
I have exactly same problem. I have different subnets for different safety level of devices, managed with pfsense.
It seems that the implementation of this nmap integration is somehow flawed, because it does not find devices in another subnet. But when I use the nmap command in HA terminal add on, it finds the devices.
So, my HA Yellow box can’t find devices on another subnet when using the nmap tracker integration, but can find devices on another subnet when using the same nmap command in a terminal addon? What gives?
I am sorry, but this is not true. The MAC is not needed for this.
The nmap implementation is, sorry to tell, just garbage.
So again, for checking if a host/client is up or not, there is no MAC needed at all.
Not only that, also the documentation is just wrong. Because in the documentation you’ll find different subnets. But in fact the other subnet will never see a mac address from a different broadcast domain.
As it seems we are not alone, I guess we can open a new issue and bump it up together.
wh00t? This would lead any (micro) segmentation ad absurdum. Makes no sense at all. Actually I do not want to have my IOT stuff in other networks as needed.
Lol, I didn’t mean joining the subnets into a single network, but HA having an interface on each subnet, like many ip-addresses (192.168.1.10, 192.168.2.10, 192.168.3.10…)
