All,

Paul's note made me consider a few things; and, I now know why WE cannot contact some Stations:

- To test, I changed my tunl0 MTU to 512, I began having failures with my tunnel. I was no longer able to reach certain services within AMPR or on the Internet. I could only perform pings to devices that I had already been able to reach.

- I've attempted to use netalyzr.icsi.berkeley.edu to examine the connection for over a year, it was finally determined between Berkeley and myself that there must be a router in the path dropping ICMP - Fragmentation Needed messages when the tunnel's MTU (1480 for me) is reached. I confirm that my router is sending them, as I've done MTU pings from my 44LAN while running Wireshark and can see my router sending the message.

Marius,

You wrote

> I can confirm the behavior described by Don...
> I can ping ve3zda.ampr.org without problems.
> As for 44.60.44.1, 44.60.44.10, 44.60.44.11 and 44.60.44.12, ping goes out
> via encap interface but there's no response on the ipip tunnel.
>
> My system: 44.182.21.1/89.122.215.236
the VE3ZDA.ampr.org entry (44.135.90.2, which I can ping) is:

44.135.90.2 via 70.52.124.227 dev tunl0 onlink  window 840

To test, I added the following route to my routing table:
ip route add 44.182.21.1 dev tunl0 via 89.122.215.236 onlink table 44 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=158 ms
64 bytes from 44.182.21.1: icmp_req=2 ttl=63 time=157 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
The populated route reads:
44.182.21.0 via 89.122.215.236 dev tunl0 onlink  window 840
44.182.21.0 is a valid IP address on the ICANN Internet and does not imply a subnet in any form.

It should contain a /24 notation as in the AMPRPortal:
44.182.21.0/24 via 89.122.215.236 dev tunl0 onlink  window 840
No AMPR networks on my routing table (populated by RIP44d) contain the proper CIDR notations.


-Lynwood
KB3VWG