Marc, LX1DUC,

Per Brian in a Jan 22 note:
44.0.0.1 responds to pings received from the Internet. It does not
respond to pings coming into it over an encap connection to it, for
some reason that I've not been able to figure out.  I believe it to
be a difficulty in getting it to recognize decapped pings.
If you are receiving the rip44 announcements, you have properly configured your tunnel to receive IP-in-IP encapsulation from 44.0.0.1. Feel free to use:

http://44.60.44.10/tools
or
http://kb3vwg-010.ampr.org/tools

I see your encap as:

44.161.202.0 via 46.29.183.253 dev tunl0 onlink  window 840
44.161.203.0 via 46.29.183.253 dev tunl0 onlink  window 840
44.161.229.0 via 46.29.183.253 dev tunl0 onlink  window 840

Also, I am unable to ping 44.161.229.126. What script/configuration did you use to enable your tunnel; did you specify a local or remote IP (un-needed)? Feel free to look at my script at http://44.60.44.13/startampr


73,


Lynwood
KB3VWG