NTP Port 123 Issues

[Lex600]

Our WNDR3700v1 router started logging Dos Attack errors for NTP port 123 on Saturday after I upgraded our ReadyNAS servers to release RAIDiator-x86-4.2.20. This release does change something with NTP. The IP addresses shown in the router log are for Netgear NTP servers.

The log shows:

[DoS Attack: TCP/UDP Echo] from source: 209.249.181.23, port 123, Saturday, April 28,2012 22:17:01
[DoS Attack: TCP/UDP Echo] from source: 69.36.227.90, port 123, Saturday, April 28,2012 22:16:55
[DoS Attack: TCP/UDP Echo] from source: 209.249.181.23, port 123, Saturday, April 28,2012 21:59:56
[DoS Attack: TCP/UDP Echo] from source: 69.36.227.90, port 123, Saturday, April 28,2012 21:59:51

The ReadyNAS servers, and many other hosts, have been using NTP for a long time before without any objection from the WNDR3700.

Since the WNDR3700 prohibits port fowarding/triggering of port 123, is there a solution/workaround to this error logging? Thanks.

[jmizoguchi]

If the revert to old firmware goes away, contact support about the issues using portal. my.netgear.com

[quagmire]

As you already know, the release notes for RAIDiator state they have "Updated NTP service for more accurate clock syncs". As a WAG, I think they're hitting the NTP server too often in the new code.

As a comparison, I'm running three different versions of ntpd on two PCs and a Mac with nary a peep from my WNDR3700v1 running V1.0.16.98-dnsNA .

If you're running an older version of software on the router you might try updating. However, I'm guessing it's a problem with the new RAIDiator software. Since both products are Netgear, you'd think they'd be willing to fix one of them.

You'd think.

[Lex600]

Thanks for your suggestions. I submitted an online case. Case #: 18468421