Hello Rob et all crew aboard this 44 ship,

Thanks for taking time to answer,

If I ping from my jnos> ping pe1chl.ampr.org then ping is answered.

If I ping from any operating system pe1chl.ampr.org or using remote ping from https://www.wormly.com/test_remote_ping then ping is not answered.

Therefore any other function as web, telnet, nntp, etc are not answered or handled using a PC with any operating system other than a linux with encap.

This is my concern that also happens to others ampr system including yours.

In fact a ping to any ampr.org does go to amprgw (169.228.66.251) as shown by traces, and that happens using any system being or not a linux.

Question is how to resolve this, and reason of seeking help/advice from amprnet experts to guide toward finding a solution.

Best 73, lu7abf, Pedro Converso

On Tue, May 20, 2014 at 4:24 PM, Rob Janssen pe1chl@amsat.org wrote:

(Please trim inclusions from previous messages) _______________________________________________ 44net-request@hamradio.ucsd.edu wrote:

...

Subject: [44net] Pings to 44... from Internet not returning From: Pedro Converso pconver@gmail.com Date: 05/19/2014 11:26 PM

To: AMPRNet working group 44net@hamradio.ucsd.edu

Hello fellows 44 crew

I have a ping not returning syndrome from my 44 address via Internet.

It looks like you are not sending your pings back encapped to 169.228.66.251 You send them directly without encap.

That may work if you have a bad ISP, but normally it should not work. You should have separate route tables for net-44 and public-IP traffic and send all traffic originating at net-44 back out via 169.228.66.251.

I don't think jnos can do that. It really is outdated, you should consider migrating to Linux where this is no problem. (see earlier recipes provided on this list)

Rob