Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#2826 closed Enhancement (invalid)

Automatically randomize port at specified intervals to bypass traffic shaping

Reported by: alanfleming Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.82+
Severity: Normal Keywords:
Cc:

Description

Many ISPs are using traffic shaping to limit BitTorrent? traffic. This is usually done in hardware, and takes some time to notice that Bt traffic is running on a certain port. Once it is noticed, traffic shaping restricts the port, usually by TCP resets.

If there was an ability to automatically randomize the port used at regular intervals (e.g. every 10, 20, 30, mins, a lower bound will also need to be set) the effects of such traffic shaping could be minimised.

Change History (4)

comment:1 Changed 12 years ago by livings124

  • Resolution set to invalid
  • Status changed from new to closed

Changing ports while running is already not recommended because of the nature of changing ports - this would most definitely cause more problems than it would solve.

comment:2 Changed 12 years ago by alanfleming

  • Resolution invalid deleted
  • Status changed from closed to reopened

That makes no sense at all. It's already allowed and enabled in the UI by pressing the "randomize" button. If it caused problems, it would cause problems either *both* manually or automatically, or *neither*.

Can you explain why, technically, from the app point of view *what* problems it could cause, so perhaps the ticket can be refined into something workable rather than rejected out of hand?

comment:3 Changed 12 years ago by livings124

  • Resolution set to invalid
  • Status changed from reopened to closed

It does cause problems manually, and that button should be used sparingly at best. Regardless, I don't see the demand enough for such a setting.

comment:4 Changed 12 years ago by User294

Imho, if someone really needs this, they can use transmission configured to use random port + cron (or whatever task scheduler they prefer) to do process restart. Or something like this. In general such behavior is a bad idea because:

  1. It takes some time to start things up and get them running at full speed, etc (so all peers are aware you're here, etc).[BR?
  2. This also about to flood P2P network with dead peers which is not a great idea.
Note: See TracTickets for help on using tickets.