17 May
2017
17 May
'17
12:47 p.m.
This is rather disturbing. Many of the gateways in
the gateway
statistics are showing ZERO encap packets coming from them. One of
the busiest normally is the gateway for Germany, 141.75.245.225, which
has not sent ANY encap packets to amprgw since the current stats began
Is that still the case? I receive plenty of traffic from that gateway,
so when you don't there could be someone who inserted a protocol 4 filter
along the way.
I can still ping 44.0.0.1 via the tunnel...
traceroute to 169.228.66.251 (169.228.66.251), 30 hops max, 60 byte packets
1 xs4all-router (213.222.29.193) 0.262 ms 0.304 ms 0.276 ms
2 0.ae10.xr4.1d12.xs4all.net (194.109.5.57) 0.322 ms 0.ae11.xr4.1d12.xs4all.net
(194.109.5.77) 0.341 ms 0.276 ms
3 asd2-rou-1043.NL.eurorings.net (134.222.93.144) 0.320 ms 0.355 ms
asd2-rou-1044.NL.eurorings.net (134.222.97.17) 0.370 ms
4 asd2-rou-1022.NL.eurorings.net (134.222.48.222) 0.615 ms 0.544 ms 0.500 ms
5 chg-s1-rou-1041.US.eurorings.net (134.222.48.90) 95.532 ms 95.539 ms 95.543 ms
6 eq-exchange.tr01-chcgil01.transitrail.NET (206.223.119.116) 95.616 ms 95.675 ms
95.644 ms
7 ae-1.80.rtsw.chic.net.internet2.edu (64.57.20.150) 95.879 ms 95.901 ms 95.890 ms
8 et-3-1-0.4072.rtsw.kans.net.internet2.edu (64.57.20.89) 106.891 ms 106.906 ms
106.909 ms
9 ae-0.80.rtsw.salt.net.internet2.edu (64.57.20.146) 126.801 ms 126.922 ms 126.846
ms
10 ae-2.80.rtsw.losa.net.internet2.edu (64.57.20.144) 139.339 ms 139.437 ms 139.436
ms
11 64.57.20.83 (64.57.20.83) 139.681 ms 139.675 ms 140.043 ms
12 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 140.662 ms 140.780 ms 140.919
ms
13 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 142.328 ms 142.342 ms 142.395
ms
14 dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 141.823 ms 141.889 ms 141.998 ms
15 nodem-core--mx0-30ge.ucsd.edu (132.239.254.163) 142.100 ms 142.099 ms 142.086 ms
16 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131)
142.068 ms 142.094 ms 142.162 ms
Rob