Opened 10 years ago

Closed 10 years ago

#4293 closed Enhancement (invalid)

Choose incoming & outgoing port ranges

Reported by: tipper Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version:
Severity: Normal Keywords: patch-needed
Cc:

Description

Please add option to choose incoming & outgoing ports. (See image attached.)

Attachments (2)

example.png (98.0 KB) - added by tipper 10 years ago.
Incoming & Outgoing port selection
example2.png (80.3 KB) - added by tipper 10 years ago.

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by tipper

Incoming & Outgoing port selection

Changed 10 years ago by tipper

comment:1 Changed 10 years ago by tipper

  • Summary changed from Choose incoming & outgoing ports to Choose incoming & outgoing port ranges

comment:2 follow-up: Changed 10 years ago by jordan

"qBittorrent and Deluge do it" is not really a compelling reason -- Transmission is intentionally a more lightweight client than either of those two.

What is the common use case for such a feature?

comment:3 in reply to: ↑ 2 Changed 10 years ago by tipper

Replying to jordan:

"qBittorrent and Deluge do it" is not really a compelling reason -- Transmission is intentionally a more lightweight client than either of those two.

uTorrent also has it. It seems Transmission is the only one of the major torrent programs that does not offer such feature ?

Both qBittorrent and Deluge use Python. Therefore, they use far more resources than Transmission which is programmed in C. Including a user-defined port ranges feature will not be noticeable performance-wise since ports must be opened anyway whether the user specifies them or Transmission does so automatically.

What is the common use case for such a feature?

Torrent programs open a port for each download/upload client they transfer data with. Transmission selects a port automatically while other torrent programs allow manual selection. Allowing manual port selection would help with users that need to restrict traffic to certain ports. Also, it would make it easier to configure a firewall since the user would know which outgoing/incoming port ranges to open/close/restrict in iptables for example.

If this feature would be useless, none of the major torrent programs would have it.

comment:4 Changed 10 years ago by Username

Typical example is when network is partially restricted by firewall or NATed and only some ports range allowed or forwarded.

As for me I find it quite bad idea if networking app can't cope with various networking configurations. Transmission is extremely dumb when it comes to networking settings compared to virtually any other popular torrent client.

There is no even option to use separate TCP and UDP ports! As for me, networking configuration is not a good place to save on code size. Because lack of required features leads to inability to use Transmission at all. Then, if you can't use it, you have to resort to more bloated clients anyway. And say, uTorrent provides tons of networking options without being bloated. Nice example on how to write a good torrent client. It's popular because it both light-weight, featured yet remains simple to use. Even dozens of non-geeky persons able to use it.

comment:5 Changed 10 years ago by jordan

  • Keywords patch-needed added
  • Resolution set to invalid
  • Status changed from new to closed

I'm not going to add this feature, but if someone feels strongly about it and wants to write a patch for it, please attach the patch to this ticket and reopen the ticket.

Note: See TracTickets for help on using tickets.