On 10/12/18 4:55 PM, Gregory Nowak wrote:
> On Fri, Oct 12, 2018 at 04:35:17PM -0500, golinux@??? wrote:
>> Thanks for the responses. I suspect that IPv6 might indeed be the culprit.
> I doubt it, since both traceroutes are using IPv4, and both have odd delays.
>
>> $ traceroute google.com
>> traceroute to google.com (74.125.129.102), 30 hops max, 60 byte packets
>> 1 * * *
>> 2 tge0-0-0.ausdtx2802h.texas.rr.com (66.68.2.205) 45.543 ms 46.092 ms
>> 46.373 ms
>> 3 agg30.ausxtxir02r.texas.rr.com (24.175.42.144) 24.660 ms 25.364 ms
>> 25.750 ms
>> 4 agg22.hstqtxl301r.texas.rr.com (24.175.41.48) 31.765 ms 36.379 ms
>> 35.651 ms
>> 5 ae-1-0.p0.atl90.tbone.rr.com (66.109.1.218) 50.802 ms 44.462 ms
>> 39.178 ms
>> 6 bu-ether12.dllstx976iw-bcr00.tbone.rr.com (66.109.6.39) 45.106 ms
>> 34.283 ms 107.14.19.49 (107.14.19.49) 36.338 ms
>> 7 0.ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 35.058 ms
>> 0.ae2.pr1.dfw10.tbone.rr.com (107.14.17.236) 27.868 ms 25.589 ms
>> 8 ix-ae-23-0.tcore2.dt8-dallas.as6453.net (66.110.57.97) 32.475 ms
>> 39.941 ms 52.998 ms
>> 9 74.125.50.214 (74.125.50.214) 31.421 ms 34.253 ms 38.467 ms
>> 10 * * *
>> 11 216.239.63.238 (216.239.63.238) 34.677 ms 108.170.226.56
>> (108.170.226.56) 29.073 ms 108.170.226.182 (108.170.226.182) 29.651 ms
>> 12 108.170.240.145 (108.170.240.145) 29.667 ms 108.170.240.209
>> (108.170.240.209) 32.095 ms 108.170.252.130 (108.170.252.130) 34.320 ms
>> 13 216.239.59.168 (216.239.59.168) 29.987 ms 108.170.233.117
>> (108.170.233.117) 30.326 ms 108.170.228.84 (108.170.228.84) 31.091 ms
>> 14 209.85.250.37 (209.85.250.37) 30.081 ms 38.277 ms 35.229 ms
>> 15 209.85.246.182 (209.85.246.182) 56.902 ms 209.85.246.84 (209.85.246.84)
>> 77.541 ms 209.85.246.182 (209.85.246.182) 73.471 ms
> Looks to me like dropped packets start around here:
>
>> 16 216.239.56.175 (216.239.56.175) 63.061 ms 216.239.54.65 (216.239.54.65)
>> 61.564 ms 216.239.48.67 (216.239.48.67) 65.893 ms
>> 17 * * *
>> 18 * * *
>> 19 * * *
>> 20 * * *
>> 21 * * *
>> 22 * * *
>> 23 * * *
>> 24 * * *
>> 25 * * *
>> 26 * * *
>> 27 jm-in-f102.1e100.net (74.125.129.102) 168.457 ms 171.191 ms 170.337
>> ms
>>
> I reproduced the above traceroute to the same IP, and am seeing
> similar results, even though my packets took a different route from
> yours. This suggests it could be a problem with that particular IP.
>
>> Good grief!!! Another trace route eventually got to one of my websites:
>>
>> $ traceroute stopcta.info
>> traceroute to stopcta.info (185.203.114.117), 30 hops max, 60 byte packets
>> 1 * * *
>> 2 tge0-0-0.ausdtx2801h.texas.rr.com (66.68.2.201) 330.761 ms 331.380 ms
>> 331.773 ms
>> 3 agg30.ausutxla01r.texas.rr.com (24.175.42.142) 25.345 ms 26.732 ms
>> 27.302 ms
>> 4 agg22.dllatxl301r.texas.rr.com (24.175.41.46) 37.000 ms 33.044 ms
>> 37.558 ms
>> 5 bu-ether14.dllstx976iw-bcr00.tbone.rr.com (66.109.6.88) 41.860 ms
>> 66.109.1.216 (66.109.1.216) 40.157 ms 41.325 ms
>> 6 66.109.5.121 (66.109.5.121) 31.192 ms 42.090 ms 25.595 ms
>> 7 dls-b21-link.telia.net (62.115.156.208) 27.346 ms 28.104 ms 27.084 ms
>> 8 atl-b22-link.telia.net (80.91.246.74) 49.968 ms 58.985 ms 49.461 ms
>> 9 mai-b1-link.telia.net (62.115.122.53) 69.445 ms 67.043 ms 59.106 ms
>> 10 init7-ic-318278-mai-b1.c.telia.net (62.115.148.55) 70.009 ms 77.143 ms
>> 72.151 ms
>> 11 r2nyc3.core.init7.net (193.47.153.231) 71.850 ms 70.682 ms 78.191 ms
>> 12 r1nyc3.core.init7.net (193.47.153.238) 80.221 ms 73.209 ms 69.531 ms
>> 13 r1nyc2.core.init7.net (193.47.153.234) 84.886 ms 74.355 ms 70.098 ms
> A rather large delay seems to start here:
>
>> 14 r1lon2.core.init7.net (77.109.128.14) 140.249 ms 140.124 ms 147.072
>> ms
>> 15 r1bsl1.core.init7.net (77.109.128.102) 173.037 ms 162.066 ms 164.498
>> ms
>> 16 r1zrh2.core.init7.net (77.109.128.129) 159.150 ms 152.605 ms
>> r1bsl3.core.init7.net (82.197.168.18) 160.159 ms
>> 17 r1glb1.core.init7.net (77.109.128.238) 165.343 ms r1zrh8.core.init7.net
>> (82.197.168.74) 155.252 ms r1glb1.core.init7.net (77.109.128.238) 171.133
>> ms
>> 18 empty.init7.net (77.109.141.139) 159.961 ms 156.963 ms 165.937 ms
>> 19 * r1glb1.core.init7.net (77.109.140.205) 156.057 ms 159.736 ms
>> 20 empty.init7.net (77.109.141.139) 165.136 ms
>> 117-114-203-185.place5.ungleich.ch (185.203.114.117) 169.960 ms
>> empty.init7.net (77.109.141.139) 161.785 ms
>>
>> I (or rather Evilham and Nico) recently moved my websites to a devuan IPv6
>> VPS which is set up to serve IPv4 too through some sort of server-side magic
>> I don't really understand. I suspect this might be what triggered
>> things.
> It's possible. I reproduced this traceroute also, and am seeing the
> large delay as well. This suggests that everything is fine with your
> home network, as well as your ISP.
>
>> I
>> am clueless how to test if IPv6 is actually enabled on my network or how to
>> disable it if it is.
> If you've disabled IPv6 already, you'll need to enable it again
> first. Then, use traceroute6 (which actually just calls traceroute
> with the -6 flag), like:
>
> traceroute6 google.com
>
> There are other ways of course, but that's probably the simplest. If
> you have IPv6, the traceroute will have output similar to what you
> posted, but with IPv6 addresses. If you don't have IPv6, it will just
> fail from the start.
>
>
> Greg
>
>

