4 Oct
2018
4 Oct
'18
7:11 a.m.
Well much like Tony reported. I am running ampr-ripd (1.16) I use
multiple routing tables
I have no specific route for 44.0.0.1, just the default route:
ip route add default dev tunl0 via 169.228.34.84 onlink table 44
And I can ping 44.0.0.1 from my subnet.
I recall some talk about this last summer (July 2017)
But it has been working for me for quite some time (more than 3 years
I'd say). I do recall a time when it did not work though. Thinking
back to that, there was a time when once and a while there would be
packet loss thru the ucsd gateway to my subnet. I seem to recall
after Brian Kantor fixed that, that the ping to 44.0.0.1 has worked
ever since for me. Sorry that's about as good as I can remember.
Steve, KB9MWR
On Wed, Oct 3, 2018 at 2:43 PM Brian Kantor <Brian(a)bkantor.net> wrote:
Pinging 44.0.0.1 from outside 44net has always worked, as far as I know.
I believed the problem with pinging from tunneled hosts was
still there, but if it works for you, I must have forgotten.
Sorry for the misinformation.
- Brian
On Wed, Oct 03, 2018 at 01:58:58PM -0500, Steve L wrote:
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net