16 Jun
2017
16 Jun
'17
2:26 a.m.
On Fri, Jun 16, 2017 at 10:40:20AM +1000, Josh wrote:
I've now confirmed with my service provider that
they are not blocking
traffic either to or from amprgw.
About 12 hours ago I started logging inbound ipip connections on my wan
interface, but so far have seen nothing from 169.228.34.84.
This may be of interest:
# traceroute -n -P 4 110.175.89.41
traceroute to 110.175.89.41 (110.175.89.41), 64 hops max, 40 byte packets
1 169.228.34.82 0.268 ms 0.206 ms 0.208 ms
2 132.239.254.178 0.255 ms 0.222 ms 0.238 ms
3 132.239.254.162 0.274 ms 0.241 ms 0.238 ms
4 132.239.254.149 0.291 ms 0.291 ms 0.306 ms
5 137.164.23.57 3.034 ms 2.987 ms 2.963 ms
6 137.164.11.2 5.529 ms 5.415 ms 5.394 ms
7 * 4.35.156.65 5.372 ms 5.311 ms
8 * * *
9 4.68.62.106 5.265 ms 5.388 ms 5.221 ms
10 63.243.205.65 14.564 ms 13.385 ms 13.322 ms
11 63.243.205.2 13.394 ms 13.246 ms 13.925 ms
12 64.86.21.150 215.916 ms 215.933 ms 216.003 ms
13 203.29.134.2 217.874 ms 216.001 ms 215.935 ms
14 203.219.107.86 223.699 ms 223.964 ms 224.025 ms
15 203.219.35.202 190.371 ms 190.465 ms 190.584 ms
16 * * *
17 * * *
--- vs ---
# traceroute -n 110.175.89.41
traceroute to 110.175.89.41 (110.175.89.41), 64 hops max, 40 byte packets
1 169.228.34.82 0.375 ms 1.037 ms 0.273 ms
2 132.239.254.178 0.249 ms 0.246 ms 0.230 ms
3 132.239.254.162 0.325 ms 0.243 ms 0.255 ms
4 132.239.254.149 0.313 ms 0.310 ms 0.294 ms
5 137.164.23.57 3.005 ms 2.902 ms 2.934 ms
6 137.164.11.2 5.531 ms 5.553 ms 5.429 ms
7 4.35.156.65 5.365 ms 5.368 ms 5.364 ms
8 * * *
9 4.68.62.106 5.318 ms 5.373 ms 5.559 ms
10 63.243.205.65 13.297 ms 13.341 ms 14.143 ms
11 63.243.205.2 13.390 ms 13.346 ms 13.149 ms
12 64.86.21.150 214.013 ms 215.975 ms 216.021 ms
13 203.29.134.2 215.013 ms 215.982 ms 215.926 ms
14 203.219.107.86 221.514 ms 223.975 ms 223.946 ms
15 203.219.35.202 190.589 ms 190.382 ms 190.583 ms
16 * * *
17 110.175.89.41 211.795 ms 211.134 ms 213.325 ms
The first traceroute is done using protocol 4 (IPIP) packets, the second
using UDP. Note that the IPIP packets are not getting to hop 17.
Hop 16 doesn't respond to traceroute probes, no matter what protocol
I use. I have no way of telling whether it is dropping IPIP or not.
The problem seems to be within a couple of hops to your end
of things.
- Brian