Print

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

[mbtoloczko]

I just bought a second DIR-655 (A4) for a friend, and upgraded the firmware to 1.32NA.  After I enabled NTP lookup in the options, the router started crashing continuously.  I had to use the manual reset button to regain control, and the second time through I avoided enabling NTP.  Working great now.  I haven't tried duplicating the crash, but thought I would mention it anyhow.

[bluenote]

You would think somebody would care about this, wouldn't you? 
Its been documented and written about really well on this forum, and yet, the problem still exists...

Good on you for posting anyways though

[EddieZ]

minor issues will remain... As with all other software and more or less all firmwares from whatever brand.

[bluenote]

It's not a minor issue.  If you run into it and you aren't extremely tech savvy, it's going to bring you down permanently.

And, even more worrisome, is that it shows the crap error handling that they use over at dlink HQ.

You show your bias by basically supporting this NOT being fixed.  How silly.

[EddieZ]

It's not a minor issue.  If you run into it and you aren't extremely tech savvy, it's going to bring you down permanently.

And, even more worrisome, is that it shows the **** error handling that they use over at dlink HQ.

You show your bias by basically supporting this NOT being fixed.  How silly.

It's minor since choosing 99% of other NTP will work. And will give the same result (time) 
I'm in IT and know something about issue/bug classification. This is not a major bug. Also I cannot reproduce any of the NTP crashes. Not even with the pool ntp's. So I doubt firmware is th cause.

Major issues get solved first, minor issues might never get ssolved. D-link is no exception to that. And rule number one in bugfixing: never fix more then 1 issue simultanuously in the code by different coders. And luckily they're doing that, doing it step by step.

[kthaddock]

I just bought a second DIR-655 (A4) for a friend, and upgraded the firmware to 1.32NA.  After I enabled NTP lookup in the options, the router started crashing continuously.  I had to use the manual reset button to regain control, and the second time through I avoided enabling NTP.  Working great now.  I haven't tried duplicating the crash, but thought I would mention it anyhow.

Have you look at this side ?  http://www.pool.ntp.org/zone/europe

rgs
kthaddock

[grking]

It's minor since choosing 99% of other NTP will work. And will give the same result (time) 
I'm in IT and know something about issue/bug classification. This is not a major bug. Also I cannot reproduce any of the NTP crashes. Not even with the pool ntp's. So I doubt firmware is th cause.

Major issues get solved first, minor issues might never get ssolved. D-link is no exception to that. And rule number one in bugfixing: never fix more then 1 issue simultanuously in the code by different coders. And luckily they're doing that, doing it step by step.

Have tried several NTP sites. I have verified logs stating that connection to ntp site failed. This was followed by a reboot and resetting  of time on several, but not all occasions. This leads me to believe NTP plays a role but isn't the only culprit for reboots. Manually setting time seems to help....... somewhat.

[EddieZ]

Try resetting to factory defaults, reflash and set it up manually. This has worked with many others experiencing reboots. I know it sux, but the flash mechanism can give these errors sometimes.

[jdrom]

I've only been able to get the D-Link servers to work (aka the ones in the list). If I use something like ca.pool.ntp.org, the router just crashes and gets stuck in a reboot loop. That was with the 1.32NA final, haven't bothered trying with the beta09. D-Link's NTP works good enough.

[kthaddock]

I've only been able to get the D-Link servers to work (aka the ones in the list). If I use something like ca.pool.ntp.org, the router just crashes and gets stuck in a reboot loop. That was with the 1.32NA final, haven't bothered trying with the beta09. D-Link's NTP works good enough.

If you have wrote like in the text ca.pool.ntp.org (,) try to remove ,

rgs
kthaddock

[mbtoloczko]

It's minor since choosing 99% of other NTP will work. And will give the same result (time) 
I'm in IT and know something about issue/bug classification. This is not a major bug. Also I cannot reproduce any of the NTP crashes. Not even with the pool ntp's. So I doubt firmware is th cause.

Major issues get solved first, minor issues might never get ssolved. D-link is no exception to that. And rule number one in bugfixing: never fix more then 1 issue simultanuously in the code by different coders. And luckily they're doing that, doing it step by step.

If it isn't a bug, then its poor error handling.

[partach1]

Have tried several NTP sites. I have verified logs stating that connection to ntp site failed. This was followed by a reboot and resetting  of time on several, but not all occasions. This leads me to believe NTP plays a role but isn't the only culprit for reboots. Manually setting time seems to help....... somewhat.

For me NTP causes the same problems. Only standard DLink NTP (chose from drop down on page) seems to work. Setting manual time does not work. Within a day it can lag half a day regarding time. This can be observed via syslog. The router seems to keep different time variables inside the code. Syslog prints two different ones if you disable NTP.....
Btw this is the first time I have seen a device not being to able general NTP. Severity is not A (saftey) nor B (show stopper) but certainly C (major annoyance). Handling time is a problem with the software versions. Have seem problems with this since March.
Which region are you from? I am from the Netherlands, maybe it is region related with GMT settings or whatever.

[lizzi555]

Mine works with d-link NTP and german ptbtime1.ptb.de without problems.
Did not try any other servers - to lazy 

[chaicka]

I am using NTP for my 655 with 1.32NA firmware. The NTP server defined points to one of my telco's NTP servers.

Everything works fine. No issue at all. It's able to sync time on the pre-defined intervals.

[Neblinio]

I experienced this problem yesterday for the first time.
I've been using NTP with the server "hora.roa.es" (official time in Spain) for months, and only had the issue of the router time being changed sometimes (specially with no active WAN connection). Yesterday morning I found my network connection rebooting constantly, and I could barely access the admin interface to reboot it. The rebooting only stopped when I disconnected the WAN cable, so I did it and then logged to the admin interface to disable NTP. Now the router works normally.