stefansundin / traceroute-mapper

Map your traceroutes easily.
https://stefansundin.github.io/traceroute-mapper/
GNU Affero General Public License v3.0
285 stars 27 forks source link

It turns out that the $traceroute never come to an end #1

Open majorcool opened 8 years ago

majorcool commented 8 years ago

When I execute $traceroute, it seems like that it never stop, as a result, it never jump to the mapper webpage. Hope someone can tell me how to resolve this.(Mac+zsh)

stefansundin commented 8 years ago

If there's a host blocking ICMP traffic somewhere along the route, traceroute might never know when it has "arrived", and it's even harder to know this when you can't see any output. If this happens then it will just go on until traceroute stops (on mac it's after 64 hops). I suggest just running traceroute manually and then copying the output to the website. If you see a lot of lines with * showing up at the end, this is most likely what is happening.

Example:

$ traceroute amazonaws.com
[ ... ]
 6  bu-ether26.lsancarc0yw-bcr00.tbone.rr.com (66.109.3.230)  42.638 ms  39.093 ms  42.319 ms
 7  bu-ether11.tustca4200w-bcr00.tbone.rr.com (66.109.6.5)  60.588 ms  54.393 ms  78.709 ms
 8  bu-ether16.dllstx976iw-bcr00.tbone.rr.com (66.109.6.1)  52.357 ms  60.392 ms  75.144 ms
 9  0.ae4.pr0.dfw10.tbone.rr.com (66.109.9.105)  74.019 ms
    0.ae1.pr0.dfw10.tbone.rr.com (66.109.6.179)  59.598 ms  51.696 ms
10  24.27.236.27 (24.27.236.27)  55.293 ms  146.672 ms  169.692 ms
11  * * *
12  * * *
13  * 54.240.229.20 (54.240.229.20)  92.032 ms
    54.240.229.0 (54.240.229.0)  84.410 ms
14  * 54.240.229.172 (54.240.229.172)  207.366 ms
    54.240.229.168 (54.240.229.168)  87.961 ms
15  54.240.228.143 (54.240.228.143)  136.652 ms
    54.240.229.131 (54.240.229.131)  172.105 ms
    54.240.229.133 (54.240.229.133)  149.583 ms
16  54.239.108.182 (54.239.108.182)  172.648 ms
    54.239.108.186 (54.239.108.186)  168.964 ms
    54.239.109.94 (54.239.109.94)  170.331 ms
17  54.239.109.79 (54.239.109.79)  169.291 ms
    54.239.108.199 (54.239.108.199)  137.537 ms
    54.239.109.79 (54.239.109.79)  130.623 ms
18  72.21.222.157 (72.21.222.157)  170.836 ms
    205.251.245.236 (205.251.245.236)  130.101 ms *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  205.251.248.94 (205.251.248.94)  93.700 ms * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *
tom-snow commented 1 year ago

I found that when I use Mac surge enhanced mode, the result of my running traceroute becomes:

traceroute to 154.40.47.72 (154.40.47.72), 64 hops max, 72 byte packets
 1  198.18.0.1 (198.18.0.1)  18.337 ms
 2  *
 3  *
 4  *
 5  *
 6  *
...
52 *
...