I don’t think it’s working yet. The “network unreachable” tells me the client isn’t finding its way to the server Beryl. Let’s walk through the steps:
- Your home connection from the internet (Shaw Cable in Canada?) goes through a modem to your Home Router. Those two things may be combined into one unit, and it would be helpful to know the brand/model to fine tune this. Your home router needs to have a routable public IP address, which I’m hoping is the 70.77.7.32 address. More on that later. Let’s just call that the public ip address and come back and edit out the numbers later for security reasons.
- Assuming that the public ip address is the Home Router WAN address, then on its LAN side it has a private IP address, which might be 10.xx.xx.xx address or something else. If you plug the Beryl WAN port into one of the Home Router LAN ports, the Beryl will get a WAN port address in that private range of 10.xx.xxx.xx. Now, in the Home Router, we want to reserve that address for the Beryl, so it doesn’t change.
- Now, on the Home Router, you want to forward a port (call it 1194 for the moment) in the Home Router, so something that rings that port on your Public IP will be forwarded to the same port on the Beryl WAN address. In this way, when you try to make a connection from out in the interwebs, the client Beryl will ring the Home Router, which forwards the request to the Beryl to answer.
- The next step is to get the Beryl OpenVPN server working, and export the configuration file to the Beryl OpenVPN client device. If these 4 steps are in place, you may not make a successful connection but you should get a better error result.
- Now, Shaw Cable may from time to time shift your public IP address, but probably not for weeks or months. You will want to set up a DDNS service to deal with that, but that’s down the road.
2 Likes