the first thing I'd suggest is to repeat the trace with

traceroute -n

That disables resolving the names of the hops.  dropped ICMP inside of peoples networks isn't uncommon.... Not good form, but what can you say?

That will eliminate name resolution from the network diagnosis.

Without name resolution:

traceroute -n stopcta.info

traceroute to stopcta.info (185.203.114.117), 30 hops max, 60 byte packets
 1  50.196.187.254  0.194 ms  0.189 ms  0.215 ms
 2  96.120.90.137  8.580 ms  8.050 ms  8.525 ms
 3  68.86.248.205  7.864 ms  7.857 ms  7.829 ms
 4  162.151.78.93  10.033 ms  10.106 ms  10.100 ms
 5  68.86.91.73  11.642 ms  11.561 ms  11.476 ms
 6  68.86.84.14  10.921 ms  10.785 ms  10.790 ms
 7  96.87.8.2  9.704 ms  9.635 ms  9.541 ms
 8  62.115.122.37  78.000 ms  77.673 ms  78.973 ms
 9  213.155.130.28  82.572 ms 62.115.137.99  80.985 ms  80.939 ms
10  62.115.148.51  80.962 ms  80.830 ms  79.996 ms
11  193.47.153.234  81.874 ms  82.478 ms  79.359 ms
12  77.109.128.14  177.899 ms  177.897 ms  172.374 ms
13  77.109.128.102  165.399 ms  162.659 ms  172.281 ms
14  82.197.168.18  167.963 ms  164.476 ms 77.109.128.129  163.835 ms
15  82.197.168.74  168.079 ms  168.094 ms 77.109.128.238  162.543 ms
16  82.197.168.238  162.385 ms 77.109.141.139  168.592 ms 82.197.168.238  164.678 ms
17  77.109.140.205  176.823 ms  164.205 ms *
18  185.203.114.117  163.781 ms  163.734 ms 77.109.141.139 164.768 ms


