Hi, can I describe how to use the Torrent client ??
In system hints there is no such information and the system expects only one parameter.
[admin@MikroTik] > ip torrent/torrents/ add copy-from=
CopyFrom ::= see documentation
Thanks in advance.
I was able to get the torrent client working but it wouldn’t save the USB I had installed. It just ate up the ram disk.
Kali has torrents available and I downloaded a .torrent file and uploaded it to the 3011.
https://www.kali.org/downloads/
Then I enabled the client and it started downloading to RAM.
Placing the .torrent file in the USB or the changing the download location to the USB did not work. I suspect this might be used to download ROS updates for devices either on your network or from MT.
I don’t quite understand you. Do you mean that you have downloaded something or not?
If so, how did you point to the torrent file to download?
Torrent is an experimental thing in v7beta. Currently threre is a bug with filepathing that will be fixed in upcomming beta releases.
It kind of works now. You can download a torrent by enabling the service (/ip/torrent/set enabled=yes) and downloading a .torrent file to the router. It should automatically detect the file and it will appear under /ip/torrent/torrents/print. The implementation is quite old and basic and “download-directory” parameter is quite broken in beta1 as you have already observed.
Anyway, this is an experimental feature and we have not yet decided whether it will be removed from RouterOS or not after beta. If you have any interesting use-case ideas, please share them here.
Please remove it, or at a minimum put it in a separate .NPK from the base OS. maybe a separate soho.npk that includes the torrent client, kid-control and SMB server.. 
… and Quick Set
Please put these kind of features in a external packages. Completely unnecessary for the majority of the users and will only end up as an security issue.
Normal people gets an NAS or mini-server to run torrents.
+1000
100% agreed.
+1
Please remove torrent or put it in a separate .NPK from the base OS, together with kid-control and SMB server.
Amen! 
Don’t know what MT was thinking to add a torrent client, in a router?!?!?!?!
+1 - remove.
No torrent client, please. It will waste resources from both the router and Mikrotik as a company. Better to focus in the router/wireless part, and deliver those long needed features.
torrent is used in the Terragraph ecosystem for node software distribution. just saying. in this interpretation to me it perfectly makes sense to download stuff only to ramdisk.
please, think in scale: upgrading 10s or 100s of 1000s CPEs can run into serious bottleneck.
but i do support the exile of QuickSet.
in my opinion quickset could be replaced by an IOS/Android app, that is solely dedicated for regular home users.
So there has to be years worth of “please enable feature X in v7” threads, why not investigate and prioritize those? If you don’t know the use cases already, you have a solution in search of a problem. As for what to do with the torrent client, perhaps it’s too simplistic but from a security perspective I think of functionality going into two buckets:
- Features I don’t personally use, and there is no specific means of securing (kid control goes here)
- Features that need to be secured, whether I use them or not. Assuming I don’t use a feature, this could be not installing an optional package, ensuring a feature is disabled, etc
I think a torrent client goes into the second bucket, and I could see how a hacker would love to enable and abuse this feature. So I’d much rather have it in an extra package that I wouldn’t install.
Well for me torrent client would be most awesome for home use, schedule download/s over night when nobody is using net to download some stuff on external drive, silent, and low power use compared to PC, + you can use the same drive for direct access over network ..
Big + 1 from me.
I don’t think it would be that big of a problem. If your network has thousands of routers the bandwidth must be equally big. The firmware is about 12MB to each router. As of today, one can barely load 20 web pages with so little data - probably less. If your users watch youtube - even at SD - your network can cope with this load.
To me, torrent client adds complexity, attack surface, bloat to the firmware and takes developers from what is really important.
it is a bit tricky to serve this amount of data quickly. esp. upgrading large number of CPEs managed by some tr-069 based system can be a bottleneck.
sw delivery with torrent is like nuclear fission, once it gets momentum, everything happens very quickly. torrent also offers great integrity checking as well. you can google “software deployment with torrent” and there are quite some solutions out there, so it is not just about movies and iso.
using the built-in torrent client we deployed ~200MB image files to ~250 units in less than 3 minutes - centrally controlled with just a push of a button [but it also can be controlled via API calls]
i agree with you, the function should be easily and completely deactivated if not needed. but this doesn’t necessarily mean it must be removed from the system.
mikrotik’s current package system is a bit old-school with all the reloads required for package activation/deactivation.
But one should never do a network wide upgrade: it should be staged - at least to minimize the convergence time of routes and everything else. I don’t want to imagine 10k routers rebooting a few minutes apart one from another.
Yes, torrent is magical in this way: it scales linearly and can easily move an astounding number of bits. I just don’t think it’s worth the trouble, to distribute a system that is almost 12MB - and we don’t want to share this distribution with the world.
But yes, the package system could do with a revamp: it is showing its age.