Random port

[GanetMarV]

It will be great to have an option that, given a specific range, Transmission selects a random port every time it starts.

[livings124]

What are the benefits of randomization? The clear disadvantage is that this will make port forwarding more difficult for users (who work to get a port opened, and then have it closed next launch).

[GanetMarV]

For the benefits: Some Universities/ISPs are blocking ports like 6881-6889 because they are the default ports in bittorrent. But some ISPs are monitoring traffic and stats on the ports used for heavy up/down. By doing changing the port at every start, their stats are less informative and inconclusive for them. I agree on you regarding the port forwarding. If the forwarding is done by hand, this feature is pointless. It should not be the default. But for users that opens the ports using NAT-uPNP, it is completely transparent.

[livings124]

[7352] has this in libtransmission and the Mac client.

[livings124]

This is available in 1.50's libtransmission, but won't be implemented in the interfaces until 1.60.

[charles]

gtk: r8151

[Rolcol]

It is not displayed. Something like this needs to be added:

Index: gtk/tr-prefs.c
===================================================================
--- gtk/tr-prefs.c	(revision 8168)
+++ gtk/tr-prefs.c	(working copy)
@@ -1377,6 +1377,7 @@
 
     s = _( "Randomize the port every launch" );
     w = new_check_button( s, TR_PREFS_KEY_PEER_PORT_RANDOM_ON_START, core );
+    hig_workarea_add_wide_control( t, &row, w );
 
     s = _( "Use UPnP or NAT-PMP port _forwarding from my router" );
     w = new_check_button( s, TR_PREFS_KEY_PORT_FORWARDING, core );

The option itself is not saved though so it's uncheck if Transmission is closed and reopened.

[charles]

Fixed in r8170

[Rolcol]

It still does not save the setting on quit. It's unchecked when Transmission is closed and reopened.

[charles]

Re-fixed in r8172 ;)