With name resolution:

traceroute  stopcta.info
traceroute to stopcta.info (185.203.114.117), 30 hops max, 60 byte packets
 1  50-196-187-254-static.hfc.comcastbusiness.net (50.196.187.254)  0.304 ms  0.341 ms  0.199 ms
 2  96.120.90.137 (96.120.90.137)  7.387 ms  7.415 ms  7.463 ms
 3  po-103-rur01.oakland.ca.sfba.comcast.net (68.86.248.205) 7.631 ms  7.606 ms  7.579 ms
 4  162.151.78.93 (162.151.78.93)  9.552 ms  9.475 ms  9.404 ms
 5  be-3651-cr02.sunnyvale.ca.ibone.comcast.net (68.86.91.73) 11.312 ms  14.370 ms  11.112 ms
 6  be-11083-pe02.529bryant.ca.ibone.comcast.net (68.86.84.14) 10.450 ms  10.128 ms  10.030 ms
 7  96-87-8-2-static.hfc.comcastbusiness.net (96.87.8.2)  9.912 ms  9.169 ms  15.321 ms
 8  nyk-bb3-link.telia.net (62.115.114.4)  80.856 ms nyk-bb4-link.telia.net (62.115.122.37)  81.519 ms  81.953 ms
 9  nyk-b2-link.telia.net (213.155.130.28)  81.408 ms  81.401 ms nyk-b2-link.telia.net (62.115.137.99)  81.050 ms
10  init7-ic-318276-nyk-b2.c.telia.net (62.115.148.51)  81.353 ms 81.275 ms  81.210 ms
11  r1nyc2.core.init7.net (193.47.153.234)  84.784 ms  76.640 ms 77.631 ms
12  r1lon2.core.init7.net (77.109.128.14)  148.050 ms  147.872 ms 147.906 ms
13  r1bsl1.core.init7.net (77.109.128.102)  169.217 ms  163.665 ms  202.439 ms
14  r1bsl3.core.init7.net (82.197.168.18)  238.483 ms  238.570 ms 238.471 ms
15  r1zrh8.core.init7.net (82.197.168.74)  202.187 ms r1glb1.core.init7.net (77.109.128.238)  228.406 ms  228.315 ms
16  r1zug2.core.init7.net (82.197.168.238)  202.015 ms  201.878 ms  201.870 ms
17  * r1glb1.core.init7.net (77.109.140.205)  227.998 ms *
18  empty.init7.net (77.109.141.139)  210.102 ms  210.027 ms 227.854 ms
19  117-114-203-185.place5.ungleich.ch (185.203.114.117)  167.822 ms  167.736 ms  166.978 ms

Looks like a packet got dropped on hop 17 this time

ping  stopcta.info
PING stopcta.info (185.203.114.117) 56(84) bytes of data.
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=1 ttl=44 time=169 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=2 ttl=44 time=167 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=3 ttl=44 time=163 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=4 ttl=44 time=163 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=5 ttl=44 time=163 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=6 ttl=44 time=166 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=7 ttl=44 time=163 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=8 ttl=44 time=165 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=9 ttl=44 time=171 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=10 ttl=44 time=164 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=11 ttl=44 time=163 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=12 ttl=44 time=163 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=13 ttl=44 time=165 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=14 ttl=44 time=165 ms
64 bytes from 117-114-203-185.place5.ungleich.ch (185.203.114.117): icmp_seq=15 ttl=44 time=163 ms

--- stopcta.info ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14197ms
rtt min/avg/max/mdev = 163.174/165.347/171.354/2.384 ms

The ping times are a little more interesting... Pretty stable and in 15 seconds, no drops.

with and without name resolution show no RTT lag betwen them so the problem looks to be as the traffic transitions to telia.net and then get's worse at init7

This isn't helped because the path from roadrunner (I think that what rr.com used to be) has several hops all by itself.  Mine go concast -> telia with llow RTT