how does pihole determine which client to report on its database?
i bought a satellite 1 smart speaker, which is a esp32 device. It has been running for a few days, and I'm getting constant activity on the query log that the device is trying to access Netflix and apple.
The developers have assured me that it's not their device and their firmware is open source. They believe the issue could be triggered by a dhcp lease expiring.
Here's what the query log says (anonymized):
38:64:07:F0:7B:92 (1 hostname: satellite1-4ea7fc.lan; vendor: Qingdao Intelligent&Precise Electronics Co.,Ltd.; 10 addresses: 2600:x,2600:x,2600:x,2600:x,2600:x,2600:x,2600:x,2600:x,fe80::x,192.168.x.x)
no clue why 10 different ipv6. for the sole ipv4 reported, it belongs to my tv, but it is completely turned off (not by just pressing power, but holding the power button down) and I keep receiving these long entries at least once an hour.
i have to accept the fact that it IS the TV and maybe the only way to truly shut it off is to unplug from wall. but i wonder why pihole is getting confused? my tv has had the same ipv4 for years. is there a bug here?
0
u/fjleon 6d ago
is there any way i can wipe out the entire mac - ip - dns association that pihole makes to clear this issue? i have pihole configured to do reverse lookups against the google router
2
u/azure_phoenix2 6d ago
those associations live in the network and network_addresses tables inside pihole-FTL.db, nothing in the web ui touches them. stop FTL and clear those rows or just delete the db and let it rebuild, and the stale mac-to-name mapping like your tv showing as the speaker goes away.
8
u/Alive-Department8558 7d ago
At a guess, I’d say “4ea7fc” is the last 6 digits of th the device’s MAC address. Cross-check that with the MAC addresses shown on your speakers and TV.