rtorrent is NOT connectable

georgedirac · 2015-12-15 18:12:49

Hello, I have a problem, I have been using transmission as a torrent client for a while but recently switched to rtorrent, I am not using any interface with it, I just launch it via terminal.

When I was using transmission, everything was fine, but since I switched to rtorrent, I am not set as connectable on some sites.

Here's .rtorrent.rc content:

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.

# Maximum and minimum number of peers to connect to per torrent.
min_peers = 40
max_peers = 100

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = -1
max_peers_seed = -1

# Maximum number of simultanious uploads per torrent.
max_uploads = 4

# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# Default directory to save the downloaded torrents.
directory = ~/Downloads/temp_torrent_downloads

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = ~/.rtorrent.session

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=~/Downloads/temp_torrent_downloads/.torrents/*.torrent
#schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low.
#schedule = low_diskspace,5,60,close_low_diskspace=100M

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 60125-64125

# Start opening ports at a random position within the port range.
port_random = yes

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
check_hash = yes

# Set whether the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,try_outgoing,enable_retry

# Enable DHT support for trackerless torrents or when all trackers are down.
# May be set to "disable" (completely disable DHT), "off" (do not start DHT),
# "auto" (start and stop DHT as needed), or "on" (start DHT immediately).
# The default is "off". For DHT to work, a session directory must be defined.
# 
dht = auto

# UDP port to use for DHT. 
# 
dht_port = 63425

# Enable peer exchange (for torrents not marked private)
#
peer_exchange = yes

Slithery · 2015-12-15 18:22:51

Have you forwarded the relevant ports to your machine?

Torrent clients such as transmission usually use uPnP to automatically request the router to forward ports. Rtorrent doesn't do this so you will need to configure your router manually.

It doesn't really matter if you do this though, theoretically it will limit your uploading as other clients can't connect to you but I still manage to saturate my upload without it.

Last edited by Slithery (2015-12-15 18:25:16)

georgedirac · 2015-12-15 18:33:38

slithery wrote:

Have you forwarded the relevant ports to your machine?
Torrent clients such as transmission usually use uPnP to automatically request the router to forward ports. Rtorrent doesn't do this so you will need to configure your router manually.
It doesn't really matter if you do this though, theoretically it will limit your uploading as other clients can't connect to you but I still manage to saturate my upload without it.

Hey, thanks for reply. Is there any way to make rtorrent automatically request the router to forward ports, like transmission?

Slithery · 2015-12-15 18:46:04

Nope, afraid not.

Arch Linux

#1 2015-12-15 18:12:49

rtorrent is NOT connectable

#2 2015-12-15 18:22:51

Re: rtorrent is NOT connectable

#3 2015-12-15 18:33:38

Re: rtorrent is NOT connectable

#4 2015-12-15 18:46:04

Re: rtorrent is NOT connectable

Board footer