Custom Query (2445 matches)


Show under each result:

Results (76 - 78 of 2445)

Ticket Resolution Summary Owner Reporter
#77 Invalid Connections to/from (ssh tunnel) are not affected by Speed Limit markybob dominik@…

I use ssh tunnel as SOCKS5 proxy for my tracker and peer connections. Incoming connections are coming from as this is the way the tunnel works. These connections are not affected by Speed Limit and this chokes my connection.

I request for option to include localhost into Speed Limit with a note that this applies for those using ssh-tunnel proxy.

#78 Duplicate High cpu usage with lots of peers markybob lacyc3@…

Deluge make lots of cpu usage, if the torrent file has much seeders and peers.

English translation: Források = Seeders; Partnerek = Peers

I made a screenshot:

Deluge run on Ubuntu 7.10

#79 Fixed Bind outgoing connections to local port andar peterdk

I am using QoS at home to manage my bittorrent traffic. Unfortunately not all trafic is caught with the L7 and IPP2P filters. Though it is possible to set incoming ports, it is not possible yet to define the outgoing port(s). QoS filtering is therefore not really possible, only if one would totally define all traffic except www traffic as "low" class.

A solution to this problem is to bind all the outgoing Deluge connections to a specified local port instead of just letting the OS randomly assigning a unique port for every single one.

Azureus has implemented this and this allows for a easy QoS rule that filters all traffic coming from the defined port. It is a ideal solution for home QoS filtering without having any effect on the QoS of ISP's, so possible encryption doesn't need to be turned off.

Someone from the Azureus channel explained how it could be done:

[17:55] <wereHamster> so I'd like to know how it's possible to initiate multiple connections from the same port :)
[17:58] <The_8472> tools -> options -> connections -> advanced network settings -> bind to port
[17:58] <wereHamster> I know, but how is it technically done, bind() fails if the port is already taken (EADDRINUSE
[17:59] <The_8472> use SO_REUSEADDR
[18:01] <wereHamster> This socket option tells the kernel that even if this port is busy (in the TIME_WAIT state), go ahead and reuse it anyway. If it is busy, but with another state, you will still get an address already in use
[18:02] <wereHamster> error.
[18:02] <The_8472> that only applies to the same socket pair
[18:03] <The_8472> if it's a different socket pair then it does what you want
[18:03] <wereHamster> ok, thanks

Since I am planning to move from Azureus to a more native Linux app, I would like to request that the option of forced binding to a local port be added to Deluge. I also submitted this feature request to Transmission and I hope this will help making Deluge too a better client.

Something from the Azureus wiki that maybe is good to know if this feature is added/developed:

  • Bind to local Port This sets outgoing connections to a fixed source port. This can be used with full cone NAT routers to reduce the number of NAT table entries and thus prevent crashes on some router models. When the outgoing port is bound to the same as the incoming port that might even solve NAT problems on full cone NAT routers.

Note: Binding to the same port as the incoming port works under Windows 2k and greater only. Unix users should use a different port. It's not working at all under Mac OS X.

Note: See TracQuery for help on using queries.