#2121: Rework Deluge towards static incoming port
-----------------------------+----------------------------------------------
Reporter: bmnot | Owner:
Type: feature-request | Status: new
Priority: major | Milestone: 1.4.0
Component: core | Version: other (please specify)
Keywords: |
-----------------------------+----------------------------------------------
This will sadly require libtorrent 0.16 in order to work (because that
release adds port-reusing and forced ports
http://code.google.com/p/libtorrent/issues/detail?id=305), but it would be
a MAJOR improvement to Deluge, for multiple reasons:
* A static port is best for DHT, because old clients will be lookng for
you at your last-known IP and port, which is why clients like uTorrent
have a single port setting.
* Your router will be getting requests to old ports and will fill its logs
with "UDP blocked" messages, similar to a Denial of Service attack, which
can actually crash lower specced routers.
Once Deluge works well with libtorrent 0.16, it really would be worth
looking into defaulting to a single, static port, randomly selected on
config file generation.
Requesting a single port is easy in 0.16; see the libtorrent bug tracker
link above. You just pass in two flags to tell it to re-use the port even
if it's in TIME_WAIT state (the state just before it is freed by the
system) and to disallow the system from choosing another port at random.
It'll also require a small check that says "the only port we wanted is in
use? okay, don't start the daemon, instead log a fatal error"
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2121>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
