
- #DELUGE CLIENT KEEPS SEEDING EVEN WHEN UPLOAD IS SET TO 0 INSTALL#
- #DELUGE CLIENT KEEPS SEEDING EVEN WHEN UPLOAD IS SET TO 0 TORRENT#
# iptables -t raw -I OUTPUT -p tcp -sport 56881:57200 -j NOTRACK # iptables -t raw -I PREROUTING -p tcp -dport 56881:57200 -j NOTRACK # iptables -t raw -I OUTPUT -p udp -sport 56881:57200 -j NOTRACK # iptables -t raw -I PREROUTING -p udp -dport 56881:57200 -j NOTRACK Then issue the following commands (after substituting the relevant port ranges): Note: Limiting incoming connections is not recommended with libtorrent as this will limit the ability to keep multiple connections to the same client, even for different torrents. To fully turn off connection tracking for torrents, specify ports for both Incoming and Outgoing traffic in Deluge, for instance, 56881-56889 for incoming connections and 56890-57200 for outgoing connections.
#DELUGE CLIENT KEEPS SEEDING EVEN WHEN UPLOAD IS SET TO 0 TORRENT#
For this reason, it may be necessary to disable connection tracking of all torrent traffic for optimal performance, even with the listening ports set to ACCEPT (as the causes for dropping INVALID packets, for instance conntrack's memory problems, may supercede any rules to accept traffic to/from those ports). Symptoms of this problem include torrents not seeding, especially when the torrent client has been active for more than a day or two continuously, and consistently low overhead traffic (in one experience, less than 3KiB/s in either in or out) with DHT enabled, even when deluge/libtorrent has been continuously running for more than forty-eight hours and many torrents are active. On many default configurations, when using iptables with connection tracking (conntrack) set to drop "INVALID" packets, sometimes a great deal of legitimate torrent traffic (especially DHT traffic) is dropped as "invalid." This is typically caused by either conntrack's memory restrictions, or from long periods between packets among peers (see and ). Note: One can limit this to a single port, just be sure to enable both TCP and UDP. # chown -R deluge:deluge /mnt/torrent_data


The client can disconnect but the daemon continues to run transferring the torrent files in the queue.

The server is referred to as the daemon and runs in the background waiting for a client (console, gtk, or web-based) to connect.

#DELUGE CLIENT KEEPS SEEDING EVEN WHEN UPLOAD IS SET TO 0 INSTALL#
Be sure to read and install the optional dependencies for the gtk client deluge-gtk to enable desktop notifications and appindicator notifications.ĭeluge works with a client/server model. Install deluge and optionally install deluge-gtk.
