Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[emk]

I am having the exact same problem.  I've tried both the internally coded NTP servers (ntp1.dlink.com, ntp.dlink.com.tw).  In the log it shows they have been unsuccessful sync'ing the time.  So I tried ca.pool.ntp.org, and even the north-america.pool.ntp.org servers.  This sends my router into a downward spiral and it becomes a $109 useless brick.

I had NTP turned off at home last night.  This morning remotely from work I tried to set it up again, but the same crap happened.  My WAN connection goes mental as you can see from my ping output below:

ping -a x.x.x.x
PING x.x.x.x (x.x.x.x): 56 data bytes
64 bytes from x.x.x.x: icmp_seq=11 ttl=58 time=17.784 ms
64 bytes from x.x.x.x: icmp_seq=12 ttl=58 time=1607.947 ms
64 bytes from x.x.x.x: icmp_seq=13 ttl=58 time=607.836 ms
64 bytes from x.x.x.x: icmp_seq=14 ttl=58 time=2406.850 ms
64 bytes from x.x.x.x: icmp_seq=15 ttl=58 time=1406.759 ms
64 bytes from x.x.x.x: icmp_seq=16 ttl=58 time=406.635 ms
64 bytes from x.x.x.x: icmp_seq=28 ttl=58 time=17.844 ms
<snip>
.
.
.
<snip>
64 bytes from x.x.x.x: icmp_seq=2434 ttl=58 time=29.192 ms
64 bytes from x.x.x.x: icmp_seq=2435 ttl=58 time=18.902 ms
64 bytes from x.x.x.x: icmp_seq=2436 ttl=58 time=1002.894 ms
64 bytes from x.x.x.x: icmp_seq=2437 ttl=58 time=18.679 ms
64 bytes from x.x.x.x: icmp_seq=2438 ttl=58 time=1810.220 ms
64 bytes from x.x.x.x: icmp_seq=2439 ttl=58 time=810.122 ms
^C
--- x.x.x.x ping statistics ---
2446 packets transmitted, 834 packets received, 65% packet loss
round-trip min/avg/max/stddev = 16.796/916.474/3225.398/771.878 ms

Look at the amount of packet loss (65%), and the terrible round trip times!  And this all because of flaky NTP implementation.  I need time to be synchronised because I use schedules.

I am also an irate customer of the physical power-cycle camp as I have to regularly physically power down/up the router to even obtain internet access.  This router is becoming a POS with every passing minute.

C'mon Dlink, get your act together and do right by your customers... else you won't have any left.

[ironic77]

Wow.  Me too.

I know for a fact that one of my (now many) sets of rebooting issues was after I noticed that the router time was incorrect.  I noticed it was getting a bad time from the default d-link NTP servers (Dec 28 2009 when it was Jan 6 2010).

I switched to time.windows.com which is what my PCs use.  Since then, the NTP related flakiness seems to have died down and my device clock is now correct again.  I haven't tried turning NTP off to further reduce my nearly constant reboots, but I think I will go try this now.

I am definitely thinking that my reboots are caused by maybe just one or two buggy features in the firmware.  A simple dump and source code would prove it.  But alas, no one from D-Link cares or wants to take me up on the offer to get them data.

[emk]

@ironic77, I also figured out the using the seemingly problematic Dlink NTP servers was causing issues.  I have remote access into my home network from my workplace based on a business day schedule (9pm-6pm).  Since last week my attempts to remotely connect have failed and I didn't know why.  Yesterday I figured out that the time on my DIR-655 was way off, just like yours... causing me to not have remote access.

So that's when I started moving away from D-Link's NTP servers.  Something is wrong with them.  Trying the pool addresses have caused havoc with my internet access now.  Router is rebooting every 30 seconds!

[Cobra]

If using Windows, open the clock and choose one of those other than time.windows.com

[tzzhc4]

I can't say how happy I am to have found this thread. I am having the exact same issue and was going nuts trying to figure out what was wrong with my router. For now I have disabled NTP and all is well.

Any idea when or if DLink will actually fix this?

[nienberg]

The problem has existed for some time and is well documented here:

http://forums.dlink.com/index.php?topic=5980.0

Make sure the ntp server you want to use is NOT part of a pool or using a round-robin dns.  Don't use something like time.apple.com or time.microsoft.com because those are certainly servicing ntp requests by using several machines.  Perhaps your ISP has a single ntp server. 

If you get into the reboot loop, then unplug the cable to the WAN interface and the rebooting will stop.  After that you can connect to the router again and change your ntp settings.

By the way, on my router the option to manually set the time doesn't work either.  It sets the time correctly when I save the changes in the web interface, but then it also resets the time to the same thing the next time I log on to the web interface.  I've just stopped trying to use schedules at all, so it doesn't matter that the time is always wrong.