That's what I thought, it's not 44.182.21.0 but rather 44.182.21.1 and maybe that's part of the problem for those attempting to ping you..
Yes I was able to ping 44.182.21.1 long ago but as I"ve been reviewing the replies I only see .0 referred to and not .1
73, Don
On Fri, Apr 12, 2013 at 9:26 AM, lleachii@aol.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
Marius,
With rip44d v1.3 I now see:
44.182.20.0/24 via 89.122.215.236 dev tunl0 onlink window 840 44.182.21.0/24 via 89.122.215.236 dev tunl0 onlink window 840
PING 44.182.21.1 (44.182.21.1) 56(84) bytes of data. 64 bytes from 44.182.21.1: icmp_req=1 ttl=63 time=161 ms 64 bytes from 44.182.21.1: icmp_req=2 ttl=63 time=174 ms 64 bytes from 44.182.21.1: icmp_req=3 ttl=63 time=156 ms 64 bytes from 44.182.21.1: icmp_req=4 ttl=63 time=156 ms
Though, I'm still unable to traceroute you.
-Lynwood
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html