NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but ...
V2.1.3.4 firmware has been good no crashes for a week (used to happen almsot twice a day)
have noticed some *dns dropping(what my software complains about) related lag if mildly (5-10mbs) using more then 5 devices regardless if LAN or WAN ** havent had time to play with it
also have allot of false DoS attack rst scanns from google/amazon/netflix servers sometimes heavy playback lag of videos is created because of it.
I have had some DNS issues too. Did a paper clip reset and they stopped. Not sure if that was the difference. A friend of mine on the beta firmware was having dns issues too going to basic sites like gmail would say it couldn’t get there.
It's highly recommeded to do a factory reset after upgrading FW and set up from scratch. I've seen issues myself and other with just upgrading FW over top of prior FW and having issues. Doing a full factory reset on the entire system after a FW update then setup from scratch resolves these issues.
jeffholidaywrote:
I have had some DNS issues too. Did a paper clip reset and they stopped. Not sure if that was the difference. A friend of mine on the beta firmware was having dns issues too going to basic sites like gmail would say it couldn’t get there.It's been a full week since updating to V2.1.3.4. We've not experienced any of the network issues on iOS devices that we were seeing before.
- router mode
- beamforming, and fast-roaming ENABLED
- MU-MIMO DISABLED
- satellites got factory reset witht the update; router WAS NOT reset
Seems solid so far.
What is the best procedure to set up a system w/ wired backhaul? I can't seem to get the system to fully recognize the sats with wired backhaul. To even get close I need to turn off daisy chain, sync with the sats unpluged, and then once the system is stable on the wireless side plug everything in...eventually it will start reporting wired backhaul, but even jumping through hoops like this the GUI never reports stable connections to the sats. Is there an optimal procedure that repeatably gets this to a stable, wired system?
I really can't understand how this wouldn't be tested even for a beta - did they really not factory reset, turn on the RBR, plug in ethernet, turn on RBS and sync? I'm not trying anythng remotely complicated here - so it's shocking to me that it doesn't just work...
Bei mir läuft seit dem letzten Update alles für mich korrekt und stabil vor allen Dingen !
Die Task-Force von Netgear hat ja wohl auch etwas gebracht!
Endlich nicht mehr jeden Tag Gedanken machen um sein Internet bzw WiFi Verbindung!
Ich habe das rbk50 + den RBS 40 + den RBS30😁🍻
.
