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 ...
I highly recommend doing a Factory reset after installing the beta FW. This probably has major changes and updates to the code. To ensure the beta FW is installed and seated well and to give it a solid chance, a factory reset should be performed and set up from scratch. I can attest to ethernet back haul IS working on my Orbi system. Factory reset performed and then set up from scratch. Two non managed Gb network switches between my 1 Satellite and the Orbi router.
Give the new FW a chance. Take the time and do the reset and set up from scratch.
- I’m curious:
Doesn’t Orbi have a way to Export a config file of all of our settings, that we can simply reimport after a Factory reset?
Even if it does, I wonder then, if by doing so would just eliminate any of the benefits of doing a Factory Reset to begin with?
Also, is it just me or is it that we can only disable SSID Broadcasting from the Guest Network, but not from the main WiFi Network?
They also need to add a way to force WiFi devices to only connect to either 2.4GHz or 5GHz.
BJYes under Advanced/Backup settings. Under normal circumstances and with in the same version of FW, this back up file is valid. However after updating FW from one version to the next major version, there maybe some items with in the new FW that could have adverse operations if a older config file is applied from a prior version of FW. So, with this, I recommend after upgrading to the next major version of FW or Beta or from Beta to official releaed FW. Do a factory reset, set up from scratch and then save off a new back up config file for this next version thats loaded. Then you have a good back up for the current version of FW that your working with. Seen odd issues over the years in working with routers and configurations and many different FW versions. All this lead me to just take the plunge and do a resets then set up from scratch and make a new backup config file at each upgrade stage in the FW cycle. I presume when the FW become more stable and all non beta official FW, you mgiht be able to just upgrade the FW and any current configurations should remain and persist which is NG normal idea of upgrading FW.
You should be able to disable the main wifi radios under Advanced/Advanced/Wireless settings. Is this what your looking for?
The Orbi system is designed Smart Connect. It's supposed to handle which devices get connected to which freqency based on device support and operation automatically. So this feature isn't supposed to rely on any user intervention.
b1ggjoewrote:
I’m curious:
Doesn’t Orbi have a way to Export a config file of all of our settings, that we can simply reimport after a Factory reset?
Even if it does, I wonder then, if by doing so would just eliminate any of the benefits of doing a Factory Reset to begin with?
Also, is it just me or is it that we can only disable SSID Broadcasting from the Guest Network, but not from the main WiFi Network?
They also need to add a way to force WiFi devices to only connect to either 2.4GHz or 5GHz.
BJ- Aaah ok, makes sense. As far as the WiFi question, I was just trying to hide and keep the SSID from broadcasting, not so much disabling the radio.
I see where this can be done for the Guest Network, but not the main WiFi SSID.
b1ggjoewrote:
Doesn’t Orbi have a way to Export a config file of all of our settings, that we can simply reimport after a Factory reset?
Even if it does, I wonder then, if by doing so would just eliminate any of the benefits of doing a Factory Reset to begin with?It is worrisome that the exported .CFG file is binary and not text. To me, that suggests that importing the .CFG will, as you say, eliminate the benefits of a factory reset because it's just reading old settings back into memory. If the .CFG file were text, at least we would know what was in there and understand that the firmware was interpreting the old settings from text back into binary.
For security reasons, I presume, the config file isn't open text anymore. Most router Mfrs don't use clear text files anymore.
Well, 16 hours up time on the new firmware with..
Daisy-Chain Topology enabledImplicit BEAMFORMING enabled
MU-MIMO enabled
Fast Roaming enabled.
I have the RBR50 and two RBS50s. So far everything is working flawless! *knocks on wood*. I didn't go as far as factory resetting everything, just updated that sats, then the routers. Figured I'd try that before resetting everything. So far so good, no errors in the logs, no issues on any devices. Best stability I've had in months.
YAY!!! :smileyvery-happy:
TrickyTwrote:Well, 16 hours up time on the new firmware with..
Daisy-Chain Topology enabledImplicit BEAMFORMING enabled
MU-MIMO enabled
Fast Roaming enabled.
I have the RBR50 and two RBS50s. So far everything is working flawless! *knocks on wood*. I didn't go as far as factory resetting everything, just updated that sats, then the routers. Figured I'd try that before resetting everything. So far so good, no errors in the logs, no issues on any devices. Best stability I've had in months.
Running this for almost 12 hours and all is good. For now, every 1-2 min, I see this in the logs:
[DoS Attack: IP Spoofing] from source: 192.168.1.254. Don't see any attached devices to the router or satellite with this IP.
Any idea what this may be?
