Timeline for Setting up Bridged VPN using: RPi 3G Hotspot router + openvpn client to connect to home RPi OpenVPN server
Current License: CC BY-SA 4.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2019 at 4:38 | vote | accept | Agustin | ||
| Nov 15, 2019 at 4:12 | history | bounty ended | Agustin | ||
| Nov 15, 2019 at 1:04 | comment | added | Agustin | Let us continue this discussion in chat. | |
| Nov 14, 2019 at 16:43 | comment | added | Agustin | Okay, I’ll make the change tonight. However this was pretty much the setup I’ve made before, different approach of the openvpn instead of static.key I used ovpn file and different subnet as you’ve suggested, I’d be able to ping client and server from each side, but nothing attached to each other. And when I start the ovpn server I lose internet network with the attached devices to the client. Again, I’ll test it with a different subnet than the server’s subnet and go from there. Thank you | |
| Nov 14, 2019 at 16:40 | comment | added | Ingo | @Agustin You should always use different subnets. Having the hotspot and the servers the same subnet is not a good idea because we use routing. | |
| Nov 14, 2019 at 16:30 | comment | added | Agustin | 10.10.10.3 is the address I want to use, instead of your 192.168.50.1. From your comment in “Setup the bridge and the internet connection” And it’s not the same as my modem, which is something like 204.17. Something something. I did add this particular info in the route options in both the server and the client. I’ll copy the full logs later tonight after work. Thank you. To clarify the address I changed from 192.168.4.1 to 10.10.10.3 this is the subnet address that the hotspot is routing all attached clients into right? My thought was to use the same as server’s subnet for interaction | |
| Nov 14, 2019 at 16:20 | comment | added | Ingo |
@Agustin What is ip address 10.10.10.3? It is nowhere reflected on the command outputs. Do you add the correct route options into /etc/openvpn/client.conf and /etc/openvpn/server.conf? What external program exited with error status: 2?
|
|
| Nov 14, 2019 at 15:37 | comment | added | Agustin | I’ve implemented the changes, I’ve even started from scratch, and while I can ping server to client and client to server, I cannot ping anything else in the server side, nor anything else in the client side. I have updated my results in the question. Thank you | |
| Nov 14, 2019 at 0:30 | comment | added | Agustin | Thank you, I’ll try it out in an hour! Thank you for taking the time! | |
| Nov 14, 2019 at 0:16 | comment | added | Ingo | @Agustin I have rewritten the answer. | |
| Nov 14, 2019 at 0:14 | history | edited | Ingo | CC BY-SA 4.0 |
Rewritten complete answer with detailed solution
|
| Aug 5, 2019 at 10:51 | history | edited | Ingo | CC BY-SA 4.0 |
Clarified info about pinging everything.
|
| Aug 3, 2019 at 16:25 | history | edited | Ingo | CC BY-SA 4.0 |
Finished setup
|
| Aug 2, 2019 at 22:24 | comment | added | Ingo | Let us continue this discussion in chat. | |
| Aug 2, 2019 at 19:03 | comment | added | Agustin | No it’s fine let’s see the first step first. | |
| Aug 2, 2019 at 18:56 | comment | added | Ingo | @Agustin No, in the first step I will only look at the RasPi and assume that the tunnel endpoint on the server has ip address 10.8.0.1/24 to be accessible by the RasPi through the tunnel. If you like I can set the ip addresses on both sides to 10.10.10.2/24 and 10.10.10.1/24. Setting ip addresses to 10.8.0.2/8 and 10.10.10.1/8 is a waste of millions of ip addresses and may conflict with additional vpn nodes. Look at Subnetwork. | |
| Aug 2, 2019 at 18:36 | comment | added | Agustin | I’d like to add if it’s okay. On your drawing, to the rightmost (to the right of VPN server) maybe add my local network at home with the 10.10.10.1 ip? | |
| Aug 2, 2019 at 18:23 | comment | added | Ingo | @Agustin I have updated the drawing with a bridge. That should now be the final solution. Please add the additional information about using eth0 to your question. The OpenVPN server must have an ip address from the same subnet of the RasPi as shown in the drawing. I will not have a focus on the vpn server in the first step. I just assume that it is working. When the local hostspot on the RasPi is running we can have a look at it. Just a moment please. I have to setup the test. | |
| Aug 2, 2019 at 18:15 | history | edited | Ingo | CC BY-SA 4.0 |
Added bridge
|
| Aug 2, 2019 at 17:34 | comment | added | Agustin | The eth0 interface is being used to provide a LAN to any device that needs access to internet through ethernet. In other words, similarly to the WLAN, the eth0 interface will be used to provide internet from the hotspot ppp0 (pi). So on your drawing both the wlan0 and eth0 interfaces provide the same 192.168.50.1 routing. The RPI hotspot doesn’t have yet a tunnel, the RPI that has a vpn installed is currently at home and is independent from the RPI hotspot. At home the IP range is in the 10.10.10.1 range and the RPI VPN has a tun0 at indeed 10.8.0.1 range. I have also updated the wordin | |
| Aug 2, 2019 at 16:51 | comment | added | Ingo | @Agustin I have updated the answer. You mention interface eth0 in your comment the first time. What do you want to do with it? | |
| Aug 2, 2019 at 16:48 | history | edited | Ingo | CC BY-SA 4.0 |
Updated ip addresses for the vpn tunnel.
|
| Aug 2, 2019 at 13:04 | comment | added | Agustin | from your drawing, it's not too clear whether thanks to the tunnel the attached devices will have a similar 10.10.10.x range, but if that's the case then I would say yes this is what I would like to have, my vpn server indeed has a 10.10.10.X range but the IP address on the tun0 is not in that range. it's in the 10.8.0.x range, the wlan0 range is also indeed in the 192.168.50.x range as well as eth0. | |
| Aug 2, 2019 at 12:19 | history | answered | Ingo | CC BY-SA 4.0 |