Split tunneling - Revision history

Ractive at 00:20, 4 March 2022

2022-03-04T00:20:07Z

← Older revision		Revision as of 00:20, 4 March 2022
Line 25:		Line 25:
	You will still be able to remotely manage your services by reverse proxy!		You will still be able to remotely manage your services by reverse proxy!

	==Installation Overview==		=Installation Overview=
	This is an advanced guide but every effort has been made to make it friendly for new users with basic Linux knowledge. Should anything go wrong, feel free to comment or post on the Forum, we will do our best to help you. Since the publication of the VPN Split Tunnel guide for Ubuntu Server 14.04 LTS there are many interesting posts in the forum section.		This is an advanced guide but every effort has been made to make it friendly for new users with basic Linux knowledge. Should anything go wrong, feel free to comment or post on the Forum, we will do our best to help you. Since the publication of the VPN Split Tunnel guide for Ubuntu Server 14.04 LTS there are many interesting posts in the forum section.

Ractive at 00:19, 4 March 2022

2022-03-04T00:19:01Z

← Older revision		Revision as of 00:19, 4 March 2022
Line 6:		Line 6:
	The sections which are marked Minibian are needed only if you are, well, running Minibian. Ubuntu Server 16.04 LTS users should skip those parts (it will be always indicated in the relevant section).		The sections which are marked Minibian are needed only if you are, well, running Minibian. Ubuntu Server 16.04 LTS users should skip those parts (it will be always indicated in the relevant section).

	Why Split VPN Tunnel?		==Why Split VPN Tunnel?==
	If you are running a home server based on Ubuntu Server and you configure your OpenVPN client, you will be completely tunneled over the active VPN connection. But what if we would like to tunnel only few applications' traffic over VPN (for example Transmission or Deluge) and allow everything else direct connection? This is called split tunneling the VPN connection. What if your VPN connection breaks because the VPN server is offline? Without proper firewall rules you will automatically fall back to your direct Internet connection and immediately expose your real IP address. This poses privacy and anonymity risks!		If you are running a home server based on Ubuntu Server and you configure your OpenVPN client, you will be completely tunneled over the active VPN connection. But what if we would like to tunnel only few applications' traffic over VPN (for example Transmission or Deluge) and allow everything else direct connection? This is called split tunneling the VPN connection. What if your VPN connection breaks because the VPN server is offline? Without proper firewall rules you will automatically fall back to your direct Internet connection and immediately expose your real IP address. This poses privacy and anonymity risks!

	he Benefits of VPN Split Tunneling		==The Benefits of VPN Split Tunneling==
	Control		====Control====
	You can select which services/applications should be tunneled over the VPN connection by running the selected services/application as vpn user, therefore you can protect your identity.		You can select which services/applications should be tunneled over the VPN connection by running the selected services/application as vpn user, therefore you can protect your identity.

	Automation		====Automation====
	The VPN connection with Split Tunneling is started automatically on each system start, restarted automatically once the VPN provider is online again.		The VPN connection with Split Tunneling is started automatically on each system start, restarted automatically once the VPN provider is online again.

	Increased Safety		====Increased Safety====
	If the VPN connection breaks, the vpn user is “disconnected” from the Internet (Automatic Kill Switch), if VPN connection is established again, vpn user will have access to Internet again over VPN. This ensures that your real IP address is never exposed publicly, only the IP address assigned by VPN provider is visible.		If the VPN connection breaks, the vpn user is “disconnected” from the Internet (Automatic Kill Switch), if VPN connection is established again, vpn user will have access to Internet again over VPN. This ensures that your real IP address is never exposed publicly, only the IP address assigned by VPN provider is visible.

	Increased Convenience		====Increased Convenience====
	You retain you direct internet connection for all the other users, bypassing the VPN for services/applications that don't require you to hide your real IP address		You retain you direct internet connection for all the other users, bypassing the VPN for services/applications that don't require you to hide your real IP address

	Keep Remote Access		====Keep Remote Access====
	You will still be able to remotely manage your services by reverse proxy!		You will still be able to remotely manage your services by reverse proxy!

	Installation Overview		==Installation Overview==
	This is an advanced guide but every effort has been made to make it friendly for new users with basic Linux knowledge. Should anything go wrong, feel free to comment or post on the Forum, we will do our best to help you. Since the publication of the VPN Split Tunnel guide for Ubuntu Server 14.04 LTS there are many interesting posts in the forum section.		This is an advanced guide but every effort has been made to make it friendly for new users with basic Linux knowledge. Should anything go wrong, feel free to comment or post on the Forum, we will do our best to help you. Since the publication of the VPN Split Tunnel guide for Ubuntu Server 14.04 LTS there are many interesting posts in the forum section.

