Closed XanderStrike closed 4 weeks ago
@XanderStrike Tangentially related, but how did you get arp-scan working on the home assistant docker container? I get the following error in the logs:
2024-06-10 21:46:53.110 DEBUG (SyncWorker_7) [custom_components.arpscan_tracker.device_tracker] Scanning...
2024-06-10 21:46:53.119 DEBUG (SyncWorker_7) [custom_components.arpscan_tracker.device_tracker] Scandata /bin/sh: arp-scan: not found
Closing because stale ticket
Thanks for this project, I've been using it happily for a very long time.
After the 1.0.7 release I noticed tracking was no longer working for my devices, finally took the time to dig into it today.
It turns out that arp-scan with the default arguments specified here cause it to choke on docker-provided veth devices:
Weird veth behavior when it comes to pings and arp tables isn't surprising, they're not meant to be used this way. I'm confused how it ever worked actually, perhaps something has changed with the way arp-scan's
--localnet
deals with veth interfaces.In any case, I had to specify the interface in my configuration, which looks like this:
It's now working perfectly again. Just thought I'd share in case other people have this issue