You will find this feature in builds including Transmission the ope source bittorrent client. This allows you to perform downloads/uploads of torrents directly on your router, a feature particularly interesting if you're not willing to leave LAN devices on specifically for this task.
Transmission binary path: Internal/Optware/Custom - Defines where the Transmission binary is to be found on the filesystem. Please note
Optware covers also
Entware in this context as it will still point to
Click here to open Transmission GUI: As the name suggests it will open the Transmission administration GUI in a new browser's tab.
Keepalive: If enabled it performs a “process keepalive” activity and restart Transmissions if it is not to be found amongst the list of running processes.
Check alive every: The frequency at which the above control should be performed.
Delay at startup: For different reasons, but possibly waiting for external storage to be fully up and running, defining a time here in seconds would, as the name suggests, delay the kick off of the process at boot time.
Listening port: Define here the port linked to the process. This will be both TCP and UDP.
Downloading directory: Here goes the path where you want your completed downloads to be moved to.
Use incomplete/: If enabled a subfolder called incomplete will store the temporary files/folders until the download is fully completed.
Autoadd .torrents: Also known as “blackhole”, Transmission will scan the download folder for .torrents and import them automatically.
Enable GUI: This option enables the build in Transmission GUI from where you can administer your download/upload activity and set up some of the program options.
Listening GUI port: Define the port where the Transmission administration page should be reachable.
Authentication required: It disables anonymous access (strongly suggested) and uses the credentials defined in the below two fields.
Username: Define your administration username here.
Password: Define your administration password here.
Allow remote access: If enabled the Listening port becomes reachable also on the WAN side.
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.
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.
Save settings location: Download directory/JFFS/CIFS1/RAM/Custom - to save NVRAM space most of the settings are saved in a file that is read directly by Transmission. Here you can define the preferred filesystem location where this configuration file is to be saved.
Blocklist: Transmission comes with built in blocking capability. You can define here the IP Blocklist of choice (usually Level 1). Essentially these are lists publicly maintained list of “bad IP addresses” like monitoring servers, robot, and much more that undermines the end user privacy. An alternative method to define the single list here is to use the P2Partisan instead where more lists can be defined however a manual script installation is required in the latter case.
Custom Log File Path: Define here the location where you want Transmission to log its activity.
Custom Configuration: Please refer to the official Transmission documentation for additional detail on what it could/should be defined in this field.