[ipv6-wg] V6 connectivity
- Previous message (by thread): [ipv6-wg] V6 connectivity
- Next message (by thread): [ipv6-wg] V6 connectivity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marko Veelma
marko.veelma at data.ee
Fri Jun 9 10:08:28 CEST 2006
You should ask your upstreams. I don't have any problem traceroute to kite-www.ripe.net (2001:610:240:0:a843::8), 30 hops max, 40 byte packets 1 r21-ge-0-3-0-201-Tln-TIX.EE.DataBone.net (2001:ad0:1:1:290:6900:c96e:5c5d) 0.397 ms 0.444 ms 0.494 ms 2 r20-lo0-Tln-TIX.EE.DataBone.net (2001:ad0:fe:0:290:6900:650:5000) 0.709 ms 0.570 ms 0.659 ms 3 ar1.arn2.gblx.net (2001:ad0:ff:20::49) 6.322 ms 6.323 ms 6.276 ms 4 2001:450:2001:1000:0:670:1708:179 32.303 ms 32.235 ms 32.331 ms 5 Gi6-0.BR1.Amsterdam1.surf.net (2001:610:ff:13::1) 35.730 ms 35.582 ms 35.538 ms 6 Lo0.AR5.Amsterdam1.surf.net (2001:610:25:5006::6) 36.084 ms 35.766 ms 35.914 ms 7 * * * 8 nikipv6.ripe.net (2001:7f8:1::a500:3333:1) 36.996 ms 36.945 ms 37.361 ms 9 kite-www.ripe.net (2001:610:240:0:a843::8) 36.894 ms 36.559 ms 36.466 ms -- Cougar On Fri, 9 Jun 2006, Max Tulyev wrote: > Hi! > > I see v6 connectivity is much worse than v4: > > traceroute to kite-www.ripe.net (2001:610:240:0:a843::8) from > 2a01:d8:0:99:211:11ff:fe1f:bfc9, 30 hops max, 16 byte packets > 1 2a01:d8:0:99::1 (2a01:d8:0:99::1) 0.782 ms 0.719 ms 2.227 ms > 2 2a01:d8:0:1::1 (2a01:d8:0:1::1) 40.904 ms 2.346 ms 2.754 ms > 3 2001:b08:0:2::1 (2001:b08:0:2::1) 35.849 ms 7.533 ms 2.576 ms > 4 2001:b08:b08:3::2 (2001:b08:b08:3::2) 35.205 ms 25.399 ms 25.649 ms > 5 se-kth.nordu.net (2001:948:0:f02c::1) 29.649 ms 25.579 ms 25.545 ms > 6 se-ov.nordu.net (2001:948:0:f027::2) 33.705 ms 25.539 ms 25.927 ms > 7 dk-gw2.nordu.net (2001:948:0:f03f::2) 39.785 ms 33.901 ms 33.688 ms > 8 * * * > 9 * * * > 10 * * * > 11 * * * > 12 nikipv6.ripe.net (2001:7f8:1::a500:3333:1) 214.93 ms 226.989 ms 215.676 > ms > 13 kite-www.ripe.net (2001:610:240:0:a843::8) 214.484 ms 215.588 ms 221.891 > ms > > 1: greentheatre (195.209.50.18) 0.273ms pmtu 1500 > 1: gw.gpt.ru (195.209.50.1) 1.366ms > 2: LEO-MG-2.Garnet.ru (195.209.63.20) 57.568ms > 3: d2-msk-m9-ge0-0-0-v102.ruscomnet.ru (80.249.128.117) asymm 4 > 3.034ms > 4: c1-msk-m9-ge0-1-0.ruscomnet.ru (80.249.132.9) asymm 5 4.265ms > 5: d1-fft-as0.ruscomnet.ru (80.249.132.26) asymm 6 51.486ms > 6: gigabitethernet3-0.104.gw9.fft4.de.ALTER.NET (139.4.144.5) 51.952ms > 7: so-7-1-0.XR1.FFT4.ALTER.NET (149.227.48.25) asymm 8 > 52.247ms > 8: so-0-1-0.TR2.FFT1.ALTER.NET (146.188.8.138) asymm 9 52.400ms > 9: so-5-1-0.TR2.AMS2.ALTER.NET (146.188.2.169) asymm 10 58.617ms > 10: POS2-0.BR1.AMS3.ALTER.NET (146.188.3.218) 58.315ms > 11: Amsterdam1.ripe.net (195.69.144.68) 53.182ms > 12: kite.ripe.net (193.0.0.214) asymm 11 53.245ms > reached > Resume: pmtu 1500 hops 12 back 11 > > And some parts of v6 Internet is completly unreachable. Is it my bug or real > situation? > > -- > WBR, > Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO) > "Garant-Park-Telecom", +7 095 783-3-783 >
- Previous message (by thread): [ipv6-wg] V6 connectivity
- Next message (by thread): [ipv6-wg] V6 connectivity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]