[Libtorrent-devel] Port range vs. just one port

Charles Clark cmc at stegosaur.us
Mon Mar 12 22:28:24 UTC 2007

Michael Alger <libtorrent at mm.quex.org> wrote:
| On Mon, Mar 12, 2007 at 02:35:41PM +0300, Evgeniy Karyakin wrote:
| >
| > That way you won't let incoming connections to be made. You'll be
| > able to download files and upload it back to peers that *you* have
| > connected to, but others won't be able to connect to you. It's a
| > little bit unfair.
| > Or am I getting it wrong?

Incoming connections being made or rejected is dependant on
firewall settings, not port ranges. To be "connectable" the port
or port range allowed by your firewall for incoming connections
must match what you set for the rtorrent port range. If your
firewall does NAT, then it must redirect incoming connections
for that port or port range to the correct internal IP as well.

| A larger port range increases the chances that rtorrent will find an
| unbound port it can use. This can be useful if you have several
| programs using the same port range for inbound connections.

Note that this includes if you ever run multiple copies of
rtorrent using the same port settings; a port range of only one
in that case would be bad. If you only ever run one rtorrent,
and you want to list only one port for incoming access/redirect
in your firewall/NAT router (perhaps it is easy to list
individual port numbers but not ranges), a port range of only
one would be the way to go.

Charles Clark | cmc at stegosaur.us

More information about the Libtorrent-devel mailing list