Eero Gold stability issues?
I got my gold setup a couple days ago. It is running in router mode with some Eero Pros behind it in bridge mode. Once or twice an hour, each of the Eeros go red and cannot be connected to from the Eero app. After 30-60s, everything is fine again. AFAICT I'm losing connectivity during this period.
Any hints for something that I can go do? I've rebooted every Eero a couple times so far without any real change.
-
I’m running Gold in router mode, with four Erro Pro’s in bridge mode.
I haven’t had any issues like what you describe. Do you have any policies that could block traffic inbound/outbound on the Eero’s?
I noticed that I can’t seem to match up exactly MAC addresses of the Eero units; the Eero app shows one address, Firewalla sees another.
Last question, are these using a wired connection for backhaul or wireless?
-
Take a look at this https://help.firewalla.com/hc/en-us/articles/360008005173-Setup-Guide-Mesh-Routers
scroll to the bottom comment section. Seems the eero will require to be wired differently if you use backhaul.
-
> Do you have any policies that could block traffic inbound/outbound on the Eero’s?
Not AFAIK, pretty vanilla OOB setup. I'll disable monitoring for those devices but this is intermittent enough I don't have a lot of faith it'll work.
> Last question, are these using a wired connection for backhaul or wireless?
Wireless, and it happens on both the main and satellite Pros.
The only thing I can come up with is to factory reset the Eeros and set them up in bridge mode from the beginning.
@Firewalla - I'm running in router mode, that article says that it is for simple/dhcp only. Am I following the wrong link?
-
Actually, if your eero is in Bridge mode, either setup is fine. I have a Firewalla Gold with 3x Eero Pro in bridge mode, and I have it connected as the "This is NOT OK" mode.
In bridge mode, much of the "advanced" controls of the Eero are gone, and you really don't care about it, because you use your Firewalla to achieve the same result. (Stopping internet for a certain client etc)
I'm on a 1Gbps line, and Eero App reports 938Mbps speeds.
I have not experienced any drop-outs with this setup, which leads me to believe that it must be something with your rules.
In bridge mode the Eeros don't really report much traffic, just control traffic to the Eero cloud services. This is because they don't NAT so Firewalla see the other traffic as coming directly from the other hosts. This also mean that you can safely put your Eeros into their own group, and set rules which will avoid any drops.
You can for example enable "Emergency Access" to the group, which means the traffic from the Eeros will bypass any rules you set up.Try that and see if your drop-outs disappear or lessen.
If not, it could be that your eeros are just too close to each other, so reduce to using 1 less eero and see if it becomes more stable.
-
Read this to get an understanding on why that topology is not good.
-
OK, so I'm stuck. Figured I would post herein case someone else runs into this.
So I started with my network wired exactly like "This is OK", Eero running as a router, everything grand. Until I try to put into bridge mode.
It reboots, when it comes back up again it basically doesn't get an IP address (light is red) and devices trying to connect via wifi don't get IP addresses.
To get back to working again, I basically delete the network, reset each node and create a new network (with the same name as before). So I'm back to where I was before.
Any ideas? I suspect the Eeros are trying to be clever, maybe the gateway getting confused about the connections?
-
so just not able to get bridge mode to work at all then? (I did just see an update get installed on my Eeros...).
I was considering removing one of the nodes from my network, setting it up as a single node router, and with ONLY the connection to the FWG connected see if I can switch it to bridge mode.
I figure that would have the least impact; I can always just power back on the old ones to get my old network back...
-
Edit: false alarm. I'm getting "bouncy" connections on the wireless eeros after removing the FWP also, though not as frequently.
I have the following topology:
Modem -> Firewalla Purple (router mode) -> eero (bridge mode) -> switch -> PC & Chromecast
My other 2 eeros are wireless.My and my wife's phones intermittently, though consistently, get kicked off the WiFi when they're connected to one of the wireless eeros. After a few seconds, they reconnect to the satellite, and the connection works fine until it bounces again.
I've tried with the eeros unmonitored and monitored, but it doesn't make a difference.
I'm almost positive the problem is FWP. In frustration, I set the eero back to Automatic, and took the Purple off the network (modem -> eero). The phone connections stabilized during the few minutes I was still downstairs connected to them.
Anybody have any idea why FWP is making those connections unstable?
Thanks,
David -
When you are getting kicked off wifi, what does it mean? no longer have an IP address? or can not access the network? Firewalla devices should never cause wifi to go down, since it is layer 2 ...
When eero in bridge mode, do you have "client steering" on?
Also, if you connect to the main eero, will you ever having issues?
(there is no need to play with monitoring mode, it doesn't do much if you are running in router mode)
-
i have the exact same issue as the OP from 2 years ago.
I got my gold plus setup a couple days ago. It is running in router mode with one Eero Pro behind it in bridge mode and several beacons. Once or twice a MINUTE, the THE EERO PRO CONNECTED TO THE FWG goes red and cannot be connected to from the Eero app. After 30-60s, everything is fine again. AFAICT I'm losing connectivity during this every 10-30 seconds.
The eero Pro is in bridge mode. Steering is off. Monitoring is off.
Any hints for something that I can go do? I've rebooted every Eero a couple times so far without any real change.
Setup:
Modem ——> FWGP —-> Eero Pro (bridge mode)
-
Is the guidance regarding using wired backhaul for eeros behind a Firewalla Purple also the same for newer eeros like the 6E? I would like to put a Purple in front of my 6E gateway and be able to connect to my other 6E satellite wirelessly as I don’t have access to Ethernet between the two eeros.
Is this possible?
-
@sendmespampls, if you are using a purple and you are not using ethernet backhaul, then you all you need to do is
[Modem]<-->[purple in router mode]<-->EEro 6E main unit
And have other units wirelessly connect back to the eero ...
The backhaul restriction by eero is only if you are using ethernet as backhaul, that ethernet need to connect to the main unit.
-
OK I returned the TP Link Deco AXE5400 to Costco.
After 6 hrs. I gave up on TP-Link. I'm sure it works for some people, but not for me. I literally tried everything but the system kept dropping wifi.
Bought a Eero 6 Pro 3 pack next.
THAT WORKED like a charm.
Modem -----> WAN Port of FWGP
FWGP Port1 ------> Left Port of EEro base station ----> Right Port of EEro base station to switch
EEro in BRIDGE MODE.
This was weird because for some reason it did not want to restart in bridge mode but after several retries on the Eero app it worked.
Erro satellite stations connected through ethernet backhaul using the switch above. I wanted to use a 2.5GB switch but my Savant home theater system would not play nice with it so I am using a Cisco Managed Switch.
-
@firewalla sorry, I'm still a bit of a newbie when it comes to networking, but I'm still relatively confused based on the conversations, and looking at the 'OK / Not OK' charts.
Context: I have two Eeros in separate rooms:
- Eero A is the Gateway, plugged into the modem, with the other available port plugged into a switch
- Eero B is in another room which cannot be connected via Ethernet
In the simplest terms, I believe the following set up is what I'd need to:
Modem -> FWP -> Eero A -> Switch -> X other devices
- Question 1: Am I right in assuming Eero A can still generate the mesh WiFi without an Ethernet connection and I'll still have internet on Eero B?
- Question 2: Will the FWP be able to accurately identify ALL devices (both on my Eeros Wifi networks + Switch) and provide the advertised functionalities for each one?
- Question 3: I understand I'll lose some Eero functionalities, like creation of guest networks, but are there any other major capabilities I'd lose? Or in any way does this impact the stability of these devices? They have been reliable in handling a large number of WiFi devices.
- Question 4: Can I create VLANs with this current setup? Or would each Eero need to be converted to a dedicated wifi network, in which case I assume FWG would be needed given the number of ports on FWP? Or would I need to get rid of the Eeros...?
Thanks in advance!
-
Answers
1. Yes, Eero A will handle internet, and it will mesh with B
2. It should be able to identify all devices
3. I think you still can create networks, that network will likely shows up as traffic from Eero node.
4. You can always create VLAN's, eeros won't understand them ... for that you need SSID to VLAN mapping and managed switches
-
Hi, thanks for your prompt response.
I'm weighing up the purchase of Firewalla device but question 2 really is a critical piece of information I'd hope you'd be able to answer given how often Eeros are used to complement one of your devices. I appreciate it is a separate product and you cannot officially vouch for performance, but it sounds like it's the typical setup.
For question 2, could you please clarify whether it "will" be able to identify all devices rather than "should"? If I purchase a FWP and it's unable to do so I'll have to return it which I'd rather avoid.
Thanks again
-
It really depends on the device. Some times don't announce themselves, so firewalla has to "guess" what the device is. This guess may be right or may be wrong.
If the device does announce itself like your iPhone, even with MAC Randomization, you should see the device name "Joe's iPhone".
If you want a perfect identification of the model number, this is not possible.
Please sign in to leave a comment.
Comments
25 comments