> On Sep 11, 2015, at 11:52 AM, Paul Koning <paulkon...@comcast.net> wrote: > > >> On Sep 11, 2015, at 11:40 AM, Jay Jaeger <cu...@charter.net> wrote: >> >> On 9/10/2015 8:32 PM, Jon Elson wrote: >> >>> >>> So, I wonder if I can ask classiccmp members, especially in the US, to >>> check if they can view this page: >>> http://members.iinet.net.au/~daveb/simplex/simplex.html >>> >>> >> >> I cannot make a connection. My DNS is able to resolve the address. >> >> ISP is Charter cable, Madison WI (Fitchburg, from the DNS name), then to >> Eau Claire WI, then Chicago, IL where it looks like they apparently peer >> with Cogent. >> >> As with others, the traceroute stopped at Cogent. Note that this may >> mean that the next hop after that blocks all of the packets or it could >> mean that the next hop is blocking just the traceroute packets. >> >> JRJ >> >> 1 * * * >> 2 dtr01ftbgwi-tge-0-6-0-3.ftbg.wi.charter.com (96.34.25.58) 15.413 ms >> 16.531 ms 16.524 ms >> 3 crr01ftbgwi-bue-4.ftbg.wi.charter.com (96.34.18.108) 23.528 ms >> 21.479 ms 23.501 ms >> 4 crr01euclwi-bue-1.eucl.wi.charter.com (96.34.16.77) 21.431 ms * * >> 5 bbr01euclwi-bue-4.eucl.wi.charter.com (96.34.2.4) 21.157 ms 21.153 >> ms 21.318 ms >> 6 bbr02euclwi-bue-5.eucl.wi.charter.com (96.34.0.7) 25.319 ms 16.876 >> ms 22.938 ms >> 7 bbr01chcgil-bue-1.chcg.il.charter.com (96.34.0.9) 25.460 ms 26.958 >> ms 23.483 ms >> 8 bbr02chcgil-bue-6.chcg.il.charter.com (96.34.0.67) 26.751 ms >> 27.724 ms 27.695 ms >> 9 te0-18-0-2.ccr41.ord03.atlas.cogentco.com (38.122.181.65) 25.728 ms >> 30.118 ms 28.197 ms >> 10 be2216.ccr41.ord01.atlas.cogentco.com (154.54.24.201) 27.315 ms >> 27.427 ms be2217.ccr42.ord01.atlas.cogentco.com (154.54.24.205) 27.389 ms >> 11 be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85) 41.659 ms >> be2157.ccr22.mci01.atlas.cogentco.com (154.54.6.117) 40.758 ms 38.666 ms >> 12 be2432.ccr21.dfw01.atlas.cogentco.com (154.54.3.133) 47.510 ms >> be2433.ccr22.dfw01.atlas.cogentco.com (154.54.3.213) 53.865 ms >> be2432.ccr21.dfw01.atlas.cogentco.com (154.54.3.133) 52.515 ms >> 13 be2441.ccr21.iah01.atlas.cogentco.com (154.54.41.65) 53.141 ms >> be2443.ccr22.iah01.atlas.cogentco.com (154.54.44.229) 55.853 ms >> be2441.ccr21.iah01.atlas.cogentco.com (154.54.41.65) 55.407 ms >> 14 be2066.ccr22.lax01.atlas.cogentco.com (154.54.7.54) 86.437 ms >> be2065.ccr21.lax01.atlas.cogentco.com (154.54.5.66) 89.222 ms 87.085 ms >> 15 be2017.ccr21.lax04.atlas.cogentco.com (154.54.0.237) 94.160 ms >> be2019.ccr21.lax04.atlas.cogentco.com (154.54.88.10) 90.385 ms 88.573 ms >> 16 * * * >> 17 * * * >> 18 * * * >> 19 * *^C > > I saw the same sort of thing but I let traceroute keep running. The result > is that it started giving real answers again just one or two hops later. > > Conclusion: hops 16-20ish are blocking traceroute packets. Later hops aren't. > > It's hard to be patient sometimes, but while * * * sometimes indicates "this > is as far as you get" it may also indicate just a few nodes that are not > cooperating with traceroute on a functional route.
Sorry, I misremembered the different traceroute runs. The one that goes into cogentco fails for me too, all the way to 64 hops. But I had a different traceroute run from a different location that shows gtt.net, then 5 lines of * * *, then ii.net and on to the destination. So * * * is not necessarily the sign of a black hole, though it can be that. paul