NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
"Config sync" loop with firmware V2.3.1.44
RBR50 and my two satellites (RBS50 + RBW30) were very stable out of the box for a couple of months now after getting the initial configuration right. However after updating (involuntarily!) to the "a...
Yeah, v210 has been solid for me as well.
If you haven't already, try these options and see if it works out for you.
1. Disable 20/40 MHz Coexistence
4. Enable Implicit BEAMFORMING - Boosts WiFi speed, reliability, & range for all mobile devices
To the above questions . . .
- I've had Disable 20/40 turned on (disabled) from the beginning, so no idea if that ever made a difference
- WMM has been on from the beginning
- MU-MIMO has been off. I did enable it in my first week with the Orbi system a couple months ago and it seemed less stable so I turned it back off.
- I've really wanted Implicit Beamforming to work but it's always been a disaster, and I've tried it about four times over the past couple of months. It doesn't really mess up any of the client connections, but for whatever reason when I turn it ON, it makes the satellites go from "Good" to dropping down to "Poor" every few minutes and then going back. And yes, I know that's ridiculous as it should have NOTHING to do with the backhaul connection -- but I can't argue with observed reality. So I've kept it off.
Bottom line is that it's working great on 210 so I'm going to call it a day for now. Maybe after another FW release or two I'll try it again and see if I can go back to one SSID.
For what it's worth, on some level I'm just frustrated that bandwidth steering takes a little control away -- I know they theory is that with one SSID "you just don't have to worry about it, it just works," but that hasn't been my experience. Even beyond the iPads, I've had other devices get flipped over to the 2.4 band because the signal was stronger and the 5G band was starting to get weak at that distance. But in those cases I can clearly see throughput on 5G that's still as much as 433Mbps, versus half that or less on 2.4 -- so it's frustrating to know it's preferring a stronger but slower signal over a faster connection. With two SSID's, I can control which devices use which bands and optimize everything.
I guess this is a topic for a new thread, but next I need to figure out why devices associated to different satellites can't always ping each other. Sometimes they can, sometimes they can't. Shouldn't every assigned IP address be visible to every other one? (I know not every devices responds to a ping -- I'm talking about the ones that should, like my Raspberry Pi servers.)
Yeah, the best version isn't necessary the latest version. The best firmware version is the version that works best for your setup.
BTW, if you get "Poor" backhaul, it's a sign of weaker signal post v210. I discovered that post update from v210 as well. My Satellite had "Good" backhaul in v210, then it's "Poor" after v210. When I checked the main UI, one of my Satellites had switched its backhaul from 5GHz to 2.4GHz. All my devices that connected to that Satellite either ran into trouble or suffered from slow WiFi speed.
My solution was to move that Satellite to a new location to get "Good" backhaul, which it did. But then it threw me a curve ball via "Config_Sync" madness. I was planning to stay in v210 as well before I figured out the single SSID solution to the "Config_Sync" madness.
If you can't ping all your devices, check if you have packet drops.
Yeah, it's very frustrating -- no packet loss, just hard to ping between devices that are connected to different Orbis (whether router or satellite). I can ping anything on the same Orbi with no problem, and often can ping devices between Orbis. But just as often I can't, and there's not really a pattern as to which devices.
For example, I have a Raspberry Pi server in my home office that always connects to the satellite in that room. If my PC or phone is connected to a different Orbi in another part of the house, it's about 80-20 odds that I can ping it. No dropped packets, it's just as if it doesn't exist on the network. But it's connected to the Internet via the satellite back to the router and works great on its own; it's just invisible to a large part of my network. On the other hand, sometimes after a reboot of the Orbi system, it's "visible" everywhere. Makes no sense.
Are the SSIDs sepearated?
I haven't seen this with the RBK50 system I have. SSIDs are not separated. I did see config sync during the initial setup. Then it's gone.
What is the Mfr and model# of the ethernet switch if one is in the configuration.
MrMediaGuy wrote:
Yeah, it's very frustrating -- no packet loss, just hard to ping between devices that are connected to different Orbis (whether router or satellite). I can ping anything on the same Orbi with no problem, and often can ping devices between Orbis. But just as often I can't, and there's not really a pattern as to which devices.
For example, I have a Raspberry Pi server in my home office that always connects to the satellite in that room. If my PC or phone is connected to a different Orbi in another part of the house, it's about 80-20 odds that I can ping it. No dropped packets, it's just as if it doesn't exist on the network. But it's connected to the Internet via the satellite back to the router and works great on its own; it's just invisible to a large part of my network. On the other hand, sometimes after a reboot of the Orbi system, it's "visible" everywhere. Makes no sense.
