• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How 'bout them long traceroutes?

Zap

Elite Member
I'm kind of limited to 30 hops with the Windows tracert function, but I got 27 to sis.com.tw from home (Roadrunner). From school I get 21 to the same site. I'm tracing from Southeast Wisconsin.

Anyone hit 30 to any site?

Tracing route to sis.com.tw [203.67.208.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 23 ms 10.82.224.1
3 8 ms 6 ms 5 ms srp2-0.ungvwiykvl-rtr2.wi.rr.com [24.160.226.65]

4 7 ms 8 ms 7 ms srp10-0.milwwirtco-rtr1.wi.rr.com [24.160.224.1]

5 27 ms 25 ms 25 ms RDC-24-94-160-33.kc.rr.com [24.94.160.33]
6 201 ms 31 ms 31 ms ge-5-1-203.hsa1.StLouis1.Level3.net [4.79.132.13
]
7 30 ms 44 ms 30 ms ae-11-11.car2.StLouis1.Level3.net [4.69.132.186]

8 23 ms 36 ms 36 ms ae-4-4.ebr2.Chicago1.Level3.net [4.69.132.190]
9 24 ms 23 ms 21 ms ae-23-54.car3.Chicago1.Level3.net [4.68.101.103]

10 23 ms 22 ms 31 ms ge-2-1-0.r02.chcgil09.us.bb.gin.ntt.net [129.250
.9.117]
11 23 ms 26 ms 28 ms as-0.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
42]
12 70 ms 71 ms 70 ms p64-2-1-0.r20.sttlwa01.us.bb.gin.ntt.net [129.25
0.5.28]
13 82 ms 85 ms 82 ms p64-2-2-0.r21.mlpsca01.us.bb.gin.ntt.net [129.25
0.4.23]
14 212 ms 209 ms 206 ms p64-0-1-0.r21.tokyjp01.jp.bb.gin.ntt.net [129.25
0.3.206]
15 225 ms 230 ms 223 ms p16-2-0-0.r01.taiptw01.tw.bb.gin.ntt.net [129.25
0.4.202]
16 238 ms 239 ms 238 ms ge-2-0-0.a01.taiptw01.tw.ra.gin.ntt.net [61.58.3
2.226]
17 241 ms 237 ms 245 ms 61.58.33.126
18 255 ms 257 ms 257 ms R58-41.seed.net.tw [139.175.58.41]
19 256 ms 257 ms 256 ms R56-137.seed.net.tw [139.175.56.137]
20 257 ms 258 ms 257 ms R56-189.seed.net.tw [139.175.56.189]
21 257 ms 256 ms 255 ms R59-17.seed.net.tw [139.175.59.17]
22 259 ms 258 ms 257 ms R58-102.seed.net.tw [139.175.58.102]
23 259 ms 260 ms 258 ms sh39-97.dialup.seed.net.tw [139.175.39.97]
24 263 ms 266 ms 264 ms h2-192-72-157.seed.net.tw [192.72.157.2]
25 * * * Request timed out.
26 * * * Request timed out.
27 265 ms 263 ms 261 ms dns1.sis.com.tw [203.67.208.66]

Trace complete.
 
Hey, another SW Wisconsiner. I'm on Charter and I think they require ultra small ICMP packets or something like that as normal traceroutes don't work. You on Charter too?
 
frank@frank-desktop:~$ tracepath iwill.com.tw -n
1: 192.168.1.137 0.482ms pmtu 1500
1: 192.168.1.1 2.565ms
2: 73.162.98.1 13.915ms
3: 68.87.155.161 22.005ms
4: 68.87.144.157 36.671ms
5: 12.118.88.5 asymm 9 32.342ms
6: no reply
7: no reply
8: 12.122.82.1 asymm 10 17.095ms
9: 129.250.8.157 asymm 12 28.598ms
10: 129.250.2.33 asymm 12 34.584ms
11: 129.250.5.16 asymm 16 104.245ms
12: 129.250.4.16 asymm 16 96.804ms
13: 129.250.4.23 asymm 15 94.793ms
14: 129.250.3.206 203.739ms
15: 129.250.4.202 asymm 17 247.860ms
16: 61.58.32.226 asymm 17 247.904ms
17: 61.58.33.134 249.415ms
18: 139.175.58.41 asymm 23 273.828ms
19: 139.175.58.78 asymm 22 274.048ms
20: 192.72.123.182 asymm 23 274.781ms
21: 211.78.152.25 asymm 23 275.864ms
22: 211.78.152.9 asymm 24 274.423ms
23: 61.66.239.249 asymm 26 277.511ms
24: no reply
25: 61.66.176.15 asymm 26 309.597ms
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
frank@frank-desktop:~$
 
Originally posted by: cmv
Hey, another SW Wisconsiner. I'm on Charter and I think they require ultra small ICMP packets or something like that as normal traceroutes don't work. You on Charter too?

SE Wisconsin, on RR.

Originally posted by: OrganizedChaos
by any chance is this your homework?

😱 DOH, yes. No problems doing it on my own, but get extra credit if I get longest trace out of whole class.
21

Second one, the trace dies after a while (continuous request timed out).

Same thing with Iwill's site, indeed can't even ping it, but the site comes up albeit slowly. Interesting... 16 DIMM slot server boards... Mmmm.

I need to go with sites that will finish tracing.

Originally posted by: ATLien247
Use the -h switch with tracert to specify maximum hops above the default...

Thanks for the tip!

Well, seems like the sites where the trace dies with "timed out" never finish tracing.
 
Know any address off hand? What's their domain name end in? One thing I've noticed is that I would trace to some "foreign" site only to find it is co-located somewhere here. I did find one site ending in .TW that takes a full 30 hops w/o timing out on any of them. Will probably use that one. Hmmm, wonder if I can artificially increase the hops by 1, by daisy-chaining broadband routers... LOL.
 
Originally posted by: Zap
Know any address off hand? What's their domain name end in? One thing I've noticed is that I would trace to some "foreign" site only to find it is co-located somewhere here. I did find one site ending in .TW that takes a full 30 hops w/o timing out on any of them. Will probably use that one. Hmmm, wonder if I can artificially increase the hops by 1, by daisy-chaining broadband routers... LOL.

2 routers, set up static routes so that they route traffic to each other, you will get infinate hops if you do it right.
 
Originally posted by: Zolty

2 routers, set up static routes so that they route traffic to each other, you will get infinate hops if you do it right.

That's what I thought immediately, just setup a routing loop and they'll keep going until the TTL expires. I guess you could set that to 256 and have 256 hops.
 
Back
Top