Hi,
Did the openvpn client successfully add a 44.0.0.0/8 route towards the VPN gateway?
"ip route" on Linux should show something like:
44.0.0.0/8 via 44.139.11.21 dev tun0
On windows the command is likely different, "route print" I guess?
The route would ensure that amprnet traffic is routed towards the VPN gateway.
ampr.org cannot be pinged from behind the amprnet tunnel mesh due to an implementation detail on ampr.org itself. But try http://hambook.de.ampr.org/ and ping 44.225.164.16 for example.
For debugging, you can also install wireshark and take a packet capture on the VPN tunnel interface, and observe if you are transmitting and receiving amprnet packets via the VPN.
Value of all of this is debatable, but it should work, I currently have ongoing traffic routed via that same VPN.
- Hessu, OH7LZB
On Wed, 6 Mar 2019, Mike Saeger wrote:
I connected via VPN. IPv4 Address. . . . . . . . . . . : 44.139.11.22 Subnet Mask . . . . . . . . . . . : 255.255.255.252
My DHCP server is 44.139.11.21. I am not able to ping that server. I can't ping ampr.org.
Actually, I tried pinging several IP addresses and nothing is returned.
I'm trying to figure out if connecting via VPN is of any useful value?