5 ms·
I'm curious to hear if anyone has advise on the former as well, specifically which iptable rules to apply in order to ensure that both incoming and outgoing are
by 3np 6y ago
I'm curious to hear if anyone has advise on the former as well, specifically which iptable rules to apply in order to ensure that both incoming and outgoing are routed properly.
The incoming is straight-forward using your load balancer/reverse proxy of choice, it's the outgoing that's tricky.
Or, as you say, have two torrent daemons. I have'nt done this myself, but what I have in mind, a script that:
* Syncs torrent/magnet to remote (scp or syncthing) to your vm's torrent daemon's incoming folder
* Produces a new .torrent file that is added to your local client, with only the single peer. Ensure that PEX and DHT are disabled.
For this use-case you needn't care as much about leaking, as long as you take care of the above.
- mdaniel 6y agoUp to you, but the benefit of the bittorrent protocol is downloading pieces from multiple peers at once, and then seeding that content back out to support other peers accomplishing the first part. That makes its use in a two peer, download-only, setup kind of weird. I could imagine that being a good setup if your home machine is already managing linux isos, and you want to download ... uh, your own linux iso ... from a VPS (i.e. a concession to the existing process, and not the BT protocol itself)