Print

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

[cmk1198]

Hey guys, where should I start with this... I have the DIR-655 Rev. A4, currently running firmware 1.32NA (beta 2). I have an issue many of you have, my router after some random period of time, drops the internet connection on wired devices, but wireless devices still work fine. I also have an issue where the router will spontaneously reboot. This router was completely stable with the factory shipped firmware, I believe it was 1.11. I've tried all of the various workarounds and fixes on these boards, including: disabling DNS relay, setting wan interface to 10 Mb, disabling QoS and traffic shaping, lowering the radio power to medium, disabling WMM and even trying the useless 30-30-30 flash method. None of these things have really worked, other than the router reboot issue has gone from some minutes (in some cases), to a matter of hours.
                                                                                                                                                 
I've tried a couple of different wireless configurations as well... I've tried mixed B/G/N, mixed B/G, mixed G/N, N only and with different WPA/WPA2 settings, also tried the Short GI setting as well. What I'm getting at, is I've only found 1 configuration that really seems to help at all, and I'm REALLY not happy with what seems to be working. My current settings are: WMM disabled, DNS relay disabled, standard long GI, UPnP on, radio power on high, wireless G only, no encryption and hidden SSID. I have 4 devices using the router, 2 wireless and 2 wired.

At this point, I feel my only recourse is to contact customer support and request a replacement router.
In retrospect, there are 2 things I would have done differently... #1 would have been to not upgrade past 1.11, #2 would've been to stick with linksys products (or at least something capable of supporting DD-WRT).

[Demonized]

Sorry to see you having problems. One note: Why get a DIR655 when you compare to DD-WRT? It's not that hard to see that the feature set of DD-WRT is aimend at a completely different user group...

[cmk1198]

