Search the Community

I downloaded the configuration files from here to run my openvpn in a docker container. wget https://torguard.net/downloads/OpenVPN-TCP-Linux.zip Once it is up and running I get these errors now (while this has been working for many month before. I'm not sure what changed on the Torguard side since I have not changed anything on mine (other than regular security updates, which also could have something to do with this perhaps ) 2022-02-14 19:20:01 TCP connection established with [AF_INET]206.217.216.4:1912 2022-02-14 19:20:01 TCP_CLIENT link local: (not bound) 2022-02-14 19:20:01 TCP_CLIENT link remote: [AF_INET]206.217.216.4:1912 2022-02-14 19:20:09 Connection reset, restarting [-1] 2022-02-14 19:20:09 SIGUSR1[soft,connection-reset] received, process restarting 2022-02-14 19:20:09 Restart pause, 5 second(s) What needs to change to get this working again? Are the https://torguard.net/downloads/OpenVPN-TCP-Linux.zip files still valid?

Hello, i have done all the steps in the document here https://torguard.net/knowledgebase.php?action=displayarticle&id=174 However when starting Torguard, it does not get passed this line Initialization Sequence Completed It just sits there. I have waited for over 10 minutes. I am using the TorGuard.USA-DALLAS I have successfully connected another device, Android, to the DALLAS server Any help would be apprciated.

Sorry if this is a silly question but I can't find the answer anywhere. If you have a torrent client set to start on boot, and the torguard app (Raspberry Pi) lagged a few seconds behind it, would the torrent client be open to the original network for those few seconds? Does anyone know? Thanks!

Hi guys. I need some help, I have a current Wireguard setup which is working fine, but I want to test out performance with OpenVPN and so far it seems that OpenVPN is performing better on my Rasp4. My Rasp needs internet from Wifi , then share to eth . My TG.conf without cerficates: client dev tun proto udp remote swe.torguardvpnaccess.com 1912 resolv-retry infinite nobind persist-key persist-tun tun-mtu 1500 tun-mtu-extra 32 mssfix 1450 ca ca.crt remote-cert-tls server auth-user-pass user.txt script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf compress ncp-disable verb 3 reneg-sec 0 keepalive 5 30 fast-io sndbuf 393216 rcvbuf 393216 cipher AES-256-GCM auth SHA256 key-direction 1 <tls-auth> My script #!/bin/bash # Share Wifi with Eth device # # # This script is created to work with Raspbian Stretch # but it can be used with most of the distributions # by making few changes. # # Make sure you have already installed `dnsmasq` # Please modify the variables according to your need # Don't forget to change the name of network interface # Check them with `ifconfig` ip_address="192.168.2.1" netmask="255.255.255.0" dhcp_range_start="192.168.2.2" dhcp_range_end="192.168.2.100" dhcp_time="12h" eth="eth0" wlan="tun0" sudo systemctl start network-online.target &> /dev/null sudo iptables -F sudo iptables -t nat -F sudo iptables -t nat -A POSTROUTING -o $wlan -j MASQUERADE sudo iptables -A FORWARD -i $wlan -o $eth -m state --state RELATED,ESTABLISHED -j ACCEPT sudo iptables -A FORWARD -i $eth -o $wlan -j ACCEPT sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" sudo ifconfig $eth $ip_address netmask $netmask # Remove default route created by dhcpcd sudo ip route del 0/0 dev $eth &> /dev/null sudo systemctl stop dnsmasq sudo rm -rf /etc/dnsmasq.d/* &> /dev/null echo -e "interface=$eth\n\ bind-interfaces\n\ server=1.1.1.1\n\ domain-needed\n\ bogus-priv\n\ dhcp-range=$dhcp_range_start,$dhcp_range_end,$dhcp_time" > /tmp/custom-dnsmasq.conf sudo cp /tmp/custom-dnsmasq.conf /etc/dnsmasq.d/custom-dnsmasq.conf sudo systemctl start dnsmasq My ethernet dont seem to get any ip adress: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether XXXXXXXXXXXXXXXXXXXX inet 169.254.54.236/16 brd 169.254.255.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet6 XXXXXXXXXXXXXXXXXXX/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether XXXXXXXXXXXXXXXXXXXXX inet 192.168.0.219/24 brd 192.168.0.3 scope global dynamic noprefixroute wlan0 valid_lft 85907sec preferred_lft 75107sec inet6 XXXXXXXXXXXXXX64 scope link valid_lft forever preferred_lft forever 4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 link/none inet 10.35.0.18 peer 10.35.0.17/32 scope global tun0 valid_lft forever preferred_lft forever inet6 XXXXXXXXXXXXXXXXXXX64 scope link stable-privacy valid_lft forever preferred_lft forever DNSMASQ info: [email protected]:~ $ sudo systemctl status dnsmasq.service ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-09-24 10:48:54 CEST; 10min ago Process: 567 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Process: 570 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 580 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS) Main PID: 579 (dnsmasq) Tasks: 1 (limit: 4915) CGroup: /system.slice/dnsmasq.service └─579 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-d Sep 24 10:58:39 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:40 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:41 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:42 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:43 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:44 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:45 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:46 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:57 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 Sep 24 10:58:58 raspberrypi dnsmasq-dhcp[579]: no address range available for DHCP request via eth0 What am I missing here ?

