44net-request@hamradio.ucsd.edu wrote:

Subject: Re: [44net] 44Net Digest, Vol 3, Issue 103 From: Pedro Converso pconver@gmail.com Date: 05/21/2014 12:17 AM

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

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 fromhttps://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.

Oh but that is because pe1chl.ampr.org allows only traffic from net-44. It is a NET system and I don't want to open it to the abusers and portscanners. Try sys2.pe1chl.ampr.org or www.pe1chl.ampr.org. Those are Linux systems and you can ping them both from net-44 and from the entire internet.

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

What I deduced from your trace was that incoming the packets were encapped as IP-in-IP but outgoing they were not. But maybe it is a characteristic of the way you traced, sometimes those extra encapsulations are not shown in a trace.

I think the best solution today is to handle the net-44 routing in Linux and then when you want to run jnos put that behind an extra address that you route locally.

Rob