this post was submitted on 19 Jul 2023
1 points (100.0% liked)

eero

187 readers
1 users here now

A place to have discussions, ask for help, and share new ideas related to the eero mesh Wi-Fi system.

founded 2 years ago
MODERATORS
 

Not sure if this ever got solved, but I’m running Pihole on my network and eero for gateway, routing, Wi-Fi, and dhcp functions. The gateway address (i.e. 192.168.0.1) is the only one that shows up in the pihole logs.

I have DNS Caching off on my eero configuration, and I’ve got conditional forwarding on on the pihole config.

Anything else I can do to have the individual IPs actually make requests to the pihole without being intercepted by the eero?

you are viewing a single comment's thread
view the rest of the comments
[–] firepenny@lemmy.world 2 points 2 years ago (8 children)

I followed this guide and have not had any issues since. guide

[–] ikilledlaurapalmer@lemmy.world 2 points 2 years ago (7 children)

Are you seeing all of your devices as clients in the Pihole app?

[–] firepenny@lemmy.world 2 points 2 years ago (6 children)

Yes, I see their ips under active clients.

[–] ikilledlaurapalmer@lemm.ee 1 points 2 years ago

Ok—that is an excellent sanity check. Thanks for confirming.

The only difference for my setup is that I have enabled HomeKit support in the eero. Never thought twice about it, but looks like it works in part by forcing dns onto the gateway router. I’ll be turning it off now.

https://community.eero.com/t/y4ht25q/separate-dns-settings-for-non-homekit-devices

https://talk.macpowerusers.com/t/for-eero-users-did-you-bother-setting-up-the-homekit/20629/2

load more comments (5 replies)
load more comments (5 replies)
load more comments (5 replies)