Synology/ Docker/ rTorrent... behind a VPN

AnotherForumReaderAnotherForumReader
edited November 2017 in Other Devices VPN Setup
If you want to set up rTorrent on your NAS, this is the post for you. I can show you how to set everything up, but your real IP will be exposed. I am working on a solution to that in the second half of this post.

Here's the scenario: Like many others, I want to use the Synology NAS as a Seedbox, using rTorrent/ruTorrent to manage the files. 
  • I used this Dr Frankenstein guide to set up Docker/ Linux/ rTorrent/ ruTorrent.
  • It worked great, except the Listen Port was closed because he forgot to add the Listen Port to the port settings on the Docker container, which caused a "Port closed" issue in ruTorrent, which I have since fixed. 
  • (For anyone who bumps into this problem later, you have to add a port forward on the Docker Container and possibly on your edge router. I wrote up instructions to help you fix that.

Ok... so now I have Docker/Linux/rTorrent set up and running on the NAS. It basically looks something like this:



So this is great... except that I dont want to be blasting out my home IP address, which means I need to connect the Docker container to a VPN. (If you arent concerned about exposing your true IP address, then the info above should give you everything you need to set this up.)

Since I want to use the VPN to mask my IP, I added a VPN profile on the NAS and connected to the PIA VPN.... and rTorrent still works. 
  • The good news is, I can DL files, and I can seed files, and my true IP is hidden behind the VPN... and I didnt have to do anything particularly special.
  • The bad news is, the Listen Port is now closed again.

To solve this, I think I need to set up a port forward on the NAS, to allow the Listen Port thru the VPN.... but I cant figure out how to forward ports on the NAS itself. Im guessing I need to add a Traffic Control rule, or a Static Route rule. But maybe I should be looking for something else?

Here is a diagram to help depict all this... its a little crude but hopefully this will help explain the problem as I see it.
So... can someone point me in the right direction to port forward on the VPN for incoming connections?


Comments

  • AnotherForumReaderAnotherForumReader
    Btw, for what it's worth. I tried connecting the NAS to the PIA Proxy Server, but my real IP was still broadcasting, so that approach doesn't work.... which is why I am trying to connect to PIA via the VPN Profile.

    There may be a command line script that can be run to help me connect to PIA, but if there is, I dont know how to do that.

    If you ever want to know which IP is broadcasting while seeding, use this to help you test and verify things: http://ipmagnet.services.cbcdn.com
Sign In or Register to comment.