rTorrent don't start downloading (Solved)

Moeboy · 2015-09-20 02:28:18

Well, i'm pretty new in the archlinux distribution, so don't know much.
Here is my problem, when i press Ctrl+s nothing happen. I've configure the .rc like the wiki say.
Check the file to tell me where i'm wrong.

# 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 = 10
max_peers_seed = 50

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

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

# Default directory to save the downloaded torrents.
directory = /home/l/Telechargements/Rtorrent/Dl

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

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/home/l/Telechargements/Rtorrent/Tracker/*.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 = 49164-49164

# 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,prefer_plaintext

# 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 = on

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

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

I also show you the rules of iptables, don't know if it can help. (not sure if it's a good idea ^^)

# Generated by iptables-save v1.4.21 on Thu Sep 17 20:08:48 2015
*filter
:INPUT DROP [885:204774]
:FORWARD DROP [0:0]
:OUTPUT DROP [0:0]
-A INPUT -s 192.168.0.0/24 -p icmp -j ACCEPT
-A INPUT -s 192.168.1.3/32 -i eno1 -p tcp -m tcp --sport 22 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m multiport --sports 80,443,8000,49164 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -m conntrack --ctstate NEW,RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -p icmp -j ACCEPT
-A OUTPUT -d 192.168.1.3/32 -o eno1 -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW,RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -p tcp -m multiport --dports 80,443,8000,49164 -m conntrack --ctstate NEW,RELATED,ESTABLISHED -j ACCEPT
COMMIT
# Completed on Thu Sep 17 20:08:48 2015

I can't be more accurate cause i don't know where the problem come from, thanks for your time and more thanks if you answer me !
Also I don't think the problem come from the rooter, have another computer with fedora on it and transmission works well.

Last edited by Moeboy (2015-09-20 16:33:36)

ssfdust · 2015-09-20 10:52:59

I don't know if it is a good idea...why not try qbittorrrent.
In my memory, rTorrent performs terribly..

Slithery · 2015-09-20 13:51:25

Is your torrent appearing in rtorrent and just not starting, or not appearing at all?

Where did you get your firewall rules from, because I'm pretty sure they're not doing what you think they are.
There is no rule that is allowing requests either to or from your machine for torrent traffic.

ssfdust wrote:

...rTorrent performs terribly...

I'm not sure where you get this from, I have hundreds of torrents running at the same time and can always use all my bandwidth if the torrent allows.
It's also the only client I've found that doesn't crash with torrents containing >500000 files.

Last edited by Slithery (2015-09-20 14:42:22)

Moeboy · 2015-09-20 14:45:31

Yes torrents appears and i can select them, but only Ctrl+d work. My iptables rules are mostly coming from the wiki en and fr, maybe i'm wrong but if you look at it, you will see the 49164 port on the tcp output and input. Another way to do this ?

Slithery · 2015-09-20 14:59:11

Moeboy wrote:

...maybe i'm wrong...

Yes, you are.

For downloading torrents you need a rule allowing traffic from your machine to any destination port - as you don't know what ports the clients you're connecting to are going to be using - as well as allowing any related traffic back in.

For uploading you need to allow traffic in to your machine with a destination port of 49164 - not a source port as in your rules - as well as allowing related traffic back out.

Do you really need a firewall running in the first place? If your behind a router and have no unnecessary services running then it really isn't needed IMHO.

PS - Welcome to the forums Moeboy just realised this was your first post.

Last edited by Slithery (2015-09-20 15:01:19)

Moeboy · 2015-09-20 15:46:18

Ok thanks, indeed the problem was coming from the iptables rules, so for now i'll just disable it.
Not really the right place to ask this but can you tell me where can i find information about iptables rules configuration for torrents ?

Thank you again slithery, hope one day i'll return the favor

Last edited by Moeboy (2015-09-20 15:47:03)

Slithery · 2015-09-20 16:26:05

Moeboy wrote:

Not really the right place to ask this but can you tell me where can i find information about iptables rules configuration for torrents ?

I've pretty much covered it all above. The only other rule you need is to allow you to contact the tracker but this usually happens over http(s) so should be covered by your web browsing rule anyway.

Edit - Don't forget to mark this topic as solved.

Last edited by Slithery (2015-09-20 16:30:13)

Arch Linux

#1 2015-09-20 02:28:18

rTorrent don't start downloading (Solved)

#2 2015-09-20 10:52:59

Re: rTorrent don't start downloading (Solved)

#3 2015-09-20 13:51:25

Re: rTorrent don't start downloading (Solved)

#4 2015-09-20 14:45:31

Re: rTorrent don't start downloading (Solved)

#5 2015-09-20 14:59:11

Re: rTorrent don't start downloading (Solved)

#6 2015-09-20 15:46:18

Re: rTorrent don't start downloading (Solved)

#7 2015-09-20 16:26:05

Re: rTorrent don't start downloading (Solved)

Board footer