This feature is included in builds that contain Transmission, an open source BitTorrent client. It lets you download/upload torrents directly on your router. This means you don't have to leave a LAN device, such as a PC, running just to share Torrents.
To share large files, you'll need some form of external storage, such as an external USB drive or a CIFS share.
Enable: checking this/Save immediately runs Transmission and starts it at each boot.
Transmission binary path: specifies the location of the Transmission binary.
Click here to open Transmission GUI: opens the administration GUI in a new browser tab.
Keepalive: performs “process keepalive” activity, and restarts Transmission if it's not running.
Delay at startup: the time value defined here (seconds) will delay the running of the process at boot time.
This can be useful when waiting for external storage to be fully ready for use.
Listening port: here, specify the port linked to Transmission. This applies to TCP and UDP.
Downloading directory: the path where completed downloads will be stored.
Use incomplete: if checked, a folder named “incomplete” stores temp files until the download completes.
Autoadd .torrents: makes Transmission scan the download folder for .torrent files and import them automatically.
Enable GUI: enables the Transmission GUI, where you can manage downloads/uploads and set options.
Authentication required: disables anonymous access (suggested) and uses these credentials:
Allow remote access: if enabled, the Listening port becomes reachable from the WAN.
Settings here define resource limits. While most options are self-explanatory, consult official documentation for details. Transmission
Download queuing: controls how many active downloads can run simultaneously.
Upload queuing: specifies how many active uploads can run simultaneously.
Find more peers using: sets the Torrent network types in which Transmission participates, and with which protocols.
Be selective with these settings. Some protocols don't work well through a VPN, or interrupt private peering. For best results, see the Transmission documentation and perhaps generic Torrent protocol documentation.
Message level: defines the lowest level of Transmission messages to capture in the system logs:
Save settings location: here, define the preferred filesystem location for settings to be saved.
To save NVRAM space, most settings are saved in a file read directly by Transmission.
Blocklist: here, specify a URL to an IP Blocklist of your choice (usually Level 1).
Transmission has a built-in blocking feature. IP blacklists are publicly-maintained lists of “bad” Torrent addresses, like monitoring servers or robots that undermine your privacy.
Another way of doing this is to define a blocklist here to use P2Partisan instead. With P2Partisan, you can define more lists and block ranges of addresses. To use it, you must install a script, per the instructions here: Linksysinfo.org: P2Partisan
Custom Log File Path: here, define the location where Transmission will log activity.
Custom Configuration: refer to Transmission documentation to learn about these options.