Hey everyone, This is my first post so please be kind. I waned to post a tutorial about how I got a kill switch system working on my raspberry pi using openvpn and connecting through TorGuard. For my purposes, this kill switch is customizable to kill any applications' connections to the internet if the VPN goes down for whatever reason. This method also attempts to reconnect to alternative servers and when connection is established again, it relaunches the application(s) you originally killed. I couldn't find a tutorial for a killswitch that was specific to raspberry pi and torguard. NOTE: I am a novice, through and through. I know this probably can be done easier and more elegantly by someone with any amount of experience. This method currently serves my needs, but if you have constructive feedback, please do share! Credit: This post is a conglomeration of tutorials and instruction from various sites including: OpenVPN with deluge and PIA various other google searches to solve problems that I ran into NOTES: - if you already have deluge setup and openvpn installed, skip to step step 18 for killswitch ASSUMPTIONS: - you are logged in as a non-root user 1) sudo apt-get update 2) sudo apt-get upgrade 3) install deluge: sudo apt-get install deluged sudo apt-get install deluge-console 4) run deluge to create configuration file: deluged 5) kill deluge while we make changes sudo pkill deluged 6) *OPTIONAL: make a backup of the configuration file before we modify it: sudo cp ~/.config/deluge/auth ~/.config/deluge/auth.bkp 7) open the configuration file in an editor: sudo nano ~/.config/deluge/auth 8) add this to the end of the configuration file user:password:level NOTE: user is whatever user account you want the deluge to run under; password is the password for the account; and level 10 gives full administrative privileges to deluge mine: I set mine as user "pi" (no quotes) 9) exit the editor by pressing "ctrl+x" then "y" then "enter" 10) start deluge again: deluged 10) let's one up deluge's console to make some changes: deluge-console 11) the code below will allow the thin client to access deluge: config -s allow_remote True then config allow_remote then exit the console: exit 12) let's restart deluge again: sudo pkill deluged then deluged TEST: let's make sure that you can connect to the deluge daemon on your raspberry pi. open another computer on the same local network as your raspberry pi and download the application deluge from their official website (http://deluge-torrent.org). After finishing installing that on your other computer, open the deluge client application on your computer (not the raspberry pi) 13) we need to change one setting in the deluge client in order for it to connect to deluge on the raspberry pi open up the preferences of the deluge client and go to "Interface" then uncheck the box "classic mode/enabled" 14) go ahead and restart the deluge client app on your non-raspberry pi computer 15) this time it will prompt you with a connection manager window. follow the steps: - click "add" - hostname: enter static IP address of your raspberry pi - username: enter the username you selected in step 8 - password: enter the password you created in step 8 - leave the port as default 16) while you are in the preferences of the deluge client app on your non-raspberry pi, you should set the folder where your torrents download to. look under the "downloads" section of the preferences to set this TEST: let's make sure you can download torrents. go ahead and grab a legal copy of a torrent (any of these: http://whirlpool.net.au/wiki/test_torrents)and drag it onto the deluge client app on your non-raspberry pi computer to see if it starts downloading it; 17) install openvpn with the corresponding torguard .ovpn files by following this tutorial: https://torguard.net/knowledgebase.php?action=displayarticle&id=174 18) let's modify one part of that tutorial (step 17). we are going to change a command that was outlined in that tutorial. do the following: cd /etc/openvpn/ crontab -e - choose whatever editor you want if it prompts you (I use nano) - modify this line: @reboot sudo openvpn --daemon --cd /etc/openvpn --config TorGuard.Canada.ovpn and replace it with: @reboot sudo openvpn --daemon --cd /etc/openvpn --config mastervpn.ovpn we will create this "matervpn.ovpn file in a bit, don't worry, it doesn't exist yet NOTE: before you start this next part, make sure you have killed the openvpn process: sudo killall -9 openvpn KILLSWITCH PART After you have openvpn installed, let's setup the killswitch that will: - immediately kill deluge on your raspberry pi if the VPN connection goes down - attempt to reconnect to alternative VPN servers - when a successful connection is established, it will restart deluge 19) first let's create our master .ovpn file that we are going to use to connect to torgaurd's VPN server(s) cd /etc/openvpn/ sudo mkdir mastervpn.ovpn you can call the file whatever you want, I named it "mastervpn.ovpn" in this case 20) next let's make it executable: sudo chmod u+x,g+x,o+x mastervpn.ovpn 21) first let's copy the configuration file of any of the other servers, preferably one of the ones you want to connect to: nano TorGuard.USA-CHICAGO.ovpn - highlight everything in that window and copy it press "crtl+x" then to exit the editor 22) now open up the mastervpn.ovpn file and paste the code you just copied: sudo nano mastervpn.ovpn 23) we are going to add some additional things you can insert them anywhere, I inserted mine just before the torguard server name. here an example of the my mastervpn.ovpn file: clientdev tun proto udp route-up route-up.sh down down.sh remote chi.central.usa.torguardvpnaccess.com 1912 remote ny.east.usa.torguardvpnaccess.com 1912 remote la.west.usa.torguardvpnaccess.com 1912 remote lon.uk.torguardvpnaccess.com 1912 resolv-retry 300 nobind persist-key persist-tun ca ca.crt tls-auth ta.key 1 auth SHA256 cipher AES-128-CBC remote-cert-tls server auth-user-pass user.txt comp-lzo verb 1 reneg-sec 0 fast-io # Uncomment these directives if you have speed issues ;sndbuf 393216 ;rcvbuf 393216 ;push "sndbuf 393216" ;push "rcvbuf 393216" almost all of this is the default, the only parts I added were the things in red: - the route-up route-up.sh line tells the VPN that when it successfully establishes a VPN connection, to execute the route-up.sh script (we haven't created that yet, we will soon) - the down down.sh similarity tells openvpn to execute the down.sh script when the VPN connection drops for whatever reason - those servers are just a list of servers that I want openvpn to connect to. you can replace these with whatever servers you want, just pull the names from the other .ovpn files that you got from torguard when you installed openvpn. if you have multiple listed like I do, openvpn will attempt to connect to the first one, and if successful will use that one. if for some reason it can't connect or drops a connection and can't reconnect, it will try the next one, and so on and so forth. you can list as many as you want. 24) let's save this file - press "ctrl x" then "y" then "enter" 25) now let's create our scripts, first "route-up.sh": cd /etc/openvpn/ sudo nano route-up.sh 26) copy and paste the following text into the blank window: sudo ip rule add from xx.x.x.x table 10 sudo ip route add default via yy.y.y.y table 10 sudo iptables -t nat -I POSTROUTING -o tun0 -j MASQUERADE sudo -u pi deluged PID=$! sleep 3 kill -2 $PID 2>/dev/null - the first and second lines allow you to still SSH into your raspberry pi while it is connected to the VPN. replace the "xx.x.x.x" with the static IP address of your raspberry pi and "yy.y.y.y" is the IP address of your router - the third line add the appropriate iptables rules that will route all traffic through your VPN tunnel - the last couple of lines starts deluge on your raspberry pi (the last 3 lines is get around a problem of the wrong lib torrent version being incompatible with deluge) 27) save that file press "ctrl x" then "y" then "enter" 28) let's create the "down.sh" sudo nano down.sh 29) post the following code into the blank window: sudo pkill deluged sudo iptables -t nat -D POSTROUTING -o tun0 -j MASQUERADE this will kill deluge on your raspberry pi if the VPN goes down and then removes the routing table so that when connected from the internet, you still have internet on your raspberry pi 30) save that file press "ctrl x" then "y" then "enter" 31) now let's make sure they are executable: sudo chmod u+x,g+x,o+x down.sh sudo chmod u+x,g+x,o+x route-up.sh Everything should work now. you can test by manually running your down.sh and route-up.sh scripts to see if they properly quit and restart deluge on your raspberry pi. Thanks!

Hi everybody, As a linux n00b and first time poster on this forum I wanted to share my experiences and gained knowledge setting up a VPN on OpenElec. The main reason I wanted to set op a VPN-client on my raspberry Pi was to watch BBC iPlayer from outside the UK. I tried xBian but got into trouble with some DNS-stuff and the TUN adapter. So I flashed openELEC on it and tried again. Setting Up Raspberry Pi 1 Windows 7 PC ExtraPutty Winrar Notepad++ Filezilla Win32 disk imager OpenELEC-RPi.arm-6.95.3 8GB SD card Tips & trics for linux n00bs: You can use TAB to autofill folders the command pwd gives you the current folder name the command ls gives a list of files in the current folder the command cd ~ brings you to your home folder When the terminal looks frozen after running a command, use CTRL+C to return. OpenElec installation First download the latest beta version of openELEC for the Raspberry Pi, then extract the .img file to a folder. Use Win32 disk imager to write the .img to the SD card. Insert the SD card into the raspberry pi and supply power to the device. Complete the wizard. Get the openvpn files Download the openvpn config files from TorGuard HERE and unzip them somewhere. I only needed the TorGuard.UK.London.ovpn files and isolated this one to my desktop. Open the file in Notepad++ and look for: auth-user-pass replace this by: auth-user-pass /storage/login.txt I read somewhere that the TorGuard ovpn files got he incorrect line endings and need to be changed to the Linux EOL. To do this in notepad++, Edit -> EOL Conversion -> Convert to UNIX format. Save the file as all files and rename it to: TorGuard.UK.London.conf Then create a new file in notepad++ and insert yout TorGoard username and password on two lines. [email protected] TGpassword Convert the line endings as stated above and save as, all files, login.txt SSH into the device Make sure your windows computer is connected to the same network as the Raspberry Pi, preferably wired. Find the IP-address of raspberry pi and write it down. (System -> System info -> Network) My IP-address was 192.168.178.30 but your's is definitely different. Open extraputty and insert the IP-address, tick SSH and click "OPEN". A black console should appear asking for a login. If not, upgrade the putty client and check connection with raspberry pi. The password and username are as following: login: root password: openelec congratulations! you're connected to the raspberry pi. Overclock Raspberry pi (optional) I got a Raspberry pi version 1, so speed is a bit of a problem. To overclock the device use: mount /flash -o remount,rw nano /flash/config.txt Look for the line: arm_freq=700 core_freq=250 and replace this by: arm_freq=800 core_freq=300 reboot the device to see the effects. Getting openvpn OpenELEC doesn't have apt-get so you need some hassle to get openvpn. I'ts in the unofficial repository so lets download it. I copy pasted the steps from here, to prevent link rot I also post them here. Make sure you are connected to the internet for this steps. * Open Kodi * Select SYSTEM > File Manager * Select Add Source * Select None * Type the following EXACTLY http://fusion.tvaddons.ag and select Done * Highlight the box underneath Enter a name for this media Source & type fusion * Select OK * Go back to your Home Screen* Select SYSTEM * Select Add-Ons * Select Install from zip file * Select fusion * Select xbmc-repos * Select english * Select repository.metalkettle-x.x.x.zip * Wait for Add-on enabled notification * Select Install from repository or Get Add-Ons on Helix * Select MetalKettles Addon Repository * Select Program add-ons * Select openvpn * Select Install * Wait for Add-on enabled notification * Select VPN for OpenELEC * Select Install * Wait for Add-on enabled notification Copy files to raspberry pi I use Filezilla to transfer files from the Windows computer to the raspberry PI. Open Filezilla HOST: sftp://192.168.178.30 (insertyour own IP) USERNAME: root PASSWORD: openelec quickconnect Drag and drop the TorGuard.UK.London.conf file from the Windows computer in the storage folder. Do the same with the login.txt file. Test the VPN connection SSH into the device using extraPutty, insert root/openelec and you are in the terminal. First test if openvpn is installed: openvpn --help When you see alot of commands and information pop-up, congratulations. then test the VPN connection: openvpn /storage/TorGuard.UK.London.conf When you see: Initialization Sequence Completed the connection is established. To test if the external IP-address is foreign use: openvpn /storage/TorGuard.UK.London.conf & wget http://ipinfo.io/ip -qO - The result is an IP-address you can check online to see if it's foreign. Run on Startup To run the line of code on startup openelec is different from other linux distro's. It uses a file called autostart.sh to tun things. run this to edit/create the file: nano /storage/.config/autostart.sh insert this into the file: ( openvpn /storage/TorGuard.UK.London.conf ) & CTRL-X to save and exit. reboot reboot the system and test the connection. DONE!