pi-hole/docs
1
0
Fork 0
mirror of https://github.com/pi-hole/docs.git synced 2024-12-06 19:27:12 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Update dual-VPN.md

Browse Source 
fixed
This commit is contained in:
RamSet
2018-06-20 12:25:13 -06:00
committed by GitHub
parent 932b5420de
commit 0d09c6171e
1 changed files with 19 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guides/vpn/dual-VPN.md
+19 -8
View File
@@ -8,36 +8,47 @@ So why not use the VPN tunnel to answer to DNS queries only? No traffic goes thr
You can even use the same .ovpn file, with minor modifications (no need to generate it again).
```Prerequisites and Configuration```
###Prerequisites and Configuration
We're going to use the original configuration file and copy it and then, edit the second file:
sudo cp /etc/openvpn/server.conf /etc/openvpn/server2.conf sudo nano /etc/openvpn/server2.conf
```sudo cp /etc/openvpn/server.conf /etc/openvpn/server2.conf sudo nano /etc/openvpn/server2.conf```
We'll need to change the port to a diferent one from the original, so that it does not conflict with the first instance of OpenVPN
Assuming you used default port configuration, you should have 1194 as the port. You need to change this do a different value (make sure the port is available - 1195 should be) and if needed, port forward it from your router into your device. You also need to assign a different class of IPs that will server for this connection only (server line).
```server 10.9.0.0 255.255.255.0```
```
server 10.9.0.0 255.255.255.0
```
And make sure that the DNS requests go though the instance of OpenVPN: push "dhcp-option DNS 10.9.0.1"
And make sure that the DNS requests go though the instance of OpenVPN:
```
push "dhcp-option DNS 10.9.0.1"
```
One other setting that we need to change is comment out (the already existing line) `# push "redirect-gateway def1 bypass-dhcp"`.
Save the file and run the second instance of VPN:
`systemctl start openvpn@server2.service`
```
systemctl start openvpn@server2.service
```
If your distro doesn’t have “systemctl” you may use commands like below to start your OpenVPN with your second configuration as a daemon:
`/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/server2.pid --cd /etc/openvpn --config server2.conf --script-security 2`
```
/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/server2.pid --cd /etc/openvpn --config server2.conf --script-security 2
```
The next step is to edit the exisitng .ovpn file that is used for this connection.
When editing the file, update the port from the provious value, to the port you set-up for the second instance of OpenVPN configuration file.
### Testing
`Before testing, make sure you:`
Before testing, make sure you:
1. have the port forwarded to the second instance of VPN
2. ps ax | grep openvpn should show you two instances of openvpn running (with different configs)
2. ```ps ax | grep openvpn``` should show you two instances of openvpn running (with different configs)
3. you modified the ovpn file and loaded it onto the client.
**Note, when connected to your secondary VPN connection (the DNS only one), you will not get a Pi-hole splash page when accessing a blocked domain directly. The page will not load or it will load with an error, and that's because we didn't route the traffic through the VPN and we didn't create an iptables rule for masquerading, so the return packets (since they are not part of the same LAN subset as your VPN-CLient-AssignedIps) get lost.**