Or, you can use the system in bridge mode to extend your existing Wi-Fi coverage to a wider area. Really need a push in the right direction of settings that allows the Eero's to work.You can also use a single Eero box as a standalone wireless router. If needed I can generate more debug logs based on whatever suggested setup data.
RED LIGHT ON EERO ROUTER INSTALL
I'm trying all kinds of permutations since the simple install doesn't appear to work with the Eero routers. That is all while nf has the following setting: interface eth0 Setting nameserver to 127.0.0.1 and doing an nslookup results in things getting blocked.Setting nameserver to 192.168.0.40 (Pi & Pi-hole static IP) and doing an nslookup results in things getting blocked.Setting nameserver to 192.168.0.1 (Eero's IP) and doing an nslookup, results in things not getting blocked.In trying the following from the Pi directly without the Eero's DNS pointing at the Pi-hole: Output of scutil -dns is (when device directly connected):īoth Homebridge and strongswan are working fine as well.Īny help or advice would be appreciated! Debug Token: Reach : 0x00020002 (Reachable,Directly Reachable Address) Output of scutil -dns is (when device not direct connected): Output of nslookup (when device not directly connected) is: Server: 192.168.0.1 Output of nslookup (when device direct connected) is: Server: 192.168.0.40 Output of nslookup pi.hole 192.168.0.40 (when not directly connected) is: Server: 192.168.0.40 Output of nslookup pi.hole (when device direct connected) is: Server: 192.168.0.40 I can log into the pi-hole GUI via a webbrowser as well. WPA3 is not on due to two old devices on the network. That does not seem to have changed anything.Įero does not have local DNS caching on. I have turned of HomeKit secure in the HomeKit app - as that was suggested elsewhere. For the life of me, I can not figure out why it was working for a brief time and then stopped. Then promptly stopped and the Eero hit a red light situation.Īt this point, I generated a debug token after resetting the DNS at the router to the known good configuration.
After hours of trying things, I tried pihole -r which is what got it working network wide for about 15 minutes. I have tried all sorts of things like adding and removing dns entries on pi-hole (127.0.0.1# & 1.1.1.2, 1.0.0.2 and others). Blocklists, gravity is up to date, ipv6 is off for eth0 pihole: rpi running a light version of raspbian 192.168.0.40.
RED LIGHT ON EERO ROUTER PRO
RED LIGHT ON EERO ROUTER MANUAL
If I set the Eero back to use say 1.1.1.2 DNS, the manual DNS server assignments will work again. Then suddenly nothing resolves for any client - the internet dies. Initially it worked for about 15 minutes. I set a single ipv4 dns entry at the router via the Eero app. Works exactly as it should.Īfter testing at the client level, I decided to try pihole network wide. DHCP addresses are doled out from the eero router, then the clients resolve via pihole. I have started with several clients manually set to resolve through it. It also has an install of Homebridge & Strongswan installed as well. I have pihole running on an rpi at 192.168.0.40. I have been researching for the last few days and have read through a number variations of this issue that I can find. Strongswan, fully updated Actual Behaviour: Pi: Butter, fully updated - using Lighttpd Router: Eero Pro 6 + Eero 6 Extender - providing DHCP (v6.6.1) System wide traffic requests resolve through pi-hole. Please follow the below template, it will help us to help you! Expected Behaviour:
0 kommentar(er)
