NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JMU1998
Dec 19, 2017Luminary
Orbi firmware v2.1.1.16 discussion
do we need to do nvram wipe for this 2.1.1.16 Firmware just released today? noticed it downloaded automatically.
orbirick
Dec 26, 2017Apprentice
tkshaffer wrote:Still not able to get my sonos...will continue to try but I am getting downright constant denial of service attacks. Just constant. I never saw these at all prior to this firmware. Is there something I should be doing about this? They look like this:
[DoS Attack: ARP Attack] from source: 173.28.128.1, Tuesday, December 26, 2017 02:39:20
[DoS Attack: ARP Attack] from source: 173.22.120.1, Tuesday, December 26, 2017 02:38:37
I see similar entries in my log file too. Here's a sample:
[DoS Attack: RST Scan] from source: 216.237.221.42, port 53, Tuesday, December 26, 2017 09:52:30
[DoS Attack: TCP/UDP Echo] from source: 93.174.95.106, port 27221, Tuesday, December 26, 2017 09:31:39
[DoS Attack: ACK Scan] from source: 216.237.221.42, port 53, Tuesday, December 26, 2017 08:53:25
[Time synchronized with NTP server] Tuesday, December 26, 2017 08:53:13
[DoS Attack: ACK Scan] from source: 216.237.221.42, port 53, Tuesday, December 26, 2017 08:52:34
[DoS Attack: RST Scan] from source: 216.237.221.42, port 53, Tuesday, December 26, 2017 08:23:27
[DoS Attack: RST Scan] from source: 52.207.123.174, port 443, Tuesday, December 26, 2017 08:23:24
[DoS Attack: RST Scan] from source: 216.237.221.42, port 53, Tuesday, December 26, 2017 08:22:35
[DoS Attack: ACK Scan] from source: 199.62.84.153, port 443, Tuesday, December 26, 2017 07:31:48
[DoS Attack: RST Scan] from source: 216.237.221.42, port 53, Tuesday, December 26, 2017 06:40:08
orbirick
Dec 26, 2017Apprentice
I have no idea what to make of the DoS attacks. Nothing seems to be affected, best I can tell. Everything seems to be running normally with no known issues.
- ratickleDec 26, 2017Apprentice
When I Telnet'ed into Orbi to try and prevent future auto firmware updates, one of the three nvram variable was not set to the expected value. Here is what I found:
orbi_auto_upgrade=3404316802
auto_check_for_upgrade=1
auto_update=1I was expecting the first variable to be set to 1 like the other two. From what I have read on this forum, to turn off auto updates, we change the values from 1 to 0. Does it matter that the first variable is not set to 1? Is it safe to set it to 0?