D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Fed_Up on January 22, 2010, 03:16:54 PM
-
Here is the real reason why Dlink can't come up with non-beta firmware.
They send out pre-releases to Mr. Personality.
Quick Lycan,
Lock it, delete it, cover it up...
Bye.
-
:'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'( :'(
-
FedUp - whoever you are I don't think it is appropriate that you post in the way that you have in the last 24 hours. This is a support forum and not a place for abuse. I have similar problems to the majority of members but I don't think stooping to being childish the way you have helps the situation. Whilst I share your frustration in the supposed "user" EzzieZ's comments, it is only reasonable that Dlink should have a couple of these type of "users" on the forum to at least point out the router is stil a good product despite it's flaws. They have a commercial product to protect. And for the most part it IS a good product. The problems are largely due to corporate interference in insisting they fitted sharepoint (or whatever it's called) into the router to make a few dollars.
If you must post again then please do so under a proper identity and with a little respect.
-
tentimes,
have you tried the 1.33 code? Does it work for you?
-
Not yet, I'm waiting a few days to see how other people go. The 1.32NA09 is doing a lot better than the last one (only have to restart once a week or so now) so I will wait to see how others fair before I risk it. Like I said - it's a good router, even with the problems ;)
-
1.33 works very well.
Although when put under long torrent strain the time in the router starts lagging, sometimes up to two days. Have noticed this since all 1.3x and 1.21 firmwares. Not using schedules for a while now, so no real damage.
-
I suppose I could start using my dir655 as a test bed only, but I'm afraid of the code being modified so that I can't use it in bridge mode. lol.
-
It's still useable in bridge. I doubt they will take the stuff out. Too much work.
-
When you say the time runs off.....is that with or without a NTP server?
-
When you say the time runs off.....is that with or without a NTP server?
With NTP server. I've set it to my ISP's and various other, to see if it was timezone or server related. But apparently using any NTP server causes my 655 clock to slow down considerably. Also, there's a lack of NTP synchronization attempts in the log. It has been doing this with all 1.3x versions (I haven't noticed this with 1.2x...too long ago). Once synchronized manually with my PC it stays on track alright.
It does so in both router mode and AP mode (hidden setting, perhaps in AP mode the NTP is disabled internally?)
-
Odd. I'll take a poke at that with a stick and get back to you. Hit me up if I forget.
-
I have no such NTP slow down problem on my A4 HW with firmware version 1.33NA. So it might be something with the configuration of the person having it.
-
No time problem here. Rev A2 - 1.33NA
About 4 sec difference after hours.
And synchronizes time with restart:
[INFO] Tue Jan 26 07:17:02 2010 Time synchronized
[INFO] Sun Jan 24 22:31:34 2010 Requesting time from 192.53.103.108
[INFO] Sun Jan 24 22:31:34 2010 Time server ptbtime1.ptb.de is at IP address 192.53.103.108
Doesn't matter if I use the german NTP server or ntp1.dlink.com
-
Yeah EddieZ must of just configured it wrong because mine has been running solid since 1982.
Hopefully the netgear forum will see more of your valuable posts like this.
Good luck with your rock solid new hardware :D
-
Nope. It's the firmware ;D
Even funnier: NTP server off, all goes OK. Turning on NTP server sets back the date 4 days (!) immediately after save...Changing timezone does not alter time.
-
LOL
I use 855 here and have none of those issues. It almost sounds like a localization issue........I'll check in to it.
-
LOL
I use 855 here and have none of those issues. It almost sounds like a localization issue........I'll check in to it.
I did work on earlier firmwares, nothing changed in network topology since. Did a clean factory reset three weeks ago and upgraded to 1.33 since. Interesting... Also the fact that changing timezone does not alter the time...
-
Try to flash an older firmware and whether time works with it then.
Reset it an flash the 1.33 again. Perhaps not all blocks of the memory are written propperly.
I had a similar problem when updating to 1.21 end of 2008 and it helped to flash an older version and then the new one again.
Still in correct time here :) with my old Rev A2
-
Lycan bans accounts that show how bad the coders are. HAHA. btw im behind like 7 proxies so banning me is just going to stop me for a minute, and I got a lot of time.
-
Lycan bans accounts that show how bad the coders are. HAHA. btw im behind like 7 proxies so banning me is just going to stop me for a minute, and I got a lot of time.
This has nothing to do with dlink, what are you doing here?
-
This has nothing to do with dlink, what are you doing here?
Ego issues...
I found another user with this issue on a Dutch expert site. He might be signing in too to report the issue.
-
tentimes,
have you tried the 1.33 code? Does it work for you?
Where can I get the 1.33 code?
-
Where can I get the 1.33 code?
1.33 code can be found here
http://forums.dlink.com/index.php?topic=10677.0 (http://forums.dlink.com/index.php?topic=10677.0)
-
1.33 code can be found here
http://forums.dlink.com/index.php?topic=10677.0 (http://forums.dlink.com/index.php?topic=10677.0)
Thanks a lot! It works like a charm.
-
1.33 works very well.
Although when put under long torrent strain the time in the router starts lagging, sometimes up to two days. Have noticed this since all 1.3x and 1.21 firmwares. Not using schedules for a while now, so no real damage.
I've noticed the same thing with 1.32 and 1.33. With NTP updating disabled, time lags badly. When I installed 1.33b02 on Saturday at ~2 pm, I set the time manually. Its now Wednesday at 8:15 pm, and the router thinks its still Saturday, but now at 10:15 pm. Oddly, the seconds seem to be ticking off at a normal pace when I observe the time in the Status window. This is with almost minimal internet traffic going through the router. No servers of any sort running on the network.
-
Same here.
1.33 beta 01. NTP disabled, the time starts to get many days behind. It seemed to happen with the default dlink NTP servers too.
However, NTP enabled and pointed to time.windows.com, the time stays pretty darned close.
-
Here is alot of NTP severs to use
http://support.ntp.org/bin/view/Servers/NTPPoolServers (http://support.ntp.org/bin/view/Servers/NTPPoolServers)
kthaddock