6 Mar
2019
6 Mar
'19
8:49 p.m.
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?
Mike N9MS
7 Mar
7 Mar
12:56 a.m.
Mike,
I don't have any real experience with OH7LZB's OpenVPN server.
You can try to ping 44.92.21.50 (only 44net)
44.92.21.35 (open to the internet)
They are both part of my network.
Else for testing I usually try hambook.de.ampr.org (visit it via http
too - 44net only) and 44.60.44.3 (run by KB3VWG)
On Wed, Mar 6, 2019 at 2:51 PM Mike Saeger <mike(a)thesaegers.com> 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?
Mike N9MS
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
7:15 a.m.
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?
9:27 a.m.
Le 07/03/2019 à 08:15, Heikki Hannikainen a écrit :
On windows the command is likely different, "route print" I guess?
+1
In some situations, there's an issue with the OpenVPN client
implementation under Windows : if you don't run it as "Administrator",
the routes pushed by the server (ie, 44.0.0.0/8) are not installed on
the machine, then the traffic does not enter the VPN, and goes directly
to Internet.
"route print" should tell you if the route is active or not. If not,
running OpenVPN client as Administor may help.
In all situations, Wireshark is your friend...
73 de TK1BI
2099
days inactive
2100
days old
3 comments
4 participants
participants (4)
-
Heikki Hannikainen -
Mike Saeger -
Steve L -
Toussaint OTTAVI