Re: [44net] Gateways Unreachable after Dynamic IP Update

I get this just fyi root@w9bbs:~# ping 44.60.44.1 PING 44.60.44.1 (44.60.44.1) 56(84) bytes of data. 64 bytes from 44.60.44.1: icmp_req=1 ttl=46 time=211 ms 64 bytes from 44.60.44.1: icmp_req=2 ttl=46 time=237 ms 64 bytes from 44.60.44.1: icmp_req=3 ttl=46 time=213 ms 64 bytes from 44.60.44.1: icmp_req=4 ttl=46 time=217 ms 64 bytes from 44.60.44.1: icmp_req=5 ttl=46 time=222 ms 64 bytes from 44.60.44.1: icmp_req=6 ttl=46 time=233 ms From: 44net-bounces+n9lya=blueriver.net(a)hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Don Moore Sent: Saturday, January 19, 2013 6:01 PM To: AMPRNet working group Subject: Re: [44net] Gateways Unreachable after Dynamic IP Update I use jnos on slackware. I am still using the daily download of the encap.txt file from the gateway and they all work pretty much flawlesly. This is what jnos sends out when I ping 44.60.44.1 22:53:44.182169 IP 192.168.1.150 > 98.252.61.22: IP 44.135.90.2 > 44.60.44.1: ICMP echo request, id 162, seq 0, length 12 (ipip-proto-4) But I get no response back which is the reason I had asked if your system is actually enaping the 44. address(es) to the ampr stations. If not they just won't make it to them. I know the information is up to date or I wouldn't be encaping to the correct address. I can ping your internet address but not 44.60.44.1 Don - ve3zda