18 Jan
2013
18 Jan
'13
4:53 a.m.
Dear Bob VE3TOK (and thanks to VE3ZDA and N2NOV),
Your entry is on my route table, I'm using rip44d (not encap), so my
updates are live. The IP of my gateway is correct in the Portal. I use
the -a switch to remove my own route (and have updated it to the correct
IP); and I still receive rip44d updates over AMPR (showing that I have
not lost connectivity to the Main AMPRGW).
From testing connectivity to your subnet, I have determined that my
44GW is operational; and that some gateways may not have yet updated
their encap.
Thanks for your help; I waited a few days to to be sure that was not the
case; as I know all stations do not have dynamic routing updates, I'll
wait longer next time.
73,
Lynwood
KB3VWG
http://44.60.44.10/tools
@kb3vwg-015:~$ ping 44.135.85.1 -c 10
PING 44.135.85.1 (44.135.85.1) 56(84) bytes of data.
From 44.135.85.30: icmp_seq=7 Source Quench
From 44.135.85.30: icmp_seq=8 Source Quench
From 44.135.85.30: icmp_seq=9 Source Quench
From 44.135.85.30: icmp_seq=10 Source Quench
--- 44.135.85.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9003ms
@kb3vwg-015:~$ traceroute 44.135.85.30
traceroute to 44.135.85.30 (44.135.85.30), 30 hops max, 60 byte packets
1 kb3vwg-001.ampr.org (44.60.44.1) 0.724 ms 0.238 ms 0.218 ms
2 linux.ve3mch.ampr.org (44.135.85.151) 51.890 ms 55.835 ms 60.720 ms
3 port.ve3mch.ampr.org (44.135.85.30) 63.642 ms 62.613 ms 66.477 ms
@kb3vwg-015:~$ ping 44.135.85.30 -c 5
PING 44.135.85.30 (44.135.85.30) 56(84) bytes of data.
64 bytes from 44.135.85.30: icmp_req=1 ttl=39 time=53.9 ms
64 bytes from 44.135.85.30: icmp_req=2 ttl=39 time=51.8 ms
64 bytes from 44.135.85.30: icmp_req=3 ttl=39 time=87.4 ms
64 bytes from 44.135.85.30: icmp_req=4 ttl=39 time=52.7 ms
64 bytes from 44.135.85.30: icmp_req=5 ttl=39 time=51.9 ms
--- 44.135.85.30 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 51.899/59.607/87.406/13.919 ms