Print

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

[tentimes]

I'm having the exact same problem as the OP after upgrading to this firmware. I get a couple of days then have to reboot. I have never had this problem before and it has only started happening with this firmware. The telling point is that even though computers are connected I can no longer reach the routers control panel on 192.168.0.1 I reboot and all is fine for a couple more days. Really snnoying.

[mackworth]

Did you turn off DNS relay?


I love how more and more people are coming to the board with this problem.  Maybe d-link won't be able to keep ignoring it.

[tentimes]

Hopefully they will fix it then Yes I have now disabled it, only up one day though so waiting to see if that fixes it. Interestingly this is the first time I have had this problem, ONLY on this particular firmware (and I have been updating each new one as they come out).

[mackworth]

Hopefully they will fix it then Yes I have now disabled it, only up one day though so waiting to see if that fixes it. Interestingly this is the first time I have had this problem, ONLY on this particular firmware (and I have been updating each new one as they come out).

This problem started in 1.22B05 and affects the latest officially release 1.31.  The issue is also on the DIR-825 on its newest firmware.

[jason1722x]

Did you turn off DNS relay?


I love how more and more people are coming to the board with this problem.  Maybe d-link won't be able to keep ignoring it.

They know it's a problem, Lycan even has a poll on it. Not sure when fw1.21-fw1.22 came out but it's been around since then.

[mackworth]

They know it's a problem, Lycan even has a poll on it. Not sure when fw1.21-fw1.22 came out but it's been around since then.

Lycan created the poll because I sent him a private message after he locked the freezing thread asking if he could make a sticky post about turning off dns relay if your router is freezing.

[jason1722x]

Lycan created the poll because I sent him a private message after he locked the freezing thread asking if he could make a sticky post about turning off dns relay if your router is freezing.

If Lycan created a poll because you sent him a private message, good for you! But if you search the forum on the subject "DNS Relay", "DNS Relay Problem", etc... you will find has been around since fw1.20-1.21 releases. It's not a new problem!
It's a problem they have not fixed, or don't know how to fix.

[mackworth]

If Lycan created a poll because you sent him a private message, good for you! But if you search the forum on the subject "DNS Relay", "DNS Relay Problem", etc... you will find has been around since fw1.20-1.21 releases. It's not a new problem!
It's a problem they have not fixed, or don't know how to fix.

I know its not a new problem, I said its been around since 1.22B05.

1.21 had a DNS slowdown issue and 1.22B05 introduced a fix that caused the freezing.  Read the long freezing thread, Lycan said that DNS relay shouldn't cause a router to freeze, and if it is freezing to RMA it, I think he even said it wasn't a firmware problem.  So far I have not seen any comment by anyone at D-Link saying, "there is a problem with the firmware.".

[jason1722x]

So is it a design flaw with the chipset or something more? The DNS issue is just not with the Dir 655, other Dlink products suffer from the same issue. Explain if you can. MODS are welcome to add their 2 cents!

[mackworth]

So is it a design flaw with the chipset or something more? Explain if you can. MODS are welcome to add their 2 cents!

I have no idea.

There are a couple things we know:

This seems to happen to every hardware version but not every router
It started in 1.22B05 which "fixed" DNS relay
Its also happening on the DIR-825 only on 1.11+ (I have the original 825 running 1.01 no freezing)


If you read the read the Freezing thread, it sounded like no one at D-link had been able to reproduce this issue or admit that it was a firmware problem.  I am fairly confident this isn't a hardware problem.  I ran 1.11 on my DIR-655 for months without rebooting it with DNS relay turned on.  I upgraded to 1.21 for shareport but didn't end up using it.  I then experienced the DNS slowdown problem so I upgraded to 1.22B05 and had freezes that were only fixed by turning off DNS relay.  Same issue on 1.32.

[jason1722x]

I will bet the problems has to do with shareport and the programming involved to make it functional.
All in the name of marketing to keep up the competition. Nevermind if it works right just market it and they (us) will buy.
It's sad really because I bought my Dir 655 A2 with FW1.11, it was a router then. Not a NAS device or print server. I upgraded FW because of VOIP problem I had, I like Dlink created my own problem.

[davevt31]

Its hard to tell because everyone doesn't have the problem, nor are they all running the same configurations.  I have had an A2 since 10/2007 that has never had any issues.  I have run every beta firmware that has been put out.  I have DNS Relay checked and have not experienced any lockups.  I do NOT have shareport installed as I use the USB port to power a laptop cooler that I have sitting underneath the router to keep it cool.

[jason1722x]

Its hard to tell because everyone doesn't have the problem, nor are they all running the same configurations.  I have had an A2 since 10/2007 that has never had any issues.  I have run every beta firmware that has been put out.  I have DNS Relay checked and have not experienced any lockups.  I do NOT have shareport installed as I use the USB port to power a laptop cooler that I have sitting underneath the router to keep it cool.

maybe heat is the issue. The way it seems now if its partly cloudy and if it's Monday or Friday and if the temp is above 85 degrees and the wind is blowing out of the southwest then this issue will happen.

[mackworth]

maybe heat is the issue. The way it seems now if its partly cloudy and if it's Monday or Friday and if the temp is above 85 degrees and the wind is blowing out of the southwest then this issue will happen.

I highly doubt its a heat issue, considering I bought my router in July of 08 and I didn't have 1 freeze during the hottest parts of the summer.  I also highly doubt that a firmware upgrade could cause the router to "go over the edge" as if the router was teetering on the edge of heat related stability.

Its clearly environment related, network environment and use environment, not physical.

[abjurian]

I disabled the DNS relay. but now for some reason we have not gotten disconnected but now I am so slow it is unbelievable.  what the heck!  AHHHHHHHHHHHHHHHHHHHHHHH.