Print

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

[fireboy]

I've got 11 Day 23 Hour 35 Min 39 Sec on this BETA with no issues to date.  Over the weekend I downloaded about 11 GIG worth of files as I downloaded the ISO for Windows 7 and the game client for WoW after reloading my machine.  Didn't hiccup a bit.

I also don't use SharePoint, so can't verify anything there.  No lockups otherwise so far.

[partach1]

This new firmware version (beta 9) seems to decide to do some sort of soft reset from time to time.
Anyone else observed this?
I have observed from the alive counter that there were 4 'reboots'. This is what it looks like as the alive timer was reset in all those cases.
On average after about a day (1 time the router lasted for several days)
The log pretty much (this new version does not completely loose the logs after automated reset?) tells the same story:

[INFO]   Tue Nov 24 08:14:38 2009   Wireless restart
[INFO]   Tue Nov 24 07:01:31 2009   Time synchronized
<------------------- after trying to synchorinse NTP it seems to go wrong -------->
[INFO]   Fri Nov 20 19:12:32 2009   Requesting time from 207.232.83.70
[INFO]   Fri Nov 20 19:11:35 2009   Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO]   Fri Nov 20 19:11:32 2009   Time synchronization failed (status 2)
[INFO]   Fri Nov 20 19:11:30 2009   Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO]   Fri Nov 20 19:11:29 2009   Requesting time from 207.232.83.70
[INFO]   Fri Nov 20 19:11:29 2009   Time server ntp1.dlink.com is at IP address 207.232.83.70

After requesting time the router does not log anything anymore. This was the kind of break point all four times. According the current alive time the system was operational for about 10 hours meaning that the entry at about 7:00 am is the first one.
The logs tell me it was not a full reboot as the standard intialisation stuff does not apear at 7:00 ish in the log. Or?
Who can explain this?
I will make a new topic for this

[Lycan]

Disable the NTP server and see if the unit boots normally?

[brink668]

I tried the firmware, it's still been a rocky road.
Can we just get a utility to go back to 1.21?  Why drag on like this.

[point]

I tried the firmware, it's still been a rocky road.
Can we just get a utility to go back to 1.21?  Why drag on like this.

And what about to report the problem you're having instead of making posts without any content that can help to solve the problems??

For me, this beta 9 is working just fine

[EddieZ]

And what about to report the problem you're having instead of making posts without any content that can help to solve the problems??

For me, this beta 9 is working just fine

Point, welcome to the forum. But as you noticed there's a bunch of users that do not use the board to get help (and provide the data required). Ranting is their hobby, I wonder what happens when they need to see a doctor in personal  life 

And for 1.21: That's about the worst FW ever from Dlink 

BTW: beta09 is working fine with heavy wired and wireless load.

[outFire]

I second this Eddiez "BTW: beta09 is working fine with heavy wired and wireless load". However, I still wanted dlink to do something to extend the range of the signal and its about the last thing to make dir-655 a killer router.

[EddieZ]

I second this Eddiez "BTW: beta09 is working fine with heavy wired and wireless load". However, I still wanted dlink to do something to extend the range of the signal and its about the last thing to make dir-655 a killer router.

1. the max amount of 'transmitter power' is legally bound (otherwise you would need a permit (like a radiostation  ) to use this device)
2. the range is much more influenced by environment than tech solutions inside the router.

So theres just a tech limit on what a router can do.

[martok]

And for 1.21: That's about the worst FW ever from Dlink 

EddieZ,
not to hijack this thread (don't think this deserves a new topic), but I was wondering what your current recommended FW version was for the DIR655. I am running 1.21 now, but if it is the "worst FW ever" I suppose I should change it. However, I am extremely against the idea of using 1.3+ as I have read many horror stories (here and elsewhere) and am not willing to take that risk. I also do not feel comfortable using Beta firmware, especially when there is no choice to revert once it has been put in place (although from the looks of it, they are doing a fine job with it and it will be 'the one' once it has been vetted and released).

I realize this puts a lot of restrictions and narrows down the choices, but I am all ears

[point]

EddieZ,
not to hijack this thread (don't think this deserves a new topic), but I was wondering what your current recommended FW version was for the DIR655. I am running 1.21 now, but if it is the "worst FW ever" I suppose I should change it. However, I am extremely against the idea of using 1.3+ as I have read many horror stories (here and elsewhere) and am not willing to take that risk. I also do not feel comfortable using Beta firmware, especially when there is no choice to revert once it has been put in place (although from the looks of it, they are doing a fine job with it and it will be 'the one' once it has been vetted and released).

I realize this puts a lot of restrictions and narrows down the choices, but I am all ears

Do you have any problem with 1.21?

If you don't, keep it.

[vadskar]

Running 1.32b09NA with DNS relay on, for 25 days now. Seems like it's a keeper. Again, I'm not using SharePort, therefore cannot validate this feature.

[mbtoloczko]

I'm getting occasional router crashes with 1.32b09.  The cause of the crash is not clear as it seems the log is truncated at the time of the crash, however my guess is that its occuring only when I am VPNed into my company network.  Setup:  I reset the modem to the factory defaults before uploading b09, and then reset it again to factory defaults after installing.  I did not restore settings with a config file, but instead redid the few custom settings manually.

[martok]

Do you have any problem with 1.21?

If you don't, keep it.

Unfortunately, I am having a problem with the router, although I am unclear of the cause and whether it is even the router at all, although all indications seem to be yes. I am just looking for the 'official' word from a Moderator or Tech Support person on what they recommend.

[fireboy]

Just another quick update Ruf... 

So far I gave 8 Day 2 Hour 35 Min 59 Sec on the version of the FW with NO crashes or major issues.  While I'm a competent network guy (i do it for a living), i don't stress this router at home all that hard as far as port forwarding, etc. etc....

so whatever you've done here so far seems to have corrected at least the random lockup issues I was having with the internal website becoming non-responsive and suddenly not being able to get to the internet.

[jdrom]

Running 1.32b09NA with DNS relay on, for 25 days now. Seems like it's a keeper. Again, I'm not using SharePort, therefore cannot validate this feature.

Similar situation here. Though I'm on 27 days I think it's the longest this DIR-655 has ever been up.

DNS Relay enabled, NTP enabled using ntp1.dlink.com