FreshTomato Wiki

User Tools

Site Tools

Trace:
nas-bittorrent

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
nas-bittorrent [2023/06/04 17:09] – -formatting hogwildnas-bittorrent [2023/06/04 17:34] – -formatting, condense hogwild
Line 1: Line 1:
 ====== BitTorrent client (Transmission) ====== ====== BitTorrent client (Transmission) ======
  
-This feature is included in builds that contain Transmission, an open source BitTorrent client. It allows you to perform downloads/uploads of torrents directly on your router. This means you don't have to leave a LAN device, such as a PC, running just to share Torrent files. To share large files, you will require some form of external storage, such as an external USB hard drive.+This feature is included in builds that contain Transmission, an open source BitTorrent client. It allows you to perform downloads/uploads of torrents directly on your router. This means you don't have to leave a LAN device, such as a PC, running just to share Torrent files. To share large files, you will require some form of external storage, such as an external [[nas-usb|USB drive]] or a [[admin-cifs|CIFS]] share.
  
  \\  \\
Line 7: Line 7:
 {{:pasted:20220222-124628.png}} {{:pasted:20220222-124628.png}}
  
-**Enable:**  Selecting this runs the Transmission process immediately after clicking Save. It then starts the Transmission process at every boot.\\  \\+ \\ 
 + 
 +**Enable:**  Selecting this runs the Transmission process immediately after clicking Save. It then starts the Transmission process at every boot.\\  \\  \\
  
 {{:pasted:20220222-124844.png}} {{:pasted:20220222-124844.png}}
  
- \\ + \\ **Transmission binary path:**  This specifies where the Transmission binary will be found on the filesystem.
- +
-**Transmission binary path:**  This specifies where the Transmission binary will be found on the filesystem.+
  
   * Internal - Selecting this means FreshTomato's built-in binary will be used.   * Internal - Selecting this means FreshTomato's built-in binary will be used.
Line 19: Line 19:
   * Custom - Choosing this lets you specify a custom path to the location of the binary.\\   * Custom - Choosing this lets you specify a custom path to the location of the binary.\\
  
- \\ {{:pasted:20220222-125424.png}}\\  \\+ \\
  
-**Click here to open Transmission GUI**:  This will open Transmission's administration graphical interface in a new browser tab.+**Click here to open Transmission GUI:**  This will open Transmission's administration graphical interface in a new browser tab.
  
 **Keepalive:**  Enabling this performs "process keepalive" activity, and will restart Transmission if it isn't found to be running. **Keepalive:**  Enabling this performs "process keepalive" activity, and will restart Transmission if it isn't found to be running.
Line 27: Line 27:
 **Check alive every:**  This value specifies the frequency at which Keepalive is performed. **Check alive every:**  This value specifies the frequency at which Keepalive is performed.
  
-**Delay at startup:**  The time value defined here (in seconds) will delay starting of the process at boot time. \\ This can be useful, for example, when waiting for external storage to be fully ready for use.+ \\ \\ {{:pasted:20220222-125424.png}}\\  \\  \\ **Delay at startup:**  The time value defined here (in seconds) will delay the starting of the process at boot time. \\ This can be useful, for example, when waiting for external storage to be fully ready for use.
  
 **Listening port:**  Here, you specify the port linked to the Transmission process. This will apply to both TCP and UDP. **Listening port:**  Here, you specify the port linked to the Transmission process. This will apply to both TCP and UDP.
Line 33: Line 33:
 **Downloading directory:**  This configures the path where you want completed downloads to be stored. **Downloading directory:**  This configures the path where you want completed downloads to be stored.
  
-**Use incomplete/:**  If enabled, a subfolder called "incomplete" will store the temporary files/folders until the download is completed.+**Use incomplete/:**  If enabled, a subfolder named "incomplete" will store temporary files/folders until the download is completed.
  
-**Autoadd .torrents:**  Also known as "blackhole", Transmission will scan the download folder for .torrent files and import them automatically.\\+**Autoadd .torrents:**  Enabling this feature, (also known as "blackhole") will cause Transmission to scan the download folder  \\ for .torrent files and import them automatically.\\
  
- \\+===== Remote Access =====
  
-{{:pasted:20220222-142445.png}}\\  \\ **Enable GUI:**  This option enables the built-in Transmission GUI. From it, you can administer download/upload activity and configure some program options.+{{:pasted:20220222-142445.png}}\\  \\
  
-**Listening GUI port:**  This specifies the port on which the Transmission administration page should be reachable.+**Enable GUI:**  This option enables the built-in Transmission GUI. From it, you can administer download/upload activity and configure some program options. 
 + 
 +**Listening GUI port:**  This specifies the port on which the Transmission administration page will be reachable.
  
 **Authentication required:**  Choosing this disables anonymous access (strongly suggested) and uses these credentials: **Authentication required:**  Choosing this disables anonymous access (strongly suggested) and uses these credentials:
Line 49: Line 51:
  
 **Allow remote access:**  If enabled, the Listening port becomes reachable from the WAN.\\ **Allow remote access:**  If enabled, the Listening port becomes reachable from the WAN.\\
 +
 +===== Limits =====
 +
 +The Limits section contains settings to define the Transmission's resource limits. The options are pretty much self-explanatory however is more details are needed it is advised to consult the official Transmission documentation.
  
  \\  \\
Line 54: Line 60:
 {{:pasted:20220222-143038.png}}\\  \\ {{:pasted:20220222-143038.png}}\\  \\
  
-**Limits**:  The next paragraph "Limits" is where you define the program resources limit. The options are pretty much self-explanatory however is more details are needed it is advised to consult the official Transmission documentation.+===== Queue torrents =====
  
-{{:pasted:20220222-143353.png}}\\  **Download queuing**:  Is yet another form of limit and controls how many concurrents active Downloads can run simultaneously.\\  **Upload queuing**:  Same as the option above but applies to Uploads instead.\\+{{:pasted:20220222-143353.png}}\\  \\ **Download queuing**:  Is yet another form of limit and controls how many concurrents active Downloads can run simultaneously.\\ **Upload queuing**:  Same as the option above but applies to Uploads instead.\\
  
 {{:pasted:20220222-143604.png}}\\  **Find more peers using**:  Defines on what torrent network type/protocols your Transmission client should participate into. This is not necessarily "all of them". Some protocols have issues over VPN, others must be disabled when using private peering. You might want to consult the official Transmission documentation and perhaps also the generic Torrent Protocol documentation.\\ {{:pasted:20220222-143604.png}}\\  **Find more peers using**:  Defines on what torrent network type/protocols your Transmission client should participate into. This is not necessarily "all of them". Some protocols have issues over VPN, others must be disabled when using private peering. You might want to consult the official Transmission documentation and perhaps also the generic Torrent Protocol documentation.\\
nas-bittorrent.txt · Last modified: 2023/06/04 18:32 by hogwild

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki