11 Sep
2015
11 Sep
'15
10:41 a.m.
On 9/11/2015 10:52 AM, Paul Koning wrote:
Not me.
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Also, if an ISP is actually blocking traceroute packets, then the trace
will STOP THERE - it can't get past that point.
JRJ
On Sep 11, 2015, at 11:40 AM, Jay Jaeger
<cube1 at charter.net> wrote:
I cannot make a connection. My DNS is able to resolve the address.
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.
paul