Nice Traffic Engineering by Swisscom ...
www.bluewin.ch vs. www.swisscom.ch
traceroute www.bluewin.ch traceroute to www.bluewin.ch (195.186.3.80), 64 hops max, 44 byte packets 1 public-gw (212.101.4.129) 0.472 ms 0.422 ms 0.422 ms 2 zuchwil-b-xmr1-v4 (212.101.0.161) 0.356 ms 0.305 ms 0.273 ms 3 zurich-t-bb5-v-2 (212.101.0.231) 2.210 ms 2.072 ms 2.086 ms 4 sl-gw10-zur-5-0-0.sprintlink.net (80.93.9.145) 2.492 ms 2.435 ms * 5 sl-bb20-zur-13-0.sprintlink.net (80.93.8.37) 2.267 ms 2.212 ms 2.546 ms 6 sl-bb20-fra-11-1.sprintlink.net (213.206.129.155) 8.045 ms 7.715 ms 7.568 ms 7 sl-bb21-fra-15-0.sprintlink.net (217.147.96.34) 7.731 ms 7.569 ms 7.551 ms 8 ge-6-13.car1.Frankfurt1.Level3.net (4.68.111.141) 24.140 ms * 24.193 ms 9 ae-31-55.ebr1.Frankfurt1.Level3.net (4.68.118.158) 19.180 ms ae-31-53.ebr1.Frankfurt1.Level3.net (4.68.118.94) 19.079 ms ae-32-54.ebr2.Frankfurt1.Level3.net (4.68.118.126) 19.027 ms 10 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 24.612 ms ae-1-100.ebr1.Frankfurt1.Level3.net (4.69.132.125) 23.228 ms ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 29.033 ms 11 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 35.436 ms ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 112.251 ms ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 30.059 ms 12 ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 111.073 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 115.081 ms ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 104.589 ms 13 ae-74-74.ebr4.Washington1.Level3.net (4.69.134.181) 104.390 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 104.975 ms ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 108.475 ms 14 ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 107.689 ms ae-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 173.372 ms 161.967 ms 15 ae-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 161.863 ms ae-2.ebr3.SanJose1.Level3.net (4.69.132.9) 167.725 ms ae-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 172.804 ms 16 * ae-2.ebr3.SanJose1.Level3.net (4.69.132.9) 167.666 ms ae-73-73.csw2.SanJose1.Level3.net (4.69.134.230) 167.334 ms 17 ae-73-73.csw2.SanJose1.Level3.net (4.69.134.230) 178.840 ms ae-83-83.csw3.SanJose1.Level3.net (4.69.134.234) 179.588 ms ge-1-3-0-89.bbr2.SanJose1.Level3.net (4.68.18.130) 168.250 ms 18 ge-1-3-0-89.bbr2.SanJose1.Level3.net (4.68.18.130) 167.554 ms so-14-0.hsa4.SanJose1.Level3.net (4.68.114.158) 167.686 ms ge-1-3-0-89.bbr2.SanJose1.Level3.net (4.68.18.130) 168.224 ms 19 * so-14-0.hsa4.SanJose1.Level3.net (4.68.114.158) 168.031 ms * 20 * * * 21 * * * 22 i79zhb-005-pos4-0.bb.ip-plus.net (138.187.159.5) 654.770 ms * i00nye-005-pos5-2.bb.ip-plus.net (138.187.159.9) 657.152 ms 23 * * * 24 tge3-3.bwrt1inb.bluewin.ch (195.186.0.113) 661.318 ms * * 25 * * * 26 * * *
traceroute to www.swisscom.ch (138.190.1.60), 64 hops max, 44 byte packets 1 public-gw (212.101.4.129) 0.717 ms 0.574 ms 0.397 ms 2 zuchwil-b-xmr1-v4 (212.101.0.161) 0.342 ms 0.407 ms 0.357 ms 3 zurich-t-bb5-v-2 (212.101.0.231) 2.280 ms 2.030 ms 2.050 ms 4 sl-gw10-zur-5-0-0.sprintlink.net (80.93.9.145) 2.510 ms 2.259 ms * 5 sle-swiss3-1-0.sprintlink.net (80.93.9.66) 2.362 ms 2.189 ms 2.207 ms 6 i79tix-015-gig2-13.bb.ip-plus.net (138.187.129.58) 153.872 ms 208.285 ms 3.572 ms 7 i79zhh-015-xxx1-4.bb.ip-plus.net (138.187.129.73) 18.265 ms 2.460 ms 2.306 ms 8 i64beb-000-gig0-3.bb.ip-plus.net (138.187.130.161) 4.573 ms 4.601 ms 4.274 ms 9 i64beb-061-gig0-1.bb.ip-plus.net (138.187.156.142) 5.306 ms 5.153 ms 5.154 ms 10 cit-00-lb-ser1-0.ce.ip-plus.net (164.128.156.242) 6.172 ms 5.535 ms 7.259 ms 11 * * *
Regards Erich
well, it's less than 30 hops, so it should be ok :)
--- Erich Hohermuth eh@solnet.ch wrote:
Nice Traffic Engineering by Swisscom ...
www.bluewin.ch vs. www.swisscom.ch
traceroute www.bluewin.ch traceroute to www.bluewin.ch (195.186.3.80), 64 hops max, 44 byte packets 19 * so-14-0.hsa4.SanJose1.Level3.net (4.68.114.158) 168.031 ms * 20 * * * 21 * * * 22 i79zhb-005-pos4-0.bb.ip-plus.net (138.187.159.5) 654.770 ms * i00nye-005-pos5-2.bb.ip-plus.net (138.187.159.9) 657.152 ms 23 * * * 24 tge3-3.bwrt1inb.bluewin.ch (195.186.0.113) 661.318 ms * * 25 * * * 26 * * *
Where's the problem? Your traffic reaches with Hop 3 already Zurich...
Cheers, Günti
-----Ursprüngliche Nachricht----- Von: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] Im Auftrag von Erich Hohermuth Gesendet: Freitag, 6. Juli 2007 15:35 An: swinog@swinog.ch Betreff: [swinog] Route of the day
Nice Traffic Engineering by Swisscom ...
www.bluewin.ch vs. www.swisscom.ch
traceroute www.bluewin.ch traceroute to www.bluewin.ch (195.186.3.80), 64 hops max, 44 byte packets 1 public-gw (212.101.4.129) 0.472 ms 0.422 ms 0.422 ms 2 zuchwil-b-xmr1-v4 (212.101.0.161) 0.356 ms 0.305 ms 0.273 ms 3 zurich-t-bb5-v-2 (212.101.0.231) 2.210 ms 2.072 ms 2.086 ms 4 sl-gw10-zur-5-0-0.sprintlink.net (80.93.9.145) 2.492 ms 2.435 ms * 5 sl-bb20-zur-13-0.sprintlink.net (80.93.8.37) 2.267 ms 2.212 ms 2.546 ms 6 sl-bb20-fra-11-1.sprintlink.net (213.206.129.155) 8.045 ms 7.715 ms 7.568 ms 7 sl-bb21-fra-15-0.sprintlink.net (217.147.96.34) 7.731 ms 7.569 ms 7.551 ms 8 ge-6-13.car1.Frankfurt1.Level3.net (4.68.111.141) 24.140 ms * 24.193 ms 9 ae-31-55.ebr1.Frankfurt1.Level3.net (4.68.118.158) 19.180 ms ae-31-53.ebr1.Frankfurt1.Level3.net (4.68.118.94) 19.079 ms ae-32-54.ebr2.Frankfurt1.Level3.net (4.68.118.126) 19.027 ms 10 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 24.612 ms ae-1-100.ebr1.Frankfurt1.Level3.net (4.69.132.125) 23.228 ms ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 29.033 ms 11 ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 35.436 ms ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 112.251 ms ae-2.ebr2.Paris1.Level3.net (4.69.132.141) 30.059 ms 12 ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 111.073 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 115.081 ms ae-5.ebr2.Washington1.Level3.net (4.69.132.113) 104.589 ms 13 ae-74-74.ebr4.Washington1.Level3.net (4.69.134.181) 104.390 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 104.975 ms ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 108.475 ms 14 ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 107.689 ms ae-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 173.372 ms 161.967 ms 15 ae-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 161.863 ms ae-2.ebr3.SanJose1.Level3.net (4.69.132.9) 167.725 ms ae-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 172.804 ms 16 * ae-2.ebr3.SanJose1.Level3.net (4.69.132.9) 167.666 ms ae-73-73.csw2.SanJose1.Level3.net (4.69.134.230) 167.334 ms 17 ae-73-73.csw2.SanJose1.Level3.net (4.69.134.230) 178.840 ms ae-83-83.csw3.SanJose1.Level3.net (4.69.134.234) 179.588 ms ge-1-3-0-89.bbr2.SanJose1.Level3.net (4.68.18.130) 168.250 ms 18 ge-1-3-0-89.bbr2.SanJose1.Level3.net (4.68.18.130) 167.554 ms so-14-0.hsa4.SanJose1.Level3.net (4.68.114.158) 167.686 ms ge-1-3-0-89.bbr2.SanJose1.Level3.net (4.68.18.130) 168.224 ms 19 * so-14-0.hsa4.SanJose1.Level3.net (4.68.114.158) 168.031 ms * 20 * * * 21 * * * 22 i79zhb-005-pos4-0.bb.ip-plus.net (138.187.159.5) 654.770 ms * i00nye-005-pos5-2.bb.ip-plus.net (138.187.159.9) 657.152 ms 23 * * * 24 tge3-3.bwrt1inb.bluewin.ch (195.186.0.113) 661.318 ms * * 25 * * * 26 * * *
traceroute to www.swisscom.ch (138.190.1.60), 64 hops max, 44 byte packets 1 public-gw (212.101.4.129) 0.717 ms 0.574 ms 0.397 ms 2 zuchwil-b-xmr1-v4 (212.101.0.161) 0.342 ms 0.407 ms 0.357 ms 3 zurich-t-bb5-v-2 (212.101.0.231) 2.280 ms 2.030 ms 2.050 ms 4 sl-gw10-zur-5-0-0.sprintlink.net (80.93.9.145) 2.510 ms 2.259 ms * 5 sle-swiss3-1-0.sprintlink.net (80.93.9.66) 2.362 ms 2.189 ms 2.207 ms 6 i79tix-015-gig2-13.bb.ip-plus.net (138.187.129.58) 153.872 ms 208.285 ms 3.572 ms 7 i79zhh-015-xxx1-4.bb.ip-plus.net (138.187.129.73) 18.265 ms 2.460 ms 2.306 ms 8 i64beb-000-gig0-3.bb.ip-plus.net (138.187.130.161) 4.573 ms 4.601 ms 4.274 ms 9 i64beb-061-gig0-1.bb.ip-plus.net (138.187.156.142) 5.306 ms 5.153 ms 5.154 ms 10 cit-00-lb-ser1-0.ce.ip-plus.net (164.128.156.242) 6.172 ms 5.535 ms 7.259 ms 11 * * *
Regards Erich
internet@guentensperger.org wrote:
Where's the problem? Your traffic reaches with Hop 3 already Zurich...
Maybe the part where it takes another 600ms+ to actually reach the final destination in Switzerland again? :)
22 i79zhb-005-pos4-0.bb.ip-plus.net (138.187.159.5) 654.770 ms * i00nye-005-pos5-2.bb.ip-plus.net (138.187.159.9) 657.152 ms 23 * * * 24 tge3-3.bwrt1inb.bluewin.ch (195.186.0.113) 661.318 ms * * 25 * * * 26 * * *
Instead of the 8ms to reach that same host from the other trace.
/me also wonders when "ISP's" start to drop those silly ICMP filters which are really far from helpful when trying to debug issues.
Greets, Jeroen
Jeroen
I still don't see the problem. Where and when can you have such a round-trip for free? Go at the "Zuerifaescht" and you will have to pay quite a lot for a much shorter ride. ;-))
PS: As Stanislav wrote, it's still below 30 hops.
Happy weekend, Günti
-----Ursprüngliche Nachricht----- Von: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] Im Auftrag von Jeroen Massar Gesendet: Freitag, 6. Juli 2007 16:58 An: swinog@swinog.ch Betreff: Re: AW: [swinog] Route of the day
internet@guentensperger.org wrote:
Where's the problem? Your traffic reaches with Hop 3 already Zurich...
Maybe the part where it takes another 600ms+ to actually reach the final destination in Switzerland again? :)
22 i79zhb-005-pos4-0.bb.ip-plus.net (138.187.159.5) 654.770 ms * i00nye-005-pos5-2.bb.ip-plus.net (138.187.159.9) 657.152 ms 23 * * * 24 tge3-3.bwrt1inb.bluewin.ch (195.186.0.113) 661.318 ms * * 25 * * * 26 * * *
Instead of the 8ms to reach that same host from the other trace.
/me also wonders when "ISP's" start to drop those silly ICMP filters which are really far from helpful when trying to debug issues.
Greets, Jeroen
On the Fri, Jul 06, 2007 at 05:04:35PM +0200, robert@guentensperger.org blubbered:
Hoi.
I still don't see the problem. Where and when can you have such a round-trip for free? Go at the "Zuerifaescht" and you will have to pay quite a lot for a much shorter ride. ;-))
And the packets do have stickers from all the places they visited on their trip?
CU, Venty
Instead of the 8ms to reach that same host from the other trace.
/me also wonders when "ISP's" start to drop those silly ICMP filters which are really far from helpful when trying to debug issues.
well. icmp is devil, because you can tunnel everything with it, but more used is TCP/UDP so why not block those two unsecure ip-protocol as well ? </paranoiamode> some admin block icmp echo so people can's figure out where the network bottleneck is, or not let discover the fact of carrying traffic over an rented MPLS instead of the marketing propagated "own fiberconnection between x- y" others don't like game-freaks complaining about an 25msec RTT...
all good reason to block icmp-8 ;-)
just my small opinion
-
Erich Hohermuth -
internet＠guentensperger.org -
Jeroen Massar -
Martin Ebnoether -
robert＠guentensperger.org -
roger＠mgz.ch -
Stanislav Sinyagin