NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 Massive Security Fail - Many ports responding to requests
Just bought the thing, using the latest firmware V3.2.9.2_1.2.4. Did not Disable Port Scan and DoS Protection. WAN ports respond to unsollicited requests, instead of ignoring. They do respond clo...
Well seems the RBR is doing something. Wheather GRC is correct or Orbi isn't. Those are the results I got. Again when in normal operation and other devices online and connected, there will be ports being OPEN and in use and seen as such by GRC.
For all the years i've been uPnP I have had not 1 problem with it or anyone trying nefarious things with uPnP what so ever.
If your not happy or satisfied with Orbi AX and it's security, return it and find something that is to your satisfaction.
I tried replying twice yesterday and my posts didn't get through - images again I suspect.
Bottom-line, the reason you are seeing the difference now is because of the 15.25 version has fixed the issue we were raising.
After updating that, I also get the ports showing stealthed properly now even with several devices connected.
It had *nothing* to do with you running an isolated test with just 1 wired device this time.
Blanca_O - I don't know if this fix came about at all from this thread, I suspect the coding and testing was already underway for this before I started posting on it at least. Either way I'm very thankful to see this improvement, and if you would pass my thanks on to engineering please, I would appreciate it.
Try selecting the Choose File button at the bottom to attach posts.
So the new FW is working for you then?
This was reported way back in January FYI...
tantrum wrote:I tried replying twice yesterday and my posts didn't get through - images again I suspect.
Bottom-line, the reason you are seeing the difference now is because of the 15.25 version has fixed the issue we were raising.
After updating that, I also get the ports showing stealthed properly now even with several devices connected.
It had *nothing* to do with you running an isolated test with just 1 wired device this time.