I can get to you from PA
C:\>tracert 44.136.24.60
Tracing route to
net.vk2hff.ampr.org [44.136.24.60]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms
t30.wa4zlw.homedns.org [10.195.10.3]
2 1 ms <1 ms 1 ms
core100.wa4zlw.ampr.org [44.56.53.1]
3 321 ms 320 ms 323 ms
net.vk2hff.ampr.org [44.136.24.60]
Trace complete.
C:\>
On 6/16/2017 6:36 AM, Josh wrote:
Thanks Tom.It's reassuring to see that your
connection made it through too, and that you didn't get your ipip packets dropped just
upstream of me like amprgw's. I think I'll try and convince my ISP's network
engineers to take a look at Brian's ipip traceroute output, maybe they overlooked
something last time.
Cheers,Josh
-------- Original message --------
From: Tomasz Stankiewicz <sp2l(a)wp.pl>
Date: 16/06/2017 20:18 (GMT+10:00)
To: josh(a)festy.org
Cc: AMPRNet working group <44net(a)hamradio.ucsd.edu>
Subject: Re: [44net] 44 net connectivity problems ?
Josh.
Just to confirm availability of your host:
root@linux:/# ip route get 44.136.24.60 from 44.165.2.2
44.136.24.60 from 44.165.2.2 via 110.175.89.41 dev tunl0
cache window 840
root@linux:/# traceroute 44.136.24.60
traceroute to 44.136.24.60 (44.136.24.60), 30 hops max, 60 byte packets
1
net.vk2hff.ampr.org (44.136.24.60) 717.780 ms 740.340 ms 762.076 ms
root@linux:/#
Best regards.
Tom - SP2L
---
This email has been checked for viruses by AVG.
http://www.avg.com