4 ms·

Somewhat off topic, but is anyone aware of a bittorrent proxy? I regularly end up downloading torrents on a remote box, and then have to copy them to my local

Somewhat off topic, but is anyone aware of a bittorrent proxy? I regularly end up downloading torrents on a remote box, and then have to copy them to my local network. In an ideal world, I could run a torrent client at home and have it proxy though my vps so it doesn't leak my home IP. The other way I can see it working is being able to add a torrent to both my vps and server at home, and have the torrent client at home only ever talk to the single remote box so I still end up with the torrent at home without leaking my home IP and without having to download the finished files as a second step.

deleted 6y ago
[deleted]
corobo 6y ago
I've heard decent things about put.io for the remote side of things, then using `rclone move` [1] to pull the content down at frequent intervals (put.io doesn't show the files till they're done downloading so no worries of pulling half files) If you're not a fan of the full setup there you could look at just the rclone part and have your torrent client move completed downloads into the folder you pulling using rclone [1]: https://rclone.org/commands/rclone_move/ https://rclone.org/commands/rclone_move/ I realise this isn't quite what you've asked for but the direct answer would be to set up either a VPN or a proxy yourself, of which I have no suggestions or recommendations software/host-wise
- mmastrac 6y ago
  put.io has rclone support? I've been using aria in the past and it's not bad but not super convenient. EDIT: https://help.put.io/en/articles/3480094-plex-rclone https://help.put.io/en/articles/3480094-plex-rclone
  - corobo 6y ago
    Aye. This is a Plex-centric guide but you can ignore the plex part https://help.put.io/en/articles/3480094-plex-rclone https://help.put.io/en/articles/3480094-plex-rclone I'd personally go off-guide and use rclone move rather than mounting it just to avoid having to keep bumping up storage space on put.io e: hah you already got it
    - mmastrac 6y ago
      Makes sense. I use plex, but I've only got ~100GB at put.io and it fills up fast (especially with those DS9 AI-upscaled seasons...)
georgyo 6y ago
Do you mean a VPN? But be warned, your home internet, VPS, and/or VPN are all most likly all strongly tied to you. That is because you paid for them. A VPS where you are the only user is a 1:1 mapping to you.
- BuildTheRobots 6y ago
  It's not just for the sake of hiding my IP - I torrent a lot of linux distros. It's just nice to be able to seed at the 200mbit of my VPS than with the 20mbit upstream from the home connection - but this is a very good point.
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 ago
  Up 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)
vaccinator 6y ago
I like xdcc because you dont need to upload
tekromancr 6y ago
I got something similar, but without a remote box (or a remote box that I control, rather). I made a docker container that has the torrent client and openvpn installed in it. All torrent traffic bounces off the VPN, and uses the VPN IP but I am still able to access the torrent client interface via the direct IP
silvereye 6y ago
I also use the same setup. I made a script using python transmissionrpc which watch the torrent pieces being downloaded and send them with sftp as soon as they are available. Then on the receiving side it just creates a sparse file and fill in the pieces using dd (so no dependencies on receiving side). The sending speed was not very good. It could probably be improved by doing multiple transfers in parallel and using a less hacky way to transfers the data.

deleted 6y ago

[deleted]

corobo 6y ago

I've heard decent things about put.io for the remote side of things, then using `rclone move` [1] to pull the content down at frequent intervals (put.io doesn't show the files till they're done downloading so no worries of pulling half files) If you're not a fan of the full setup there you could look at just the rclone part and have your torrent client move completed downloads into the folder you pulling using rclone [1]: https://rclone.org/commands/rclone_move/ https://rclone.org/commands/rclone_move/ I realise this isn't quite what you've asked for but the direct answer would be to set up either a VPN or a proxy yourself, of which I have no suggestions or recommendations software/host-wise

mmastrac 6y ago
put.io has rclone support? I've been using aria in the past and it's not bad but not super convenient. EDIT: https://help.put.io/en/articles/3480094-plex-rclone https://help.put.io/en/articles/3480094-plex-rclone
- corobo 6y ago
  Aye. This is a Plex-centric guide but you can ignore the plex part https://help.put.io/en/articles/3480094-plex-rclone https://help.put.io/en/articles/3480094-plex-rclone I'd personally go off-guide and use rclone move rather than mounting it just to avoid having to keep bumping up storage space on put.io e: hah you already got it
  - mmastrac 6y ago
    Makes sense. I use plex, but I've only got ~100GB at put.io and it fills up fast (especially with those DS9 AI-upscaled seasons...)

georgyo 6y ago

Do you mean a VPN? But be warned, your home internet, VPS, and/or VPN are all most likly all strongly tied to you. That is because you paid for them. A VPS where you are the only user is a 1:1 mapping to you.

BuildTheRobots 6y ago
It's not just for the sake of hiding my IP - I torrent a lot of linux distros. It's just nice to be able to seed at the 200mbit of my VPS than with the 20mbit upstream from the home connection - but this is a very good point.

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 ago
Up 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)

vaccinator 6y ago

I like xdcc because you dont need to upload

tekromancr 6y ago

I got something similar, but without a remote box (or a remote box that I control, rather). I made a docker container that has the torrent client and openvpn installed in it. All torrent traffic bounces off the VPN, and uses the VPN IP but I am still able to access the torrent client interface via the direct IP

silvereye 6y ago

I also use the same setup. I made a script using python transmissionrpc which watch the torrent pieces being downloaded and send them with sftp as soon as they are available. Then on the receiving side it just creates a sparse file and fill in the pieces using dd (so no dependencies on receiving side). The sending speed was not very good. It could probably be improved by doing multiple transfers in parallel and using a less hacky way to transfers the data.