NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Sep 17, 2020Guru - Experienced User
New - RBR50 / RBS50 Firmware Version 2.5.2.4 Officially Released
Bug Fixes: Fixes the issue where the Nintendo switch failed to connect to the Internet after the Orbi installation due to IP conflicts. Fixes the system stability issues that occurred after the fi...
thisoldhouse
Oct 25, 2020Aspirant
Where in the menu do find the option to disable DoS? I looked around in Advanced area but didn’t see it.
thisoldhouse
Oct 25, 2020Aspirant
Found it under the logs. Well that worked perfectly!!!! All the issues are now gone and internet is back to normal. Netgear must not have a very good QA dept if they’re releasing firmware like this.
- RaekonOct 26, 2020Tutor
thisoldhouse wrote:
Found it under the logs. Well that worked perfectly!!!! All the issues are now gone and internet is back to normal. Netgear must not have a very good QA dept if they’re releasing firmware like this.The option to disable DoS protection and port scan is under Advanced -> Setup -> WAN setup and tick “Disable Port Scan and DoS protection”. I did this and it fixed most of the problem for me. Sometimes when I’m downloading and saturating my bandwidth my wifi still crashes for a little bit but in a normal scenario it works fine for now. Definitely not ideal but definitely usable.
If you just unticked “Known DoS attacks and port scans” under the logs page, then I don’t think you disabled the actual protection but just the logging of those attacks. Interesting that it works just as well as what I did though, I will try that aswell since having the protection active is better than nothing. Howerver it was blocking alleged dos attacks from Facebook IPs, basically anything it was blocking it shouldn’t really be blocked when I tried to lookup the IPs. It’s just doing a very poor job. As for Netgear’s QA department, I think the answer to your question is pretty obvious.
- thisoldhouseOct 26, 2020AspirantYep, I just unticked it under logging and it solved the issue. Maybe writing to the logs is the issue. Seems pretty odd that it would cause it but it resolved the issue immediately.
- FURRYe38Oct 26, 2020Guru - Experienced User
NG is looking to v4 and v70 versions of FW.
You can keep using v4 or downgrade back to v16.