Print

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

[binaryhat]

Disabling DNS Relay fixed it.  Thanks!

[Arvald]

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.

[bluenote]

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.

[bigeyes0x0]

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 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.

[KevTech]

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.

[EddieZ]

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.