I am in International E, without v6 on WLAN, but can v4 ssh home and trace from there to the v6 router here. Then I see VERY good response over the JANET-GEANT-Abilene-IETF route.
Maybe it's a Euro6IX issue for you, for specific routing to that prefix as opposed to the production prefix, if GEANT does offer transit for you? (You might try asking to [EMAIL PROTECTED]) login ~]$ /usr/sbin/traceroute6 2001:468:c12:1::1 traceroute to 2001:468:c12:1::1 (2001:468:c12:1::1) from 2001:630:d0:115:230:48ff:fe23:58df, 30 hops max, 16 byte packets 1 servers-router.6core.ecs.soton.ac.uk (2001:630:d0:115::1) 0.431 ms 0.276 ms 0.275 ms 2 zaphod.6core.ecs.soton.ac.uk (2001:630:d0:101::1) 0.841 ms 0.527 ms 0.706 ms 3 ford.6core.ecs.soton.ac.uk (2001:630:d0:100::1) 0.99 ms 0.975 ms 1.668 ms 4 2001:630:c1:100::1 (2001:630:c1:100::1) 1.309 ms 1.411 ms 0.952 ms 5 2001:630:c1:10::1 (2001:630:c1:10::1) 2.855 ms 1.851 ms 2.023 ms 6 * * * 7 2001:630:c1::1 (2001:630:c1::1) 3.35 ms 2.651 ms 2.379 ms 8 2001:630:c1::1 (2001:630:c1::1) 2.338 ms 3.192 ms 2.778 ms 9 po9-0.cosh-scr.ja.net (2001:630:0:10::85) 79.361 ms 3.606 ms 3.264 ms 10 po2-0.lond-scr.ja.net (2001:630:0:10::29) 5.147 ms 5.02 ms 7.123 ms 11 po6-0.lond-scr3.ja.net (2001:630:0:10::36) 5.306 ms 4.906 ms 5.095 ms 12 2001:630:0:10::166 (2001:630:0:10::166) 5.447 ms 4.241 ms 4.248 ms 13 janet.uk1.uk.geant.net (2001:798:2028:10aa::1) 5.798 ms 5.709 ms 5.006 ms 14 uk.ny1.ny.geant.net (2001:798:20cc:1c01:2801::1) 74.333 ms 74.8 ms 73.537 ms 15 nycmng-esnet.abilene.ucaid.edu (2001:468:ff:15c3::1) 78.41 ms 128.5 ms 74.054 ms 16 washng-nycmng.abilene.ucaid.edu (2001:468:ff:1518::2) 101.141 ms 95.373 ms 96.015 ms 17 max-washng.abilene.ucaid.edu (2001:468:ff:184c::2) 95.498 ms 94.944 ms 94.517 ms 18 2001:468:c12:1::1 (2001:468:c12:1::1) 95.006 ms 108.128 ms 96.164 ms On Wed, Nov 10, 2004 at 02:18:31PM -0500, JORDI PALET MARTINEZ wrote: > Agree, good job. Is working for me since over 10 minutes ago. > > BUT the routing to Europe is really stupid and absolutely unacceptable: > Ordenador-de-Jordi-Palet:/Users/Jordi/Desktop jordi$ traceroute6 > www.euro6ix.org > traceroute6 to www.euro6ix.org (2001:800:40:2a03::3) from > 2001:468:c12:136:20d:93ff:feeb:73, 30 hops max, 12 byte packets > 1 2001:468:c12:136::4 2.491 ms 1.672 ms 1.641 ms > 2 2001:468:c12:1::1 2.353 ms 2.463 ms 2.387 ms > 3 2001:468:ff:185c::1 17.22 ms * 3.112 ms > 4 atlang-washng.abilene.abilene.ucaid.edu 21.407 ms 18.55 ms 18.519 ms > 5 hstnng-atlang.abilene.ucaid.edu 44.552 ms 43.544 ms 38.279 ms > 6 losang-hstnng.abilene.ucaid.edu 69.868 ms 69.807 ms * > 7 3ffe:8140:101:1::2 178.257 ms 173.559 ms 174.291 ms > 8 hitachi1.otemachi.wide.ad.jp 175.771 ms 174.657 ms 173.76 ms > 9 pc6.otemachi.wide.ad.jp 195.116 ms 183.588 ms 190.05 ms > 10 * 3ffe:1800::3:2d0:b7ff:fe9a:6233 185.624 ms 183.481 ms > 11 3ffe:1800::3:230:48ff:fe41:4e95 184.689 ms 183.501 ms 184.908 ms > 12 2001:468:ff:16c1::5 183.309 ms 184.138 ms 194.804 ms > 13 v6-tunnel62-uk6x.ipv6.btexact.com 457.111 ms 456.848 ms 455.127 ms > 14 2001:800:40:2e02::1 513.549 ms 511.013 ms 515.763 ms > 15 2001:800:40:2f02::2 514.232 ms 512.886 ms 520.444 ms > 16 ns1.euro6ix.com 520.54 ms 516.964 ms 510.757 ms > > Can we please fix this, PLEASE ? No idea why hasn't been fixed already since > when reported on Monday, in parallel with the rest. > > By the way, the press should take note about Airespace marketing versus > reality. I hope this company can be honest an make a public correction on > that, otherwise customers should not trust them anymore. > > Regards, > Jordi > > > > De: [EMAIL PROTECTED] > > Responder a: [EMAIL PROTECTED] > > Fecha: Wed, 10 Nov 2004 18:43:07 -0000 > > Para: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > > Asunto: RE: IPv6 in the network, please > > > > So somebody needs to get Airespace's marketroids to slow down a little > > bit: > > > > http://www.airespace.com/news/press_releases/04_1026b.php > > > > --Mat > > > > P.S. Sincere thanks to the IETF61 NOC for making these efforts to get > > IPv6 functional on the entire network - I'll try that new config now > > from Lincoln. > > > > On , [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Begin forwarded message: > >> > >>> From: Ben Crosby <[EMAIL PROTECTED]> > >>> Date: November 10, 2004 12:07:08 PM EST > >>> To: [EMAIL PROTECTED] > >>> Subject: IPv6 > >>> Reply-To: Ben Crosby <[EMAIL PROTECTED]> > >>> > >>> Folks, > >>> > >>> To expand on Jeff's explanation of the IPv6 status here at > > IETF61; > >>> The entire network, both wired and wireless, was designed from the > >>> get-go as being IPv6 capable. It also had a very real and major > >>> requirement to be stable in the face of hundreds of clients all at > >>> 100% transmit power, rogue APs, and all the other problems that have > >>> plagued previous IETF wireless networks. The good folks at Airespace > >>> seemed to have a system that met this goal, and as we all can see, > >>> it indeed works well. > >>> > >>> However, when we asked Airespace to join us in this adventure, > > it > >>> became clear that the "intelligence" of their system worked through > >>> tracking IPv4 DHCP requests, and thus wouldn't work with IPv6. This > >>> lack of IPv6 support was nearly a show stopper, however Airespace > >>> jumped through some major hoops to design, implement, and deploy code > >>> that monitors RAs and RSs specifically to handle IPv6 for this > >>> network. > >>> > >>> Like most brand new code, when we deployed it, we encountered > >>> problems. Problems that lead to instability in ALL wireless network > >>> access. After several long days and nights of working on this long > >>> before the first attendees arrived (we've been on site since Tuesday > >>> 2nd - Election Day ;) we decided to disable the IPv6 support on the > >>> wireless network, rather than risk the overall network stability. > >>> Airespace continues to work on the problems, and we believe that we > >>> have a reasonable interim solution. > >>> > >>> We have phased in a new image with limited deployment, which we > > will > >>> monitor. If we experience no problems, IPv6 will be back on the > >>> wireless lan, however we need to maintain the overall stability of > >>> the wireless network as our highest priority. > >>> > >>> For those who need IPv6 on wireless: > >>> > >>> SSID: ietf61v6 > >>> WEP Key: thisisav6wlan > >>> Hex: 746869736973617636776c616e > >>> > >>> Coverage will be available in Georgetown, Lincoln, Jefferson, > >>> Monroe, Military and Hemisphere. You should not associate with this > >>> wireless network if you need stable IPv4. This is a dedicated > >>> network with new AP's and a new controller. > >>> > >>> My thanks to our volunteer staff who worked to deploy this > > network > >>> in the late hours last night (and very early hours this morning) > >>> after the social event. > >>> > >>> For those that are inconvenienced by the loss of IPv6, I > > sincerely > >>> apologize, and remind you that native IPv6 is available at every > >>> wired port in the terminal room. > >>> > >>> Thanks for bearing with us, and have a good meeting! > >>> > >>> - Ben Crosby > >>> Alcatel / IETF61 NOC > >>> > >> -----BEGIN PGP SIGNATURE----- > >> Version: GnuPG v1.2.3 (Darwin) > >> > >> iD8DBQFBklluLWqnmaznXfoRAi/qAJ4nUW48fV51MGYwRdX1IOqh2OAYHQCgvyZT > >> nuUrX42hGaM8Xg7/fKPj1jc= =t7zw > >> -----END PGP SIGNATURE----- > >> > >> > >> _______________________________________________ > >> Ietf mailing list > >> [EMAIL PROTECTED] > >> https://www1.ietf.org/mailman/listinfo/ietf > > > > _______________________________________________ > > Ietf mailing list > > [EMAIL PROTECTED] > > https://www1.ietf.org/mailman/listinfo/ietf > > > > > > ********************************** > Madrid 2003 Global IPv6 Summit > Presentations and videos on line at: > http://www.ipv6-es.com > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the use of the > individual(s) named above. If you are not the intended recipient be aware > that any disclosure, copying, distribution or use of the contents of this > information, including attached files, is prohibited. > > > > > _______________________________________________ > Ietf mailing list > [EMAIL PROTECTED] > https://www1.ietf.org/mailman/listinfo/ietf -- Tim North American IPv6 Task Force Technologist Seminar More info at http://www.ipv6seminar.com/ _______________________________________________ Ietf mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf
