• This is odd, I'm able to reach the server and 44.60.44.1 from AMPR and the Public Internet

(what exactly are you trying to 'reach' at 44.60.44.1 to determine its status, as I've only announced NTP as being available there)

• using 'ntpdate -q 44.60.44.1' or 'ntpdate -q kb3vwg-001.ampr.org' works for me anywhere on the Internet

Maybe you are suffering the problem with some types of cable router that I noticed when trying to reach another US amprnet station.

Those routers claim to support a DMZ mode and you set the IPIP tunnel server as the DMZ host, but in reality they do not forward new incoming IPIP packets to the DMZ host, they only forward "replies" to outgoing IPIP tunnel packets just like they do for normal NAT traffic.

So, you configure your IPIP tunnel host, you test connectivity with other systems by pinging or telnet or whatever, and all appears to be fine. However, when anyone else attempts to connect to you from the outside, your system is just unreachable.

When you do a ping to one of them and they try to reach you, it works OK. But when there is no traffic for a few minutes, the gate closes again and you are unreachable.

The DMZ feature probably only works for TCP and UDP. For IPIP, you are just relying on the standard NAT feature which of course is causing the problem described above.

Rob