Don't forget, there is a difference between other 44Net nodes getting to him with IPIP & non-44Net source getting there via AMPRGW with IPIP. If testing connectivity, we must do it from both 44Net & non-44Net sources.
On 6/16/2017 7:05 AM, Leon Zetekoff wrote:
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