NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Terrible Bug - Adding a RBS20 satellite to RBK 50 system breaks the LAN
Following up from another thread- I just got done with a full troubleshoot and it appears that Interoperability between Orbi systems is rather badly broken. Many users may not even notice this as th...
superczar wrote:I added a static route on the RBR50 to provide 192.168.5.1 (My router) as the gateway for all traffic on the 192.168.5.0/24 subnet
Wow, this is creative. I would have assumed that all of those features (static routes, port forwarding, triggering, etc.) would not be available when the Orbi is in AP mode.
Unfortunately the static route workaround did not solve the problem completely.
Devices connected to the RBS50 would stop seeing other devices on the LAN after some time.
Having wasted 8+ hours on it, decided to give up and set the Orbi to router mode this morning.
The ER-X handles the dual WAN and passes on the Internet to the RBR50 - The RBR50 is now acting as the primary router for the rest of the network.
I am not facing any of the mentioned issues in Router mode now.
While this setup with its double NAT is certainly not optimal , plus I also lose the ability to VPN to my home from outside
I still like the Orbi but these odd issues make it very difficult to recommend it to others
If your going to use the ERX and RBR both in router mode, I would set the RBR into the ERX's DMZ for less hassle with double NAT. I do this for routers i periodically test from time to time behind my primary router.
Thanks - That's a good tip.
Sadly the issue is back - even in router mode, things worked fine all day but I see dropped LAN connectivity from RBS50 again.
I enabled fast roaming an hour ago - while this doesn't seem related, I will try disabling and retesting.
On a separate note, this does not appear to be an isolated issue
Think I figured out the issue (though it may be too early to say for sure)
As strange as this may sound, The Fast-roaming flag does seem to be the underlying issue.
The symptom was lack of access to devices connected to the satellite 1 to LAN devices on router/sat2.
After having tested this out for a day, it appears that the problem does not occur if fast roaming is disabled
This would lead me to believe that the MAC lookups (ARP?) for devices that switched from router to SAT1 are getting messed up somehow if FR is enabled - With FR disabled, the Orbi (Probably ) works like a regular multi Access Point LAN and the issue doesn't happen
The new FW release note seems to have fixes for Iot devices so maybe that fixes the LAN issues - will try and report
Hi,
Thanks for all your investigation on this, you've jumped through a bunch of hoops I wouldn't have thought of. - I have the same set up (RBR50 + RBS50 + RBS20) and have also have horrible ping times on local lan.
I've updated to latest firmware, V2.5.0.38 for RBR + S 50, and V2.3.5.26 for RBS20, and seeing same results, latency can look alright for a short while before spikes of > 1000ms come in, then persist.
As the issue can be sporadic I'm not 100% sure if the RBS20 satellite is the key, particular as there are other user who seem to have similar issues without additional satellites.\
I'll keep on tinkering and let you know if I find anything
Alex
In my case, I lose connectivity altogether between some devices on RBR50 and some devices on the rest of the network . e.g. A Macbook (device A) , when connected to RBS50 cannot reach let's say my Hue unit (device B) which is connected wired to the RBR50
One definitive that I have noticed is that switching off the RBS20 resolves all the issues almost immediately
One likely link I have noticed over the last two days is when I switch off fast roaming, the network has been running stable.
Tried this 3-4 times now - When I Enable fast roaming , device A can reach dev B for some time , 10-15 mins later, A cannot reach B at all
Then I disable fast roaming and reboot - Device A can now reach device B even after say 10 hours.
The last FR toggle I did was 12AM local time (Indian Standard time). It's 2 PM now and the network is stable.
