Ubuntu/Bespin/Second AP Tunnel - Revision history

Unknown user at 23:40, 8 July 2020

2020-07-08T23:40:28Z

← Older revision		Revision as of 23:40, 8 July 2020
Line 2:		Line 2:

	Old version (ended in failure): [[Ubuntu/Bespin/Second AP Tunnel/Fail]]		Old version (ended in failure): [[Ubuntu/Bespin/Second AP Tunnel/Fail]]


			<pre>
			▄████████████▄▐█▄▄▄▄█▌
			█████▌▄▌▄▐▐▌██▌▀▀██▀▀
			███▄█▌▄▌▄▐▐▌▀██▄▄█▌
			▄▄▄▄█████████████
			</pre>

	This page contains instructions for modifying the existing Access Point-to-VPN tunnel to include multiple access points and multiple tunnels, with each access point going through a different tunnel.		This page contains instructions for modifying the existing Access Point-to-VPN tunnel to include multiple access points and multiple tunnels, with each access point going through a different tunnel.

2020-07-08T23:21:31Z

The Fail Whale

← Older revision		Revision as of 23:21, 8 July 2020
Line 199:		Line 199:
	Seems to be some kind of issue with two instances of PIA running at once.		Seems to be some kind of issue with two instances of PIA running at once.

	=The Fail Whale=		=The Fail Whale For The Second Time=

	<pre>		<pre>

2020-07-08T23:18:13Z

Test OpenVPN Tunnel

← Older revision		Revision as of 23:18, 8 July 2020
Line 198:		Line 198:

	Seems to be some kind of issue with two instances of PIA running at once.		Seems to be some kind of issue with two instances of PIA running at once.

			=The Fail Whale=

			<pre>
			▄████████████▄▐█▄▄▄▄█▌
			█████▌▄▌▄▐▐▌██▌▀▀██▀▀
			███▄█▌▄▌▄▐▐▌▀██▄▄█▌
			▄▄▄▄█████████████
			</pre>

			You can't even do this, because you can't have two PIA instances running simultaneously. PIA only expects one PIA process to run, so when you run two, the second one doesn't actually do anything, and when you kill it, it also kills the first one.

	==Iptables Modifications==		==Iptables Modifications==

2020-07-08T23:13:22Z

Test OpenVPN Tunnel

← Older revision		Revision as of 23:13, 8 July 2020
Line 196:		Line 196:
	curl: (45) bind failed with errno 99: Cannot assign requested address		curl: (45) bind failed with errno 99: Cannot assign requested address
	</pre>		</pre>

			Seems to be some kind of issue with two instances of PIA running at once.

	==Iptables Modifications==		==Iptables Modifications==

2020-07-08T23:13:05Z

Test OpenVPN Tunnel

← Older revision		Revision as of 23:13, 8 July 2020
Line 187:		Line 187:

	<pre>		<pre>
	curl --interface <ip-addr-of-~~tun2~~> -4 icanhazip.com		curl --interface <ip-addr-of-tun3> -4 icanhazip.com
	</pre>		</pre>

Line 193:		Line 193:

	<pre>		<pre>
	$ curl --interface ~~10.2.11.6~~ -4 icanhazip.com		$ curl --interface <ip-addr-of-tun3> -4 icanhazip.com
	curl: (45) bind failed with errno 99: Cannot assign requested address		curl: (45) bind failed with errno 99: Cannot assign requested address
	</pre>		</pre>

2020-07-08T23:12:49Z

Test OpenVPN Tunnel

← Older revision		Revision as of 23:12, 8 July 2020
Line 182:		Line 182:
	===Test OpenVPN Tunnel===		===Test OpenVPN Tunnel===

	Check that the new tunnel <code>~~tun2~~</code> appears when you run <code>ifconfig</code>.		Check that the new tunnel <code>tun3</code> appears when you run <code>ifconfig</code>.

	Use curl to get the IP address for a request that is forced to go through that tunnel:		Use curl to get the IP address for a request that is forced to go through that tunnel:

