3 Oct
2018
3 Oct
'18
7:58 p.m.
I thought that bug was fixed some time back...
[kb9mwr@kb9mwr ~]$ ping 44.0.0.1
PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=2 ttl=61 time=62.3 ms
And even from outside 44net:
C:\Users\user>ping 44.0.0.1
Pinging 44.0.0.1 with 32 bytes of data:
Reply from 44.0.0.1: bytes=32 time=72ms TTL=48
Reply from 44.0.0.1: bytes=32 time=71ms TTL=48
On Wed, Oct 3, 2018 at 10:00 AM Brian Kantor <Brian(a)bkantor.net> wrote:
If you are attempting to ping 44.0.0.1, you will not get a response.
This is due to a bug in the tunneling code at the gateway. Try a
tcp connection to port 80 or one of the other common ports to see
if you have connectivity to the gateway.
- Brian
On Wed, Oct 03, 2018 at 02:00:20PM +0100, Aaron Jackson wrote:
No worries - I had another look last night but
for some reason cannot
figure out why I can't get a response back from the gateway. The Pings
go out of the right tun interface and I can receive the routes from RIP
- so bidirectional communication should be possible. Not sure!
I think I'll leave it for the weekend
Aaron
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net