From maxtul at parkline.ru Fri Jun 9 10:03:55 2006 From: maxtul at parkline.ru (Max Tulyev) Date: Fri, 09 Jun 2006 12:03:55 +0400 Subject: [ipv6-wg] V6 connectivity Message-ID: <44892B6B.70603@parkline.ru> 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 From berni at birkenwald.de Fri Jun 9 10:14:44 2006 From: berni at birkenwald.de (Bernhard Schmidt) Date: Fri, 09 Jun 2006 10:14:44 +0200 Subject: [ipv6-wg] V6 connectivity In-Reply-To: <44892B6B.70603@parkline.ru> References: <44892B6B.70603@parkline.ru> Message-ID: <44892DF4.3080102@birkenwald.de> 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 I don't know whether 2a01:d8::/32 is supposed to be routed through GEANT (going through nordu.net suggests so), but currently I see it only through Sprint. The Sprint upstream of Nordunet has been a great joy for several occasions now (I have an IPv6-in-IPv6 tunnel to UNINETT for Multicast which is routed back to me via Sprint). 2: rt4.muc1.m-online.net 46.408ms 3: 2001:a60:0:101:89:1:1:9 asymm 4 48.232ms 4: ge-1-0-0-132.rt7.muc3.m-online.net asymm 5 80.360ms 5: ge-0-1-0-302-gar1.muc.cw.net asymm 6 47.831ms 6: so-4-3-0-dcr2.fra.cw.net asymm 7 57.416ms 7: so-4-0-0-dcr1.amd.cw.net asymm 8 71.665ms 8: so-3-0-0-zcr1.amt.cw.net asymm 9 70.195ms 9: nl-ams04a-re1-fe-0-0.ipv6.aorta.net 72.908ms 10: be-bru01a-re1-t-2.ipv6.aorta.net 77.627ms 11: uk-lon01a-re1-t-2.ipv6.aorta.net asymm 12 83.444ms 12: us-nyc02a-re2-t-0.ipv6.aorta.net asymm 13 151.593ms 13: us-nyc02a-re1-fe-0-0.ipv6.aorta.net asymm 14 154.725ms 14: sprarpa-gw2.us.ipv6.aorta.net asymm 15 169.199ms 15: sl-s1v6-nyc-t-1000.sprintv6.net asymm 16 184.698ms 16: sl-bb1v6-sto-t-101.sprintv6.net asymm 17 281.296ms 17: 2001:7f8:d:fb::24 221. 74ms 18: se-kth.nordu.net 219.620ms 19: SE-gw.RUN.net asymm 18 223.267ms 20: 2001:b08:b08:3::1 asymm 19 239.308ms 21: 2001:b08:0:2::2 asymm 20 244.649ms 22: 2a01:d8:0:1::4 asymm 21 246. 81ms 23: 2a01:d8:0:99:211:11ff:fe1f:bfc9 asymm 22 246.726ms reached Resume: pmtu 1280 hops 23 back 22 I suggest you kick Nordunet/GEANT to transit this prefix (if it is academic) or try to get a better upstream. > And some parts of v6 Internet is completly unreachable. Is it my bug > or real situation? It is a real problem, but not a common one in IPv6. Regards, Bernhard > From rogerj at jorgensen.no Fri Jun 9 10:17:30 2006 From: rogerj at jorgensen.no (Roger Jorgensen) Date: Fri, 9 Jun 2006 10:17:30 +0200 (CEST) Subject: [ipv6-wg] V6 connectivity In-Reply-To: <44892B6B.70603@parkline.ru> References: <44892B6B.70603@parkline.ru> Message-ID: On Fri, 9 Jun 2006, Max Tulyev wrote: > Hi! > > I see v6 connectivity is much worse than v4: > > And some parts of v6 Internet is completly unreachable. Is it my bug or > real situation? >From my point of view it looks you're just not well connected really. Not often I have to cross the atlantic twice to get to someone anymore, over a year since last I saw it. Anyway, I'm just a simple downstream but here are my two AS-path's for you 6830 6175 2603 3343 5537 and the other are 30071 3257 6175 2603 3343 5537 Would suggest you get your another transit provider in Europe really, should solve most of your problem. If not full transit so atleast partial. -- ------------------------------ Roger Jorgensen | roger at jorgensen.no | - IPv6 is The Key! ------------------------------------------------------- From mohacsi at niif.hu Fri Jun 9 10:17:40 2006 From: mohacsi at niif.hu (Mohacsi Janos) Date: Fri, 9 Jun 2006 10:17:40 +0200 (CEST) Subject: [ipv6-wg] V6 connectivity In-Reply-To: <44892B6B.70603@parkline.ru> References: <44892B6B.70603@parkline.ru> Message-ID: <20060609101608.Y10068@mignon.ki.iif.hu> 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? > According to your test, and my quick test, it seems to me that there is some IPv6 connectivity problem inside Surfnet. Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 > -- > WBR, > Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO) > "Garant-Park-Telecom", +7 095 783-3-783 > > From thuthuy at vnnic.net.vn Fri Jun 9 11:02:33 2006 From: thuthuy at vnnic.net.vn (Thu Thuy) Date: Fri, 9 Jun 2006 16:02:33 +0700 Subject: [ipv6-wg] 6to4 address utilisation Message-ID: <006a01c68ba3$7206dba0$100977cb@thuthuy> Hi, I have a question about 6to4 address utilisation. May i post it here ? Thanks everyone for your guidance. 6to4 is a tunnel method. From an IPv4 address, we have /48 6to4 IPv6 space. So i'm wonder if this /48 range can be commonly used for our IPv6 network (workstations, servers) like native IPv6, or it just be used only for tunnel, to connect native IPv6 lands. Thank you once more, Thu Thuy Development & Research Department. Vietnam Internet Network Information Center - VNNIC. From marko.veelma at data.ee Fri Jun 9 10:08:28 2006 From: marko.veelma at data.ee (Marko Veelma) Date: Fri, 9 Jun 2006 11:08:28 +0300 (EEST) Subject: [ipv6-wg] V6 connectivity In-Reply-To: <44892B6B.70603@parkline.ru> References: <44892B6B.70603@parkline.ru> Message-ID: 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 > From jako.andras at eik.bme.hu Fri Jun 9 10:14:06 2006 From: jako.andras at eik.bme.hu (JAKO Andras) Date: Fri, 9 Jun 2006 10:14:06 +0200 (CEST) Subject: [ipv6-wg] V6 connectivity In-Reply-To: <44892B6B.70603@parkline.ru> References: <44892B6B.70603@parkline.ru> Message-ID: Hi Max, > 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 > [...] > > And some parts of v6 Internet is completly unreachable. Is it my bug or real > situation? Please take a look at the recent ipv6-ops@ thread with the subject "Outdated bogon filtering seems pervasive.." You'll find the archives here: http://lists.cluenet.de/pipermail/ipv6-ops/2006-June/thread.html Regards, Andras From james at ripe.net Wed Jun 28 14:35:23 2006 From: james at ripe.net (James Aldridge) Date: Wed, 28 Jun 2006 14:35:23 +0200 Subject: [ipv6-wg] IPv6 access to ftp.ripe.net Message-ID: <20060628123523.BDC402F592@herring.ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, IPv6 access to ftp.ripe.net is currently not possible. IPv4 access is unaffected. The current ScreenOS firewall software is unable to support extended passive-mode FTP. We have therefore temporarily removed the AAAA record for ftp.ripe.net from the DNS. We hope to restore IPv6 access as quickly as possible and will inform you when this occurs. We apologise for any inconvenience. Regards, James Aldridge Systems & Network Engineer RIPE NCC Operations Group