On Fri, Jan 18, 2013 at 12:37 PM,
<lleachii@aol.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Dear Bob VE3TOK and Don VE3ZDA,
Bob, I can confirm that 44.60.44.10, 11 and 12 had an MTU (1480) mismatch with my 44Router 98.252.61.22/44.60.44.1 (1500). That was fixed around the time you specified.
I receive the following RIP44 announcement for you from 44.0.0.1, it is in my 44routing table:
44.135.85.0/24 via 69.165.175.62 dev tunl0 onlink window 840
Don, without a reference to your GW WAN IP or 44subnet address, I'm unable to test or confirm anything here (I recall a file on the old gateway service that included gateway notes - but those notes can only be referenced on the portal by WAN IP). Yes, I am certain my end is encapsulating, as I have not lost connection to AMPRGW nor VE3TOK. I see IP-in-IP datagrams thru routers I'm in control of between 98.252.61.22 and the tunnel interface - addressed to AMPRGW and VE3TOK.
Feel free to check your 44net connection via:
>From anywhere
http://kb3vwg-010.ampr.org/tools/ping/php-ping.php
http://kb3vwg-010.ampr.org/tools/trace/php-trace.php
On AMPR
http://whatismyip.ampr.org
nslookup server 44.60.44.3
dns-mdc.ampr.org
(looks up 44.in-addr.arpa and ampr.org. for all Internet hosts and is ICANN recursive for 44.0.0.0/8 hosts).
At this time, I am left to assume that I am not reaching valid IPs, or the router of the other 44endpoint has not updated their routing table.
73,
Lynwood