Skip to content

transmission_daemon.md #2113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 12, 2024
Merged

transmission_daemon.md #2113

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions docs/guides/file_sharing/transmission_daemon.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,23 @@
---
title: Transmission BitTorrent Seedbox
author: Neel Chauhan
contributors: Steven Spencer
contributors: Steven Spencer, Ganna Zhyrnova
tested_with: 9.4
tags:
- file transfer
---

## Introduction

BitTorrent needs no introduction at this point but if you are unaware, BitTorrent is a peer-to-peer file sharing protocol. BitTorrent relies on multiple peers seeding (uploading) the requested file to you but you also back to future downloaders.
BitTorrent needs no introduction, but if you are unaware, BitTorrent is a peer-to-peer file-sharing protocol. BitTorrent relies on multiple peers seeding (uploading) the requested file to you, but you are also back to future downloaders.

Transmission is an popular open source BitTorrent client with multiple frontends and backends. Here you will be installing the headless "daemon" backend.
Transmission is a popular open-source BitTorrent client with multiple frontends and backends. Here, you will install the headless "daemon" backend.

In today's mobile-centric world, it makes more sense to run Transmission as a headless server than directly on a laptop or a desktop. This way you can seed files 24/7 while not consuming battery life on a mobile device if used for downloading.
In today's mobile-centric world, it makes more sense to run Transmission as a headless server than directly on a laptop or a desktop. This way, you can seed files 24/7 while a mobile device's battery life is not consumed when downloading.

## Installation

To install Transmission you first need to install EPEL:
To install Transmission, you first need to install EPEL:

```bash
dnf install -y epel-release
Expand All @@ -31,14 +31,14 @@ dnf install -y transmission

## First setup

Unlike most Linux daemons Transmission sets up the configuration upon first startup, so start and stop Transmission with:
Unlike most Linux daemons, Transmission sets up the configuration upon first startup, so start and stop Transmission with:

```bash
systemctl start transmission-daemon
systemctl stop transmission-daemon
```

After these steps, you will have a configuration file. You will need to stop Transmission as you cannot edit the configuration file while it is running.
After these steps, you will have a configuration file. It would be best to stop Transmission, as you cannot edit the configuration file while running.

## Configuration

Expand All @@ -49,7 +49,7 @@ cd /var/lib/transmission/.config/transmission-daemon
vi settings.json
```

Navigate down to the `"peer-port"` JSON entry and if desired, replace the stock port with the desired port:
Navigate down to the `"peer-port"` JSON entry, and if desired, replace the stock port with the desired port:

```bash
"peer-port": 51413,
Expand All @@ -75,7 +75,7 @@ If you want to allow access from other IP addresses, navigate to the `"rpc-white
"rpc-whitelist": "127.0.0.1,::1",
```

For instance if you want to allow access to your desktop on IP address `192.168.1.100` you can add it to the comma separated value:
For instance, if you want to allow access to your desktop on IP address `192.168.1.100`, you can add it to the comma-separated value:

```bash
"rpc-whitelist": "127.0.0.1,::1,192.168.1.100",
Expand Down Expand Up @@ -103,7 +103,7 @@ firewall-cmd --permanent --zone=public --add-port=9091/tcp
firewall-cmd --runtime-to-permanent
```

If you are not behind a NAT-PMP or uPNP-enabled router or connected without NAT you will need to forward the BitTorrent port (`12345` in our example). Each router is different but as an example on the author's MikroTik router:
If you are not behind a NAT-PMP, uPNP-enabled router, or connected without NAT, you must forward the BitTorrent port (`12345` in our example). Each router is different, but as an example on the author's MikroTik router:

```bash
/ip firewall nat add action=dst-nat chain=dstnat dst-port=12345 in-interface=ether1 protocol=tcp to-addresses=SERVER_IP to-ports=12345
Expand All @@ -119,4 +119,4 @@ Navigate to the IP address running our Transmission server. As an example, you c

## Conclusion

BitTorrent was designed in the early 2000s when most people connected to the internet via a desktop PC. While it is impractical to run BitTorrent on a laptop or phone, it is perfect to run it on a headless server via Transmission. In this way you can seed files 24/7 and yet our downloads will always be available to you.
BitTorrent was designed in the early 2000s when most people connected to the internet via a desktop PC. While running BitTorrent on a laptop or phone is impractical, running it on a headless server via Transmission is perfect. In this way, you can seed files 24/7, yet our downloads will always be available.