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.
Well, 16 hours up time on the new firmware with..
Daisy-Chain Topology enabled
Implicit 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?
In my expoerience, the "DoS Attack" warning in the Netgear logs tend to have alot of false positives. For instance, I run my Orbi behind a dedicated firewall that blocks all inbound connection attempts before it even reaches the Orbi at all, and yet the Orbi logs regularly tell me that it sees inbound "attacks", which are not possible. My assumption is that for many of these, the Orbi is just not doing an adequate job of maintiaing connection state tables, and sometimes what it thinks is an inbound attack is simply a valid response to a legit outbound packet.
I'm not sure about the "IP spoofing" message, however. That might be caused by a packet being received from an address that is not "local" to that interface's network. Or, perhaps it's the result of some sort of NAT behavior. I've not noticed that particular one in my logs.