Deluge Forum

I have been happily using Deluge for well over a year.

Now, my ISP appears to have made some changes to their configuration last week, with the result that I experience horrendous delays when browsing while Deluge is running - I have seen ping reporting 90%+ packet loss. What I believe has happened (trying to get confirmation from my ISP is like the proverbial blood/stone) is that they have severely limited the maximum number of concurrent sessions.

I have attempted to reduce the number of connections in the Deluge Preferences. having now set Maximum Connections, under Global Bandwidth Usage, to 10.

However, when I look at the Active Sessions Table on my router, it is showing 100+ sessions on the server IP, port 63655 (the port currently Active. according to the Deluge Preferences dialogue), and browsing performance is still appalling. It appears, to me, that the Maximum Connections is not working.

Likewise, I have a proxy configured for Deluge, yet all the sessions show different remote peer IPs - I would have expected all of these to be the IP of the proxy host ... am I mistaken?

I am running deluge 1.3.11 (libtorrent 0.16.17.0) on my ArchLinux desktop, and deluge 1.3.10 in an Ubuntu docker on my Slackware server.

Can anyone suggest what is going wrong here?

BTW, changing ISP isn't really an option - my choices here, in a remote corner of Philippines, is very limited.

Just to say that changing the Peer TOS byte from 8 to 0 seems to have improved matters somewhat (Maybe that should have been obvious?), but I've also disabled all Network Extras temporarily.

I'll see how it goes.

Edit:

Okay, after a while, the active sessions dropped to 15. I then re-enabled DHT and, within seconds, the number of active connections had shot up to 200 - the per machine limit I have set on my router. I turned DHT off again and, after a further delay of several minutes, the sessions had dropped back down.

I then enabled Peer Exchange and there was no noticeable jump in the number of active sessions.

My conclusion, therefore, is that the number of active sessions opened by DHT is uncontrolled and I will have to leave that turned off, relying on Peer Exchange to promulgate the details of active peers.

Hopefully I will not now find myself being further constrained by the limitations imposed by my ISP.

Further, I hope that my post will help anyone else who finds themselves in a similar position.