Print

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

[bigeyes0x0]

Performance so far.  However, the performance decline is so frustrating that I may not be giving it enough time to freeze completely.  This week I made it to 1 day 17 hours before performance was unacceptable, but it also was not at the very poor performance it typically reaches and I did not give it a chance to get very poor since I'm back on my routine of rebooting when performance begins to decline instead of waiting until it's practically unusable.

I need to describe this very carefully so it's properly understood.  I did not allow the performance to get as bad as it has when the router becomes inaccessible, and my reason is that because it progressed more slowly, I had to deal with poor performance for many days (rather than a quick downward spiral over a period of 12-36 hours and rebooting) and I eventually couldn't cope with it any longer.  Again, performance was well below normal, but it had not yet reached the 10% chance of having a webpage load as before; it was at about 50-60% chance of having a webpage load but I was dealing with having to refresh pages for many days and I couldn't bear dealing with it any longer since the performance problem obviously had not gone away.  If I had the patience to wait until what probably would have been 25 days of uptime (with 22 days of declining performance) until I reached that common 10% success rate, I would be able to check if the router had frozen...it's painfully frustrating to know how to restore performance so easily yet force myself to suffer through an awful internet experience.  I'm surprised I made it to day 10 instead of rebooting at day 3, when it first became problematic.

To reiterate, I did not have any performance or lockup problems with firmware 1.21 with DNS relay enabled and although disabling DNS relay appears to have helped, I believe that it's a partial fix for the symptom rather than a fix for the problem.  It still feels like a memory leak since I only made it to 1 day 17 hours this round despite DNS relay being disabled.

You may try disabling QoS entirely. If it works after that I recommend you to try some online speed testing of dslreport or speedtest for at different times in a day to figure out if the problem lies with unstable upstream speed. At least that was my problem with my unstable DSL line until I fixed it with my ISP.

[Krauser15]

I've had the worst problems ever with the DIR-655 after I upgraded from 1.11 (WAS PERFECT) to 1.31 - 1.32 - now with DNS Relay disabled and the IPs from the router revoked. It's running fine, but not as good as 1.11 stable, mediocre at best. Last time I dump any money into D-Link or recommend them to friends, family and any business associates. Unless they send me a working unit or they eventually fix the problem.

[bananaman]

Can you be more specific about what's not as good as 1.11, mediocre as best?

[rdubs]

So far so good! I have been looking for a cure to my problem now for over two weeks. I did not receive very good troubleshooting from dlink support over the phone. I have 3 wireless PC's and a hard wired desktop all running vista and a PS3. I could not go more then 5 minutes and it was done.

[Geeman]

I have been having a problem with Net-Flix. I can stream a movie for about 30-40 minutes then  suddenly the connection drops and I can no longer access any configure options.  Unfortunately disabling DNS relay did nothing to solve the problem.   

[Jon8RFC]

You may try disabling QoS entirely. If it works after that I recommend you to try some online speed testing of dslreport or speedtest for at different times in a day to figure out if the problem lies with unstable upstream speed. At least that was my problem with my unstable DSL line until I fixed it with my ISP.

No difference with QoS off.  I've also tried having SPI disabled.  My speeds, when tested, have been a reliable 30+ mbit down and 2mbit up for a couple of years since the ISP bumped up my service.

[rdubs]

***update so disabling DNS relay has decreased the amount of times it drops off. It does seem to be only when the hardwired computer is running I get this problem any Ideas?

[lucypotato]

My 655 would lock-up at least daily, but with  dns-relay disabled I've been up for almost three weeks.
What's interesting is that we don't seem to missing out on whatever dns-relay was providing. Perhaps, the first web page loads a little slower, but I could be imagining that.

[newtoncd]

DIR-655 A4 1.32NA.

Disabling DNS relay cured the lockups, but after a few days, I think I checked enable "advanced DNS service" and then unchecked it after the system locked up again. The enable DNS relay must have been automatically selected, because the router was routinely locking up again.  I disabled DNS relay and things are good again.  I hope they can fix this soon.

[Krauser15]

Can you be more specific about what's not as good as 1.11, mediocre as best?

Sure, for one, in 1.11 I was able to get an avg rate of 281Mbit's, when I upgraded to 1.32 it has a REALLY hard time getting past 170Mbit's. Nothing has changed except for the firmware. Two, N connections like to reset themselves every 3-4 hours at random. Three, router locks up every 24-36 hours - if it does not lock after 24 hours, then browsing the net is very slow until it locks up, or I power cycle it. Overall, browsing the web feels a little sluggish, DNS Relay off, for the obvious reasons.

[zwei]

I'm also having issues with my DIR-655 after upgrading to 1.32NA

Every couple days it things slow to a crawl or fail outright and I cannot access the router's config page to restart it so I have to pull the power. I will turn off the DNS Relay to see if that helps. (I'll have to manually configure OpenDNS into every machine on my network, which sucks.)

I sincerely hope this gets fixed soon. I went out on a limb and bought a premium router for a reason. Right now, I'm wishing I had my old DI-624 back... 

[Krauser15]

I sincerely hope this gets fixed soon. I went out on a limb and bought a premium router for a reason. Right now, I'm wishing I had my old DI-624 back... 

Unfortunately, this has been going on for over 4 months (for me anyways, longer for others), if a fix was coming, it would have came.

[pp1111]

same here, 1.32 is bad, a very bad step for me to upgrade from 1.11
My internet get slow to connect to every page after 24 hours.
Have to reset router.

[KevTech]

Not sure but it may help to know what hardware versions are having problems.

Myself, I have A3 and 1.32 is totally solid for me.

[tjberens]

Not sure but it may help to know what hardware versions are having problems.

Myself, I have A3 and 1.32 is totally solid for me.

A3 here also, but I had to disable DNS relay to get everything working properly.