Nate,
Sorry, I'll have to update that page to make it more clear. The purpose of it for setting up your own Open VPN server that uses LoTW certificates to mimic what Heikki is doing.
When you are running a sever then obviously you are in control of the address range it offers as part of the dynamic assignment. When you are the client/ end-user then obviously no.
Steve, KB9MWR
On Fri, May 10, 2019 at 7:27 PM Nate Sales via 44Net 44net@mailman.ampr.org wrote:
---------- Forwarded message ---------- From: Nate Sales nate.wsales@gmail.com To: AMPRNet working group 44net@mailman.ampr.org Cc: Bcc: Date: Fri, 10 May 2019 17:24:47 -0700 Subject: Re: [44net] VPN Question Thank you for explaining, I totally misunderstood the purpose. Either way, thanks for the quick responses, I really appreciate it. I was mainly looking at https://qsl.net/k/kb9mwr//wapr/tcpip/lotw-vpn.html which led me to believe that was possible. -Nate
On Fri, May 10, 2019 at 2:28 PM Heikki Hannikainen hessu@hes.iki.fi wrote:
Hi,
No. If you're using ipencap to join the amprnet tunnel mesh, you don't need to use my VPN service.
If you use the VPN, you can't use ipencap at the same time.
With the VPN you get a single tunnel to the Amprnet, and you'll be assigned a dynamic 44.139.11.x IP address during the VPN session.
It is not possible to route your own 44.x.y.z subnet via this VPN. You're limited to communicating with the dynamic 44.139.11.x address assigned to you by the VPN server. Sorry!
On Fri, 10 May 2019, Nate Sales wrote:
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
- Hessu
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
---------- Forwarded message ---------- From: Nate Sales via 44Net 44net@mailman.ampr.org To: AMPRNet working group 44net@mailman.ampr.org Cc: Nate Sales nate.wsales@gmail.com Bcc: Date: Fri, 10 May 2019 17:24:47 -0700 Subject: Re: [44net] VPN Question _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Steve L