2020-07-08T23:12:42Z

Modify Profiles

← Older revision		Revision as of 23:12, 8 July 2020
Line 169:		Line 169:
	sudo sed -i 's+^ca ca.rsa.2048.crt+& /etc/openvpn/ca.rsa.2048.crt+' /etc/openvpn/${PROFILE}.ovpn		sudo sed -i 's+^ca ca.rsa.2048.crt+& /etc/openvpn/ca.rsa.2048.crt+' /etc/openvpn/${PROFILE}.ovpn
	sudo sed -i 's+^crl-verif crl.rsa.2048.pem+& /etc/openvpn/crl.rsa.2048.pem+' /etc/openvpn/${PROFILE}.ovpn		sudo sed -i 's+^crl-verif crl.rsa.2048.pem+& /etc/openvpn/crl.rsa.2048.pem+' /etc/openvpn/${PROFILE}.ovpn
	sudo sed -i 's+dev tun$+dev ~~tun2~~+' /etc/openvpn/${PROFILE}.ovpn		sudo sed -i 's+dev tun$+dev tun3+' /etc/openvpn/${PROFILE}.ovpn
	</pre>		</pre>

2020-07-08T23:11:38Z

Note on Network Names

← Older revision		Revision as of 23:11, 8 July 2020
Line 26:		Line 26:

	LAN10 <code>wlan1</code> refers to the first access point at <code>192.168.10.0/24</code> and uses tunnel <code>tun1</code>		LAN10 <code>wlan1</code> refers to the first access point at <code>192.168.10.0/24</code> and uses tunnel <code>tun1</code>

			LAN20 <code>tun2</code> refers to the OpenVPN network [[Ubuntu/Bespin/OpenVPN Server]] at <code>192.168.20.0/24</code>

	LAN30 <code>wlan1:0</code> refers to the second access point at <code>192.168.30.0/24</code> and uses tunnel <code>tun3</code>		LAN30 <code>wlan1:0</code> refers to the second access point at <code>192.168.30.0/24</code> and uses tunnel <code>tun3</code>

2020-07-08T23:10:57Z

Note on Network Names

← Older revision		Revision as of 23:10, 8 July 2020
Line 25:		Line 25:
	==Note on Network Names==		==Note on Network Names==

	LAN10 refers to the first access point at <code>192.168.10.0/24</code>		LAN10 <code>wlan1</code> refers to the first access point at <code>192.168.10.0/24</code> and uses tunnel <code>tun1</code>

	LAN30 refers to the second access point at <code>192.168.30.0/24</code>		LAN30 <code>wlan1:0</code> refers to the second access point at <code>192.168.30.0/24</code> and uses tunnel <code>tun3</code>

	LAN0 refers to the internet-connected network that Bespin is on, at <code>192.168.0.0/24</code>		LAN0 refers to the internet-connected network that Bespin is on, at <code>192.168.0.0/24</code>

2020-07-08T23:09:41Z

Overview of Setup

← Older revision		Revision as of 23:09, 8 July 2020
Line 18:		Line 18:

	* Update the hostapd file so it will run two APs		* Update the hostapd file so it will run two APs
	* Open second VPN tunnel to different PIA servers, ~~tun2~~		* Open second VPN tunnel to different PIA servers, tun3 (LAN 30)
	* One access point to serve clients, ~~wlan2~~		* One access point to serve clients, wlan1:0
	* Iptables rules to forward traffic from ~~wlan2~~ to ~~tun2~~ and vice-versa		* Iptables rules to forward traffic from wlan1:0 to tun3 and vice-versa
	* dnsmasq will do DHCP and DNS for BOTH access points		* dnsmasq will do DHCP and DNS for BOTH access points


	==Note on Network Names==		==Note on Network Names==