Ok thank you! So the ip in the 44.139.11.x range becomes the gateway, then just set up ipencap like normal? -Nate
On Fri, May 10, 2019 at 8:29 AM Heikki Hannikainen hessu@hes.iki.fi wrote:
On Thu, 9 May 2019, Ruben ON3RVH wrote:
If the subnet is routed to the openvpn server, the openvpn server can route that network to the endpoint.
This particular openvpn server (that I run) does not offer such a service. It allows you to get connected to AMPRnet, but I don't have the time to do custom configurations to route subnets or do other per-user manual tweaking at this time.
So, Rob's "You can't" answer is correct. You'll get the dynamic 44.139.11.x IP address and you can use that to communicate with the amprnet. Sorry!
- Hessu
On 9 May 2019, at 11:14, Rob Janssen pe1chl@amsat.org wrote:
I cant figure out where to go from here. Can anyone point me in the right direction in how to get the routes set up for my little subnet?
You can't. Such a VPN offers you a connection, with an IP, and routes traffic for
that IP to you.
You cannot route arbitrary subnets over that because you cannot setup
routes on the VPN server
pointing to your subnet.
If that is what you want, you need to setup a gateway on the IPIP
tunnel mesh.
Or, find someone else who has done that and arrange for some VPN
between you two.
Rob
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net