D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: binaryhat on November 06, 2009, 07:45:46 PM
-
My DIR-655 is randomly dropping my DSL connection. Yes, I have infamous 1.32NA firmware. Any suggestions?
-
1) What kind of connections
2) How do you know
3) Please confirm the router is or isn't actually rebooting itself
4) Are you talking about wireless only?
-
1) 2 wired, 2 wireless
2) My connection dropped at 1:45am, 1233pm, 410pm today so far. Happens everyday.
3) How do I confirm?
4) Wired and wireless are effected.
Disabling DNS Relay does not help.
Running Bittorrent be causing this? client: azureus on linux
-
It appears that bittorrent is crashing my router. Any suggestions?
-
When I'm on the final 1.32 or the latest 1.32 beta, which was released later than the final, for torrents, I do these:
- Uncheck Enable HTTPS Server http://support.dlink.com/Emulators/dir655/132NA/Admin.html
- Uncheck Enable UPnP http://support.dlink.com/Emulators/dir655/132NA/Network.html and use Port Forwarding to forward ports.
- Uncheck Enable DNS Relay http://support.dlink.com/Emulators/dir655/132NA/Basic_Network.html
- Set My plug of USB type is: WCN Configuration http://support.dlink.com/Emulators/dir655/132NA/USB.html . This is to disable Shareport.
It has been going for weeks stably after I did these settings.
-
When I'm on the final 1.32 or the latest 1.32 beta, which was released later than the final, for torrents, I do these:
- Uncheck Enable HTTPS Server http://support.dlink.com/Emulators/dir655/132NA/Admin.html
- Uncheck Enable UPnP http://support.dlink.com/Emulators/dir655/132NA/Network.html and use Port Forwarding to forward ports.
- Uncheck Enable DNS Relay http://support.dlink.com/Emulators/dir655/132NA/Basic_Network.html
- Set My plug of USB type is: WCN Configuration http://support.dlink.com/Emulators/dir655/132NA/USB.html . This is to disable Shareport.
It has been going for weeks stably after I did these settings.
Torrents work fine for me without doing any of this and my router has been up for months.
-
Sign, ok it works fine for you but it does not for him, so at least he needs some straws, ain't he? If my configuration works for him, that's good, isn't it? In that sense, your post is completely uninformative.
@OP: you don't need to do all of it, but you can try one by one until you get a configuration that works for u.
-
Bittorrent is still crashing my router/connection even with the suggested changes. I did not disable DNS Relay because I can't connect to the net.
-
Bittorrent is still crashing my router/connection even with the suggested changes. I did not disable DNS Relay because I can't connect to the net.
Every router will collapse when having too much incoming and outgoing connections, you cannot imagine how much overhead they cause. So you might want to try cutting down on those in your BT client config.
-
After disabling DNS Relay you need to open the run command dialog box, type in cmd then enter. If you have administrator rights, you should be able to do "ipconfig /release" and "ipconfig /renew" commands (without quotes) and you can access the net then.
And as EddieZ said, you need to setup your client right, too. If the settings are too much it will overload the router in any case.
-
You need to disable dns relay! I had the same problem and after disabling it, haven't had a single drop in connection in over a month. Before it was multiple times per week.
-
Same here, my router has been up for 34 days without a reboot/disconnect.
Definitely disable DNS relay and then run the ipconfig /renew command on each of your workstations.
-
You don't really need it anyway...
-
disabling dns relay worked for me so far. I was getting pissed until I disabled it.
-
The router IS working for many people, obviously the majority of the people posting about it have some sort of issue or optimization they're looking for. I've been through many firmware incarnations, some MUCH better than others (I hated the captcha 'feature'- it killed me!), for me 1.32NA Rev3 hardware has been pretty solid and I'd recommend it to others.
So I don't believe suing D-Link would be worth the time or effort, nor accomplish much, other than hurt or annoy the company that you should be supporting if you want their products to work the best they can. In my mind, D-Link continues to show willingness to swap hardware in order to revert to older firmware, even provide unreleased firmwares in some cases, and continue to develop new firmwares and strongly support their product, much better than many tech companies.
If you need to sue, then so be it, but the DIR-655 IS NOT bunk for everyone. I actually love it, and own 5 Mac's and decided to keep the DIR-655 over the Airport Base Station Extreme. I like all the customizations and its flying fast and has great uptime. I've gone weeks without a single reboot, I don't use the Shareport feature (so I can't comment on that, and you could have a serious flawed feature, but minus that, the router itself and its basic functionality has continued to impress me.
I noticed that it helps to have it mounted vertically, with good airflow over the vents on the side (bottom), put it at the top of a tall IKEA bookshelf and wireless N is 100% throughout most of the top floor and 90% or greater downstairs. I havent regretted this purchase once, and it KILLS all the past Linksys routers I've owned. I sometimes wonder if the hardware version or the hardware itself is flawed or flaky and that's why some people have issues. Or more likely, some people just use configurations that stray from the norm or constantly stress the router out pushing it to its limits, I dunno, but I dont get all the hate on this model.
Game on...
-
Disabling DNS Relay fixed it. Thanks!
-
Every router will collapse when having too much incoming and outgoing connections, you cannot imagine how much overhead they cause. So you might want to try cutting down on those in your BT client config.
My issue i have found is that the trackers pass hundreds of new connections my way every few minutes. I limit my upload to 3-5 clients per torrent. checking the logs I see the trackers passing me tens of thousands of new connection attempts even when those 3-5 are full a day.
i think it is a problem with the logic of torrents that the trackers do not know your limits you've set.
My logs on the DIR655 fill up within the hour usually. I gave up on having it send me the logs as the amount of torrent connection failures in them is astounding and makes them useless.
-
My issue i have found is that the trackers pass hundreds of new connections my way every few minutes. I limit my upload to 3-5 clients per torrent. checking the logs I see the trackers passing me tens of thousands of new connection attempts even when those 3-5 are full a day.
i think it is a problem with the logic of torrents that the trackers do not know your limits you've set.
My logs on the DIR655 fill up within the hour usually. I gave up on having it send me the logs as the amount of torrent connection failures in them is astounding and makes them useless.
It's none of the routers business if utorrent is going to accept or reject a packet. This is a design flaw, and it shouldn't be rejecting anything on the behalf of your torrent client.
Anyways, your thousands of connections probably have more to do with DHT or PXE. They are known to cause a LOT of connections. (which, I believe, dont actually obey the connection limits but dont quote me).
And, to the OP -- I've had similar problems with more than one dlink router, and most recently I've found that you don't actually have to disable UPNP on the router (which is going to cause you headaches with other software, like MSN messenger for example), you just have to turn off UPNP use in your torrent client. And/or you may also have to turn down your connections through the torrent client as well.
-
The router only rejects packets go to unforwarded ports, so that's a normal behavior of a firewall/NAT router. If you want more relaxed operation mode, check this page (http://support.dlink.com/Emulators/dir655/132NA/Firewall.html) on your router and select Endpoint Independent for both TCP and UDP. DHT and PEX use UDP which doesn't get counted as connection by the client. This is by design. You can only control the rate your client send out these packets in some clients.
-
And, to the OP -- I've had similar problems with more than one dlink router, and most recently I've found that you don't actually have to disable UPNP on the router (which is going to cause you headaches with other software, like MSN messenger for example), you just have to turn off UPNP use in your torrent client. And/or you may also have to turn down your connections through the torrent client as well.
µTorrent works fine for me with UPnP enabled in the client and router.
No slowdowns or issues of any kind.
-
The router does not deny anything on behalf of the torrent client. It just denies access/connections because of the firewall settings.
It does work fine here, the number of connections is set max to 200. I do believe also that the new torrent features disrespect this.