This “boot-up” port is required to be connected during the boot process of the device. And somehow someway, the device might mark this port as a “boot-up” port (a term I came up with myself). What I am guessing right now is that: the LEFT port is the one I used when I setup my Eero for the first time, when it was still in Router mode. During the boot process, if I am quick enough and plug the ethernet cable back to LEFT port, everything is fine again. However, if the gateway Eero restarts while it connects to USG through the RIGHT port, it will never boot (it does not get any IP address from the firewall), and eventually turns the red light on. I can then even switch the cable to the right ethernet port and the network is still up.
If I restart my gateway Eero while it connects to the USG through its LEFT ethernet port, everything is fine. The “gateway” Eero is connected to my Ubiquiti USG firewall.
Red light on eero router pro#
My network consists of two Eero Pro 6 devices running in Bridge Mode. What I found is very interesting bug, which fortunately could be replicated (not random). I have created a new post to summarize this lengthy post, as well as to attract more attention LOL:
Red light on eero router update#
UPDATE 4: I changed my firewall to an Ubiquiti Edge Router X but the problem still persists. Right now, I want to focus more on the other bug (see UPDATE 2) I found. I will switch back to bridge mode in the future, when Eero team will be less busy than this period of time. UPDATE 3: I have switched to router mode for my Eero network for the time-being. Tonight (Nov 17), I tried another restart and sadly getting the Red light right away. Support responded to me with a workaround if this ever happens: unplug the power cable and wait for 2 minutes.Ģ. And since I love Eero, I want it to be as perfect as possible ).ġ. This is not a really big issue, but it is annoying. I will wait Eero support to contact me so that I can provide the logs from the Eero devices for them to troubleshoot. And guess what, it booted up successfully and yes, it also survived 3 reboots. 30 minutes later, I plugged the "gateway" Eero back and connected it to USG Firewall. The Office Eero booted up without any issue and survived 3 reboots after that.ģ. I then unplugged the "gateway" Eero and replaced it with my Office Eero. It only seemed to be back online if I manually cycle the power of both USG firewall and the Eero itself.Ģ. Things went from bad to worse this morning (Nov 17): I got red light every time I tried rebooting the "gateway" Eero, regardless of which port I used. My speculation about that "boot-up" port is no longer valid. They're unsurprisingly well-suited to anyone steeped in Amazon's ecosystem, with streamlined setup (if you have an Amazon account), Alexa voice control and a Zigbee hub for compatible smart home devices.1. The allure of Eero Pro routers is simple: they provide a compact, straightforward way to blanket your home in wireless networking with more coverage than you'd get from regular Eero models - a three-pack will cover an enormous 6,000 square feet. And if you're happy with WiFi 5, the earlier Eero Pro is down to a record-low $336, or 25 percent off - it'll even dip to $314 if you have Amazon Prime.īuy Eero Pro 6 (2-pack) - $319 Buy Eero Pro (3-pack) - $336 The Eero Pro 6 represents one of the better values, and is down to $319 (20 percent off) for a two-pack and $479 (also 20 percent off) for a three-pack.
Amazon is running a sale on Eero mesh routers that includes particularly steep discounts for higher-end Eero Pro models. Does your lone WiFi router not quite cover your home? This might be a good time to upgrade.
0 kommentar(er)