Well, there were a couple of things that made my mind up for the DIR-655... I wanted a wireless router that had a gigabit switch built in, needed to be wireless N, and of course be a reasonable price ($200+ USD isn't reasonable)... other than that, I pulled a few reviews of routers, looked up speed test comparisons, checked out user reviews and came to the conclusion that the DIR-655 would be my best bet. What I should have done, however, was to check compatibility with DD-WRT in case the D-Link firmware was buggy/insufficient (oops).  Thanks for the reply though Demonized, I've seen quite a few of your posts on these forums.

[Demonized]

No problem. Just being curious why somebody with knowledge/experience with DD-WRT would switch to a non-customized device.

[cabopablo]

I don't know that I have tried every single workaround you have, but I have done most of them.  I too was rock solid with my 1.21 firmware.  It might reboots once every month or so.  Since going to the 1.31NA release it drops the internet connection every other day at best.  At first it was every few minutes when I restored my 1.21 settings.  I ended up reflashing it to 1.31NA and then setting everything manually.  This was moderately better, except for the fact that now it will go not quite 2 days before it happens.

I actually go into the router admin interface and see that the connection time has started back at 0.  I also noticed today that my logs are resetting when this happens.  It is not keeping logs enough to see if there might be something there.  I do not have a syslog server to feed things to, but am about to check into setting one up.

DLink support basically told me to reset it to factory by holding the button in for 20-30 seconds... which I was already doing.  I do not know what to do about this.  My Vonage lines are dropping in the middle of my work day.  I am seriously considering a different router.

[Ice9]

Also having problems with 1.3X.

I'm currently using the Beta2 build of 1.32 - and while it seems to have fixed the auto-reboot problem in 1.31, all my wired devices still fall off the net after around a day and a half, like others have reported.

I was also rock solid at 1.21.

D-Link: I have to ask - if 1.21 (and 1.31 for that matter) is a firmware like any other, why make it so we can't backrev to it? Why make your customers suffer when we know we could go back to that rev and make all these nightmares go away?

It just doesn't make any sense to me - and it's situations like this that make even the most technologically savvy people doubt those who are supposed to be smarter than they are themselves!

[davevt31]

Also having problems with 1.3X.

I'm currently using the Beta2 build of 1.32 - and while it seems to have fixed the auto-reboot problem in 1.31, all my wired devices still fall off the net after around a day and a half, like others have reported.

I was also rock solid at 1.21.

D-Link: I have to ask - if 1.21 (and 1.31 for that matter) is a firmware like any other, why make it so we can't backrev to it? Why make your customers suffer when we know we could go back to that rev and make all these nightmares go away?

It just doesn't make any sense to me - and it's situations like this that make even the most technologically savvy people doubt those who are supposed to be smarter than they are themselves!

The not being able to go back has been explained in some different threads.  If I remember right it has to do with the new SDK and the way it rewrites the base code stuff.

[Demonized]

correct. Ubicom Kernel update in the 1.3x firmware which is locked.

[Ice9]

That's profoundly awful.

I don't know what the heck went wrong with this horrible slew of firmwares - and while I primarily blame myself for upgrading to this nightmare, I blame d-link for not giving us any recourse.

I somehow doubt that these problems are somehow worth the effort - whatever the effort may be.

[davevt31]

That's profoundly awful.

I don't know what the heck went wrong with this horrible slew of firmwares - and while I primarily blame myself for upgrading to this nightmare, I blame d-link for not giving us any recourse.

I somehow doubt that these problems are somehow worth the effort - whatever the effort may be.

When the router first came out, everyone (well, not everyone...) was upset that they couldn't use the USB port for anything but Windows Connect Now (WCN).  They all wanted to be able to attach things to the USB (Printers, hardrives) so DLink broke down and made this function available.  Then came other features.  As with anything, when you add stuff there are more things that can go wrong.  Also how much of the blame should be pointed to Ubicom, its their SDK that is used to build the firmware and their chipset.

[cmk1198]

Also having problems with 1.3X.

I'm currently using the Beta2 build of 1.32 - and while it seems to have fixed the auto-reboot problem in 1.31, all my wired devices still fall off the net after around a day and a half, like others have reported.

I was also rock solid at 1.21.

D-Link: I have to ask - if 1.21 (and 1.31 for that matter) is a firmware like any other, why make it so we can't backrev to it? Why make your customers suffer when we know we could go back to that rev and make all these nightmares go away?

It just doesn't make any sense to me - and it's situations like this that make even the most technologically savvy people doubt those who are supposed to be smarter than they are themselves!

I got a little tired of the issues I was having, I went back and reset the router and re-flashed the firmware. I have an uptime of 2 days 1 hour with DNS relay disabled and wireless N only. This seems to be working well, so far... but this may not be an option for everybody.

[Ice9]

I got a little tired of the issues I was having, I went back and reset the router and re-flashed the firmware. I have an uptime of 2 days 1 hour with DNS relay disabled and wireless N only. This seems to be working well, so far... but this may not be an option for everybody.

Certainly isn't for me - 95% of my network is wired... I run a busy gaming network off my two DIR655's (www.trashedgamers.com). These routers worked SWIMMINGLY until this 1.31 business came about. Now, they need to be reset every day and a half.

So - dlink doesn't have enough leverage with whoever made their firmware SDK to make a backrev possible? I find that incredibly hard to believe.

[Demonized]

Certainly isn't for me - 95% of my network is wired... I run a busy gaming network off my two DIR655's (www.trashedgamers.com). These routers worked SWIMMINGLY until this 1.31 business came about. Now, they need to be reset every day and a half.

So - dlink doesn't have enough leverage with whoever made their firmware SDK to make a backrev possible? I find that incredibly hard to believe.

The kernel update & locking is not something that's easily corrected. It's not about leverage, that's for sure. It's of a technical nature, that's for sure.

[timandjulz]

No problem. Just being curious why somebody with knowledge/experience with DD-WRT would switch to a non-customized device.

Hey Demonized... I thought I would chime in here too.

I had been running openwrt for three years on different devices.  I switched to a dlink DIR-655 because I wanted gigabit speed.  I rarely use the wireless feature.

 I have found the stability of my DIR-655 to be poor after I upgraded from the pre-installed firmware.  I am hoping D-Link fixes the firmware soon.

[Johnnyboy!]

I had been running openwrt for three years on different devices.  I switched to a dlink DIR-655 because I wanted gigabit speed.  I rarely use the wireless feature.

I bet you're wishing that you kept your OpenWRT router running and just bought an 8-port Gigabit switch for $60 instead.

:-)

jB