From tboss at research.earthlink.net Mon May 2 12:31:27 2005 From: tboss at research.earthlink.net (Tim Bosserman) Date: Mon May 2 12:33:12 2005 Subject: [6bone] An IPv6 pilot project Message-ID: EarthLink R&D has been working for some time on a pilot project for bringing IPv6 "to the home". Toward that end, we have hacked the open-source firmware of the Linksys WRT54G wireless access point and turned the WRT54G into an IPv6 router. We are now making our customized firmware available for download, and are allowing interested users to have a /64 network delegated to them via DHCPv6. Essentially, this is how it works: Using our customized firmware, at boot time the WRT54G will create an IPSEC tunnel to a router in our lab. We aren't using IPSEC for encryption, just for authenticating the session (using IPSEC "Authenticated Header" mode). Once the IPSEC tunnel is established, the WRT54G then uses DHCPv6 to get the /64 network prefix allocated to it over the IPSEC tunnel. The WRT54G then advertises that prefix on the local LAN (both wired and wireless) and acts as an IPv6 router for all nodes on the LAN. For more information, refer to: http://www.research.earthlink.net/ipv6/ Strictly speaking this may be somewhat off-topic for this mailing list, but I thought some folks on this list might find this of interest. -- Tim Bosserman EarthLink R&D From frlinux at frlinux.net Thu May 5 08:17:54 2005 From: frlinux at frlinux.net (FRLinux) Date: Thu May 5 08:19:09 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <20050428095038.S32740@mignon.ki.iif.hu> References: <20050428095038.S32740@mignon.ki.iif.hu> Message-ID: <59794.160.6.1.82.1115306274.squirrel@webmail.frlinux.net> Hello, I am currently using a Cisco 7204vxr router with IOS 12.3(12b). We are dual-stacked on a high speed link. Whilst ipv4 gets full speed (2.5MB/s practical download speed), i am only getting 50-100kb/s on v6 which is wrong. It used to work properly but is now dead slow. I can't think what changed but the IOS version (12a before the icmp advisory). I have cef enabled for v4/v6 but still no joy. Has anyone seen such a behavior ? Thanks, Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc From dr at cluenet.de Thu May 5 09:57:59 2005 From: dr at cluenet.de (Daniel Roesen) Date: Thu May 5 09:58:58 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <59794.160.6.1.82.1115306274.squirrel@webmail.frlinux.net> References: <20050428095038.S32740@mignon.ki.iif.hu> <59794.160.6.1.82.1115306274.squirrel@webmail.frlinux.net> Message-ID: <20050505165759.GA28243@srv01.cluenet.de> On Thu, May 05, 2005 at 04:17:54PM +0100, FRLinux wrote: > I am currently using a Cisco 7204vxr router with IOS 12.3(12b). We are > dual-stacked on a high speed link. > > Whilst ipv4 gets full speed (2.5MB/s practical download speed), i am only > getting 50-100kb/s on v6 which is wrong. It used to work properly but is > now dead slow. I can't think what changed but the IOS version (12a before > the icmp advisory). How did you test? Please describe your environment in detail. Can you put up the config? Regards, Daniel PS: please don't use "reply" to open a new thread as you actually hijack the one you're replying to. -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 From 6bone at schlund.de Mon May 9 01:21:10 2005 From: 6bone at schlund.de (Armin Arh) Date: Mon May 9 01:21:13 2005 Subject: [6bone] icmp ttl exceeded, not for packets > 112 (FreeBSD-5.3) Message-ID: <20050509082110.GI16586@nero.net.schlund.de> Hi, we have found an interesting behaviour about ttl exceeded with FreeBSD-5.3: Packets larger than 112 bytes do not get answered with this error. In the following output, bge0.gw-tunnel-a.v6.schlund.net is our FreeBSD- box. (Second parameter of traceroute6 is packet size) armin@nero traceroute6 test.rot13.de 112 traceroute6 to test.rot13.de (2001:8d8:81:550::1) from 2001:8d8:41::6, 64 hops max, 112 byte packets 1 gw-ma6 0.452 ms 0.327 ms 0.323 ms 2 v999.gw-dists.bs.ka.schlund.net 0.780 ms 0.662 ms 0.652 ms 3 bge0.gw-tunnel-a.v6.schlund.net 1.343 ms 1.510 ms 1.365 ms 4 test.rot13.de 1.166 ms 1.267 ms 1.154 ms armin@nero traceroute6 test.rot13.de 113 traceroute6 to test.rot13.de (2001:8d8:81:550::1) from 2001:8d8:41::6, 64 hops max, 113 byte packets 1 gw-ma6 0.412 ms 0.347 ms 0.323 ms 2 v999.gw-dists.bs.ka.schlund.net 0.845 ms 0.667 ms 0.649 ms 3 * * * 4 test.rot13.de 1.318 ms 1.148 ms 1.157 ms die anyone else experience this? bye, Armin -- Armin Arh Schlund + Partner AG -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://mailman.isi.edu/pipermail/6bone/attachments/20050509/e3a6bd2f/attachment.bin From xiyang at sharesec.com Mon May 9 08:05:58 2005 From: xiyang at sharesec.com (??) Date: Mon May 9 08:06:27 2005 Subject: [6bone] ??,?: 6bone Digest, Vol 17, Issue 2 In-Reply-To: <200505051901.j45J13d29241@gamma.isi.edu> Message-ID: -----????----- ???: 6bone-bounces@mailman.isi.edu [mailto:6bone-bounces@mailman.isi.edu]?? 6bone-request@mailman.isi.edu ????: 2005?5?6? 3:01 ???: 6bone@mailman.isi.edu ??: 6bone Digest, Vol 17, Issue 2 Send 6bone mailing list submissions to 6bone@mailman.isi.edu To subscribe or unsubscribe via the World Wide Web, visit http://mailman.isi.edu/mailman/listinfo/6bone or, via email, send a message with subject or body 'help' to 6bone-request@mailman.isi.edu You can reach the person managing the list at 6bone-owner@mailman.isi.edu When replying, please edit your Subject line so it is more specific than "Re: Contents of 6bone digest..." Today's Topics: 1. cisco ipv6 slow perfs (FRLinux) 2. Re: cisco ipv6 slow perfs (Daniel Roesen) ---------------------------------------------------------------------- Message: 1 Date: Thu, 5 May 2005 16:17:54 +0100 (IST) From: "FRLinux" Subject: [6bone] cisco ipv6 slow perfs To: 6bone@mailman.isi.edu Message-ID: <59794.160.6.1.82.1115306274.squirrel@webmail.frlinux.net> Content-Type: text/plain;charset=iso-8859-1 Hello, I am currently using a Cisco 7204vxr router with IOS 12.3(12b). We are dual-stacked on a high speed link. Whilst ipv4 gets full speed (2.5MB/s practical download speed), i am only getting 50-100kb/s on v6 which is wrong. It used to work properly but is now dead slow. I can't think what changed but the IOS version (12a before the icmp advisory). I have cef enabled for v4/v6 but still no joy. Has anyone seen such a behavior ? Thanks, Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc ------------------------------ Message: 2 Date: Thu, 5 May 2005 18:57:59 +0200 From: Daniel Roesen Subject: Re: [6bone] cisco ipv6 slow perfs To: 6bone@mailman.isi.edu Message-ID: <20050505165759.GA28243@srv01.cluenet.de> Content-Type: text/plain; charset=us-ascii On Thu, May 05, 2005 at 04:17:54PM +0100, FRLinux wrote: > I am currently using a Cisco 7204vxr router with IOS 12.3(12b). We are > dual-stacked on a high speed link. > > Whilst ipv4 gets full speed (2.5MB/s practical download speed), i am only > getting 50-100kb/s on v6 which is wrong. It used to work properly but is > now dead slow. I can't think what changed but the IOS version (12a before > the icmp advisory). How did you test? Please describe your environment in detail. Can you put up the config? Regards, Daniel PS: please don't use "reply" to open a new thread as you actually hijack the one you're replying to. -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 ------------------------------ _______________________________________________ 6bone mailing list 6bone@mailman.isi.edu http://mailman.isi.edu/mailman/listinfo/6bone End of 6bone Digest, Vol 17, Issue 2 ************************************ From frlinux at frlinux.net Wed May 11 03:50:39 2005 From: frlinux at frlinux.net (FRLinux) Date: Wed May 11 03:51:04 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <20050505165759.GA28243@srv01.cluenet.de> References: <20050428095038.S32740@mignon.ki.iif.hu> <59794.160.6.1.82.1115306274.squirrel@webmail.frlinux.net> <20050505165759.GA28243@srv01.cluenet.de> Message-ID: <50499.134.226.32.57.1115808639.squirrel@webmail.frlinux.net> On Thu, May 5, 2005 5:57 pm, Daniel Roesen said: > How did you test? I was using wget from various machines (solaris, linux, freebsd) > Please describe your environment in detail. Can you put up the config? The config is a bit sensitive to post, it is a dual-stack link both enabled on v4/6 with cef (i don't have route cache enabled though). Every single ipv6 download is limited to 50/100kb, i don't have cisco support either (although i am currently arranging one). Is there anything people might actually suggest for me to test ? Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc From frlinux at frlinux.net Thu May 12 13:13:42 2005 From: frlinux at frlinux.net (FRLinux) Date: Thu May 12 13:14:12 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: References: Message-ID: <4283B8F6.6000304@frlinux.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Bednarczyk wrote: > We are about to enable (next week) IPv6 dual stacked accross all > interfaces on one of our field offices with cat 4500 and SupIIIG > module. I hope we get more then 100K throughput though. Our provider currently use several dual stacked cisco routers (i believe they have 7600 series) and they didn't notice any problem, so that leaves me with 3 possibilities : - - i wrongly configured my router - - there is an unknow bug in the IOS version i am currently running (although my release did not appear in the deferred list yet :) - - my 7204 is too getting limited by its hardware and the amount of ACLs it is putting up with but i'd expect to see some pikes on the cpu usage which is not the case ... Please let us know how you get on! Steph - -- Mail sent on Gentoo Linux (http://www.gentoo.org) http://frlinux.net - frlinux@frlinux.net public key : http://frlinux.net/files/frlinux_public_key.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCg7j2plbM2wjOZgMRAt5WAJ9vcfwceWWXmLW6Mpygg9h/vp1QZACfSTjW +eX1IefRPscVJnu+5+jUA74= =f2Ci -----END PGP SIGNATURE----- From iljitsch at muada.com Sat May 14 02:30:18 2005 From: iljitsch at muada.com (Iljitsch van Beijnum) Date: Sat May 14 02:31:12 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <4283B8F6.6000304@frlinux.net> References: <4283B8F6.6000304@frlinux.net> Message-ID: <52D9DC22-2BE6-4A3B-9A65-9E70BB668DE9@muada.com> On 12-mei-2005, at 22:13, FRLinux wrote: > - - i wrongly configured my router > - - there is an unknow bug in the IOS version i am currently running > (although my release did not appear in the deferred list yet :) > - - my 7204 is too getting limited by its hardware and the amount > of ACLs > it is putting up with but i'd expect to see some pikes on the cpu > usage > which is not the case ... It's much more likely that the IPv6 traffic takes a very different route from the IPv4 traffic. Have a look at the traceroutes. From frlinux at frlinux.net Wed May 25 00:58:58 2005 From: frlinux at frlinux.net (FRLinux) Date: Wed May 25 00:59:40 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <52D9DC22-2BE6-4A3B-9A65-9E70BB668DE9@muada.com> References: <4283B8F6.6000304@frlinux.net> <52D9DC22-2BE6-4A3B-9A65-9E70BB668DE9@muada.com> Message-ID: <40926.160.6.1.82.1117007938.squirrel@webmail.frlinux.net> On Sat, May 14, 2005 10:30 am, Iljitsch van Beijnum said: > It's much more likely that the IPv6 traffic takes a very different > route from the IPv4 traffic. Have a look at the traceroutes. I did some further testing and surprisingly, ipv6 takes shorter routes. For instance, tracerouting to kame.net takes 19 hops on v4 and only 11 via v6. I also since enabled route cache on the main interface and the atm interface without any luck still getting an average of 80kb/s transfer speed ... Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc From jeroen at unfix.org Wed May 25 01:32:57 2005 From: jeroen at unfix.org (Jeroen Massar) Date: Wed May 25 01:33:41 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <40926.160.6.1.82.1117007938.squirrel@webmail.frlinux.net> References: <4283B8F6.6000304@frlinux.net> <52D9DC22-2BE6-4A3B-9A65-9E70BB668DE9@muada.com> <40926.160.6.1.82.1117007938.squirrel@webmail.frlinux.net> Message-ID: <1117009978.12776.17.camel@firenze.zurich.ibm.com> On Wed, 2005-05-25 at 08:58 +0100, FRLinux wrote: > On Sat, May 14, 2005 10:30 am, Iljitsch van Beijnum said: > > It's much more likely that the IPv6 traffic takes a very different > > route from the IPv4 traffic. Have a look at the traceroutes. > > I did some further testing and surprisingly, ipv6 takes shorter routes. > For instance, tracerouting to kame.net takes 19 hops on v4 and only 11 via > v6. 19 fast hops, versus 11 slow ones, most likely going through a mess of tunnels. Dump the traceroutes here and complain to the underlying AS's, or get a better transit. Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 240 bytes Desc: This is a digitally signed message part Url : http://mailman.isi.edu/pipermail/6bone/attachments/20050525/4ef28984/attachment.bin From frlinux at frlinux.net Wed May 25 03:28:27 2005 From: frlinux at frlinux.net (FRLinux) Date: Wed May 25 03:28:42 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: References: <4283B8F6.6000304@frlinux.net> <52D9DC22-2BE6-4A3B-9A65-9E70BB668DE9@muada.com> <40926.160.6.1.82.1117007938.squirrel@webmail.frlinux.net> Message-ID: <48352.160.6.1.82.1117016907.squirrel@webmail.frlinux.net> On Wed, May 25, 2005 10:11 am, Simon Leinen said: > At these performance levels, router performance is probably not the > problem. Let's see these traceroutes... Ok, let's take ftp.nluug.nl for instance. $ host ftp.nluug.nl ftp.nluug.nl has address 192.87.102.36 ftp.nluug.nl has IPv6 address 2001:610:1:80aa:192:87:102:36 Here are the traceroutes from the router : traceroute 192.87.102.36 Type escape sequence to abort. Tracing the route to ftp.nluug.nl (192.87.102.36) 1 mantova-atm3-1-30.bh.access.hea.net (193.1.194.137) 4 msec 0 msec 4 msec 2 hyperion-gige3-3-0.bh.core.hea.net (193.1.196.121) 0 msec 4 msec 0 msec 3 deimos-gige5-2.cwt.core.hea.net (193.1.195.86) 4 msec 0 msec 4 msec 4 heanet.ie1.ie.geant.net (62.40.103.229) 0 msec 0 msec 0 msec 5 ie.uk1.uk.geant.net (62.40.96.138) 16 msec 16 msec 16 msec 6 uk.nl1.nl.geant.net (62.40.96.181) 24 msec 24 msec 20 msec 7 surfnet-gw.nl1.nl.geant.net (62.40.103.98) 104 msec 108 msec 200 msec 8 PO11-0.CR1.Amsterdam1.surf.net (145.145.166.33) 24 msec 24 msec 36 msec 9 po0-0.ar5.amsterdam1.surf.net (145.145.162.2) 24 msec 24 msec 24 msec 10 te1-1.sw14.amsterdam1.surf.net (145.145.140.158) 24 msec 24 msec 24 msec 11 * * !A traceroute 2001:610:1:80aa:192:87:102:36 Type escape sequence to abort. Tracing the route to ftp.nluug.nl (2001:610:1:80AA:192:87:102:36) 1 mantova-atm3-1-30.bh.access.hea.net (2001:770:8:20::1) 0 msec 0 msec 4 msec 2 hyperion-gige5-3.bh.core.hea.net (2001:770:8:1F::1) 0 msec 4 msec 0 msec 3 deimos-gige5-1.cwt.core.hea.net (2001:770:8:C::2) 4 msec 0 msec 4 msec 4 heanet.ie1.ie.geant.net (2001:798:2019:10AA::1) 0 msec 0 msec 4 msec 5 ie.uk1.uk.geant.net (2001:798:20CC:1901:2801::2) 16 msec 16 msec 16 msec 6 uk.nl1.nl.geant.net (2001:798:20CC:2201:2801::1) 20 msec 24 msec 20 msec 7 PO6-0.BR2.Amsterdam1.surf.net (2001:798:2022:10AA::6) 116 msec 204 msec 228 msec 8 Gi10-3.AR5.Amsterdam1.surf.net (2001:610:14:160::161) 24 msec 24 msec 24 msec 9 Gi5-1.SW14.Amsterdam1.surf.net (2001:610:14:160::162) 24 msec 24 msec 24 msec 10 Gi5-1.SW14.Amsterdam1.surf.net (2001:610:14:160::162) 36 msec 24 msec 24 msec 11 Gi5-1.SW14.Amsterdam1.surf.net (2001:610:14:160::162) !A !A !A Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc From frlinux at frlinux.net Wed May 25 08:15:45 2005 From: frlinux at frlinux.net (FRLinux) Date: Wed May 25 08:16:44 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: References: <4283B8F6.6000304@frlinux.net> <52D9DC22-2BE6-4A3B-9A65-9E70BB668DE9@muada.com> <40926.160.6.1.82.1117007938.squirrel@webmail.frlinux.net> <48352.160.6.1.82.1117016907.squirrel@webmail.frlinux.net> Message-ID: <45423.134.226.32.57.1117034145.squirrel@webmail.frlinux.net> On Wed, May 25, 2005 3:29 pm, Simon Leinen said: > No, I would like to see the IPv4 vs. IPv6 traceroutes that you were > referring to in your other mail, i.e. those where the IPv4 path with > 19 hops gives you better performance than the IPv6 path with 11 hops. Sure. But just before doing this, I was discussing that off-list and even downloading from ftp.heanet.ie (which is only 3 hops from us), i am still getting the same problems which now indicate a problem on my router rather than routing issues ... host www.kame.net www.kame.net has address 203.178.141.194 www.kame.net has IPv6 address 2001:200:0:8002:203:47ff:fea5:3085 Tracing the route to orange.kame.net (203.178.141.194) 1 mantova-atm3-1-30.bh.access.hea.net (193.1.194.137) 4 msec 0 msec 0 msec 2 hyperion-gige3-3-0.bh.core.hea.net (193.1.196.121) 0 msec 4 msec 0 msec 3 deimos-gige5-1.cwt.core.hea.net (193.1.195.129) 4 msec 4 msec 0 msec 4 lola-pos0-3-0.nyc.core.hea.net (193.1.196.138) 68 msec 68 msec 76 msec 5 abilene-manlan.nyc.peer.hea.net (193.1.196.142) 72 msec 84 msec 76 msec 6 chinng-nycmng.abilene.ucaid.edu (198.32.8.82) 96 msec 116 msec 96 msec 7 iplsng-chinng.abilene.ucaid.edu (198.32.8.77) 116 msec 100 msec 96 msec 8 kscyng-iplsng.abilene.ucaid.edu (198.32.8.81) 100 msec 100 msec 112 msec 9 dnvrng-kscyng.abilene.ucaid.edu (198.32.8.13) 120 msec 112 msec 112 msec 10 snvang-dnvrng.abilene.ucaid.edu (198.32.8.1) 136 msec 140 msec 140 msec 11 losang-snvang.abilene.ucaid.edu (198.32.8.94) 144 msec 152 msec 148 msec 12 transpac-local.lsanca.pacificwave.net (207.231.240.136) 148 msec 144 msec 156 msec 13 192.203.116.146 264 msec 264 msec 256 msec 14 tpr4-10gi0-1-0.jp.apan.net (203.181.248.109) 280 msec 276 msec 284 msec 15 203.178.133.142 260 msec 256 msec 260 msec 16 ve-51.foundry4.otemachi.wide.ad.jp (203.178.141.141) 256 msec 260 msec 268 msec 17 pc3.yagami.wide.ad.jp (203.178.138.245) 268 msec 260 msec 256 msec 18 fe-2-0.hitachi1.k2.wide.ad.jp (203.178.138.218) 268 msec 264 msec 260 msec 19 orange.kame.net (203.178.141.194) 260 msec 260 msec 260 msec Tracing the route to orange.kame.net (2001:200:0:8002:203:47FF:FEA5:3085) 1 mantova-atm3-1-30.bh.access.hea.net (2001:770:8:20::1) 0 msec 0 msec 4 msec 2 hyperion-gige5-3.bh.core.hea.net (2001:770:8:1F::1) 0 msec 4 msec 0 msec 3 luna-gige0-0-0.kil.core.hea.net (2001:770:90:5::1) 4 msec 0 msec 0 msec 4 gx-link.core.hea.net (2001:770:90:7::2) 0 msec 4 msec 0 msec 5 2001:CC8:102:5::2 156 msec 156 msec 156 msec 6 2001:CC8:102:5::2 160 msec 160 msec 156 msec 7 2001:CC8:102:5::1 320 msec 320 msec 324 msec 8 hitachi1.otemachi.wide.ad.jp (2001:200:0:1800::9C4:2) 268 msec 272 msec 272 msec 9 pc3.yagami.wide.ad.jp (2001:200:0:1C04::1000:2000) 276 msec 272 msec 268 msec 10 gr2000.k2.wide.ad.jp (2001:200:0:4819::2000:1) 272 msec 272 msec 276 msec 11 orange.kame.net (2001:200:0:8002:203:47FF:FEA5:3085) 276 msec 284 msec 272 msec Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc From dimitrygv at hotmail.com Wed May 25 18:17:06 2005 From: dimitrygv at hotmail.com (dimitry verkholashin) Date: Wed May 25 18:17:45 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <45423.134.226.32.57.1117034145.squirrel@webmail.frlinux.net> Message-ID: here is what I am getting: traceroute to www.kame.net (203.178.141.194), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 0.505 ms 0.478 ms 0.450 ms 2 tukw-dsl-gw11-203.tukw.qwest.net (63.231.10.203) 68.017 ms 56.747 ms 57.869 ms 3 tukw-agw1.inet.qwest.net (63.231.10.93) 57.085 ms 64.601 ms 49.734 ms 4 tkw-core-01.inet.qwest.net (205.171.11.97) 57.092 ms 56.530 ms 58.112 ms 5 svl-core-01.inet.qwest.net (205.171.14.117) 73.406 ms 71.507 ms 71.176 ms 6 tko-core-01.inet.qwest.net (65.120.19.69) 209.370 ms 212.992 ms 198.795 ms 7 jpx-brdr-01.inet.qwest.net (65.120.19.66) 202.752 ms 201.067 ms 213.821 ms 8 203.181.102.189 (203.181.102.189) 204.248 ms 195.227 ms 198.548 ms 9 gsr-ote102.kddnet.ad.jp (203.181.96.120) 211.458 ms 207.737 ms 213.568 ms10 cm-ote128.kddnet.ad.jp (59.128.5.42) 204.523 ms 197.879 ms 198.531 ms 11 210.132.94.78 (210.132.94.78) 211.204 ms * 213.978 ms 12 ve-5.foundry4.otemachi.wide.ad.jp (203.178.140.209) 207.723 ms 207.678 ms 211.841 ms 13 pc3.yagami.wide.ad.jp (203.178.138.245) 199.631 ms 185.890 ms 187.210 ms 14 fe-2-0.hitachi1.k2.wide.ad.jp (203.178.138.218) 202.845 ms 189.120 ms 198.796 ms 15 orange.kame.net (203.178.141.194) 201.140 ms 187.462 ms 200.269 ms traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:5c0:877a::3, 64 hops max, 12 byte packets 1 oberon 0.581 ms 0.401 ms 0.342 ms 2 2001:5c0:8fff:fffe::21c4 143.683 ms 136.765 ms 144.341 ms 3 ipv6.hexago.com 138.949 ms 143.395 ms 142.394 ms 4 sl-bb1v6-nyc-t-23.sprintv6.net 157.376 ms 154.765 ms 144.331 ms 5 sl-bb1v6-sj-t-1001.sprintv6.net 230.125 ms 227.885 ms 230.124 ms 6 2001:478:ffff::9 259.852 ms * 259.036 ms 7 2001:478:ffff::1e 256.406 ms 256.29 ms 248.322 ms 8 3ffe:80a::e 260.125 ms 259.385 ms * 9 bb.v6.pwd.ne.jp 359.722 ms 355.429 ms 377.373 ms 10 bb.v6.pwd.ne.jp 364.614 ms 361.872 ms 356.03 ms 11 pc6.otemachi.wide.ad.jp 407.438 ms 432.639 ms 406.014 ms 12 hitachi1.otemachi.wide.ad.jp 404.192 ms 413.235 ms 412.384 ms 13 pc3.yagami.wide.ad.jp 413.894 ms 410.092 ms 413.917 ms 14 gr2000.k2.wide.ad.jp 415.488 ms 537.124 ms 415.676 ms 15 orange.kame.net 422.456 ms 407.234 ms 415.371 ms >From: "FRLinux" >Reply-To: frlinux@frlinux.net >To: "Simon Leinen" >CC: 6BONE List <6bone@mailman.isi.edu> >Subject: Re: [6bone] cisco ipv6 slow perfs >Date: Wed, 25 May 2005 16:15:45 +0100 (IST) > > >On Wed, May 25, 2005 3:29 pm, Simon Leinen said: > > No, I would like to see the IPv4 vs. IPv6 traceroutes that you were > > referring to in your other mail, i.e. those where the IPv4 path with > > 19 hops gives you better performance than the IPv6 path with 11 hops. > >Sure. But just before doing this, I was discussing that off-list and even >downloading from ftp.heanet.ie (which is only 3 hops from us), i am still >getting the same problems which now indicate a problem on my router rather >than routing issues ... > >host www.kame.net >www.kame.net has address 203.178.141.194 >www.kame.net has IPv6 address 2001:200:0:8002:203:47ff:fea5:3085 > >Tracing the route to orange.kame.net (203.178.141.194) > 1 mantova-atm3-1-30.bh.access.hea.net (193.1.194.137) 4 msec 0 msec 0 >msec > 2 hyperion-gige3-3-0.bh.core.hea.net (193.1.196.121) 0 msec 4 msec 0 >msec > 3 deimos-gige5-1.cwt.core.hea.net (193.1.195.129) 4 msec 4 msec 0 msec > 4 lola-pos0-3-0.nyc.core.hea.net (193.1.196.138) 68 msec 68 msec 76 msec > 5 abilene-manlan.nyc.peer.hea.net (193.1.196.142) 72 msec 84 msec 76 >msec > 6 chinng-nycmng.abilene.ucaid.edu (198.32.8.82) 96 msec 116 msec 96 msec > 7 iplsng-chinng.abilene.ucaid.edu (198.32.8.77) 116 msec 100 msec 96 >msec > 8 kscyng-iplsng.abilene.ucaid.edu (198.32.8.81) 100 msec 100 msec 112 >msec > 9 dnvrng-kscyng.abilene.ucaid.edu (198.32.8.13) 120 msec 112 msec 112 >msec > 10 snvang-dnvrng.abilene.ucaid.edu (198.32.8.1) 136 msec 140 msec 140 >msec > 11 losang-snvang.abilene.ucaid.edu (198.32.8.94) 144 msec 152 msec 148 >msec > 12 transpac-local.lsanca.pacificwave.net (207.231.240.136) 148 msec 144 >msec 156 msec > 13 192.203.116.146 264 msec 264 msec 256 msec > 14 tpr4-10gi0-1-0.jp.apan.net (203.181.248.109) 280 msec 276 msec 284 >msec > 15 203.178.133.142 260 msec 256 msec 260 msec > 16 ve-51.foundry4.otemachi.wide.ad.jp (203.178.141.141) 256 msec 260 msec >268 msec > 17 pc3.yagami.wide.ad.jp (203.178.138.245) 268 msec 260 msec 256 msec > 18 fe-2-0.hitachi1.k2.wide.ad.jp (203.178.138.218) 268 msec 264 msec 260 >msec > 19 orange.kame.net (203.178.141.194) 260 msec 260 msec 260 msec > >Tracing the route to orange.kame.net (2001:200:0:8002:203:47FF:FEA5:3085) > 1 mantova-atm3-1-30.bh.access.hea.net (2001:770:8:20::1) 0 msec 0 msec 4 >msec > 2 hyperion-gige5-3.bh.core.hea.net (2001:770:8:1F::1) 0 msec 4 msec 0 >msec > 3 luna-gige0-0-0.kil.core.hea.net (2001:770:90:5::1) 4 msec 0 msec 0 >msec > 4 gx-link.core.hea.net (2001:770:90:7::2) 0 msec 4 msec 0 msec > 5 2001:CC8:102:5::2 156 msec 156 msec 156 msec > 6 2001:CC8:102:5::2 160 msec 160 msec 156 msec > 7 2001:CC8:102:5::1 320 msec 320 msec 324 msec > 8 hitachi1.otemachi.wide.ad.jp (2001:200:0:1800::9C4:2) 268 msec 272 >msec 272 msec > 9 pc3.yagami.wide.ad.jp (2001:200:0:1C04::1000:2000) 276 msec 272 msec >268 msec > 10 gr2000.k2.wide.ad.jp (2001:200:0:4819::2000:1) 272 msec 272 msec 276 >msec > 11 orange.kame.net (2001:200:0:8002:203:47FF:FEA5:3085) 276 msec 284 msec >272 msec > >Steph >-- >Mail sent under Debian GNU/Linux >http://frlinux.net - Site d'aide a Linux en Francais >http://frlinux.net/files/frlinux_public_key.asc > >_______________________________________________ >6bone mailing list >6bone@mailman.isi.edu >http://mailman.isi.edu/mailman/listinfo/6bone _________________________________________________________________ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement From haesu at towardex.com Thu May 26 10:51:14 2005 From: haesu at towardex.com (James) Date: Thu May 26 10:52:09 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: References: <45423.134.226.32.57.1117034145.squirrel@webmail.frlinux.net> Message-ID: <20050526175113.GD73687@scylla.towardex.com> On Wed, May 25, 2005 at 06:17:06PM -0700, dimitry verkholashin wrote: > here is what I am getting: > > traceroute to www.kame.net (203.178.141.194), 30 hops max, 40 byte packets > 1 192.168.0.1 (192.168.0.1) 0.505 ms 0.478 ms 0.450 ms > 2 tukw-dsl-gw11-203.tukw.qwest.net (63.231.10.203) 68.017 ms 56.747 ms > 57.869 ms > 3 tukw-agw1.inet.qwest.net (63.231.10.93) 57.085 ms 64.601 ms 49.734 ms > 4 tkw-core-01.inet.qwest.net (205.171.11.97) 57.092 ms 56.530 ms 58.112 > ms [ snip ] > 15 orange.kame.net (203.178.141.194) 201.140 ms 187.462 ms 200.269 ms > > > traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from > 2001:5c0:877a::3, 64 hops max, 12 byte packets > 1 oberon 0.581 ms 0.401 ms 0.342 ms > 2 2001:5c0:8fff:fffe::21c4 143.683 ms 136.765 ms 144.341 ms > 3 ipv6.hexago.com 138.949 ms 143.395 ms 142.394 ms [ snip ] > 15 orange.kame.net 422.456 ms 407.234 ms 415.371 ms > > It would help if you find a tunnelbroker that is more closer to you. I have some contacts at west coast area (you seem to be in northwest pacific) if you want a better tunnel, so let me know off-list. Here is how it looks from my end: traceroute to www.kame.net (203.178.141.194), 64 hops max, 40 byte packets 1 mis.0.ge-0-0-0.r2.bos.twdx.net (65.124.20.193) 0.386 ms 0.175 ms 0.255 ms 2 2.ge-0-2-0.c1.bos.twdx.net (65.116.132.193) 0.167 ms 0.167 ms 0.178 ms 3 63.239.36.245 (63.239.36.245) 0.486 ms 0.376 ms 0.483 ms 4 bos-core-02.inet.qwest.net (205.171.28.57) 0.983 ms 1.111 ms 1.021 ms 5 jfk-core-01.inet.qwest.net (205.171.8.110) 6.455 ms 6.071 ms 6.933 ms 6 svl-core-01.inet.qwest.net (205.171.14.121) 74.531 ms 74.511 ms 74.019 ms 7 tko-core-01.inet.qwest.net (65.120.19.69) 209.122 ms 209.050 ms 209.101 ms 8 jpx-brdr-01.inet.qwest.net (65.120.19.66) 209.581 ms 209.498 ms 209.615 ms 9 203.181.102.189 (203.181.102.189) 200.601 ms 200.065 ms 200.072 ms 10 gsr-ote101.kddnet.ad.jp (203.181.96.119) 209.594 ms 209.571 ms 209.113 ms 11 cm-ote128.kddnet.ad.jp (59.128.5.42) 210.934 ms 211.791 ms 211.500 ms 12 210.132.94.78 (210.132.94.78) 210.229 ms 211.098 ms 210.598 ms 13 ve-5.foundry2.otemachi.wide.ad.jp (203.178.140.216) 212.108 ms 212.195 ms 211.997 ms 14 pc3.yagami.wide.ad.jp (203.178.138.245) 195.214 ms 195.398 ms 195.589 ms 15 fe-2-0.hitachi1.k2.wide.ad.jp (203.178.138.218) 197.095 ms 197.137 ms 197.599 ms 16 orange.kame.net (203.178.141.194) 198.081 ms 197.853 ms 198.796 ms traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:4830:100:20::4, 64 hops max, 12 byte packets 1 mis.0.ge-0-0-0.r2.bos.twdx.net (2001:4830:100:20::1) 0.193 ms 0.177 ms 0.173 ms 2 2.ge-0-2-0.c1.bos.twdx.net (2001:4830:1ff:1::1) 0.169 ms 0.121 ms 0.140 ms 3 245.10ge2-0.cr1.bos1.us.occaid.net (2001:4830:e1::1) 0.328 ms 0.382 ms 0.377 ms 4 23.ge-0-0.cr1.ord1.us.occaid.net (2001:4830:ff:1300::2) 26.883 ms 26.882 ms 26.996 ms 5 57.fe-0-0.cr1.mci1.us.occaid.net (2001:4830:ff:1753::1) 38.509 ms 38.927 ms 38.483 ms 6 6.fe-0-0.cr1.sfo2.us.occaid.net (2001:4830:ff:1750::2) 74.013 ms 74.284 ms 74.538 ms 7 sf-guest.r2.sfo2.isc.org (2001:4f8:4:b:290:6900:b30:541f) 74.528 ms 74.959 ms 74.008 ms 8 2001:4f8:4:236::10 (2001:4f8:4:236::10) 127.545 ms 96.051 ms 95.544 ms 9 hitachi1.otemachi.wide.ad.jp (2001:200:0:4401::3) 205.132 ms 204.936 ms 205.086 ms 10 pc3.yagami.wide.ad.jp (2001:200:0:1c04::1000:2000) 205.120 ms 205.395 ms 205.600 ms 11 gr2000.k2.wide.ad.jp (2001:200:0:4819::2000:1) 206.600 ms 206.829 ms 207.116 ms 12 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 207.118 ms 206.508 ms 207.115 ms -- James Jun Infrastructure and Technology Services TowardEX Technologies Office +1-617-459-4051 x179 | Mobile +1-978-394-2867 james@towardex.com | www.towardex.com From mrp at mrp.net Fri May 27 19:20:14 2005 From: mrp at mrp.net (Mark Prior) Date: Fri May 27 19:21:17 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <20050526175113.GD73687@scylla.towardex.com> References: <45423.134.226.32.57.1117034145.squirrel@webmail.frlinux.net> <20050526175113.GD73687@scylla.towardex.com> Message-ID: <4297D55E.2050806@mrp.net> As tracerouting to kame seems flavour of the month :) here's my view... traceroute to www.kame.net (203.178.141.194), 30 hops max, 38 byte packets 1 gigabitethernet0-2.er2.aarnet.cpe.aarnet.net.au (202.158.193.30) 0.390 ms 0.380 ms 1.071 ms 2 gigether0-2-3.bb1.a.adl.aarnet.net.au (202.158.199.1) 18.693 ms 12.718 ms 19.560 ms 3 pos0-1-0.bb1.a.mel.aarnet.net.au (202.158.194.18) 27.824 ms 28.088 ms 35.446 ms 4 pos0-1-0.bb1.b.syd.aarnet.net.au (202.158.194.34) 39.306 ms 39.132 ms 39.051 ms 5 gigabitethernet3-0.bb3.a.syd.aarnet.net.au (202.158.194.114) 21.461 ms 21.435 ms 21.276 ms 6 pos2-0.bb1.a.suv.aarnet.net.au (202.158.194.82) 57.685 ms 57.656 ms 57.542 ms 7 pos1-0.bb1.b.hnl.aarnet.net.au (202.158.194.86) 116.910 ms 116.985 ms 116.902 ms 8 202.158.204.254 (202.158.204.254) 117.850 ms 117.614 ms 117.761 ms 9 tppr-pos5-0.jp.apan.net (203.181.248.174) 195.347 ms 195.308 ms 195.294 ms 10 tpr4-10gi2-1-0-7.jp.apan.net (203.181.249.19) 214.202 ms 211.314 ms 214.558 ms 11 wide.t-lex.net (203.178.133.142) 195.461 ms 195.988 ms 195.539 ms 12 ve-51.foundry4.otemachi.wide.ad.jp (203.178.141.141) 195.565 ms 195.886 ms 195.567 ms 13 pc3.yagami.wide.ad.jp (203.178.138.245) 196.319 ms 196.417 ms 196.420 ms 14 fe-2-0.hitachi1.k2.wide.ad.jp (203.178.138.218) 199.091 ms 197.828 ms 198.174 ms 15 orange.kame.net (203.178.141.194) 197.440 ms 197.368 ms 196.950 ms and traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:388:4000:4002:204:23ff:fea9:6440, 30 hops max, 16 byte packets 1 gigabitethernet0-2.er2.aarnet.cpe.aarnet.net.au (2001:388:4000:4002:20f:23ff:fea3:ec00) 0.405 ms 0.385 ms 0.229 ms 2 gigether0-2-3.bb1.a.adl.aarnet.net.au (2001:388:1:2003:204:e0ff:fe00:1023) 19.659 ms 19.182 ms 19.063 ms 3 pos0-1-0.bb1.a.mel.aarnet.net.au (2001:388:1:6::2) 24.934 ms 29.98 ms 22.81 ms 4 pos0-1-0.bb1.b.syd.aarnet.net.au (2001:388:1:a::2) 35.454 ms 39.694 ms 39.522 ms 5 gigabitethernet3-0.bb3.a.syd.aarnet.net.au (2001:388:1:1d:205:ddff:feff:2c54) 21.438 ms 21.312 ms 21.311 ms 6 pos2-0.bb1.a.suv.aarnet.net.au (2001:388:1:16:212:43ff:fe40:6200) 57.66 ms 57.68 ms 57.652 ms 7 pos1-0.bb1.b.hnl.aarnet.net.au (2001:388:1:17:205:ddff:fe6d:2008) 116.984 ms 117.134 ms 116.88 ms 8 2001:388:1:c803:290:6900:c8ed:e49d (2001:388:1:c803:290:6900:c8ed:e49d) 117.843 ms * * 9 3ffe:8140:101:d::4 (3ffe:8140:101:d::4) 195.811 ms * 195.915 ms 10 3ffe:8140:101:6::3 (3ffe:8140:101:6::3) 252.64 ms 252.73 ms 252.302 ms 11 hitachi1.otemachi.wide.ad.jp (2001:200:0:1800::9c4:2) 236.924 ms 236.923 ms 237.039 ms 12 pc3.yagami.wide.ad.jp (2001:200:0:1c04::1000:2000) 237.385 ms 237.371 ms 237.55 ms 13 gr2000.k2.wide.ad.jp (2001:200:0:4819::2000:1) 239.216 ms 239.232 ms 238.918 ms 14 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 238.63 ms 238.875 ms 238.556 ms Clearly I need to fix the DNS for hop 8 in both cases :) Mark. From join at uni-muenster.de Mon May 30 00:37:39 2005 From: join at uni-muenster.de (Christian Schild) Date: Mon May 30 00:38:17 2005 Subject: [6bone] cisco ipv6 slow perfs In-Reply-To: <4297D55E.2050806@mrp.net> References: <45423.134.226.32.57.1117034145.squirrel@webmail.frlinux.net> <20050526175113.GD73687@scylla.towardex.com> <4297D55E.2050806@mrp.net> Message-ID: <1117438659.31317.85.camel@lemy.ipv6.uni-muenster.de> Actually, my IPv6 traceroute is faster than IPv4. I guess you have noticed the ~80ms 6bone-gain in some of the severe traceroutes before. YTC ----- $ traceroute www.kame.net traceroute to www.kame.net (203.178.141.194), 30 hops max, 38 byte packets 1 C65RWERK-RZMITAR.UNI-MUENSTER.DE (128.176.184.96) 0.262 ms 0.212 ms 0.198 ms 2 C65UNIB-C65RWERK.UNI-MUENSTER.DE (192.168.19.33) 0.382 ms 0.449 ms 0.966 ms 3 C65RISPB-UNIB.UNI-MUENSTER.DE (192.168.16.97) 0.666 ms 0.502 ms 0.704 ms 4 C65RISPA-ISPB.UNI-MUENSTER.DE (192.168.16.1) 0.810 ms 0.635 ms 0.559 ms 5 ar-essen4-ge0-1-201.g-win.dfn.de (188.1.44.41) 1.653 ms 1.570 ms 1.644 ms 6 cr-essen1-ge4-0.g-win.dfn.de (188.1.86.1) 1.750 ms 1.818 ms 1.599 ms 7 cr-leipzig1-po11-0.g-win.dfn.de (188.1.18.106) 28.908 ms 11.994 ms 11.868 ms 8 cr-frankfurt1-po10-0.g-win.dfn.de (188.1.18.189) 20.877 ms 18.035 ms 35.506 ms 9 dfn.de1.de.geant.net (62.40.105.1) 18.232 ms 19.849 ms 25.854 ms 10 de1-2.de2.de.geant.net (62.40.96.53) 18.493 ms 18.286 ms 18.535 ms 11 abilene-gw.de2.de.geant.net (62.40.103.254) 111.948 ms 112.055 ms 112.028 ms 12 atlang-washng.abilene.ucaid.edu (198.32.8.65) 127.741 ms 127.998 ms 127.828 ms 13 hstnng-atlang.abilene.ucaid.edu (198.32.8.33) 151.793 ms 152.141 ms 152.108 ms 14 losang-hstnng.abilene.ucaid.edu (198.32.8.21) 181.499 ms 181.514 ms 182.415 ms 15 transpac-local.lsanca.pacificwave.net (207.231.240.136) 181.668 ms 181.499 ms 181.544 ms 16 192.203.116.146 (192.203.116.146) 294.986 ms 294.901 ms 294.837 ms 17 tpr3-ae0-6.jp.apan.net (203.181.249.98) 295.020 ms 295.040 ms 295.147 ms 18 wide-ge-tpr3.jp.apan.net (203.181.249.41) 295.218 ms 295.335 ms 295.359 ms 19 pc3.yagami.wide.ad.jp (203.178.138.245) 295.817 ms 296.104 ms 295.826 ms 20 fe-2-0.hitachi1.k2.wide.ad.jp (203.178.138.218) 297.915 ms 297.830 ms 298.039 ms 21 orange.kame.net (203.178.141.194) 297.049 ms 296.992 ms 296.888 ms $ traceroute6 www.kame.net traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:638:500:132:204:75ff:fe82:e0ca, 30 hops max, 16 byte packets 1 join6win.ipv6.uni-muenster.de (2001:638:500:132:208:e2ff:fe0e:2008) 0.29 ms 0.232 ms 0.327 ms 2 nr-ess1.6win.dfn.de (2001:638:f:500::500:1) 2.549 ms 2.79 ms 2.234 ms 3 nr-fra1.6win.dfn.de (2001:638:f:500::1:2) 12.261 ms 12.069 ms 12.14 ms 4 ip-0-3-0-204-r1-IPv6.de.cw.net (2001:5001:100:6::1) 19.577 ms 19.044 ms 19.21 ms 5 so-0-1-1-zcr2.muc.cw.net (2001:5000:0:2::1) 19.111 ms 19.283 ms 19.239 ms 6 as0-bcr2.fra.cw.net (2001:5000:0:5::1) 25.208 ms 25.225 ms 25.438 ms 7 so-1-3-0-dcr1.fra.cw.net (2001:5000:0:8::2) 25.148 ms 25.071 ms 25.328 ms 8 so-4-0-0-dcr1.par.cw.net (2001:5000:0:9::2) 33.61 ms 34.06 ms 33.716 ms 9 so-0-0-0-dcr1.was.cw.net (2001:5000:0:c::2) 114.82 ms 114.004 ms 114.138 ms 10 so-0-0-0-ecr1.was.cw.net (2001:5000:0:52::2) 114.139 ms 114.289 ms 113.978 ms 11 so-0-0-0-ecr1.lax.cw.net (2001:5000:0:53::2) 169.319 ms 174.752 ms 169.408 ms 12 2001:504:a::a500:2500:1 (2001:504:a::a500:2500:1) 169.734 ms 169.159 ms 169.268 ms 13 hitachi1.otemachi.wide.ad.jp (2001:200:0:4401::3) 278.923 ms 278.616 ms 278.742 ms 14 pc3.yagami.wide.ad.jp (2001:200:0:1c04::1000:2000) 279.32 ms 279.608 ms 280.838 ms 15 gr2000.k2.wide.ad.jp (2001:200:0:4819::2000:1) 280.978 ms 280.943 ms 280.969 ms 16 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 280.328 ms 280.684 ms 280.793 ms ----- -- JOIN - IPv6 reference center Christian Schild A WWU project Westfaelische Wilhelms-Universitaet Muenster http://www.join.uni-muenster.de Zentrum fuer Informationsverarbeitung Team: join@uni-muenster.de Roentgenstrasse 9-13 Priv: schild@uni-muenster.de D-48149 Muenster / Germany GPG-/PGP-Key-ID: 6EBFA081 Fon: +49 251 83 31638, fax: +49 251 83 31653 From jordan.mccabe at gmail.com Thu May 5 08:52:48 2005 From: jordan.mccabe at gmail.com (Jordan McCabe) Date: Thu, 05 May 2005 15:52:48 -0000 Subject: [6bone] (no subject) Message-ID: unsubscribe