Line 41:		Line 41:
	Check everything is configured and working correctly		Check everything is configured and working correctly
	==Install openvpn==		==Install openvpn==
			fortunately, the Ubuntu and Debian repositories are not always up to date. It is recommended to use the latest OpenVPN release to make sure you have the latest security fixes (and possible updates). In case of Ubuntu Server 16.04 the official OpenVPN repository always provides the latest version. In case of ARM CPUs like the Rasperry Pi running Raspbian or Minibian, we need to build the latest version since the OpenVPN repository doesn't provide builds for ARM based devices. It is quite easy to build OpenVPN from source (stay tuned for the guide), until then, on Debian, Minibian and Raspbian you can use the version available in the Debian repository.

			Install OpenVPN on Ubuntu Server 16.04 LTS
			If you are using Ubuntu Server 16.04 LTS we will install OpenVPN from the official OpenVPN repository. First import the public GPG key that is used to sign the packages.

			wget https://swupdate.openvpn.net/repos/repo-public.gpg -O - \| sudo apt-key add -
			Add the OpenVPN repository

			echo "deb http://build.openvpn.net/debian/openvpn/stable xenial main" \| sudo tee -a /etc/apt/sources.list.d/openvpn.list
			Install OpenVPN

			sudo apt-get update
			sudo apt-get install openvpn -y
			Update: OpenVPN apt repository has changed, the guide has been updated with the new address.

			Install OpenVPN on Debian 8 (Minibian, Raspbian)
			Since OpenVPN repository doesn't support ARM based devices, we have two options. Use the OpenVPN version available in the Debian repository (probably quite outdated version), or build the latest OpenVPN version from source following our guide. I strongly recommend to build OpenVPN to get the latest version. If you decide to build OpenVPN from source, then skip the below two lines.

			This will install OpenVPN from the Debian repository (required only if you didn't build OpenVPN from source)

			apt-get update
			apt-get install openvpn -y
	create systemd service file for openvpn		create systemd service file for openvpn

Ractive at 00:15, 4 March 2022

2022-03-04T00:15:33Z

@@ Line 1: / Line 1: @@
 =Force Torrent Traffic through VPN Split Tunnel Debian 8 + Ubuntu 16.04=
-setup openvpn
+Important: This guide is written for Ubuntu Server 16.04 LTS and Debian 8 systems (like Minibian, Raspbian, Bananian) that uses systemd services. It might work on other Linux distributions, but it is guaranteed to work on Ubuntu Server 16.04 LTS and Debian 8. For systems that use upstart script (like Ubuntu Server 14.04 LTS), upstart scripts are required instead of systemd service. If you are using Ubuntu Server 14.04 LTS, jump to the Force Torrent Traffic VPN Split Tunnel Ubuntu 14.04 guide.
 create systemd service file for openvpn

Ractive at 00:12, 4 March 2022

2022-03-04T00:12:21Z

← Older revision		Revision as of 00:12, 4 March 2022
Line 1:		Line 1:
	~~<syntaxhighlight lang~~=~~"bash">~~		=Force Torrent Traffic through VPN Split Tunnel Debian 8 + Ubuntu 16.04=
	~~</syntaxhighlight>~~

	setup openvpn		setup openvpn

Ractive at 00:10, 4 March 2022

2022-03-04T00:10:20Z

← Older revision		Revision as of 00:10, 4 March 2022
Line 348:		Line 348:

	Edit openvpn.conf to remove update-resolv-conf from up call		Edit openvpn.conf to remove update-resolv-conf from up call
			<syntaxhighlight lang="bash">
	sudo nano /etc/openvpn/openvpn.conf		sudo nano /etc/openvpn/openvpn.conf
			</syntaxhighlight>
	Locate the line down /etc/openvpn/update-resolv-conf and disable this line by putting a # at the beginning. Should look like this:		Locate the line down /etc/openvpn/update-resolv-conf and disable this line by putting a # at the beginning. Should look like this:
			<syntaxhighlight lang="bash">
	# down /etc/openvpn/update-resolv-conf		# down /etc/openvpn/update-resolv-conf
			</syntaxhighlight>
	Hit Ctrl+X, Y and Enter to Save and Exit.		Hit Ctrl+X, Y and Enter to Save and Exit.

	Next edit routing.sh script, where we will disable the call for update-resolv-conf		Next edit routing.sh script, where we will disable the call for update-resolv-conf
			<syntaxhighlight lang="bash">
	sudo nano /etc/openvpn/routing.sh		sudo nano /etc/openvpn/routing.sh
			</syntaxhighlight>
	Locate the line (should be at the end of the script): /etc/openvpn/update-resolv-conf and put a # at the beginning of the line. Should look like this:		Locate the line (should be at the end of the script): /etc/openvpn/update-resolv-conf and put a # at the beginning of the line. Should look like this:
			<syntaxhighlight lang="bash">
	# run update-resolv-conf script to set VPN DNS		# run update-resolv-conf script to set VPN DNS
	# /etc/openvpn/update-resolv-conf		# /etc/openvpn/update-resolv-conf
			</syntaxhighlight>
	Hit Ctrl+X, Y and Enter to Save and Exit.		Hit Ctrl+X, Y and Enter to Save and Exit.

	You can leave out the Configure VPN DNS Servers to Stop DNS Leaks section, if you didn't already complete it. If yes, no problem, as we will not use update-resolv-conf at all, we just disabled the calling of the script.		You can leave out the Configure VPN DNS Servers to Stop DNS Leaks section, if you didn't already complete it. If yes, no problem, as we will not use update-resolv-conf at all, we just disabled the calling of the script.

	Configure Static IP for Your Server		====Configure Static IP for Your Server====
	This part is actually something you should already have configured when you installed your server, as you need to configure the IP address, netmask and gateway here. Please use the instructions from your VPS provider or ISP on how to do this (if it is not automatically done for you, as with many VPS).		This part is actually something you should already have configured when you installed your server, as you need to configure the IP address, netmask and gateway here. Please use the instructions from your VPS provider or ISP on how to do this (if it is not automatically done for you, as with many VPS).

Line 372:		Line 376:

	Edit interfaces		Edit interfaces
			<syntaxhighlight lang="bash">
	sudo nano /etc/network/interfaces		sudo nano /etc/network/interfaces
			</syntaxhighlight>
	You should see something like this, where address, netmask and gateway should be already filled.		You should see something like this, where address, netmask and gateway should be already filled.
			<syntaxhighlight lang="bash">
	# Loopback device:		# Loopback device:
	auto lo		auto lo
Line 387:		Line 392:
	netmask 255.255.255.224		netmask 255.255.255.224
	gateway 5.X.XXX.XXX		gateway 5.X.XXX.XXX
			</syntaxhighlight>
	Here you need to add the DNS server line after the gateway entry, should look like this (don't change anything else). Remember, you can use other DNS servers, but make sure you use one that you trust.		Here you need to add the DNS server line after the gateway entry, should look like this (don't change anything else). Remember, you can use other DNS servers, but make sure you use one that you trust.
			<syntaxhighlight lang="bash">
	# Loopback device:		# Loopback device:
	auto lo		auto lo
Line 401:		Line 407:
	gateway 5.X.XXX.XXX		gateway 5.X.XXX.XXX
	dns-nameservers 209.222.18.222 209.222.18.218 8.8.8.8		dns-nameservers 209.222.18.222 209.222.18.218 8.8.8.8
			</syntaxhighlight>
	Hit Ctrl+X, Y and Enter to Save and Exit.		Hit Ctrl+X, Y and Enter to Save and Exit.

Ractive at 00:04, 4 March 2022

2022-03-04T00:04:01Z

Show changes

Ractive at 23:45, 3 March 2022

2022-03-03T23:45:21Z

← Older revision		Revision as of 23:45, 3 March 2022
Line 112:		Line 112:
	Thanks to a feedback by our member Jesus, we are now addressing a vulnerability related to the VPN Split Tunnel implementation. If the PIA login credentials are not correct, then OpenVPN will not establish the VPN connection, therefore the firewall rules are not applied (since OpenVPN will execute up scripts only on successful connection). The result is not having the kill switch enabled (iptables rules loaded) and vpn user has direct access to Internet. To prevent this scenario, we will implement a permanent firewall rule to block vpn user’s access to Internet until the OpenVPN tunnel is up and functional, and the required scripts are started. This will prevent any IP leaks even if no connection to PIA is possible for any reason.		Thanks to a feedback by our member Jesus, we are now addressing a vulnerability related to the VPN Split Tunnel implementation. If the PIA login credentials are not correct, then OpenVPN will not establish the VPN connection, therefore the firewall rules are not applied (since OpenVPN will execute up scripts only on successful connection). The result is not having the kill switch enabled (iptables rules loaded) and vpn user has direct access to Internet. To prevent this scenario, we will implement a permanent firewall rule to block vpn user’s access to Internet until the OpenVPN tunnel is up and functional, and the required scripts are started. This will prevent any IP leaks even if no connection to PIA is possible for any reason.

	Flush current iptables rules		===Flush current iptables rules===
			<syntaxhighlight lang="bash">
	sudo iptables -F		sudo iptables -F
			</syntaxhighlight>
	Add the following rule, which will block vpn user's access to Internet (except the loopback device). Note, if you configured Split Tunnel with different user then vpn, then change vpn marked in red to the user you used.		Add the following rule, which will block vpn user's access to Internet (except the loopback device). Note, if you configured Split Tunnel with different user then vpn, then change vpn marked in red to the user you used.
			<syntaxhighlight lang="bash">
	sudo iptables -A OUTPUT ! -o lo -m owner --uid-owner vpn -j DROP		sudo iptables -A OUTPUT ! -o lo -m owner --uid-owner vpn -j DROP
			</syntaxhighlight>
	Now install iptables-persistent to save this single rule that will be always applied on each system start.		Now install iptables-persistent to save this single rule that will be always applied on each system start.
			<syntaxhighlight lang="bash">
	sudo apt-get install iptables-persistent -y		sudo apt-get install iptables-persistent -y
			</syntaxhighlight>
	During the install, iptables-persistent will ask you to save current iptables rules to /etc/iptables/rules.v4 as seen on the screenshot, accept this with YES		During the install, iptables-persistent will ask you to save current iptables rules to /etc/iptables/rules.v4 as seen on the screenshot, accept this with YES

	~~iptables_persistent_split_tunnel-min~~

	Now when system starts, vpn user is not able to access Internet. If the OpenVPN service is started successfully, then this rule is flushed (only until the next system restart), and the Split Tunnel rules are applied.		Now when system starts, vpn user is not able to access Internet. If the OpenVPN service is started successfully, then this rule is flushed (only until the next system restart), and the Split Tunnel rules are applied.

	iptables Script for vpn User		===iptables Script for vpn User===
	The first script will mark the packets for vpn user, the second script will take care of proper routing.		The first script will mark the packets for vpn user, the second script will take care of proper routing.

	Create the iptables script		====Create the iptables script====
			<syntaxhighlight lang="bash">
	sudo nano /etc/openvpn/iptables.sh		sudo nano /etc/openvpn/iptables.sh
			</syntaxhighlight>
	Copy the following to the iptables.sh script, and make sure you enter the network interface and the local IP we identified and marked with red and blue respectively.		Copy the following to the iptables.sh script, and make sure you enter the network interface and the local IP we identified and marked with red and blue respectively.

Line 138:		Line 140:

	Remember, this script will flush your existing iptables rules (UFW included), therefore you need to append your own rules into this script if you need any additional firewall rules.		Remember, this script will flush your existing iptables rules (UFW included), therefore you need to append your own rules into this script if you need any additional firewall rules.
			<syntaxhighlight lang="bash">
	#! /bin/bash		#! /bin/bash
	# Niftiest Software – www.niftiestsoftware.com		# Niftiest Software – www.niftiestsoftware.com
Line 181:		Line 183:

	exit 0		exit 0
			</syntaxhighlight>
	Hit Ctrl+X, Y and Enter to save and exit.		Hit Ctrl+X, Y and Enter to save and exit.

Ractive at 23:39, 3 March 2022

2022-03-03T23:39:41Z

← Older revision		Revision as of 23:39, 3 March 2022
Line 45:		Line 45:
	Next we are going to prevent DNS leak. DNS Leaks are often the main reason your real identity gets exposed even if using VPN. You can read more about DNS leaks here and test them here. The update-resolv-conf script that comes with OpenVPN will automatically apply the preferred DNS servers when OpenVPN connects.		Next we are going to prevent DNS leak. DNS Leaks are often the main reason your real identity gets exposed even if using VPN. You can read more about DNS leaks here and test them here. The update-resolv-conf script that comes with OpenVPN will automatically apply the preferred DNS servers when OpenVPN connects.

	This script will make sure that when using OpenVPN you are not subject to DNS leaks. We will use ~~PIA~~'s DNS Servers (~~209~~.222~~.18~~.222 and ~~209~~.~~222~~.18.~~218~~) and Google's (8.8.8.8) as a third option. You are free to use the DNS servers you trust and prefer. It is advised to change the local DNS to a public even if you are not using VPN. If you are behind a router (and you probably are), it is also a good practice to configure public DNS address on the router too.		This script will make sure that when using OpenVPN you are not subject to DNS leaks. We will use Openvpn's DNS Servers (208.67.222.222 and 208.67.220.220) and Google's (8.8.8.8) as a third option. You are free to use the DNS servers you trust and prefer. It is advised to change the local DNS to a public even if you are not using VPN. If you are behind a router (and you probably are), it is also a good practice to configure public DNS address on the router too.

	Note: make sure you are using a static IP on your machine or reserved DHCP also known as static DHCP. Do not configure the static IP on your server, as resolvconf will not work then. You should set the static IP from your router!		Note: make sure you are using a static IP on your machine or reserved DHCP also known as static DHCP. Do not configure the static IP on your server, as resolvconf will not work then. You should set the static IP from your router!
Line 56:		Line 56:
	Locate this part:		Locate this part:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	# foreign_option_1='dhcp-option DNS 193.43.27.132'		# foreign_option_1='dhcp-option DNS 193.43.27.132'
	# foreign_option_2='dhcp-option DNS 193.43.27.133'		# foreign_option_2='dhcp-option DNS 193.43.27.133'
	# foreign_option_3='dhcp-option DOMAIN be.bnc.ch'		# foreign_option_3='dhcp-option DOMAIN be.bnc.ch'
	</syntaxhighlight>		</syntaxhighlight>

Line 65:		Line 65:
	It should look exactly like this:		It should look exactly like this:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	foreign_option_1='dhcp-option DNS 208.67.222.222'		foreign_option_1='dhcp-option DNS 208.67.222.222'
	foreign_option_2='dhcp-option DNS 208.67.220.220'		foreign_option_2='dhcp-option DNS 208.67.220.220'
	foreign_option_3='dhcp-option DNS 8.8.8.8'		foreign_option_3='dhcp-option DNS 8.8.8.8'
	</syntaxhighlight>		</syntaxhighlight>

Line 81:		Line 81:

	Create vpn user with no login option		Create vpn user with no login option
			<syntaxhighlight lang="bash">
	sudo adduser --disabled-login vpn		sudo adduser --disabled-login vpn
			</syntaxhighlight>
	I suggest to leave personal details blank, just proceed with Enter, and finally answer Y to create vpn user. We disabled login for the vpn user for security reasons, there is no need to log in to the system as the vpn user.		I suggest to leave personal details blank, just proceed with Enter, and finally answer Y to create vpn user. We disabled login for the vpn user for security reasons, there is no need to log in to the system as the vpn user.

Line 88:		Line 89:

	Replace username with the user you would like to add to the vpn group		Replace username with the user you would like to add to the vpn group
			<syntaxhighlight lang="bash">
	sudo usermod -aG vpn username		sudo usermod -aG vpn username
			</syntaxhighlight>
	Replace group with the group name of your regular user that you would like to add the vpn user to		Replace group with the group name of your regular user that you would like to add the vpn user to
			<syntaxhighlight lang="bash">
			sudo usermod -aG group vpn
			</syntaxhighlight>

	~~sudo usermod -aG group vpn~~		===The iptables Script===

	he iptables Script
	We need the local IP and the name of the network interface. Again, make sure you are using a static IP on your machine or reserved DHCP also known as static DHCP, but configured on your router!		We need the local IP and the name of the network interface. Again, make sure you are using a static IP on your machine or reserved DHCP also known as static DHCP, but configured on your router!
			<syntaxhighlight lang="bash">
	ip route list		ip route list
	The output will be similar to this		</syntaxhighlight>
			The output will be similar to this:
			<syntaxhighlight lang="bash">
	default via 192.168.1.1 dev eth0		default via 192.168.1.1 dev eth0
	192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.110		192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.110
			</syntaxhighlight>
	eth0 is the network interface (NETIF), and 192.168.1.110 is the local IP address (LOCALIP). You will need to enter these two into the following script, which we are going to create now.		eth0 is the network interface (NETIF), and 192.168.1.110 is the local IP address (LOCALIP). You will need to enter these two into the following script, which we are going to create now.

	UPDATE (8 November 2016)~~: thanks~~ to a feedback by our member Jesus, we are now addressing a vulnerability related to the VPN Split Tunnel implementation. If the PIA login credentials are not correct, then OpenVPN will not establish the VPN connection, therefore the firewall rules are not applied (since OpenVPN will execute up scripts only on successful connection). The result is not having the kill switch enabled (iptables rules loaded) and vpn user has direct access to Internet. To prevent this scenario, we will implement a permanent firewall rule to block vpn user’s access to Internet until the OpenVPN tunnel is up and functional, and the required scripts are started. This will prevent any IP leaks even if no connection to PIA is possible for any reason.		====UPDATE (8 November 2016)====
			Thanks to a feedback by our member Jesus, we are now addressing a vulnerability related to the VPN Split Tunnel implementation. If the PIA login credentials are not correct, then OpenVPN will not establish the VPN connection, therefore the firewall rules are not applied (since OpenVPN will execute up scripts only on successful connection). The result is not having the kill switch enabled (iptables rules loaded) and vpn user has direct access to Internet. To prevent this scenario, we will implement a permanent firewall rule to block vpn user’s access to Internet until the OpenVPN tunnel is up and functional, and the required scripts are started. This will prevent any IP leaks even if no connection to PIA is possible for any reason.

	Flush current iptables rules		Flush current iptables rules

Ractive at 23:33, 3 March 2022

2022-03-03T23:33:25Z

← Older revision		Revision as of 23:33, 3 March 2022
Line 1:		Line 1:
			<syntaxhighlight lang="bash">
			</syntaxhighlight>

	setup openvpn		setup openvpn

	create systemd service file for openvpn		create systemd service file for openvpn

			<syntaxhighlight lang="bash">
	sudo nano /etc/systemd/system/openvpn@openvpn.service		sudo nano /etc/systemd/system/openvpn@openvpn.service
			</syntaxhighlight>

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 46:		Line 51:
	Open the update-resolv-conf file		Open the update-resolv-conf file

	sudo nano /etc/openvpn/update-resolv-conf		<syntaxhighlight lang="bash">
	Locate this part		sudo nano /etc/openvpn/update-resolv-conf
			</syntaxhighlight>
			Locate this part:
			<syntaxhighlight lang="bash">
	# foreign_option_1='dhcp-option DNS 193.43.27.132'		# foreign_option_1='dhcp-option DNS 193.43.27.132'
	# foreign_option_2='dhcp-option DNS 193.43.27.133'		# foreign_option_2='dhcp-option DNS 193.43.27.133'
	# foreign_option_3='dhcp-option DOMAIN be.bnc.ch'		# foreign_option_3='dhcp-option DOMAIN be.bnc.ch'
			</syntaxhighlight>

	Replace the part highlighted in red, make sure you uncomment (remove the # from beginning) these 3 lines, and pay attention to the third line where your need to replace DOMAIN with DNS.		Replace the part highlighted in red, make sure you uncomment (remove the # from beginning) these 3 lines, and pay attention to the third line where your need to replace DOMAIN with DNS.

	It should look exactly like this		It should look exactly like this:
			<syntaxhighlight lang="bash">
	foreign_option_1='dhcp-option DNS 208.67.222.222'		foreign_option_1='dhcp-option DNS 208.67.222.222'
	foreign_option_2='dhcp-option DNS 208.67.220.220'		foreign_option_2='dhcp-option DNS 208.67.220.220'
	foreign_option_3='dhcp-option DNS 8.8.8.8'		foreign_option_3='dhcp-option DNS 8.8.8.8'
			</syntaxhighlight>

	Hit Ctrl+X, Y and Enter to Save.		Hit Ctrl+X, Y and Enter to Save.

Ractive at 22:38, 3 March 2022

2022-03-03T22:38:00Z

← Older revision		Revision as of 22:38, 3 March 2022
Line 33:		Line 33:
	</syntaxhighlight>		</syntaxhighlight>
	make sure the following are installed:		make sure the following are installed:
	apt-get install nano sudo apt-utils iptables curl resolvconf unzip		<syntaxhighlight lang="bash">
			apt-get install nano sudo apt-utils iptables curl resolvconf unzip
			</syntaxhighlight>

	===Configure VPN DNS Servers to Stop DNS Leaks===		===Configure VPN DNS Servers to Stop DNS Leaks===