Windows 10 PC always shows as not_home in device tracker

Configuration
41

Ended up solving this issue by using the new Ping device tracker added in 0.36. I would not have even known about it if it weren’t for responding to another user having problems configuring it, either. LOL

1 Like
42

thanks for posting this. i did miss that one to.
as soon as i am up to date again i can finally have an IP based devicetracker and get the problem out of the way with 1 specific device that changes mac address

1 Like
43

Works Great !. Thanks. I had been breaking my head with various inputs and this one did the magic.

44

Hello!

Just a question. I was also having problems with nmap not seeing windows 10 Pro, and I wanted the solution to discover all plataforms, not only Win10 (it is my understanding that the -PS135,445 would search for this specific ports only, which may not be open in other devices, is this correct?)

What I did was use setcap to give only the cap_net_raw privilege to nmap. That is the only additional privilege it needs to run as --privileged with the -F option and see the windows machines, because it is no longer limited to ports 80 and 443. So, it does not need to run as a different user and no core files need to be edited. I also believe this change would survive an update.

so, running:
sudo setcap cap_net_raw+eip /usr/bin/nmap

and then on the configuration:

  • plaftorm: nmap_tracker
    scan_options: " --privileged -F --host-timeout 5s "

Gave me the results I wanted, is close to the original design of the configuration, and required minimal changes.

My question is, am I seeing this wrong? Am I exposing myself to some security risk in some way, or are there downsides to my approach I am not seeing? I don’t believe cap_net_raw on nmap could be maliciously abused, but I might be wrong.