16 Jun
2017
16 Jun
'17
7:27 a.m.
Thank you to everyone who has run a test for me.
Charles: that was the result I was expecting (but not hoping for),
connectivity to me appears to be working properly from any gateway other
than amprgw.ucsd.edu - which means no connectivity to/from the public
internet for my 44 network.
Here's a list of gateways and IPIP packet count that I've received in
the last 24 hours. The gateways with high counts are where hosts on my
network connect to services like NTP or DNS.
24.115.112.147: 29
24.34.225.54: 11
69.165.175.62: 149
71.178.210.39: 15885
82.70.39.222: 9
85.188.1.118: 161
87.251.250.110: 67
89.122.215.236: 1524
118.82.200.153: 3
173.230.244.130: 16
213.222.29.194: 82
Thanks again for all the assistance and tips I've received today, I've
been trying to diagnose this for days but it's had me stumped.
-Josh
On 16/06/2017 9:26 PM, Charles J. Hargrove wrote:
Here is what I am talking about. The first trace is
from my Linux
server with AMPRIPD and knows the IPIP route to 44.136.24.60:
Fri Jun 16 07:22:43 root@host [~]# 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) 574.984 ms 597.901 ms 620.869 ms
Fri Jun 16 07:22:53 root@host [~]#
This second trace is from my Win7 laptop at home in NYC and goes
through my cable modem to UCSD where it dies:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.136.24.60
Tracing route to net.vk2hff.ampr.org [44.136.24.60]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms m0n0wall.nyc-races.org [192.168.1.1]
2 15 ms 15 ms 14 ms 142.254.170.29
3 15 ms 13 ms 14 ms be61.nycrnydf01h.nyc.rr.com
[68.173.202.8]
4 15 ms 16 ms 18 ms agg131.nyclnyrg01r.nyc.rr.com
[68.173.197.0]
5 13 ms 15 ms 23 ms
bu-ether29.nwrknjmd67w-bcr00.tbone.rr.com [107.1
4.19.24]
6 17 ms 15 ms 28 ms
bu-ether12.nycmny837aw-bcr00.tbone.rr.com [66.10
9.6.27]
7 16 ms 18 ms 15 ms 0.ae1.pr0.nyc20.tbone.rr.com
[66.109.6.163]
8 14 ms 15 ms 16 ms rtr.loss.net.internet2.edu
[198.32.118.161]
9 44 ms 48 ms 39 ms ae-0.0.rtr.eqch.net.internet2.edu
[64.57.20.33]
10 41 ms 40 ms 40 ms ae-1.80.rtsw.chic.net.internet2.edu
[64.57.20.15
0]
11 53 ms 55 ms 59 ms
et-3-1-0.4072.rtsw.kans.net.internet2.edu [64.57
.20.89]
12 89 ms 107 ms 86 ms ae-0.80.rtsw.salt.net.internet2.edu
[64.57.20.14
6]
13 107 ms 92 ms 94 ms ae-2.80.rtsw.losa.net.internet2.edu
[64.57.20.14
4]
14 84 ms 86 ms 86 ms 64.57.20.83
15 87 ms 85 ms 83 ms dc-tus-agg3--lax-agg6-100ge.cenic.net
[137.164.1
1.7]
16 89 ms 86 ms 89 ms dc-sdg-agg4--tus-agg3-100ge.cenic.net
[137.164.1
1.9]
17 86 ms 86 ms 87 ms dc-ucsd-1--sdg-agg4.cenic.net
[137.164.23.54]
18 90 ms 86 ms 89 ms mcore-flow-bypass-mx0-p2p.ucsd.edu
[132.239.254.
61]
19 88 ms 93 ms 86 ms rci-nodem-p2p.ucsd.edu [132.239.254.177]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\n2nov>
On 6/16/2017 7:14 AM, Charles J. Hargrove wrote:
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.