Low upload speed

[gfurst]

Hey folks, hello to you all and thanks for the developers of this wonderful advanced torrent application.

I guess I'm having a issue, since my upload speed is way lower than what it used to be with Transmission.
I've tried searching about this, and normally it would point to outdated libtorrent package and accompanied with lower download speeds, which is not my case.
Normally download will be pretty fast as 50% of the available bandwidth to 90%, uploads would be below 10%, but about 25% after tweaking some settings, with other client it could peak at 98% most of the time.
Just for reference, my download and upload bandwidth is 3 megabits, which gives about 360 kb/s, I limit it to 320kb/s up and down just to avoid clogging by the ISP.
Peer limit to 150 overall and 15 per torrent,I usually open a single port for torrent, but I don't think deluge uses it. By the way, whats the difference of outgoing and incoming ports? Active port always shows something different from what I've set.
Without proper explanation on specific options I don't really know what I'm doing, or if its best, such as "half-open connections", "rate limit IP overhead", "ignore limits on localnetwork".

Thanks, so what could I try?
I'm on Debian testing by the way.

[gfurst]

Package version, just in case:

Code: Select all

deluged               1.3.3-2+nmu1                              
libtorrent-rasterbar7               0.16.11-2  
python-libtorrent               0.16.11-2  

[odinian]

Make sure you have ports forwarded on your router for the incoming ports.

[gfurst]

Make sure you have ports forwarded on your router for the incoming ports.

Not trying to be mean or anything but, if you had read the thread you would know I did open ports.

But still just in case... here is how I did it:
One port only both for incoming and outgoing connections, didn't forward more cause its not easy not forward a range of ports in my router. Outgoing and incoming are the same because honestly I don't know whats the difference and how it could affect it.

Observing different clients, transfer speed and peer connection. I've concluded that others are able to connect and mantain for more time, allowing greater upload speeds. Something that Deluge roughly keeps 1 or 2 peers, rarely some peers are able to maintain and increase speed. There for I can conclude that the low speed is due to a unstable incomingo connection issue.

It would be great to hear about ANYTHING from the devs or moderators on the forum...

[Cas]

Leave the outgoing ports as random and set a range of incoming ports (~5). You should really be using the latest version of deluge.

[gfurst]

Leave the outgoing ports as random and set a range of incoming ports (~5). You should really be using the latest version of deluge.

Thanks, finally someone from the project who gives a peep.
Well, I'm using current Debian testing version. Just checked and its a couple of years behind on the release cycles, maybe something buggy with recent versions?
As I suspected "incoming" are outside peers trying to download from me, right? I'll be trying that and will report results.

[gfurst]

Hey its seems this improved peer connectivity a lot, can you explain why?

I've opened 10 ports which was easy to do in another router. Now I'm back at home and using a different router "nano station lovo M5" which is my ISP choice.
Problem is it doesn't seem to be able to open a range of ports properly:

Code: Select all

46197 2486K DNAT       tcp  --  ppp+   *       0.0.0.0/0            0.0.0.0/0           tcp dpts:21230:21239 to:192.168.1.3:21230-21239 
58727 5992K DNAT       udp  --  ppp+   *       0.0.0.0/0            0.0.0.0/0           udp dpts:21230:21239 to:192.168.1.3:21230-21239 

incoming ports from 21230:21239 forward to ip:21230-21239 the issue is with the dash part, known problem that forwards everything to 21230.
I would need to create a single rule for every port. Which I will do and test it out.

But can you explain why is that and the recommended peers/ port setting? Just saying this is something not reported in the faq and that others clients normally doesn't need.