If you are looking for an occasional torrent download, then maybe a docker container will be far less resource demanding, not to mention that you will not need a VDSM license (unless you have the free license still open to use). Now, this is useful if you will be using that same instance for more than just torrenting. I have written in the past how to utilize VPN on your NAS and one method of tunneling your torrent traffic via your NAS and a VPN connection is using a VDSM instance that will be protected with a VPN and in return, any other app running under that VDSM instance will be protected as well. Still, every now and then people tend to ask me how to set up docker containers, and most often is how to set up a torrent client with VPN protection. You can run it using the Portainer platform that can be configured following the article here. Those images are a combination of two containers (VPN and client) that run as a single stack. Because of that, I have added a few images on the bottom that runs fine in DSM 7 so consider running them. You can find the Synology range of NAS Storage devices on Amazon here.NOTE: With the new DSM 7 most containers that run in privileged mode will not work. Don’t forget to disable Telnet and Enable SSH when you’re done.Now test the VPN connection is working on your NAS using IPmagnet.If it doesn’t make sure you have forwarded UDP port 1198 to your NAS device in your routers port forwarding page (use google) Save the file and try the connection from Control Panel > Network > Network Interface, it should now connect.Under that line add the following two lines of code:.You should see a line with the IP address you entered in step 4, and a port number (1194).Now right click on the ‘client_’ file again and this time select edit.Right click on the ‘client_’ file and select duplicate, at the end of the file name add ‘.bak’ and save (this will create a backup of the original file in case you need to revert back).Navigate to /usr/syno/etc/synovpnclient/openvpn.Open WinSCP, type the IP address of your NAS, in the user name enter ‘root’ and in the password type your administrator password.Log on to Synology, Control Panel > Terminal and SNMP.Download and install WinSCP (just google it).Click Okay and Save but don’t try and connect just yet as it won’t work.Select, Use default gateway on the remote network, Reconnect when the VPN connection is lost.Enter your user name and password for PIA, the same credentials you use for the website (pXXXXXXXX).ovpn file of your chosen server in a text editor Server address use the IP address of the VPN server, you can find the IP address by opening the.Log on to Synology, Control Panel > Network > Network Interface.Download the latest OpenVPN Configuration Files, i use UDP port 1198 with AES-128-CBC+SHA1, and connect via an IP address instead of the server name.Synology stopped supporting my NAS with DSM updates many years ago, i know i should probably upgrade but if it ain’t broke (or you can fix it), why put your hand in your pocket for a new one.Īfter a lot of trial and error i did finally land on a solution: It would appear PIA have changed something and the new OpenVPN Configuration Files don’t work with DSM 5.0. I have been using Private Internet Access for many years with my Synology NAS which worked beautifully until recently when out of the blue it just stopped working and starting complaining about a certificate error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |