Mailing List Archive

1 2 3 4 5 6  View All
Re: Test your connectivity for World IPv6 Day [ In reply to ]
On 8 Jun 2011, at 20:21, Nick Hilliard <nick@foobar.org> wrote:
>
> This issue is really no different to rogue dhcp servers appearing on internal networks in the late 1990s or rogue RIP speakings appearing on networks in the late 80s / early 90s. It's a layer 2 problem and must be treated as such.

Absolutely! Thanks for reminding us of the history.

Tony.
--
f.anthony.n.finch <dot@dotat.at> http://dotat.at/
Re: Test your connectivity for World IPv6 Day [ In reply to ]
Hi Tony,

On Wed, 2011-06-08 at 18:17 +0100, Tony Finch wrote:
> Niall O'Reilly <Niall.oReilly@ucd.ie> wrote:
> >
> > Apart from that, our Customer Support team has let me know that
> > W6D has turned out to be a non-event for them.
>
> We have had a little excitement caused by rogue RAs:
>
> http://fanf.livejournal.com/113996.html

Welcome to the world of IPv6 Tony! Glad (truly) to have you here. :)

Microsoft, please fix the ICS. Pain from this is only going to grow and
deploying batch scripts / reg files to users from help desks to disable
IPv6 is not a proper solution. There's going to be a lot of LAN's in
many years to come with absolutely no RA guard of any sort. Problems
occur even if there is proper native IPv6 announced.

Thanks,
Martin
Re: Test your connectivity for World IPv6 Day [ In reply to ]
On Wed, Jun 08, 2011 at 08:21:57PM +0100, Nick Hilliard wrote:
> On 08/06/2011 18:17, Tony Finch wrote:
> >We have had a little excitement caused by rogue RAs:
> >
> >http://fanf.livejournal.com/113996.html
>
> This issue is really no different to rogue dhcp servers appearing on
> internal networks in the late 1990s or rogue RIP speakings appearing on
> networks in the late 80s / early 90s. It's a layer 2 problem and must be
> treated as such.

I've had my department's diskless Suns slowly, one after another, been
taken out of service by rogue ARP announcments from a broken Linux
system in a neighbouring department in the same broadcast domain in the
1990s.

Just a data point.

-is
Re: Test your connectivity for World IPv6 Day - Explanation? [ In reply to ]
Le 8 juin 2011 à 17:34, Rémi Després a écrit :
...
> From here, a MAC OS X in a Free.com customer site, I have run a number of times the "ipv6eyechart.ripe.net" test (a great one BTW).
> All sites have been accessible with IPv6 enabled with two exceptions.
>
> T-online is
> - unreachable with IPv6 enabled
> - always reachable with IPv6 disabled
>
> Akamai dual-test
> - has been for a long time unreachable with IPv6 enabled (but OK now)
> - has always been reachable with IPv6 disabled

Would anyone have an explanation concerning T-online?
FWIW, the problem existed the day before W6D, and persists after it.

Regards,
RD
Re: Test your connectivity for World IPv6 Day - Explanation? [ In reply to ]
Am 09.06.2011 09:56, schrieb Rémi Després:
>
> Le 8 juin 2011 à 17:34, Rémi Després a écrit :
> ...
>> From here, a MAC OS X in a Free.com customer site, I have run a number of times the "ipv6eyechart.ripe.net" test (a great one BTW).
>> All sites have been accessible with IPv6 enabled with two exceptions.
>>
>> T-online is
>> - unreachable with IPv6 enabled
>> - always reachable with IPv6 disabled
>>
>> Akamai dual-test
>> - has been for a long time unreachable with IPv6 enabled (but OK now)
>> - has always been reachable with IPv6 disabled
>
> Would anyone have an explanation concerning T-online?
> FWIW, the problem existed the day before W6D, and persists after it.

I can not confirm this problem.

They startet earlier, that's right. Also one of the important servers
called within www.t-online.de was not reachable during the morning of
the 7 of june. But this problem is solved.

Now I see the www.t-online.de portal complete from a dualstack-host as
well from a ipv6-only host, the latter has a little less advertisements,
but without errors.




Regards,

Thomas

--

There’s no place like ::1

Thomas Schäfer (Systemverwaltung)
Ludwig-Maximilians-Universität
Centrum für Informations- und Sprachverarbeitung
Schellingstraße 10 Raum J407A
80799 München ☎ +49/89/2180-9706 ℻ +49/89/2180-9701
Re: Test your connectivity for World IPv6 Day - Explanation? [ In reply to ]
The problem of T-online accessibility has now disappeared.
Thanks to anyone who fixed something today.
Regards,
RD
Le 9 juin 2011 à 10:45, Thomas Schäfer a écrit :

> Am 09.06.2011 09:56, schrieb Rémi Després:
>>
>> Le 8 juin 2011 à 17:34, Rémi Després a écrit :
>> ...
>>> From here, a MAC OS X in a Free.com customer site, I have run a number of times the "ipv6eyechart.ripe.net" test (a great one BTW).
>>> All sites have been accessible with IPv6 enabled with two exceptions.
>>>
>>> T-online is
>>> - unreachable with IPv6 enabled
>>> - always reachable with IPv6 disabled
>>>
>>> Akamai dual-test
>>> - has been for a long time unreachable with IPv6 enabled (but OK now)
>>> - has always been reachable with IPv6 disabled
>>
>> Would anyone have an explanation concerning T-online?
>> FWIW, the problem existed the day before W6D, and persists after it.
>
> I can not confirm this problem.
>
> They startet earlier, that's right. Also one of the important servers called within www.t-online.de was not reachable during the morning of the 7 of june. But this problem is solved.
>
> Now I see the www.t-online.de portal complete from a dualstack-host as well from a ipv6-only host, the latter has a little less advertisements, but without errors.
>
>
>
>
> Regards,
>
> Thomas
>
> --
>
> There’s no place like ::1
>
> Thomas Schäfer (Systemverwaltung)
> Ludwig-Maximilians-Universität
> Centrum für Informations- und Sprachverarbeitung
> Schellingstraße 10 Raum J407A
> 80799 München ☎ +49/89/2180-9706 ℻ +49/89/2180-9701
>
Re: Usage statistics of "World IPv6 Day Tools"? [was: Test your connectivity for World IPv6 Day] [ In reply to ]
On May 27, 2011, at 8:58 AM, Mirjam Kuehne wrote:

Hi Mirjam, hello everyone else,

> The RIPE NCC is preparing some measurements for World IPv6 Day. One of them is the IPv6 eye chart, a web page that allows you to test your connectivity to selected dual-stacked web sites and World IPv6 participants. The goal is to see if an end user has connectivity problems to dual-stacked websites.
>
> You can read more on RIPE Labs:
>
> http://labs.ripe.net/Members/emileaben/world-ipv6-day-ipv6-eye-chart
>
> The test can be found here: http://ipv6eyechart.ripe.net/
>
> If you have any questions or want to be included in the test, please contact us at labs at ripe dot net.

First of all thanks for this again!

As we slowly see results from one or the other organization or volunteer project, I have a silly yet simple question - how many people have actually actively used your tool? (and to others -- what about your tools?)

I am asking because you had FreeBSD on the ipv6eyechart from the beginning but looking at changes in v6 access or v4 vs. v6 access patterns I would have expected that these tools might be used a lot more and hits might be noticeable. Contrary looking at http://www.freebsd.org/ipv6/w6d-www-stats.html or if you want a longer term picture starting end of March http://people.freebsd.org/~bz/www-large.png , I couldn't see any significant changes around World IPv6 Day.
I haven't even tried to analyze how many of these hits were by your chart (also given I only used anonymized, stripped down data to generate the graphs) as it might be a lot easier for you to say?


What had been the experience of others providing similar statistics, summaries, tests? Has anyone seen a significant use from amongst the network operator people and (content provider) participants community, or by users? Please share your experience!

Regards,
Bjoern

--
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.
Re: Test your connectivity for World IPv6 Day [ In reply to ]
Hello all,

I am the Sys$admin @ www.ipv6matrix.org and remind you of the
discussion 4 months ago about routing to www.ipv6matrix.org which went
wrong at our upstream providers on IPv6 day (8th June).
Well, either we must be very unlucky with our upstream providers, or the
IPv6 network is still far from production status, but here we go again,
since Sunday 7 September 2011, approx 21:00 UTC routing's gone wrong
again at our upsteam.


>From www.ipv6matrix.org to psg.com

[ocl@www~]$ traceroute6 psg.com
traceroute to psg.com (2001:418:1::62), 30 hops max, 40 byte packets
1 isoc-eng-v6gw1.ipv6matrix.org (2a00:19e8:20:1::1) 1.734 ms 2.067
ms 2.461 ms
2 2001:a88:0:2::39 (2001:a88:0:2::39) 0.969 ms 1.042 ms 1.136 ms
3 g1-1-7-t40-cr2.ipv6.router.uk.clara.net (2001:a88:0:1::de) 1.238 ms * *
4 ten2-0-0.t40-br3.ipv6.router.uk.clara.net (2001:a88:0:1::11e) 1.312
ms * *
5 * * *
6 * * *
7 * * *

>From psg.com to www.ipv6matrix.org

psg.com:/usr/home/ocl> traceroute6 www.ipv6matrix.org
traceroute6 to elephant.ipv6matrix.org (2a00:19e8:20:1::aa) from
2001:418:1::62, 64 hops max, 12 byte packets
1 vrrp.sea.rg.net 0.323 ms 0.255 ms 0.206 ms
2 v6-10gigabitethernet1-3.core1.sea1.he.net 0.344 ms 0.444 ms 0.336 ms
3 10gigabitethernet3-1.core1.den1.he.net 32.839 ms 32.800 ms 32.064 ms
4 10gigabitethernet1-1.core1.chi1.he.net 56.813 ms 55.758 ms 73.156 ms
5 10gigabitethernet7-2.core1.nyc4.he.net 73.783 ms 73.317 ms 73.909 ms
6 10gigabitethernet3-3.core1.lon1.he.net 140.627 ms 161.913 ms
143.364 ms
7 2001:7f8:4::23e7:1 140.993 ms 141.320 ms 141.083 ms
8 2a01:178:9191:3::17 141.502 ms 142.150 ms 141.355 ms
9 2a01:178:500::6 142.529 ms 142.409 ms 142.002 ms
10 2a01:178:500::6 142.364 ms !A 147.545 ms !A 144.714 ms !A
psg.com:/usr/home/ocl>

It's been 5 days - therefore not automatically detected by anyone else.
Any chance that someone here can fix this?
Last time, Ben Wilkinson @ NewNet did his magic. I'm not sure whether
the problem's in his jurisdiction this time around.

Kind regards,

Olivier Crépin-Leblond

On 08/06/2011 15:43, ben wrote :
> >/ Perhaps not anymore?
> />/
> />/ nagios:/tmp# traceroute6 www.ipv6matrix.org
> />/ traceroute to www.ipv6matrix.org (2a00:19e8:20:1::aa), 30 hops max, 80 byte
> />/ packets
> />/ 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 3.923 ms 4.353 ms 5.383 ms
> />/ 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 6.074 ms 6.372 ms 6.713
> />/ ms
> />/ 3 sxct.movl.mtcnet.net (2607:fe28:11:1002::194) 8.271 ms 8.516 ms 9.341
> />/ ms
> />/ 4 v6-siouxcenter.movl.153.netins.net (2001:5f8:7f06::9) 16.877 ms 17.124
> />/ ms 17.332 ms
> />/ 5 v6-ins-kb1-et-11-6-307.kmrr.netins.net (2001:5f8:2:2::1) 20.513 ms
> />/ 20.781 ms 21.116 ms
> />/ 6 v6-ins-kc1-te-9-2.kmrr.netins.net (2001:5f8::10:1) 21.508 ms 17.599 ms
> />/ 17.863 ms
> />/ 7 sl-crs4-chi-te0-2-0-1.v6.sprintlink.net (2600:4::6) 26.898 ms 26.054
> />/ ms 26.249 ms
> />/ 8 sl-crs3-chi-po0-1-2-0.v6.sprintlink.net (2600:0:2:1239:144:232:3:143)
> />/ 27.093 ms 26.052 ms 26.103 ms
> />/ 9 sl-st30-chi-po0-4-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:8:184)
> />/ 26.206 ms 20.901 ms 23.879 ms
> />/ 10 * * *
> />/ 11 10gigabitethernet7-2.core1.nyc4.he.net (2001:470:0:1c6::1) 63.056 ms
> />/ 64.132 ms 63.923 ms
> />/ 12 10gigabitethernet3-3.core1.lon1.he.net (2001:470:0:128::2) 131.639 ms
> />/ 131.642 ms 132.250 ms
> />/ 13 * * *
> />/ 14 2a01:178:9191:3::17 (2a01:178:9191:3::17) 133.774 ms 134.849 ms
> />/ 134.514 ms
> />/ 15 2a01:178:500::6 (2a01:178:500::6) 128.390 ms 128.413 ms 128.602 ms
> />/ 16 2a00:19e8::1:d (2a00:19e8::1:d) 128.893 ms 127.646 ms 127.683 ms
> />/ 17 2a00:19e8::1:5 (2a00:19e8::1:5) 127.557 ms 126.850 ms *
> />/ 18 elephant.ipv6matrix.org (2a00:19e8:20:1::aa) 128.325 ms 127.747 ms
> />/ 127.941 ms
> />/ nagios:/tmp#
> />
> > I reached it earlier today - now I'm getting a loop again:
> >
> > % traceroute6 www.ipv6matrix.org
> > traceroute6 to elephant.ipv6matrix.org (2a00:19e8:20:1::aa) from 2001:8c0:9602:1::2, 64 hops max, 12 byte packets
> > 1 ge0-0-0-10.ar1.skxy.no.catchbone.net 8.520 ms 9.092 ms 10.041 ms
> > 2 ge0-0-2.cr2.osls.no.catchbone.net 10.360 ms 8.603 ms 10.351 ms
> > 3 te2-3-0.br2.mejv.se.catchbone.net 16.740 ms 14.078 ms 15.490 ms
> > 4 10gigabitethernet1-3.core1.sto1.he.net 15.663 ms 21.437 ms 24.854 ms
> > 5 10gigabitethernet3-3.core1.fra1.he.net 42.632 ms 49.032 ms 50.749 ms
> > 6 10gigabitethernet5-3.core1.lon1.he.net 51.215 ms 53.237 ms 50.208 ms
> > 7 2001:7f8:4::23e7:1 54.859 ms 54.911 ms 55.031 ms
> > 8 2a01:178:9191:3::200 54.223 ms 56.567 ms 53.365 ms
> > 9 2a01:178:9191:3::1 54.974 ms 54.340 ms 54.929 ms
> > 10 2a01:178:9191:3::200 54.552 ms 54.361 ms 55.203 ms
> > 11 2a01:178:9191:3::1 57.085 ms 52.958 ms 55.140 ms
> > <repeat ad nauseam>
>
> OK fixed
>
> ben wilkinson
> newnet plc

--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
Re: Test your connectivity for World IPv6 Day [ In reply to ]
On 07/10/2011 12:39, Olivier MJ Crepin-Leblond wrote :
> since Sunday 7 September 2011, approx 21:00 UTC routing's gone wrong
> again at our upsteam.

That's Sunday 2nd Sept. 2011 @ 21:00 UTC.

--
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
Re: Test your connectivity for World IPv6 Day [ In reply to ]
On 2011-10-07 12:39 , Olivier MJ Crepin-Leblond wrote:
> Hello all,
>
> I am the Sys$admin @ www.ipv6matrix.org and remind you of the
> discussion 4 months ago about routing to www.ipv6matrix.org which went
> wrong at our upstream providers on IPv6 day (8th June).
> Well, either we must be very unlucky with our upstream providers, or the
> IPv6 network is still far from production status, but here we go again,
> since Sunday 7 September 2011, approx 21:00 UTC routing's gone wrong
> again at our upsteam.

Did you consider contacting your upstream?

> 8 2a01:178:9191:3::17 141.502 ms 142.150 ms 141.355 ms
> 9 2a01:178:500::6 142.529 ms 142.409 ms 142.002 ms
> 10 2a01:178:500::6 142.364 ms !A 147.545 ms !A 144.714 ms !A

Seems somebody is (A)dministratively denying your packets. That somebody
seems to be the NewNet your mentioned before though.

>From GRH it also seems that next to 9191 (NewNet) you have 8426 (Clara)
as your upstreams. As such the traceroute you showed goes over the
latter, while the inbound goes over NewNet.

Only thing you can do is talk to your upstream to resolve this.

Or a quick fix: don't announce your prefix over NewNet...

Greets,
Jeroen
Re: Test your connectivity for World IPv6 Day [ In reply to ]
Hello,

Newnet, recieve prefix 2a00:19e8::/32 (where 2a00:19e8:20:1::aa and therfor AAAA www.ipv6matrix.org resides) from
AS31493 (TWENTYTWENTYMEDIA)

Network Next Hop Metric LocPrf Weight Path
*> 2a00:19e8::/32 2a01:178:500::6 0 1000 450 31493 i

In Newnet's defence this is a valid path in out BGP table, however this customer appears to not have a valid
route/firewall once this is traffic is passed to them.
Newnet will not be blocking any traffic to the range 2a00:19e8::/32

Have you tried contacting Twenty Twenty Media?
Hope this helps

Regards
ben wilkinson
newnet plc

On 07/10/11 12:17, Jeroen Massar wrote:
> On 2011-10-07 12:39 , Olivier MJ Crepin-Leblond wrote:
>> Hello all,
>>
>> I am the Sys$admin @ www.ipv6matrix.org and remind you of the
>> discussion 4 months ago about routing to www.ipv6matrix.org which went
>> wrong at our upstream providers on IPv6 day (8th June).
>> Well, either we must be very unlucky with our upstream providers, or the
>> IPv6 network is still far from production status, but here we go again,
>> since Sunday 7 September 2011, approx 21:00 UTC routing's gone wrong
>> again at our upsteam.
>
> Did you consider contacting your upstream?
>
>> 8 2a01:178:9191:3::17 141.502 ms 142.150 ms 141.355 ms
>> 9 2a01:178:500::6 142.529 ms 142.409 ms 142.002 ms
>> 10 2a01:178:500::6 142.364 ms !A 147.545 ms !A 144.714 ms !A
>
> Seems somebody is (A)dministratively denying your packets. That somebody
> seems to be the NewNet your mentioned before though.
>
>> From GRH it also seems that next to 9191 (NewNet) you have 8426 (Clara)
> as your upstreams. As such the traceroute you showed goes over the
> latter, while the inbound goes over NewNet.
>
> Only thing you can do is talk to your upstream to resolve this.
>
> Or a quick fix: don't announce your prefix over NewNet...
>
> Greets,
> Jeroen
>

1 2 3 4 5 6  View All