From yeti@bigpond.com Thu May 16 17:35:01 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4H0YxE15246 for <6bone@mailman.isi.edu>; Thu, 16 May 2002 17:35:01 -0700 (PDT) Received: from mta04ps.bigpond.com (mta04ps.bigpond.com [144.135.25.136]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4H0Ysb03870 for <6bone@isi.edu>; Thu, 16 May 2002 17:34:58 -0700 (PDT) Received: from dpro ([144.135.25.72]) by mta04ps.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GW8C9C00.D91 for <6bone@isi.edu>; Fri, 17 May 2002 10:34:24 +1000 Received: from p1013-ipadfx01hodogaya.kanagawa.ocn.ne.jp ([61.214.156.13]) by PSMAM02.mailsvc.email.bigpond.com(MailRouter V3.0m 74/5044089); 17 May 2002 10:34:24 From: "Dan Webb" To: <6bone@ISI.EDU> Date: Fri, 17 May 2002 09:39:10 +0900 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [6bone] RE: 6bone mailing list Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Yeah I was a little wrong, it did go to the correct mailing email address, but my filter didn't catch it for some reason and sent it to the wrong folder. Thats what I get for reading and replying to email before my morning coffee(s) :) Dan From pekkas@netcore.fi Thu May 16 22:03:29 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4H53SE16728 for <6bone@mailman.isi.edu>; Thu, 16 May 2002 22:03:28 -0700 (PDT) Received: from netcore.fi (netcore.fi [193.94.160.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4H53Rb16928 for <6Bone@ISI.EDU>; Thu, 16 May 2002 22:03:27 -0700 (PDT) Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id g4H50sK18462; Fri, 17 May 2002 08:00:54 +0300 Date: Fri, 17 May 2002 08:00:54 +0300 (EEST) From: Pekka Savola To: Allan Edgard Silva Freitas cc: 6Bone@ISI.EDU In-Reply-To: <00bb01c1fd2d$a204e530$1f02010a@intracefet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [6bone] Re: Some problems with sendmail, Linux and v6 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Thu, 16 May 2002, Allan Edgard Silva Freitas wrote: > I get no runing sendmail, I can only use: > "O DaemonPortOptions=Name=IPv4, Family=inet" > or > "O DaemonPortOptions=Name=IPv6, Family=inet6" > > So, I only could have an IPv6 SMTP Server or an IPv4 SMTP Server but > never the both running. I had a FreeBSD box, where IPv6 is native and I > see that the same configuration have no problems in Free. Do anyone know > some specific bug regarding about this configuration above described? > Some hint to I overpass it?? You must bind one to an IP address, like: DAEMON_OPTIONS(`port=smtp,Addr=2001:670:86::1, Name=MTA-v6, Family=inet6') This is due to the way Linux bind() currently works (reason: mapped addresses) -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From jorgen@hovland.cx Fri May 17 02:51:25 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4H9pOE15869 for <6bone@mailman.isi.edu>; Fri, 17 May 2002 02:51:25 -0700 (PDT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4H9pLb07880 for <6Bone@ISI.EDU>; Fri, 17 May 2002 02:51:24 -0700 (PDT) Received: from hera (58.80-203-6.nextgentel.com [80.203.6.58]) by mail.broadpark.no (Postfix) with SMTP id BBD847D27; Fri, 17 May 2002 11:51:13 +0200 (MEST) Message-ID: <001701c1fd88$60c753e0$0200000a@hera> From: =?iso-8859-1?Q?J=F8rgen_Hovland?= To: "Allan Edgard Silva Freitas" , <6Bone@ISI.EDU> References: <00bb01c1fd2d$a204e530$1f02010a@intracefet> Date: Fri, 17 May 2002 11:51:11 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C1FD99.23FF1DB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [6bone] Re: Some problems with sendmail, Linux and v6 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_0014_01C1FD99.23FF1DB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In linux, INET6 :: is also INET4 0.0.0.0 (atleast for sendmail) So you dont need to specify inet if you are using inet6 anyip. -j ----- Original Message -----=20 From: Allan Edgard Silva Freitas=20 To: 6Bone@ISI.EDU=20 Sent: Friday, May 17, 2002 1:01 AM Subject: Some problems with sendmail, Linux and v6 Hi folks, I get some problems running sendmail in an IPv6/IPv4 Linux box (kernel = 2.4.5 - conectiva a based-RedHat distribution). I compiled both Sendmail = 8.9.1 with WINE patch and Sendmail 8.12 using -DNETINET6 option and I = see if I use at the same time the two lines below in sendmail.cf: "O DaemonPortOptions=3DName=3DIPv4, Family=3Dinet" ("O = DaemonPortOptions=3DFamily=3Dinet6" in /etc/sendmail6.cf using WINE) "O DaemonPortOptions=3DName=3DIPv6, Family=3Dinet6" ("O = DaemonPortOptions=3DFamily=3Dinet6" in /etc/sendmail6.cf using WINE) I get no runing sendmail, I can only use: "O DaemonPortOptions=3DName=3DIPv4, Family=3Dinet" or=20 "O DaemonPortOptions=3DName=3DIPv6, Family=3Dinet6" So, I only could have an IPv6 SMTP Server or an IPv4 SMTP Server but = never the both running. I had a FreeBSD box, where IPv6 is native and I = see that the same configuration have no problems in Free. Do anyone know = some specific bug regarding about this configuration above described? = Some hint to I overpass it?? Thanks, Allan Freitas ------=_NextPart_000_0014_01C1FD99.23FF1DB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
In linux, INET6 :: is also INET4 = 0.0.0.0 (atleast=20 for sendmail)
So you dont need to specify inet if you = are using=20 inet6 anyip.
 
 
-j
----- Original Message -----
From:=20 Allan = Edgard Silva=20 Freitas
Sent: Friday, May 17, 2002 1:01 = AM
Subject: Some problems with = sendmail,=20 Linux and v6

Hi folks,
 
I get some problems running sendmail = in an=20 IPv6/IPv4 Linux box (kernel 2.4.5 - conectiva a based-RedHat = distribution). I=20 compiled both Sendmail 8.9.1 with WINE patch and Sendmail 8.12 using=20 -DNETINET6 option and I see if I use at the same time the two lines = below in=20 sendmail.cf:
"O DaemonPortOptions=3DName=3DIPv4, = Family=3Dinet"=20         ("O = DaemonPortOptions=3DFamily=3Dinet6" in=20 /etc/sendmail6.cf using WINE)
"O DaemonPortOptions=3DName=3DIPv6,=20 Family=3Dinet6"       ("O=20 DaemonPortOptions=3DFamily=3Dinet6" in /etc/sendmail6.cf using = WINE)
 
I get no runing sendmail, I can only = use:
"O DaemonPortOptions=3DName=3DIPv4, Family=3Dinet"
    or
"O DaemonPortOptions=3DName=3DIPv6, Family=3Dinet6"
So, I only could have an IPv6 SMTP Server or an IPv4 SMTP = Server but=20 never the both running. I had a FreeBSD box, where IPv6 is native and = I see=20 that the same configuration have no problems in Free. Do anyone know = some=20 specific bug regarding about this configuration above described? Some = hint to=20 I overpass it??
 
Thanks,
 
Allan Freitas
 
------=_NextPart_000_0014_01C1FD99.23FF1DB0-- From michael@kjorling.com Fri May 17 02:57:30 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4H9vTE17278 for <6bone@mailman.isi.edu>; Fri, 17 May 2002 02:57:30 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4H9vSb09012 for <6Bone@ISI.EDU>; Fri, 17 May 2002 02:57:28 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4H9rvW09857; Fri, 17 May 2002 09:53:57 GMT Date: Fri, 17 May 2002 11:53:53 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: Allan Edgard Silva Freitas cc: 6bone <6Bone@ISI.EDU> In-Reply-To: <00bb01c1fd2d$a204e530$1f02010a@intracefet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [6bone] Re: Some problems with sendmail, Linux and v6 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 16 2002 20:01 -0300, Allan Edgard Silva Freitas wrote: > I compiled both Sendmail 8.9.1 with WINE patch and Sendmail 8.12 > using -DNETINET6 option and I see if I use at the same time the two > lines below in sendmail.cf: > "O DaemonPortOptions=Name=IPv4, Family=inet" ("O DaemonPortOptions=Family=inet6" in /etc/sendmail6.cf using WINE) > "O DaemonPortOptions=Name=IPv6, Family=inet6" ("O DaemonPortOptions=Family=inet6" in /etc/sendmail6.cf using WINE) > > I get no runing sendmail, I can only use: > "O DaemonPortOptions=Name=IPv4, Family=inet" > or > "O DaemonPortOptions=Name=IPv6, Family=inet6" > > So, I only could have an IPv6 SMTP Server or an IPv4 SMTP Server but > never the both running. I had a FreeBSD box, where IPv6 is native > and I see that the same configuration have no problems in Free. Do > anyone know some specific bug regarding about this configuration > above described? Some hint to I overpass it?? Hmmm... I have sendmail accepting connections over both IPv4 and IPv6 on a dual-stacked Linux 2.4.18 box with no problem, and every now and then I do get a mail in my inbox that has travelled over IPv6 - even though most are still, obviously, IPv4. Here's what I have in my sendmail.mc that relates to this: dnl DAEMON_OPTIONS(`Port=smtp, Name=MTA-IPv4, Family=inet') dnl DAEMON_OPTIONS(`Port=smtp, Name=MTA-IPv6, Family=inet6') DAEMON_OPTIONS(`Port=smtp, Name=MTA, Family=inet6') As you can see, I effectively only have one DAEMON_OPTIONS() line, giving Family=inet6. There is some peculiarity with the Linux kernel that an IPv6 listening socket will also accept IPv4 connections - it was in the original standard but experience has shown since then that it does not always produce the desired results. Anyway, why don't you go ahead and try your sendmail over IPv4 with only an AF_INET6 socket listening? Provided that you have a stock kernel release that might do the trick. I'm running sendmail 8.11.6 compiled with IPv6 support (of course) in case that matters. Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE85NM1KqN7/Ypw4z4RAguQAKCAYDkjGdFI2QbiNVYoabEuNG8xBACg1Eem 0hzi8HmPJSjK7Kwvic5+7Tw= =t/1v -----END PGP SIGNATURE----- From hgoes@eu.uu.net Fri May 17 06:41:59 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4HDfxE04149 for <6bone@mailman.isi.edu>; Fri, 17 May 2002 06:41:59 -0700 (PDT) Received: from ams2eusosrv9.ams.ops.eu.uu.net (ams2eusosrv9.ams.ops.eu.uu.net [146.188.99.14]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4HDfwb06403 for <6bone@isi.edu>; Fri, 17 May 2002 06:41:58 -0700 (PDT) Received: from ams2eusosrv1.ams.ops.eu.uu.net by ams2eusosrv9.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: ams2eusosrv1.ams.ops.eu.uu.net [146.188.99.6]) id QQmpfy23540 for <6bone@isi.edu>; Fri, 17 May 2002 13:41:55 GMT Received: from eunoc13.ams.ops.eu.uu.net by ams2eusosrv1.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: eunoc13.ams.ops.eu.uu.net [146.188.97.230]) id QQmpfy20811 for <6bone@isi.edu>; Fri, 17 May 2002 13:41:39 GMT Received: from localhost by eunoc13.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: hgoes@localhost) id QQmpfy01668; Fri, 17 May 2002 13:41:37 GMT Date: Fri, 17 May 2002 13:41:37 +0000 (GMT) From: Hans Goes X-Sender: hgoes@eunoc13.ams.ops.eu.uu.net Reply-To: hans.goes@wcom.com To: 6bone@ISI.EDU Message-ID: X-Organization: WorldCom X-Department: EMEA Network Operations X-Address: Joan Muyskenweg 24 1096 CJ Amsterdam X-Phone: +31 20 7111 000. Telefax: +31 20 711 2445 X-URL: http://www.worldcom.com/nl MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [6bone] ipv6 software for cisco 2600 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, As far as I can see there is no IOS software available for Cisco 2600 with only 32meg memory ? 48 megs seems to be the lowest possibility. Thanks Hans Goes WorldCom EMEA Network Operations Joan Muyskenweg 24 1096 CJ Amsterdam The Netherlands Tel: +31 20 7112428 Fax: +31 20 7112455 Email: hans.goes@wcom.com http://www.wcom.com/nl/ From paitken@cisco.com Fri May 17 12:35:27 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4HJZQE00089 for <6bone@mailman.isi.edu>; Fri, 17 May 2002 12:35:26 -0700 (PDT) Received: from cisco.com (mrwint.cisco.com [144.254.98.48]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4HJZPb06794 for <6bone@ISI.EDU>; Fri, 17 May 2002 12:35:25 -0700 (PDT) Received: from cisco.com (etive.cisco.com [10.49.189.164]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id UAA18213; Fri, 17 May 2002 20:35:18 +0100 (BST) Message-ID: <3CE55B69.7040208@cisco.com> Date: Fri, 17 May 2002 20:35:05 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (compatible; MSIE 5.5; Windows NT 5.0) X-Accept-Language: en-gb, en-us MIME-Version: 1.0 To: hans.goes@wcom.com CC: 6bone@ISI.EDU Subject: Re: [6bone] ipv6 software for cisco 2600 References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hans, > As far as I can see there is no IOS software available for Cisco 2600 with > only 32meg memory ? > 48 megs seems to be the lowest possibility. Correct; the smallest footprint for a 2600 is an IP PLUS image requiring 48M RAM and 16M Flash. Note that this sort of question is best sent to either tac@cisco.com or ipv6-support@cisco.com Cheers. -- Paul Aitken IPv6 Development, Cisco Systems Ltd, Edinburgh, Scotland. EH6 6LX From itojun@itojun.org Sat May 18 02:41:50 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4I9foE23741 for <6bone@mailman.isi.edu>; Sat, 18 May 2002 02:41:50 -0700 (PDT) Received: from starfruit.itojun.org (dial-5-D02.QXO1.equant.net [57.72.132.5]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4I9fkb16768 for <6Bone@ISI.EDU>; Sat, 18 May 2002 02:41:47 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by starfruit.itojun.org (Postfix) with ESMTP id AFE4E7BC; Sat, 18 May 2002 11:44:15 +0900 (JST) To: Allan Edgard Silva Freitas , 6bone <6Bone@ISI.EDU> In-reply-to: michael's message of Fri, 17 May 2002 11:53:53 +0200. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] Re: Some problems with sendmail, Linux and v6 From: Jun-ichiro itojun Hagino Date: Sat, 18 May 2002 11:44:15 +0900 Message-Id: <20020518024415.AFE4E7BC@starfruit.itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >> I compiled both Sendmail 8.9.1 with WINE patch and Sendmail 8.12 >> using -DNETINET6 option and I see if I use at the same time the two >> lines below in sendmail.cf: > >> "O DaemonPortOptions=Name=IPv4, Family=inet" ("O DaemonPortOptions=Family=inet6" in /etc/sendmail6.cf using WINE) >> "O DaemonPortOptions=Name=IPv6, Family=inet6" ("O DaemonPortOptions=Family=inet6" in /etc/sendmail6.cf using WINE) >> >> I get no runing sendmail, I can only use: >> "O DaemonPortOptions=Name=IPv4, Family=inet" >> or >> "O DaemonPortOptions=Name=IPv6, Family=inet6" >> >> So, I only could have an IPv6 SMTP Server or an IPv4 SMTP Server but >> never the both running. I had a FreeBSD box, where IPv6 is native >> and I see that the same configuration have no problems in Free. Do >> anyone know some specific bug regarding about this configuration >> above described? Some hint to I overpass it?? The trouble is caused by the lack of standard for bind(2) behavior, when bind(2) to AF_INET and AF_INET6 are made the same port number. Linux rejects AF_INET bind(2) after AF_INET6 bind(2). therefore, you need to open only a single AF_INET6 socket, and expect IPv4 traffic to come in from AF_INET6 socket. so the following should make your sendmail to accept both IPv4 and IPv6 connections: >> "O DaemonPortOptions=Name=IPv6, Family=inet6" on other platforms, two line configuration ("inet" and "inet6") should work fine. i really feel sorry for you, and sad about the lack of standard here. itojun From Francis.Dupont@enst-bretagne.fr Sat May 18 09:17:57 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4IGHtE07287 for <6bone@mailman.isi.edu>; Sat, 18 May 2002 09:17:57 -0700 (PDT) Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4IGHsb24479 for <6Bone@ISI.EDU>; Sat, 18 May 2002 09:17:54 -0700 (PDT) Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1]) by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id g4IGBQn12681; Sat, 18 May 2002 18:11:26 +0200 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id SAA27166; Sat, 18 May 2002 18:11:26 +0200 (MET DST) Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id g4IGBPT99930; Sat, 18 May 2002 18:11:26 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200205181611.g4IGBPT99930@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Jun-ichiro itojun Hagino cc: Allan Edgard Silva Freitas , 6bone <6Bone@ISI.EDU> Subject: Re: [6bone] Re: Some problems with sendmail, Linux and v6 In-reply-to: Your message of Sat, 18 May 2002 11:44:15 +0900. <20020518024415.AFE4E7BC@starfruit.itojun.org> Date: Sat, 18 May 2002 18:11:25 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: In your previous mail you wrote: i really feel sorry for you, and sad about the lack of standard here. => the IPV6_V6ONLY stuff was added in the RFC 2553 revision (when it will be published BTW) just to fill this hole (and not in the general case where a RFC 2553 compliant implementation should accept IPv4 and IPv6 traffic on a socket bound to ::, but for the case where a different policy is applied to IPv6 and IPv5 traffics. Today the only application in this case is BIND 9). Regards Francis.Dupont@enst-bretagne.fr From itojun@itojun.org Sat May 18 15:40:14 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4IMeDE06664 for <6bone@mailman.isi.edu>; Sat, 18 May 2002 15:40:14 -0700 (PDT) Received: from starfruit.itojun.org (dial-5-D02.QXO1.equant.net [57.72.132.5]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4IMeBb03024 for <6Bone@ISI.EDU>; Sat, 18 May 2002 15:40:12 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by starfruit.itojun.org (Postfix) with ESMTP id 6429E7B9; Sun, 19 May 2002 07:40:00 +0900 (JST) To: Francis Dupont Cc: 6bone <6Bone@ISI.EDU> In-reply-to: Francis.Dupont's message of Sat, 18 May 2002 18:11:25 +0200. <200205181611.g4IGBPT99930@givry.rennes.enst-bretagne.fr> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] Re: Some problems with sendmail, Linux and v6 From: Jun-ichiro itojun Hagino Date: Sun, 19 May 2002 07:40:00 +0900 Message-Id: <20020518224000.6429E7B9@starfruit.itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >=> the IPV6_V6ONLY stuff was added in the RFC 2553 revision (when it will >be published BTW) just to fill this hole (and not in the general case >where a RFC 2553 compliant implementation should accept IPv4 and IPv6 >traffic on a socket bound to ::, but for the case where a different policy >is applied to IPv6 and IPv5 traffics. Today the only application in this >case is BIND 9). and mozilla uses it too. what IPV6_V6ONLY spec says is not really enough, IMHO. itojun From paul@timmins.net Sun May 19 09:58:13 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4JGwBE18289 for <6bone@mailman.isi.edu>; Sun, 19 May 2002 09:58:13 -0700 (PDT) Received: from mainframe.dtw.techapartment.net ([64.240.95.11]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4JGw9b24922 for <6bone@isi.edu>; Sun, 19 May 2002 09:58:10 -0700 (PDT) Received: from pikachu.dtw.techapartment.net ([10.69.8.100] helo=localhost.localdomain) by mainframe.dtw.techapartment.net with esmtp (Exim 3.35 #1 (Debian)) id 179U0U-0003o5-00 for <6bone@isi.edu>; Sun, 19 May 2002 12:58:06 -0400 From: Paul Timmins To: 6bone@ISI.EDU Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 19 May 2002 12:57:29 -0400 Message-Id: <1021827449.24642.6.camel@pikachu> Mime-Version: 1.0 Subject: [6bone] IPv6 port scanners? Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: I'm looking for an IPv6 portscanner, preferrably for UNIX, to audit my network for unnecessary services. I'd prefer something like NMAP that can scan a block of IP addresses, but one that can scan just one at a time works fine for me too. Any suggestions? -Paul From jim@daedelus.com Sun May 19 10:00:58 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4JH0vE18749 for <6bone@mailman.isi.edu>; Sun, 19 May 2002 10:00:57 -0700 (PDT) Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4JH0vb25476 for <6bone@isi.edu>; Sun, 19 May 2002 10:00:57 -0700 (PDT) Received: from imladris.daedelus.com (imladris.daedelus.com [206.197.161.13]) by uillean.fuaim.com (8.11.6/8.11.6) with ESMTP id g4JH0uR01656 for <6bone@isi.edu>; Sun, 19 May 2002 10:00:56 -0700 Received: from balrog.daedelus.com (dhcp-64.daedelus.com [206.197.161.64]) by imladris.daedelus.com (8.11.6/8.11.6) with ESMTP id g4JGwht01075 for <6bone@isi.edu>; Sun, 19 May 2002 09:58:43 -0700 Message-Id: <5.1.1.2.0.20020519095858.0294dfc8@imap.daedelus.com> X-Sender: jim@imap.daedelus.com X-Mailer: QUALCOMM Windows Eudora Version 5.1.1.3 (Beta) Date: Sun, 19 May 2002 10:00:50 -0700 To: 6bone@ISI.EDU From: Jim Martin Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] 6Bone registry entries when multihomed? Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: [This is a resend - sorry for any duplicates!] Gentlepeople, I've got a procedural question for the group. Let's say someone has gotten two tunnels from two upstream v6 providers. Each provider has delegated him a /48. When being a responsible 6Bone citizen, does he register 2 inet6num objects and one ipv6-site object? Or perhaps two inet6num objects and two ipv6-site objects? If it's two ipv6-site objects, is there a naming convention (ie, MYSITE-PROVIDER1 and MYSITE-PROVIDER2)? Just trying to play nicely with the group ... :-) - Jim From nicolas.deffayet-extml@ndsoftwaregroup.com Sun May 19 10:59:36 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4JHxaE27283 for <6bone@mailman.isi.edu>; Sun, 19 May 2002 10:59:36 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4JHxWb06004 for <6bone@ISI.EDU>; Sun, 19 May 2002 10:59:34 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 179Uxq-000M4C-00 for 6bone@ISI.EDU; Sun, 19 May 2002 19:59:26 +0200 Received: (qmail 4996 invoked from network); 19 May 2002 18:12:01 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 19 May 2002 18:12:01 -0000 From: "Nicolas DEFFAYET" To: "'Jim Martin'" , <6bone@ISI.EDU> Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Sun, 19 May 2002 19:59:18 +0200 Organization: NDSoftware Group Message-ID: <000301c1ff5e$e591a260$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <5.1.1.2.0.20020519095858.0294dfc8@imap.daedelus.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Jim Martin > Sent: Sunday, May 19, 2002 7:01 PM > To: 6bone@ISI.EDU > Subject: [6bone] 6Bone registry entries when multihomed? > > > [This is a resend - sorry for any duplicates!] > > Gentlepeople, > I've got a procedural question for the group. Let's say > someone has gotten > two tunnels from two upstream v6 providers. Each provider has > delegated him > a /48. When being a responsible 6Bone citizen, does he > register 2 inet6num > objects and one ipv6-site object? Or perhaps two inet6num > objects and two > ipv6-site objects? If it's two ipv6-site objects, is there a naming > convention (ie, MYSITE-PROVIDER1 and MYSITE-PROVIDER2)? > 2 inet6num 1 ipv6-site A exemple: http://whois.6bone.net/cgi-bin/whois?NDSOFTWARE From michel@arneill-py.sacramento.ca.us Sun May 19 13:59:45 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4JKxjE27260 for <6bone@mailman.isi.edu>; Sun, 19 May 2002 13:59:45 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4JKxib07660 for <6bone@ISI.EDU>; Sun, 19 May 2002 13:59:44 -0700 (PDT) Subject: RE: [6bone] 6Bone registry entries when multihomed? MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Sun, 19 May 2002 13:59:37 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: <2B81403386729140A3A899A8B39B046405E076@server2000.arneill-py.sacramento.ca.us> content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] 6Bone registry entries when multihomed? Thread-Index: AcH/Xyd2bVGbeLCuTqySfp6gwLIRxAAGAHVg From: "Michel Py" To: "Nicolas DEFFAYET" , "Jim Martin" , <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4JKxjE27260 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Jim, > Jim Martin wrote: > I've got a procedural question for the group. Let's say > someone has gotten two tunnels from two upstream v6 providers. > Each provider has delegated him a /48. When being a responsible > 6Bone citizen, does he register 2 inet6num objects and one > ipv6-site object? Yes. > Nicolas DEFFAYET wrote > A exemple: http://whois.6bone.net/cgi-bin/whois?NDSOFTWARE Nicolas is an ISP. If you got /48s it probably means you are not, here is an example that might be closer to your needs: http://whois.6bone.net/cgi-bin/whois?ARNEILLPY Note that this does not provide you with a multihoming solution, since both of your upstreams will filter your /48. Michel. From itojun@itojun.org Sun May 19 22:20:06 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4K5K6E11505 for <6bone@mailman.isi.edu>; Sun, 19 May 2002 22:20:06 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4K5K4b20484 for <6bone@ISI.EDU>; Sun, 19 May 2002 22:20:05 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 5D1DE4B22 for <6bone@ISI.EDU>; Mon, 20 May 2002 14:20:01 +0900 (JST) To: 6bone@ISI.EDU X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net Date: Mon, 20 May 2002 14:20:01 +0900 Message-ID: <15005.1021872001@itojun.org> Subject: [6bone] IPv6 site count Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: you may find it interesting: http://www.jp.ipv6.org/sitecount/index.en.html we think there are at least 1000 /48 IPv6 sites in Japan. (since it is rather hard to count # of 6to4 sites, there can be a lot more) itojun From michael@kjorling.com Mon May 20 05:10:03 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KCA3E08353 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 05:10:03 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KCA1b28051 for <6bone@ISI.EDU>; Mon, 20 May 2002 05:10:02 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4KBnuW23105; Mon, 20 May 2002 11:49:56 GMT Date: Mon, 20 May 2002 13:49:31 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: Paul Timmins cc: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] IPv6 port scanners? In-Reply-To: <1021827449.24642.6.camel@pikachu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 19 2002 12:57 -0400, Paul Timmins wrote: > I'm looking for an IPv6 portscanner, preferrably for UNIX, to audit my > network for unnecessary services. > I'd prefer something like NMAP that can scan a block of IP addresses, > but one that can scan just one at a time works fine for me too. > Any suggestions? > -Paul A fairly quick Google search turned up a page on Freshmeat listing halfscan6, "An IPv6 port scanner." See http://freshmeat.net/projects/halfscan6/ Disclaimer: I have not tried it myself, and have no idea about its quality! Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE86OLaKqN7/Ypw4z4RAtPvAKCinkH/8RlLp5SGSPRwJFAbcOieEQCeMF8o PozORcOM95h0C0645FRZlsk= =/eXz -----END PGP SIGNATURE----- From rocheml@httrack.com Mon May 20 05:42:02 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KCg2E16472 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 05:42:02 -0700 (PDT) Received: from pop.wanadoo.fr (ATuileries-103-1-1-54.abo.wanadoo.fr [193.251.36.54]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KCg0b12695 for <6bone@ISI.EDU>; Mon, 20 May 2002 05:42:01 -0700 (PDT) Received: from serv0.httrack.com (machine-1.localnet.loc [192.168.1.1]) by pop.wanadoo.fr (8.12.2/8.12.2/check_local4.1) with ESMTP id g4KCfrxE002443 for <6bone@ISI.EDU>; Mon, 20 May 2002 14:41:53 +0200 X-Spam-Filter: check_local@pop.wanadoo.fr by digitalanswers.org Message-Id: <5.1.0.14.0.20020520143041.00a14540@wheresmymailserver.com> X-Sender: rocheml@pop.pro.proxad.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 20 May 2002 14:41:46 +0200 To: <6bone@ISI.EDU> From: Xavier Roche Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [6bone] AAAA and A6 recent status? Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, rfc #2874 seem to suggest that AAAA records will "soon" disappear ; is the A6 record format the definitive one? If the 2874 considered as 'final' standard? Regards, Xavier From michael@kjorling.com Mon May 20 06:29:04 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KDT3E26147 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 06:29:04 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KDT2b01042 for <6bone@ISI.EDU>; Mon, 20 May 2002 06:29:02 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4KDSxW26429; Mon, 20 May 2002 13:28:59 GMT Date: Mon, 20 May 2002 15:28:46 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: Xavier Roche cc: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <5.1.0.14.0.20020520143041.00a14540@wheresmymailserver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 20 2002 14:41 +0200, Xavier Roche wrote: > Hi, > > rfc #2874 seem to suggest that AAAA records will "soon" disappear ; > is the A6 record format the definitive one? If the 2874 considered > as 'final' standard? > > > Regards, > Xavier I believe not. There is draft-ietf-dnsext-ipv6-addresses-01 which says: Abstract This document clarifies and updates the standards status of RFCs that define direct and reverse map of IPv6 addresses in DNS. This document moves the A6 and Bit label specifications to experimental status. and: 1.1 Standards action taken This document changes the status of RFCs 2673 and 2874 from Proposed Standard to Experimental. as well as: 2.2 Recommended standard action Based on the perceived consensus, this document recommend that RFC 1886 stay on standards track and be advanced, while moving RFC 2874 to Experimental status. The I-D, dated March 2002 and expiring September 2002, is available at ftp://ftp.isi.edu/in-notes/search.ietf.org/internet-drafts/draft-ietf-dnsext-ipv6-addresses-01.txt and updates RFCs 1886, 2673 and 2874. Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE86PoZKqN7/Ypw4z4RArMVAJ9gEpK3EjD3019KuwTdDbxPtba2HwCgskwx yTZbMYHyLAc7FNJomTmjN7s= =f18o -----END PGP SIGNATURE----- From nicolas.deffayet-extml@ndsoftwaregroup.com Mon May 20 06:33:47 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KDXkE27728 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 06:33:47 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KDXjb03210 for <6bone@ISI.EDU>; Mon, 20 May 2002 06:33:45 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 179nIF-0005Zp-00 for 6bone@ISI.EDU; Mon, 20 May 2002 15:33:43 +0200 Received: (qmail 13557 invoked from network); 20 May 2002 13:46:27 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 20 May 2002 13:46:27 -0000 From: "Nicolas DEFFAYET" To: "'Xavier Roche'" , <6bone@ISI.EDU> Subject: RE: [6bone] AAAA and A6 recent status? Date: Mon, 20 May 2002 15:33:31 +0200 Organization: NDSoftware Group Message-ID: <003901c20002$eeb63b90$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <5.1.0.14.0.20020520143041.00a14540@wheresmymailserver.com> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Xavier Roche > Sent: Monday, May 20, 2002 2:42 PM > To: 6bone@ISI.EDU > Subject: [6bone] AAAA and A6 recent status? > Hi, > rfc #2874 seem to suggest that AAAA records will "soon" > disappear ; is the A6 record format the definitive one? If > the 2874 considered as 'final' standard? I don't reply to your initial question, but i want add my comment: Don't forget that old system will try to resolve only AAAA. I suggest to use AAAA and A6 for each dns forward entry. It's the same problem with .int and .arpa for reverse (PTR)... Best Regards, Nicolas DEFFAYET From itojun@itojun.org Mon May 20 06:40:11 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KDeAE28728 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 06:40:11 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KDe8b06247 for <6bone@ISI.EDU>; Mon, 20 May 2002 06:40:09 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id A9A374B22; Mon, 20 May 2002 22:40:06 +0900 (JST) To: Xavier Roche Cc: 6bone@ISI.EDU X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net In-reply-to: rocheml's message of Mon, 20 May 2002 14:41:46 +0200. <5.1.0.14.0.20020520143041.00a14540@wheresmymailserver.com> Subject: Re: [6bone] AAAA and A6 recent status? Date: Mon, 20 May 2002 22:40:06 +0900 Message-ID: <20213.1021902006@itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >rfc #2874 seem to suggest that AAAA records will "soon" disappear ; is the A6 >record format the definitive one? If the 2874 considered as 'final' standard? AAAA is the final standard. draft-ietf-dnsext-ipv6-addresses-01.txt itojun From pekkas@netcore.fi Mon May 20 07:15:58 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KEFvE06175 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 07:15:57 -0700 (PDT) Received: from netcore.fi (netcore.fi [193.94.160.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KEFub22712 for <6bone@ISI.EDU>; Mon, 20 May 2002 07:15:56 -0700 (PDT) Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id g4KEFmB09668; Mon, 20 May 2002 17:15:48 +0300 Date: Mon, 20 May 2002 17:15:48 +0300 (EEST) From: Pekka Savola To: Xavier Roche cc: 6bone@ISI.EDU Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <5.1.0.14.0.20020520143041.00a14540@wheresmymailserver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, 20 May 2002, Xavier Roche wrote: > rfc #2874 seem to suggest that AAAA records will "soon" disappear ; is > the A6 record format the definitive one? If the 2874 considered as > 'final' standard? Short answer: forget about A6 altogether. Long answer: look in the archives of the mailing list and e.g. http://search.ietf.org/internet-drafts/draft-ietf-dnsext-ipv6-addresses-01.txt -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From bmanning@ISI.EDU Mon May 20 07:35:10 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KEZAE11697 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 07:35:10 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g4KEZ1i04991; Mon, 20 May 2002 07:35:01 -0700 (PDT) From: Bill Manning Message-Id: <200205201435.g4KEZ1i04991@boreas.isi.edu> Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <20213.1021902006@itojun.org> from "itojun@iijlab.net" at "May 20, 2 10:40:06 pm" To: itojun@iijlab.net Date: Mon, 20 May 2002 07:35:00 -0700 (PDT) Cc: rocheml@httrack.com, 6bone@ISI.EDU X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: % >rfc #2874 seem to suggest that AAAA records will "soon" disappear ; is the A6 % >record format the definitive one? If the 2874 considered as 'final' standard? % % AAAA is the final standard. % draft-ietf-dnsext-ipv6-addresses-01.txt % % itojun final is such a strong word. The current recommendation is: draft-ietf-dnsext-ipv6-addresses-01.txt, which might become an RFC. Even then, changes can and do occur. Its a pretty safe bet that AAAA records will get you what you want, but apps should be prepared to deal w/ A6 records, since they do exist and show every likelyhood of remaining in the code. -- --bill From thomas@habets.pp.se Mon May 20 09:06:41 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KG6eE23290 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 09:06:41 -0700 (PDT) Received: from akilles.darkface.pp.se (root@darkface.pp.se [212.105.77.200]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KG6cb20639 for <6bone@ISI.EDU>; Mon, 20 May 2002 09:06:39 -0700 (PDT) Received: from there (h15n1fls20o901.telia.com [217.208.224.15]) by akilles.darkface.pp.se (8.12.1/8.12.1) with SMTP id g4KG6VIL017008; Mon, 20 May 2002 18:06:32 +0200 (MET DST) Message-Id: <200205201606.g4KG6VIL017008@akilles.darkface.pp.se> Content-Type: text/plain; charset="iso-8859-1" From: Thomas Habets To: Michael Kjorling Subject: Re: [6bone] IPv6 port scanners? Date: Mon, 20 May 2002 17:32:36 +0200 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: Cc: 6bone <6bone@ISI.EDU> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 20 May 2002 13:49, you wrote: > A fairly quick Google search turned up a page on Freshmeat listing > halfscan6, "An IPv6 port scanner." I love it when my programs pop up on mailing lists. :-) > Disclaimer: I have not tried it myself, and have no idea about its > quality! Works on: Linux x86 Linux sparc Does not work on: OpenBSD 3.0 sparc NetBSD 1.5.2 alpha Also, Linux seems to set the source address to what it wants even though I'm sending them out a raw socket, which sucks since I've already calculated the checksum. If anyone knows why, please tell me. Same goes for getting it to work on OpenBSD, which doesn't deliver the packets to my AF_INET6/SOCK_RAW socket. In short: the argument to -s must match what Linux actually puts out as source, since I don't seem to have control over that. (at least not without going more raw). But if you just want a connect() portscanner there are others. But I do believe that mine is the only halfscan (synscan or whatever you want to call it). - --------- typedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "thomas@habets.pp.se" }; char kernel[] = { "Linux 2.4" }; char *pgpKey[] = { "http://darkface.pp.se/~thompa/pubkey.txt" }; char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" }; char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" }; } me_t; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE86RcbKGrpCq1I6FQRAjCbAKD9F9z4175KXxDluY+KTWfHbM6cIACeOyCB IPln8sdTtisQrfVP+AsO0QM= =LxZ4 -----END PGP SIGNATURE----- From rocheml@httrack.com Mon May 20 11:13:59 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KIDwE21476 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 11:13:58 -0700 (PDT) Received: from pop.wanadoo.fr (ATuileries-103-1-1-54.abo.wanadoo.fr [193.251.36.54]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KIDvb17933 for <6bone@ISI.EDU>; Mon, 20 May 2002 11:13:57 -0700 (PDT) Received: from serv0.httrack.com (machine-1.localnet.loc [192.168.1.1]) by pop.wanadoo.fr (8.12.2/8.12.2/check_local4.1) with ESMTP id g4KIDoxE014553 for <6bone@ISI.EDU>; Mon, 20 May 2002 20:13:50 +0200 X-Spam-Filter: check_local@pop.wanadoo.fr by digitalanswers.org Message-Id: <5.1.0.14.0.20020520201056.03c9b518@www> X-Sender: rocheml@pop.pro.proxad.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 20 May 2002 20:13:51 +0200 To: 6bone@ISI.EDU From: Xavier Roche Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <87it5izsar.fsf@snark.piermont.com> References: <200205201435.g4KEZ1i04991@boreas.isi.edu> <200205201435.g4KEZ1i04991@boreas.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >>With respect, Bill, I disagree. It is likely that only one would >>survive because of the complexity of dealing with both, and it appears >>at this point the survivor will be AAAA. A6 looked pretty useful for local configuration.. A6 could be kept as internal DNS entries, that is, allowing to reconfigure local dns zones without having to rewrite everything, but "hidden" from the outside world. From tjc@ecs.soton.ac.uk Mon May 20 14:44:34 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KLiYE10535 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 14:44:34 -0700 (PDT) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4KLiXb17463 for <6bone@ISI.EDU>; Mon, 20 May 2002 14:44:33 -0700 (PDT) Received: from hawk.ecs.soton.ac.uk (hawk.ecs.soton.ac.uk [152.78.68.142]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id WAA20490; Mon, 20 May 2002 22:44:31 +0100 (BST) Received: from login (IDENT:YosZv1zXHdGTwEXcqQenZDYthhOxm54+@login.ecs.soton.ac.uk [152.78.68.149]) by hawk.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id WAA26869; Mon, 20 May 2002 22:44:29 +0100 (BST) Date: Mon, 20 May 2002 22:44:27 +0100 (BST) From: Tim Chown To: Michael Kjorling cc: Paul Timmins , 6bone <6bone@ISI.EDU> Subject: Re: [6bone] IPv6 port scanners? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by gamma.isi.edu id g4KLiYE10535 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: You really want to scan an IPv6 /64 subnet? :-) Tim On Mon, 20 May 2002, Michael Kjorling wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On May 19 2002 12:57 -0400, Paul Timmins wrote: > > > I'm looking for an IPv6 portscanner, preferrably for UNIX, to audit my > > network for unnecessary services. > > I'd prefer something like NMAP that can scan a block of IP addresses, > > but one that can scan just one at a time works fine for me too. > > Any suggestions? > > -Paul > > A fairly quick Google search turned up a page on Freshmeat listing > halfscan6, "An IPv6 port scanner." > > See http://freshmeat.net/projects/halfscan6/ > > Disclaimer: I have not tried it myself, and have no idea about its > quality! > > > Michael Kjörling > > - -- > Michael Kjörling -- Programmer/Network administrator ^..^ > Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ > PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e > > ``And indeed people sometimes speak of man's "bestial" cruelty, but > this is very unfair and insulting to the beasts: a beast can never be > so cruel as a man, so ingeniously, so artistically cruel.'' > (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: Public key is at http://michael.kjorling.com/contact/pgp.html > > iD8DBQE86OLaKqN7/Ypw4z4RAtPvAKCinkH/8RlLp5SGSPRwJFAbcOieEQCeMF8o > PozORcOM95h0C0645FRZlsk= > =/eXz > -----END PGP SIGNATURE----- > > > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From bmanning@ISI.EDU Mon May 20 16:09:19 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4KN9JE20503 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 16:09:19 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g4KN97m03186; Mon, 20 May 2002 16:09:07 -0700 (PDT) From: Bill Manning Message-Id: <200205202309.g4KN97m03186@boreas.isi.edu> Subject: Re: [6bone] IPv6 port scanners? In-Reply-To: from Tim Chown at "May 20, 2 10:44:27 pm" To: tjc@ecs.soton.ac.uk (Tim Chown) Date: Mon, 20 May 2002 16:09:07 -0700 (PDT) Cc: michael@kjorling.com, paul@timmins.net, 6bone@ISI.EDU X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: naw... I want to scan a /32 -- --bill From thomas@habets.pp.se Mon May 20 18:15:09 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4L1F8E10017 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 18:15:09 -0700 (PDT) Received: from akilles.darkface.pp.se (root@darkface.pp.se [212.105.77.200]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4L1F7b27429; Mon, 20 May 2002 18:15:07 -0700 (PDT) Received: from there (h15n1fls20o901.telia.com [217.208.224.15]) by akilles.darkface.pp.se (8.12.1/8.12.1) with SMTP id g4L1F2IL010335; Tue, 21 May 2002 03:15:02 +0200 (MET DST) Message-Id: <200205210115.g4L1F2IL010335@akilles.darkface.pp.se> Content-Type: text/plain; charset="iso-8859-1" From: Thomas Habets To: Bill Manning Subject: Re: [6bone] IPv6 port scanners? Date: Tue, 21 May 2002 03:14:24 +0200 X-Mailer: KMail [version 1.3.2] Cc: 6bone@ISI.EDU References: <200205202309.g4KN97m03186@boreas.isi.edu> In-Reply-To: <200205202309.g4KN97m03186@boreas.isi.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 21 May 2002 01:09, Bill Manning wrote: > naw... I want to scan a /32 Why not just scan the whole IPv6 address space? Also, do a traceroute to every address and sell it! See you in time for IPv2^32. :-) - --------- typedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "thomas@habets.pp.se" }; char kernel[] = { "Linux 2.4" }; char *pgpKey[] = { "http://darkface.pp.se/~thompa/pubkey.txt" }; char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" }; char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" }; } me_t; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE86Z99KGrpCq1I6FQRAjoXAJ9Bf7Ma77S5KueP3TB1ct31OpJuaACeJW+X PuoMmgcqVOZYy2/1VRoaNDI= =Zd/g -----END PGP SIGNATURE----- From kre@munnari.OZ.AU Mon May 20 18:37:58 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4L1bwE16389 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 18:37:58 -0700 (PDT) Received: from delta.cs.mu.OZ.AU ([202.28.96.115]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4L1btb04540 for <6bone@ISI.EDU>; Mon, 20 May 2002 18:37:55 -0700 (PDT) Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id g4L1XQg05072; Tue, 21 May 2002 08:33:27 +0700 (ICT) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Robert Elz To: itojun@iijlab.net cc: Xavier Roche , 6bone@ISI.EDU Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <20213.1021902006@itojun.org> References: <20213.1021902006@itojun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 May 2002 08:33:26 +0700 Message-ID: <5070.1021944806@munnari.OZ.AU> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Date: Mon, 20 May 2002 22:40:06 +0900 From: itojun@iijlab.net Message-ID: <20213.1021902006@itojun.org> | AAAA is the final standard. | draft-ietf-dnsext-ipv6-addresses-01.txt That's just a draft RFC, someone's opinion, currently not accepted by anything. It doesn't even have working group consensus, let alone IETF. (Which isn't to say that A6 has WG consensus either, of course). kre From rocheml@httrack.com Mon May 20 22:38:10 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4L5cAE14765 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 22:38:10 -0700 (PDT) Received: from pop.wanadoo.fr (ATuileries-103-1-1-54.abo.wanadoo.fr [193.251.36.54]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4L5c7b10872 for <6bone@ISI.EDU>; Mon, 20 May 2002 22:38:08 -0700 (PDT) Received: from serv0.httrack.com (machine-1.localnet.loc [192.168.1.1]) by pop.wanadoo.fr (8.12.2/8.12.2/check_local4.1) with ESMTP id g4L5c1xE027729 for <6bone@ISI.EDU>; Tue, 21 May 2002 07:38:01 +0200 X-Spam-Filter: check_local@pop.wanadoo.fr by digitalanswers.org Message-Id: <5.1.0.14.0.20020521073459.03cad138@www> X-Sender: rocheml@pop.pro.proxad.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 21 May 2002 07:37:58 +0200 To: 6bone@ISI.EDU From: Xavier Roche Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <5070.1021944806@munnari.OZ.AU> References: <20213.1021902006@itojun.org> <20213.1021902006@itojun.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >>That's just a draft RFC, someone's opinion, currently not accepted >>by anything. It doesn't even have working group consensus, let alone IETF. >>(Which isn't to say that A6 has WG consensus either, of course). Any chance for this document to become more 'official' (with big quotes) ? AAAA/A6 confusion is really a nuisance, and is slowing down a little more many v6 migrations From pim@ipng.nl Mon May 20 22:43:24 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4L5hOE16101 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 22:43:24 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4L5hMb12908 for <6bone@ISI.EDU>; Mon, 20 May 2002 22:43:23 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 1172D8C2A; Tue, 21 May 2002 05:43:19 +0000 (GMT) Date: Tue, 21 May 2002 07:43:19 +0200 From: Pim van Pelt To: Michel Py Cc: Nicolas DEFFAYET , Jim Martin , 6bone@ISI.EDU Subject: Re: [6bone] 6Bone registry entries when multihomed? Message-ID: <20020521054319.GA27295@bfib.colo.bit.nl> References: <2B81403386729140A3A899A8B39B046405E076@server2000.arneill-py.sacramento.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2B81403386729140A3A899A8B39B046405E076@server2000.arneill-py.sacramento.ca.us> User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: | > Nicolas DEFFAYET wrote | > A exemple: http://whois.6bone.net/cgi-bin/whois?NDSOFTWARE | | Nicolas is an ISP. If you got /48s it probably means you are not, here | is an example that might be closer to your needs: Nicolas is an inmensly irritating clueless kiddie, because he blatantly refuses to remove his AS65526 number from the registries and to be even worse, he uses this on the 6bone, because he cannot get his hands on a real ASN (because he does not have a LIR relationship with a RIR). www.ndsoftwarenet.net (mind ND - Nicolas Defayet), does not have content and there is no company behind FastNET XP, it's just some (Windows running?) children being a total ass on the Internet. Nicolas, did you know that people were even complaining about your destructive IPv6 efforts at RIPE42 :-) ? Just to put things in proper perspective. pompompom, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From pim@ipng.nl Mon May 20 22:45:43 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4L5jhE16798 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 22:45:43 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4L5jgb13124 for <6bone@ISI.EDU>; Mon, 20 May 2002 22:45:42 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 25CC48C2A; Tue, 21 May 2002 05:45:41 +0000 (GMT) Date: Tue, 21 May 2002 07:45:41 +0200 From: Pim van Pelt To: Pekka Savola Cc: Xavier Roche , 6bone@ISI.EDU Subject: Re: [6bone] AAAA and A6 recent status? Message-ID: <20020521054541.GB27295@bfib.colo.bit.nl> References: <5.1.0.14.0.20020520143041.00a14540@wheresmymailserver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, May 20, 2002 at 05:15:48PM +0300, Pekka Savola wrote: | On Mon, 20 May 2002, Xavier Roche wrote: | > rfc #2874 seem to suggest that AAAA records will "soon" disappear ; is | > the A6 record format the definitive one? If the 2874 considered as | > 'final' standard? | | Short answer: forget about A6 altogether. haha :) The cool thing about Pekka is, that his mails on 'drop it ' come in after others explained about it, I remember mine coming in as first response half a year ago and that started quite a thread. Drop A6/DNAME. They belong in Hell. groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From nicolas.deffayet-extml@ndsoftwaregroup.com Tue May 21 03:32:26 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LAWPE23663 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 03:32:25 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LAWNb16064 for <6bone@ISI.EDU>; Tue, 21 May 2002 03:32:24 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17A6wF-000G27-00 for 6bone@ISI.EDU; Tue, 21 May 2002 12:32:19 +0200 Received: (qmail 32088 invoked from network); 21 May 2002 10:45:13 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 21 May 2002 10:45:13 -0000 From: "Nicolas DEFFAYET" To: "'Pim van Pelt'" , "'Michel Py'" Cc: "'Jim Martin'" , <6bone@ISI.EDU> Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 12:32:02 +0200 Organization: NDSoftware Group Message-ID: <004601c200b2$c00e8170$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020521054319.GA27295@bfib.colo.bit.nl> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: Pim van Pelt [mailto:pim@ipng.nl] > Sent: Tuesday, May 21, 2002 7:43 AM > To: Michel Py > Cc: Nicolas DEFFAYET; Jim Martin; 6bone@ISI.EDU > Subject: Re: [6bone] 6Bone registry entries when multihomed? I don't like reply to a troll, but i reply for many reasons. > | > Nicolas DEFFAYET wrote > | > A exemple: http://whois.6bone.net/cgi-bin/whois?NDSOFTWARE > | > | Nicolas is an ISP. If you got /48s it probably means you > are not, here > | is an example that might be closer to your needs: > ISP is not a good word for that. I prefer call it project. > Nicolas is an inmensly irritating clueless kiddie, because he > blatantly refuses to remove his AS65526 number from the > registries and to be even worse, he uses this on the 6bone, > because he cannot get his hands on a real ASN (because he > does not have a LIR relationship with a RIR). Where is problem of use a private ASN number when you notify the peer and you add a community no-export to your route ? If ISP don't want that i send my route i don't send route and/or the ISP can filter my route. I'm running with this configuration since 1 year, and no problem reported. I'm ***NOT*** the only people who use private ASN on 6bone. I plain to get a public ASN and be a LIR, but before i need to create a real IPv4 network because you can't justify a ASN with 2 IPv6 peering (native of course). Create a IPv4 network can't be do in a week (except if you have a lot of money for this). If RIPE accept to allocate me a public ASN now, i accept of course :) I recall that 6bone is for test. I don't remove my AS for your pleasure. A lot of users/other projects use the services of my projet. You want a list of projects who use my services ? Another question that you have forgot: why i have a lot of peer ? Because with a community no-export you need directly peer for that the ISP can have your route (if the ISP accept it). Why you are jealous of my projet ? > www.ndsoftwarenet.net (mind ND - Nicolas Defayet), does not have content and there is no >company behind FastNET XP, it's just some (Windows >running?) children being a total ass on the Internet. My name is with 2 f: DEFFAYET. You criticism people and you can't write correctly my name ? Yes www.ndsoftware.net is not ready (need to finish the developpement of backend), if you want help us, don't hesitate :) FastNetXP is just a name of project beetween friend, not a real company. But i have stop to use FastNetXP because many problem with the name FastNetXP (a trademark FastNet exist [...]) I'm not running Windows (except for a workstation, for many reason). On my webserver you can see: Apache/2.0.36 (Unix) mod_ssl/2.0.36 OpenSSL/0.9.6d PHP/4.2.0 I'm not a children. Just a question, are you intelligent ? Because with this mail you make a fool of oneself. >Nicolas, did you know that people were even complaining about your destructive IPv6 >efforts at RIPE42 :-) ? Just to put things in proper perspective. 6bone and RIPE is not the same. I work on 6bone, not with the RIPE. Best Regards, Nicolas DEFFAYET From chuck@snew.com Tue May 21 05:00:20 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LC0JE13169 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 05:00:20 -0700 (PDT) Received: from grover.snew.com (grover.snew.com [206.136.66.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LC0Jb05054 for <6bone@ISI.EDU>; Tue, 21 May 2002 05:00:19 -0700 (PDT) Received: from grover.snew.com (localhost [127.0.0.1]) by grover.snew.com (8.12.2/8.12.2) with ESMTP id g4LC0Hkx028146; Tue, 21 May 2002 05:00:17 -0700 (PDT) Received: (from chuck@localhost) by grover.snew.com (8.12.2/8.12.2/Submit) id g4LC0G2j028145; Tue, 21 May 2002 05:00:16 -0700 (PDT) Date: Tue, 21 May 2002 05:00:16 -0700 From: Chuck Yerkes To: "David F. Newman" Cc: 6 Bone <6bone@ISI.EDU> Message-ID: <20020521050016.A27912@snew.com> References: <200205030939.22293.dnewman@maraudingpirates.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200205030939.22293.dnewman@maraudingpirates.org>; from dnewman@maraudingpirates.org on Fri, May 03, 2002 at 09:39:22AM -0400 Subject: [6bone] Re: Internal Address Space Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Quoting David F. Newman (dnewman@maraudingpirates.org): > Hi there, > In the old IPv4 days sites would use private address space inside a firewall > for either address conservation or just plain old security through obscurity. In the old days, we'd use our real IPv4 addresses and that would route across the Internet. We eventually put up firewalls, and screening routers (or screend). As we ran out of IPv4 (they will all be gone by 1998 or so :), rfc1918 came along a bit after the concept of NAT - network address translation. Many lesser admins believe NAT to be actual firewalling (it's neat the probes that still work with an established bit set). > Now that a site can get a /48 to do with as they please is it necessary to use > private IP space anymore. I am wondering if people out there use public > routable IPs on both sides of their firewall. I figure if a node is behind a > firewall it is ok to have a valid IP, but I could be wrong. Now that I have 65k Internets of address that will route (nobody will route my class C anymore), I use actual addresses on the machines that will take them. I run firewalling software on my gateways somewhat. I also make sure that the machines on my network are hardened. There is no "soft chewy center" if you get past the firewall. From oliver.michael@gargantuan.com Tue May 21 06:04:10 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LD4AE28638 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 06:04:10 -0700 (PDT) Received: from wolverine.gargantuan.com (145bus8.tampabay.rr.com [24.94.145.8]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LD49b23403 for <6bone@ISI.EDU>; Tue, 21 May 2002 06:04:09 -0700 (PDT) Received: from MAGNETO.gargantuan.com (magneto.gargantuan.com [10.0.0.9]) by wolverine.gargantuan.com (Postfix) with ESMTP id 809A72A3 for <6bone@ISI.EDU>; Tue, 21 May 2002 09:03:51 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [6bone] AAAA and A6 recent status? X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message Date: Tue, 21 May 2002 09:04:01 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] AAAA and A6 recent status? Thread-Index: AcIAwtRCLnMWJW82SLy//kzGcqws7wAAKtGA From: "Michael W. Oliver" To: <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LD4AE28638 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Folks, Is there any negative effect of using both A6 and AAAA records? Most of the hosts on my small network are dual-stack, and I have configured BIND with A6, AAAA, and A records for each of them. Is this bad practice in anyone's opinion? Thanks in advance for your insight. Regards, Michael Oliver -----Original Message----- From: Xavier Roche [mailto:rocheml@httrack.com] Sent: Tuesday, May 21, 2002 1:38 AM To: 6bone@ISI.EDU Subject: Re: [6bone] AAAA and A6 recent status? >>That's just a draft RFC, someone's opinion, currently not accepted >>by anything. It doesn't even have working group consensus, let alone IETF. >>(Which isn't to say that A6 has WG consensus either, of course). Any chance for this document to become more 'official' (with big quotes) ? AAAA/A6 confusion is really a nuisance, and is slowing down a little more many v6 migrations _______________________________________________ 6bone mailing list 6bone@mailman.isi.edu http://mailman.isi.edu/mailman/listinfo/6bone From bmanning@ISI.EDU Tue May 21 06:27:49 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDRnE05297 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 06:27:49 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g4LDRkm14245; Tue, 21 May 2002 06:27:46 -0700 (PDT) From: Bill Manning Message-Id: <200205211327.g4LDRkm14245@boreas.isi.edu> Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: from "Michael W. Oliver" at "May 21, 2 09:04:01 am" To: oliver.michael@gargantuan.com (Michael W. Oliver) Date: Tue, 21 May 2002 06:27:46 -0700 (PDT) Cc: 6bone@ISI.EDU X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: % Folks, % % Is there any negative effect of using both A6 and AAAA records? Most of % the hosts on my small network are dual-stack, and I have configured BIND % with A6, AAAA, and A records for each of them. Is this bad practice in % anyone's opinion? % % Thanks in advance for your insight. % % Regards, % % Michael Oliver I use both A6 and AAAA on most nodes. Some only have A6 records. Some of those are chained. You can even find a DNAME or two... So I guess that, according to some, I'm in "Hell". :) --bill From sdegler@degler.net Tue May 21 06:40:34 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDeYE08545 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 06:40:34 -0700 (PDT) Received: from degler.net (crusoe.degler.net [66.114.64.229]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDeXb03920 for <6bone@ISI.EDU>; Tue, 21 May 2002 06:40:33 -0700 (PDT) Received: from crusoe.degler.net (localhost [IPv6:::1]) by degler.net (8.12.2/8.11.0) with ESMTP id g4LDeR3n023025; Tue, 21 May 2002 09:40:27 -0400 (EDT) Received: (from sdegler@localhost) by crusoe.degler.net (8.12.2/8.12.2/Submit) id g4LDeRCg023024; Tue, 21 May 2002 09:40:27 -0400 (EDT) Date: Tue, 21 May 2002 09:40:27 -0400 From: Stephen Degler To: Chuck Yerkes Cc: "David F. Newman" , 6 Bone <6bone@ISI.EDU> Subject: Re: [6bone] Re: Internal Address Space Message-ID: <20020521094027.B20244@crusoe.degler.net> References: <200205030939.22293.dnewman@maraudingpirates.org> <20020521050016.A27912@snew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020521050016.A27912@snew.com>; from chuck+6bone@snew.com on Tue, May 21, 2002 at 05:00:16AM -0700 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, Given the immediate future will continue to be Windows Impaired as well, its completely possible (and unfortunately, necessary) to establish a "soft chewy center" model with routeable addresses on the inside. Stateful firewalls are your friend. skd On Tue, May 21, 2002 at 05:00:16AM -0700, Chuck Yerkes wrote: > Quoting David F. Newman (dnewman@maraudingpirates.org): > > Hi there, > > In the old IPv4 days sites would use private address space inside a firewall > > for either address conservation or just plain old security through obscurity. > In the old days, we'd use our real IPv4 addresses and that would > route across the Internet. We eventually put up firewalls, and > screening routers (or screend). As we ran out of IPv4 (they will > all be gone by 1998 or so :), rfc1918 came along a bit after the > concept of NAT - network address translation. > > Many lesser admins believe NAT to be actual firewalling (it's > neat the probes that still work with an established bit set). > > > Now that a site can get a /48 to do with as they please is it necessary to use > > private IP space anymore. I am wondering if people out there use public > > routable IPs on both sides of their firewall. I figure if a node is behind a > > firewall it is ok to have a valid IP, but I could be wrong. > > Now that I have 65k Internets of address that will route (nobody > will route my class C anymore), I use actual addresses on the > machines that will take them. I run firewalling software on my > gateways somewhat. I also make sure that the machines on my network > are hardened. There is no "soft chewy center" if you get past the > firewall. > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone From michael@kjorling.com Tue May 21 06:46:24 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDkNE09959 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 06:46:23 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDkJb05938 for <6bone@ISI.EDU>; Tue, 21 May 2002 06:46:21 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4LDkFw09298 for <6bone@ISI.EDU>; Tue, 21 May 2002 13:46:15 GMT Date: Tue, 21 May 2002 15:46:10 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: 6bone <6bone@ISI.EDU> Subject: RE: [6bone] AAAA and A6 recent status? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 21 2002 09:04 -0400, Michael W. Oliver wrote: > Folks, > > Is there any negative effect of using both A6 and AAAA records? Most of > the hosts on my small network are dual-stack, and I have configured BIND > with A6, AAAA, and A records for each of them. Is this bad practice in > anyone's opinion? > > Thanks in advance for your insight. > > Regards, > > Michael Oliver All your slave servers have to at least be able to serve A6 RRs. Actually I think the real problem is not the A6 forward records (they can be dealt with) but bitlabels. Just as the I-D points out, queries containing bitlabels can quite easily be rejected as malformed. Not a good thing. Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE86k+nKqN7/Ypw4z4RAqSbAKDkMY+XCJuJCh8IjwqXDwUH1JEpMwCgyXyI gjtK5BWzHK+4zszBUAm+byw= =hh7X -----END PGP SIGNATURE----- From fink@es.net Tue May 21 06:51:43 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDphE11547 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 06:51:43 -0700 (PDT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LDpgb06935 for <6bone@isi.edu>; Tue, 21 May 2002 06:51:42 -0700 (PDT) Received: from ([63.196.96.113]) by postal2.es.net (Postal Node 2) with SMTP id GQF37091; Tue, 21 May 2002 06:51:39 -0700 Message-Id: <5.1.0.14.0.20020521064954.02989c98@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 21 May 2002 06:51:10 -0700 To: 6BONE List <6bone@ISI.EDU> From: Bob Fink Cc: Milos Prodanovic , 6bone reverse DNS registration Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] 6bone pTLA 3FFE:4009::/32 allocated to VERAT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: VERAT has been allocated pTLA 3FFE:4009::/32 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: [To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to hostmaster@ep.net.] Thanks, Bob From michael@kjorling.com Tue May 21 07:01:19 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LE1JE14643 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 07:01:19 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LE1Hb09984 for <6bone@isi.edu>; Tue, 21 May 2002 07:01:17 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4LE1Gw09739 for <6bone@isi.edu>; Tue, 21 May 2002 14:01:16 GMT Date: Tue, 21 May 2002 16:01:12 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: <200205211327.g4LDRkm14245@boreas.isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 21 2002 06:27 -0700, Bill Manning wrote: > I use both A6 and AAAA on most nodes. Some only have A6 records. > Some of those are chained. You can even find a DNAME or two... > So I guess that, according to some, I'm in "Hell". :) > > --bill Well, if you want to scan an IPv6 /32... :-) I personally use only AAAAs. Can't say I have devoted to IPv6-only but I do get an occasional hit over IPv6 on my servers. The reason for this is that I am unsure if one of the slave DNS servers can handle A6 records, let alone chains. Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE86lMrKqN7/Ypw4z4RAhcGAKDujRN8Sfb4SJhfGE/gdG7OhrRiIACg9Jd2 rbhUBSd5eSIAjAG0EZer8uM= =RlK7 -----END PGP SIGNATURE----- From sdegler@degler.net Tue May 21 07:09:55 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LE9tE16767 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 07:09:55 -0700 (PDT) Received: from degler.net (crusoe.degler.net [66.114.64.229]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LE9sb13201 for <6bone@ISI.EDU>; Tue, 21 May 2002 07:09:54 -0700 (PDT) Received: from crusoe.degler.net (localhost [IPv6:::1]) by degler.net (8.12.2/8.11.0) with ESMTP id g4LE8W3n023148; Tue, 21 May 2002 10:08:32 -0400 (EDT) Received: (from sdegler@localhost) by crusoe.degler.net (8.12.2/8.12.2/Submit) id g4LE8WOB023147; Tue, 21 May 2002 10:08:32 -0400 (EDT) Date: Tue, 21 May 2002 10:08:32 -0400 From: Stephen Degler To: "Michael W. Oliver" Cc: 6bone@ISI.EDU Subject: Re: [6bone] AAAA and A6 recent status? Message-ID: <20020521100832.C20244@crusoe.degler.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from oliver.michael@gargantuan.com on Tue, May 21, 2002 at 09:04:01AM -0400 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, If you are running DNS via bind 9.2 or newer you can instruct bind to convert the A6's to AAAA's on the fly "options allow-v6-synthesis". On the other hand. If you aren't specifically testing or using features available with A6 and DNAME (renumbering and the new style reverse mappings) Its unlikely that you have any clients that will make use of them. skd On Tue, May 21, 2002 at 09:04:01AM -0400, Michael W. Oliver wrote: > Folks, > > Is there any negative effect of using both A6 and AAAA records? Most of > the hosts on my small network are dual-stack, and I have configured BIND > with A6, AAAA, and A records for each of them. Is this bad practice in > anyone's opinion? > > Thanks in advance for your insight. > > Regards, > > Michael Oliver > > > > > -----Original Message----- > From: Xavier Roche [mailto:rocheml@httrack.com] > Sent: Tuesday, May 21, 2002 1:38 AM > To: 6bone@ISI.EDU > Subject: Re: [6bone] AAAA and A6 recent status? > > > > >>That's just a draft RFC, someone's opinion, currently not accepted > >>by anything. It doesn't even have working group consensus, let alone > IETF. > >>(Which isn't to say that A6 has WG consensus either, of course). > > Any chance for this document to become more 'official' (with big quotes) > ? AAAA/A6 confusion is really a nuisance, and is slowing down a little > more many v6 migrations > > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone From todd@shadow.fries.net Tue May 21 07:22:33 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEMXE21274 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 07:22:33 -0700 (PDT) Received: from fries.net (root@ns0.fries.net [206.30.141.10]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEMVb16792 for <6bone@ISI.EDU>; Tue, 21 May 2002 07:22:32 -0700 (PDT) Received: from shadow.fries.net (todd@localhost.fries.net [IPv6:::1]) by fries.net (8.12.1/8.12.1) with ESMTP id g4LEF7AK018042 (version=TLSv1/SSLv3 cipher=EDH-DSS-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 May 2002 09:15:07 -0500 (CDT) X-tlsinfo-cn: cn_issuer= cn_subj= X-tlsinfo-cert: cert_subj= cert_issuer= X-tlsinfo-serv: server= server_addr= X-tlsinfo-client: client=localhost.fries.net client_addr=IPv6:::1 Received: (from todd@localhost) by shadow.fries.net (8.12.1/8.12.1/Submit) id g4LEF758031524; Tue, 21 May 2002 09:15:07 -0500 (CDT) Date: Tue, 21 May 2002 09:15:07 -0500 From: "Todd T. Fries" To: "Michael W. Oliver" Cc: 6bone@ISI.EDU Subject: Re: [6bone] AAAA and A6 recent status? Message-ID: <20020521141507.GC32690@fries.net> Reply-To: todd@fries.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-PGP-Fingerprint: B6 3B 70 46 BC 0F 8C DD 14 D4 C7 D1 47 F6 23 FA X-URL: http://todd.fries.net X-tra-email: todd@fries.net, toddf@acm.org, todd@openbsd.org, toddfries@yahoo.com X-IM: toddfries@AIM, toddfries@Yahoo, 115268457@ICQ, {toddfries,fr[1i]es}@*.irc.fries.net Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Just beware that anything but recent dns servers cannot secondary domains that use A6 or DNAME records. Personally, I've used m4 to generate my dns zone for fries.net, and have two 'versions'... one with and one without DNAME's and A6's .. I've not used the A6/DNAME version in a while, I just hope future bind's try to lookup AAAA by default instead of A6 (you can do 'host -n 3ffe:..' but that is not default behavior) .. I do not believe any of my secondaries outside my local network can transfer zones containing A6/DNAME records, so I can setup two views, one for older slave servers, and one for 'the rest of the world' .. not that I am right now, but I certainly could if need be. Just thought I'd share my headaches with regards to A6 .. -- Todd Fries .. todd@fries.net (last updated $ToddFries: signature.p,v 1.2 2002/03/19 15:10:18 todd Exp $) Penned by Michael W. Oliver on Tue, May 21, 2002 at 09:04:01AM -0400, we have: | Folks, | | Is there any negative effect of using both A6 and AAAA records? Most of | the hosts on my small network are dual-stack, and I have configured BIND | with A6, AAAA, and A records for each of them. Is this bad practice in | anyone's opinion? | | Thanks in advance for your insight. | | Regards, | | Michael Oliver | | | | | -----Original Message----- | From: Xavier Roche [mailto:rocheml@httrack.com] | Sent: Tuesday, May 21, 2002 1:38 AM | To: 6bone@ISI.EDU | Subject: Re: [6bone] AAAA and A6 recent status? | | | | >>That's just a draft RFC, someone's opinion, currently not accepted | >>by anything. It doesn't even have working group consensus, let alone | IETF. | >>(Which isn't to say that A6 has WG consensus either, of course). | | Any chance for this document to become more 'official' (with big quotes) | ? AAAA/A6 confusion is really a nuisance, and is slowing down a little | more many v6 migrations | | _______________________________________________ | 6bone mailing list | 6bone@mailman.isi.edu | http://mailman.isi.edu/mailman/listinfo/6bone | _______________________________________________ | 6bone mailing list | 6bone@mailman.isi.edu | http://mailman.isi.edu/mailman/listinfo/6bone From michel@arneill-py.sacramento.ca.us Tue May 21 07:31:56 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEVuE23243 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 07:31:56 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEVsb20369 for <6bone@ISI.EDU>; Tue, 21 May 2002 07:31:55 -0700 (PDT) Subject: RE: [6bone] Re: Internal Address Space Date: Tue, 21 May 2002 07:31:48 -0700 Message-ID: <2B81403386729140A3A899A8B39B046405E07E@server2000.arneill-py.sacramento.ca.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] Re: Internal Address Space content-class: urn:content-classes:message Thread-Index: AcIAzevGX4uXCj1xQke0Fz4I05awxQABTB9g X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 From: "Michel Py" To: "Stephen Degler" Cc: "6 Bone" <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LEVuE23243 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Stephen Degler wrote: > Given the immediate future will continue to be Windows Impaired > as well, its completely possible (and unfortunately, necessary) > to establish a "soft chewy center" model with routeable addresses > on the inside. Stateful firewalls are your friend. Stateful firewalls are not good as they used to be. There are various mechanisms that allow to bypass them these days and it's not getting better. I would not be surprised to see an IE plugin to circumvent firewalls soon. The best way to secure a host is to use a link-local or site-local only address and go to a proxy (yuck). Michel. From michel@arneill-py.sacramento.ca.us Tue May 21 07:44:48 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEilE27425 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 07:44:48 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEilb24327 for <6bone@ISI.EDU>; Tue, 21 May 2002 07:44:47 -0700 (PDT) Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 07:44:41 -0700 Message-ID: <2B81403386729140A3A899A8B39B046405E07F@server2000.arneill-py.sacramento.ca.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] 6Bone registry entries when multihomed? content-class: urn:content-classes:message Thread-Index: AcIAst2sC2xH38O4QH6CYoBpb+z9BgAIbmzQ X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 From: "Michel Py" To: "Nicolas DEFFAYET" , "Pim van Pelt" Cc: "Jim Martin" , <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LEilE27425 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Pim van Pelt wrote. > because he blatantly refuses to remove his AS65526 number from > the registries and to be even worse, he uses this on the 6bone, > because he cannot get his hands on a real ASN (because he > does not have a LIR relationship with a RIR). There is nothing wrong in using a private ASN on the 6bone. pTLAs accept it, and it is not a long-term solution but allows people to get started. This is exactly what the 6bone is for: experiments and staging. Michel. From sdegler@degler.net Tue May 21 07:50:44 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEoiE29149 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 07:50:44 -0700 (PDT) Received: from degler.net (crusoe.degler.net [66.114.64.229]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LEohb26365 for <6bone@ISI.EDU>; Tue, 21 May 2002 07:50:43 -0700 (PDT) Received: from crusoe.degler.net (localhost [IPv6:::1]) by degler.net (8.12.2/8.11.0) with ESMTP id g4LEoa3n023409; Tue, 21 May 2002 10:50:36 -0400 (EDT) Received: (from sdegler@localhost) by crusoe.degler.net (8.12.2/8.12.2/Submit) id g4LEoaR7023408; Tue, 21 May 2002 10:50:36 -0400 (EDT) Date: Tue, 21 May 2002 10:50:36 -0400 From: Stephen Degler To: Michel Py Cc: Stephen Degler , 6 Bone <6bone@ISI.EDU> Subject: Re: [6bone] Re: Internal Address Space Message-ID: <20020521105036.D20244@crusoe.degler.net> References: <2B81403386729140A3A899A8B39B046405E07E@server2000.arneill-py.sacramento.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <2B81403386729140A3A899A8B39B046405E07E@server2000.arneill-py.sacramento.ca.us>; from michel@arneill-py.sacramento.ca.us on Tue, May 21, 2002 at 07:31:48AM -0700 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, Please be more specific. I believe that there are flaws in the implementations of statefull firewalls as there all in all things, but it is my impression that they are relatively secure from the design perspective. How exactly would this IE plugin work? skd On Tue, May 21, 2002 at 07:31:48AM -0700, Michel Py wrote: > > Stephen Degler wrote: > > Given the immediate future will continue to be Windows Impaired > > as well, its completely possible (and unfortunately, necessary) > > to establish a "soft chewy center" model with routeable addresses > > on the inside. Stateful firewalls are your friend. > > Stateful firewalls are not good as they used to be. There are various > mechanisms that allow to bypass them these days and it's not getting > better. I would not be surprised to see an IE plugin to circumvent > firewalls soon. The best way to secure a host is to use a link-local or > site-local only address and go to a proxy (yuck). > > Michel. From michel@arneill-py.sacramento.ca.us Tue May 21 08:05:39 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LF5dE04357 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:05:39 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LF5cb01831 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:05:38 -0700 (PDT) Subject: RE: [6bone] Re: Internal Address Space Date: Tue, 21 May 2002 08:05:33 -0700 Message-ID: <2B81403386729140A3A899A8B39B046405E081@server2000.arneill-py.sacramento.ca.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] Re: Internal Address Space content-class: urn:content-classes:message Thread-Index: AcIA1vCt+BMCkoDlSPyKDjkAkIJHgAAAA3Jg X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 From: "Michel Py" To: "Stephen Degler" Cc: "6 Bone" <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LF5dE04357 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Stephen, > Stephen Degler wrote: > Please be more specific. I believe that there are flaws in the > implementations of statefull firewalls as there all in all things, > but it is my impression that they are relatively secure from the > design perspective. > How exactly would this IE plugin work? By initiating the traffic from the inside at both hosts, which opens a temporary hole in the firewall to allow return traffic. A good example of that kind of trick is Morpheus: People can pull mp3s from your RFC 1918 host crossing NAT and crossing a stateful firewall _without_ having to punch a hole in the firewall and without static NAT configuration. I think that teredo also allows to do the same. All these mechanisms are based in contacting an agent outside; if that agent is listening on port 80 there is not much you can do to prevent your host talking to it. Michel. From itojun@itojun.org Tue May 21 08:09:08 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LF98E04925 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:09:08 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LF97b03069 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:09:07 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 07F6C4B22; Wed, 22 May 2002 00:09:01 +0900 (JST) To: "Michel Py" Cc: 6bone@ISI.EDU In-reply-to: michel's message of Tue, 21 May 2002 07:44:41 MST. <2B81403386729140A3A899A8B39B046405E07F@server2000.arneill-py.sacramento.ca.us> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] 6Bone registry entries when multihomed? From: itojun@iijlab.net Date: Wed, 22 May 2002 00:09:00 +0900 Message-ID: <1648.1021993740@itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >There is nothing wrong in using a private ASN on the 6bone. pTLAs accept >it, and it is not a long-term solution but allows people to get started. >This is exactly what the 6bone is for: experiments and staging. why would you advertise private ASN onto the 6bone whois? they should be used locally within certain pTLAs, not globally. also do not forget that 6bone is interconnected with worldwide IPv6 network (including commercially-operated network), and there's no well-defined boundary. therefore, my recommendation is: - to remove/forbid private ASN from 6bone whois. - do not advertise private ASNs beyond pTLA/sTLA boundary itojun From todd@shadow.fries.net Tue May 21 08:11:34 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFBYE05555 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:11:34 -0700 (PDT) Received: from fries.net (root@ns0.fries.net [206.30.141.10]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFBXb04078 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:11:33 -0700 (PDT) Received: from shadow.fries.net (todd@localhost.fries.net [IPv6:::1]) by fries.net (8.12.1/8.12.1) with ESMTP id g4LF5RAK025007 (version=TLSv1/SSLv3 cipher=EDH-DSS-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 May 2002 10:05:27 -0500 (CDT) X-tlsinfo-cn: cn_issuer= cn_subj= X-tlsinfo-cert: cert_subj= cert_issuer= X-tlsinfo-serv: server= server_addr= X-tlsinfo-client: client=localhost.fries.net client_addr=IPv6:::1 Received: (from todd@localhost) by shadow.fries.net (8.12.1/8.12.1/Submit) id g4LF5QHu012884; Tue, 21 May 2002 10:05:26 -0500 (CDT) Date: Tue, 21 May 2002 10:05:26 -0500 From: "Todd T. Fries" To: Michael Kjorling Cc: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] AAAA and A6 recent status? Message-ID: <20020521150526.GD32690@fries.net> Reply-To: todd@fries.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.3.28i X-PGP-Fingerprint: B6 3B 70 46 BC 0F 8C DD 14 D4 C7 D1 47 F6 23 FA X-URL: http://todd.fries.net X-tra-email: todd@fries.net, toddf@acm.org, todd@openbsd.org, toddfries@yahoo.com X-IM: toddfries@AIM, toddfries@Yahoo, 115268457@ICQ, {toddfries,fr[1i]es}@*.irc.fries.net Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: A6 and/or DNAME both cause 'unknown record type' style errors with bind4, and older bind8 (newer bind8 can deal with A6 and/or DNAME) .. The problem stems from the fact that prior to current bind8/bind9 .. there was hardcoded a list of valid RR types in the dns servers. A6 and DNAME both add a new 'type' that is unknown, therefore invalid to older dns servers. -- Todd Fries .. todd@fries.net (last updated $ToddFries: signature.p,v 1.2 2002/03/19 15:10:18 todd Exp $) Penned by Michael Kjorling on Tue, May 21, 2002 at 03:46:10PM +0200, we have: | -----BEGIN PGP SIGNED MESSAGE----- | Hash: SHA1 | | On May 21 2002 09:04 -0400, Michael W. Oliver wrote: | | > Folks, | > | > Is there any negative effect of using both A6 and AAAA records? Most of | > the hosts on my small network are dual-stack, and I have configured BIND | > with A6, AAAA, and A records for each of them. Is this bad practice in | > anyone's opinion? | > | > Thanks in advance for your insight. | > | > Regards, | > | > Michael Oliver | | All your slave servers have to at least be able to serve A6 RRs. | | Actually I think the real problem is not the A6 forward records (they | can be dealt with) but bitlabels. Just as the I-D points out, queries | containing bitlabels can quite easily be rejected as malformed. Not a | good thing. | | | Michael Kjörling | | - -- | Michael Kjörling -- Programmer/Network administrator ^..^ | Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ | PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e | | ``And indeed people sometimes speak of man's "bestial" cruelty, but | this is very unfair and insulting to the beasts: a beast can never be | so cruel as a man, so ingeniously, so artistically cruel.'' | (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') | -----BEGIN PGP SIGNATURE----- | Version: GnuPG v1.0.7 (GNU/Linux) | Comment: Public key is at http://michael.kjorling.com/contact/pgp.html | | iD8DBQE86k+nKqN7/Ypw4z4RAqSbAKDkMY+XCJuJCh8IjwqXDwUH1JEpMwCgyXyI | gjtK5BWzHK+4zszBUAm+byw= | =hh7X | -----END PGP SIGNATURE----- | | | _______________________________________________ | 6bone mailing list | 6bone@mailman.isi.edu | http://mailman.isi.edu/mailman/listinfo/6bone From michel@arneill-py.sacramento.ca.us Tue May 21 08:17:45 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFHjE08169 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:17:45 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFHib05801 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:17:44 -0700 (PDT) Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 08:17:38 -0700 Message-ID: <2B81403386729140A3A899A8B39B046405E082@server2000.arneill-py.sacramento.ca.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] 6Bone registry entries when multihomed? content-class: urn:content-classes:message Thread-Index: AcIA2Ze6n+MHCEEFRgexXGrm8IsZDgAABSAg X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 From: "Michel Py" To: Cc: <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LFHjE08169 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Itojun wrote: > they should be used locally within certain pTLAs, not globally. > also do not forget that 6bone is interconnected with worldwide > IPv6 network (including commercially-operated network), and > there's no well-defined boundary. therefore, my recommendation > is: > - do not advertise private ASNs beyond pTLA/sTLA boundary I completely agree with the above. > why would you advertise private ASN onto the 6bone whois? > - to remove/forbid private ASN from 6bone whois. Why not having accurate information in the 6bone database? We are not talking about a xTLA peering with a private ASN, but about a site peering with a xTLA that can use remove-private-as. Michel. From randy@psg.com Tue May 21 08:26:39 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFQdE12246 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:26:39 -0700 (PDT) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFQcb09474 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:26:38 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 4.00) id 17ABWz-000K6M-00 for 6bone@ISI.EDU; Tue, 21 May 2002 08:26:33 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] AAAA and A6 recent status? References: <20020521150526.GD32690@fries.net> Message-Id: Date: Tue, 21 May 2002 08:26:33 -0700 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: a6, dname, and bitstring labels are dog meat. folk should spend their time on useful work. randy From sdegler@degler.net Tue May 21 08:37:58 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFbwE16058 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:37:58 -0700 (PDT) Received: from degler.net (crusoe.degler.net [66.114.64.229]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFbvb12756 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:37:57 -0700 (PDT) Received: from crusoe.degler.net (localhost [IPv6:::1]) by degler.net (8.12.2/8.11.0) with ESMTP id g4LFbd3n023621; Tue, 21 May 2002 11:37:39 -0400 (EDT) Received: (from sdegler@localhost) by crusoe.degler.net (8.12.2/8.12.2/Submit) id g4LFbd3l023620; Tue, 21 May 2002 11:37:39 -0400 (EDT) Date: Tue, 21 May 2002 11:37:39 -0400 From: Stephen Degler To: Michel Py Cc: Stephen Degler , 6 Bone <6bone@ISI.EDU> Subject: Re: [6bone] Re: Internal Address Space Message-ID: <20020521113739.E20244@crusoe.degler.net> References: <2B81403386729140A3A899A8B39B046405E081@server2000.arneill-py.sacramento.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <2B81403386729140A3A899A8B39B046405E081@server2000.arneill-py.sacramento.ca.us>; from michel@arneill-py.sacramento.ca.us on Tue, May 21, 2002 at 08:05:33AM -0700 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Ok, Private addresses and a proxy won't help you against these methods either, as long as http connect methods are permitted by the proxies. Like you said, The p-to-p world utilizes these techniques already. So a statefull firewall is still protects against external attacks. If one can convince software or a user to execute malicious code, all bets are off. Being addressable doesn't alter the status quo. skd On Tue, May 21, 2002 at 08:05:33AM -0700, Michel Py wrote: > Stephen, > > > Stephen Degler wrote: > > Please be more specific. I believe that there are flaws in the > > implementations of statefull firewalls as there all in all things, > > but it is my impression that they are relatively secure from the > > design perspective. > > How exactly would this IE plugin work? > > By initiating the traffic from the inside at both hosts, which opens a > temporary hole in the firewall to allow return traffic. A good example > of that kind of trick is Morpheus: People can pull mp3s from your RFC > 1918 host crossing NAT and crossing a stateful firewall _without_ having > to punch a hole in the firewall and without static NAT configuration. I > think that teredo also allows to do the same. All these mechanisms are > based in contacting an agent outside; if that agent is listening on port > 80 there is not much you can do to prevent your host talking to it. > > Michel. From jeroen@unfix.org Tue May 21 08:56:43 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFugE27364 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:56:42 -0700 (PDT) Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFufb21174 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:56:41 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 924323188; Tue, 21 May 2002 17:56:37 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 0EC193186; Tue, 21 May 2002 17:56:32 +0200 (CEST) From: "Jeroen Massar" To: "'Michel Py'" , "'Stephen Degler'" Cc: "'6 Bone'" <6bone@ISI.EDU> Subject: RE: [6bone] Re: Internal Address Space Date: Tue, 21 May 2002 17:56:32 +0200 Organization: Unfix Message-ID: <003601c200e0$157d4240$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <2B81403386729140A3A899A8B39B046405E081@server2000.arneill-py.sacramento.ca.us> Importance: Normal X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Michel Py wrote: > By initiating the traffic from the inside at both hosts, which opens a > temporary hole in the firewall to allow return traffic. A good example > of that kind of trick is Morpheus: People can pull mp3s from your RFC > 1918 host crossing NAT and crossing a stateful firewall _without_ having > to punch a hole in the firewall and without static NAT configuration. I > think that teredo also allows to do the same. All these mechanisms are > based in contacting an agent outside; if that agent is listening on port > 80 there is not much you can do to prevent your host talking to it. As long as one has a bit of clue and has "data" going from the inside to the outside you can do anything you want. Unless you got a team of sniffing admins who destroy anything that even looks suspicious. Just think: IP over Email, IP over HTTP etc. If you want to have a secure network you'll need to fully trust your local users and ofcourse the software they use. Effectively that's a nogo everywhere you go. Greets, Jeroen BTW: Just in case someone claimes "But I can check all my OpenSource software for backdoors": Start reading _and_ understanding for instance the linux kernel, Mozilla, KDE, etc... and we'll hear back from you in a couple of years. It's all about trust, but do you trust your glass of milk ? :) From michael@kjorling.com Tue May 21 08:59:03 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFx2E28434 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 08:59:03 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LFx0b21570 for <6bone@ISI.EDU>; Tue, 21 May 2002 08:59:01 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4LFwxw13776 for <6bone@ISI.EDU>; Tue, 21 May 2002 15:58:59 GMT Date: Tue, 21 May 2002 17:58:55 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 21 2002 08:26 -0700, Randy Bush wrote: > a6, dname, and bitstring labels are dog meat. folk should spend > their time on useful work. > > randy And if you pardon my question, what do you consider to be "useful work"? I believe that working toward an actual standard with regards to IPv6 forward and reverse mapping is a good thing, instead of having the current situation with two different standards and ad-hoc solutions to "interconnect" them. Both the AAAA and A6 record types have advantages as well as disadvantages. Unfortunately I don't think there is any simple solution, especially not to combine AAAA's speed with the ease of renumbering brought forth by A6. If I had a good idea I would have submitted an I-D long ago. Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE86m7DKqN7/Ypw4z4RAhHvAKCDLvm581yw9mXJWiQgvMFuxKIduwCdENY5 OpjTTwNhOO2kJ2fPHmkGxYE= =l/g8 -----END PGP SIGNATURE----- From michel@arneill-py.sacramento.ca.us Tue May 21 09:09:43 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LG9gE04873 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 09:09:42 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LG9gb27100 for <6bone@ISI.EDU>; Tue, 21 May 2002 09:09:42 -0700 (PDT) Subject: RE: [6bone] Re: Internal Address Space Date: Tue, 21 May 2002 09:09:34 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <2B81403386729140A3A899A8B39B046405E083@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6bone] Re: Internal Address Space content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Index: AcIA3Z3fhltdK8FVRwazy0C2c2KU6gAApqOQ From: "Michel Py" To: "Stephen Degler" Cc: "6 Bone" <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LG9gE04873 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Stephen Degler wrote: > Private addresses and a proxy won't help you against these methods > either, as long as http connect methods are permitted by the proxies. Correct, but they do make the hacker's task a little more difficult as the malicious code has to figure out the proxy settings and encapsulate its own stuff into http requests. Security is not a single thing, and the more obstacles you put in the hacker's way the more secure you are. A good setup is a combination of multiple methods including but not limited to stateful firewalls. I have seen generic mechanisms to bypass stateful firewalls, I have not seen any to go trough proxies yet. Michel. From bmanning@ISI.EDU Tue May 21 09:17:06 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGH4E09007 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 09:17:05 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g4LGH3601174; Tue, 21 May 2002 09:17:03 -0700 (PDT) From: Bill Manning Message-Id: <200205211617.g4LGH3601174@boreas.isi.edu> Subject: Re: [6bone] AAAA and A6 recent status? In-Reply-To: from Randy Bush at "May 21, 2 08:26:33 am" To: randy@psg.com (Randy Bush) Date: Tue, 21 May 2002 09:17:03 -0700 (PDT) Cc: 6bone@ISI.EDU X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: % a6, dname, and bitstring labels are dog meat. folk should spend % their time on useful work. % % randy % _______________________________________________ ...dog meat? perhaps insofar as "the dog ate my homework". they are products of the IETF and, as far as I can tell, are still floating around the IESG pool as RFCs. If you feel so strongly about excising them, please use your considerable influence and postition in the IESG/IAB to move them to historic status and then remove support for them from the reference implementation. And even -IF- you are able to pull this off, your insinuation that a6,dname,bitstring work did not represent "useful work" is flawed on at least a couple of counts: ) it is useful to know what does not work ) it is useful to know why things don't work --bill From Namal@datavox.net Tue May 21 09:43:58 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGhwE25089 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 09:43:58 -0700 (PDT) Received: from mail.DATAVOXin.net ([208.251.22.20]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGhvb19007 for <6bone@ISI.EDU>; Tue, 21 May 2002 09:43:57 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C200E6.B428EDD6" Date: Tue, 21 May 2002 11:43:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: <8E8A6F537294EA4481D8821DCB2F22B75553@mail.DATAVOXin.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: unsubscribe Thread-Index: AcIA5nN6ohUG6EkRQcKoLlcayxc0Bg== From: "RS Namal" To: <6bone@ISI.EDU> Subject: [6bone] unsubscribe Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: This is a multi-part message in MIME format. ------_=_NextPart_001_01C200E6.B428EDD6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Can somebody help me to unsubscribe from 6bone? I am trying various ways, but yet unsuccessful. =20 ------_=_NextPart_001_01C200E6.B428EDD6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Can somebody help me to unsubscribe from 6bone? I am = trying various ways, but yet unsuccessful.

 

=00 ------_=_NextPart_001_01C200E6.B428EDD6-- From nicolas.deffayet-extml@ndsoftwaregroup.com Tue May 21 09:43:58 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGhwE25088 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 09:43:58 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGhub19005 for <6bone@ISI.EDU>; Tue, 21 May 2002 09:43:56 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17ACjq-000IUj-00 for 6bone@ISI.EDU; Tue, 21 May 2002 18:43:54 +0200 Received: (qmail 10862 invoked from network); 21 May 2002 16:56:51 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 21 May 2002 16:56:51 -0000 From: "Nicolas DEFFAYET" To: , "'Michel Py'" Cc: <6bone@ISI.EDU> Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 18:43:31 +0200 Organization: NDSoftware Group Message-ID: <008201c200e6$a4599e90$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <1648.1021993740@itojun.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of itojun@iijlab.net > Sent: Tuesday, May 21, 2002 5:09 PM > To: Michel Py > Cc: 6bone@ISI.EDU > Subject: Re: [6bone] 6Bone registry entries when multihomed? > > > > why would you advertise private ASN onto the 6bone > whois? they should > be used locally within certain pTLAs, not globally. > also do not forget that 6bone is interconnected with > worldwide IPv6 > network (including commercially-operated network), and > there's no > well-defined boundary. therefore, my recommendation is: > - to remove/forbid private ASN from 6bone whois. > - do not advertise private ASNs beyond pTLA/sTLA boundary I'm not agree with you. A ipv6-site who use a private ASN can peer with many pTLA/sTLA, only 1 AS is used for all peers like a real pTLA/sTLA with a public ASN. I think, that it's can be a good idea to allow register private ASN (autnum object) in 6bone whois database because a same AS can't be used for 2 differents ipv6-site. If a private AS don't respect the routing rules (announce a block in global 6bone routing table), it's more easy to contact the person. When you have register your private ASN, it will be reserved for you, any other don't must use your ASN. In all case private ASN don't must be advertised in global 6bone routing table. Peering with private ASN must be considerate as private peering, all ISP who peer with private ASN must don't reannounces routes of private ASN. pTLA/sTLA -> private ASN = full or not transit pTLA/sTLA <- private ASN = only routes of private ASN (not transit) with community no-export (if pTLA/sTLA accept route with private ASN) private ASN <-> private ASN = full or not transit Production network don't advertise/receive all 6bone routes, but use only 3ffe::/16 for can be interconnected to the 6bone (you can see this in IPv6 BGP policy of a lof of production ISP). Why remove/forbid private ASN (ipv6-site ? because a aut-num can't be registered at this time) from 6bone whois ? 6bone whois is a test whois database. mnt-lower don't work and you can register what all you want like the RIPE test whois database. I hope be clear. Sorry if my english is not perfect, it's not my native language. Best Regards, Nicolas DEFFAYET From nicolas.deffayet-extml@ndsoftwaregroup.com Tue May 21 09:46:19 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGkJE26209 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 09:46:19 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LGkIb19606 for <6bone@ISI.EDU>; Tue, 21 May 2002 09:46:18 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17ACm8-000IVP-00 for 6bone@ISI.EDU; Tue, 21 May 2002 18:46:16 +0200 Received: (qmail 11218 invoked from network); 21 May 2002 16:59:13 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 21 May 2002 16:59:13 -0000 From: "Nicolas DEFFAYET" To: "'Michel Py'" , Cc: <6bone@ISI.EDU> Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 18:45:53 +0200 Organization: NDSoftware Group Message-ID: <008301c200e6$f8f1f600$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <2B81403386729140A3A899A8B39B046405E082@server2000.arneill-py.sacramento.ca.us> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Michel Py > Sent: Tuesday, May 21, 2002 5:18 PM > To: itojun@iijlab.net > Cc: 6bone@ISI.EDU > Subject: RE: [6bone] 6Bone registry entries when multihomed? > > > why would you advertise private ASN onto the 6bone whois? > > - to remove/forbid private ASN from 6bone whois. > > Why not having accurate information in the 6bone database? We > are not talking about a xTLA peering with a private ASN, but > about a site peering with a xTLA that can use remove-private-as. > Warning, remove-private-as don't drop route with private ASN but only remove private ASN in AS path. For filtering private ASN, use: ip as-path access-list private-asn-in deny _(6451[2-9]|645[2-9][0-9]|64[6-9][0-9][0-9]|65[0-4][0-9][0-9]|655[0-2][0 -9]|6553[0-5])_ Best Regards, Nicolas DEFFAYET From pim@ipng.nl Tue May 21 11:34:35 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LIYYE10887 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 11:34:34 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LIYWb24863 for <6bone@ISI.EDU>; Tue, 21 May 2002 11:34:33 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id D45C28C2B; Tue, 21 May 2002 18:34:30 +0000 (GMT) Date: Tue, 21 May 2002 20:34:30 +0200 From: Pim van Pelt To: Michel Py Cc: itojun@iijlab.net, 6bone@ISI.EDU, peering@v6bone.de Subject: Re: [6bone] 6Bone registry entries when multihomed? Message-ID: <20020521183430.GF16534@bfib.colo.bit.nl> References: <2B81403386729140A3A899A8B39B046405E082@server2000.arneill-py.sacramento.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2B81403386729140A3A899A8B39B046405E082@server2000.arneill-py.sacramento.ca.us> User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Tue, May 21, 2002 at 08:17:38AM -0700, Michel Py wrote: | > Itojun wrote: | > they should be used locally within certain pTLAs, not globally. | > also do not forget that 6bone is interconnected with worldwide | > IPv6 network (including commercially-operated network), and | > there's no well-defined boundary. therefore, my recommendation | > is: | > - do not advertise private ASNs beyond pTLA/sTLA boundary | | I completely agree with the above. | | > why would you advertise private ASN onto the 6bone whois? | > - to remove/forbid private ASN from 6bone whois. | | Why not having accurate information in the 6bone database? We are not | talking about a xTLA peering with a private ASN, but about a site | peering with a xTLA that can use remove-private-as. Can, but doesn't, as has been visible in the global routing tables for many months now. I normally don't engage in personal flames, but this has been on my chest for a looong time. I'm sure other members of the 6bone community will agree with me, so here goes (my 2 cents worth of rant). Deffayet claims 'RIPE wont give him an AS' but this is only logical as he does not operate an autonomous system, nor is he a LIR, rather two or three cablemodems at residential sites. He may (naturally) do what he pleases, however he has been asked by numerous people not to have his AS show up all around the place, but he simply blames his uplinks for not filtering them out. My opinion is that he is using private-as numbers to gain global visibility and not for any other purpose. I might as well filter off those pTLAs that are not well behaving then, or shall I go to the root of the problem ? AS65526 is giving transit to others, which is completely ludicrous. This shows up in the looking glass at AS8954: Network Path * 3ffe:82a0::/28 15589 12337 15671 65526 7521 i Now apparently AS15671 is non-well behaved (therefor the CC to their contact), and it is leaking this as-path into its peers. Looking at the prefixes that AS15671 announces regularly, Deffayet's aren't amongst them. This leads me to believe that Deffayet is not using a private AS number to establish a session with his uplinks (he has three), but simply to circumvent the RIR policies which denied him an AS number (for, I might add, obvious reasons!). Now I ask again: can you please clean up the mess you are making ? -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From michel@arneill-py.sacramento.ca.us Tue May 21 11:56:16 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LIuFE22348 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 11:56:15 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LIuEb06034 for <6bone@ISI.EDU>; Tue, 21 May 2002 11:56:15 -0700 (PDT) Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 11:56:08 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <2B81403386729140A3A899A8B39B046405E086@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: X-MS-TNEF-Correlator: content-class: urn:content-classes:message Thread-Topic: [6bone] 6Bone registry entries when multihomed? X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Index: AcIA5yj8WsNRK7XPS6yFrYbAWzP+2AADjbXw From: "Michel Py" To: "Nicolas DEFFAYET" Cc: <6bone@ISI.EDU>, , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LIuFE22348 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Nicolas DEFFAYET wrote: > Warning, remove-private-as don't drop route with private ASN but > only remove private ASN in AS path. Correct, combined with aggregation this is what your ISP is supposed to do. Filtering private ASNs should not be necessary if everyone configured things the way they are supposed to, which is not the case. BGP table version is 29198, local router ID is 209.233.126.65 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * 3FFE:82A0::/28 3FFE:B00:C18::8C 0 10566 12337 15671 65526 7521 i The bottom line is that you should _not_ announce AS 7521 to AS 15671. Also, AS 15671 should strip the private AS from the ASPATH. Michel. From michel@arneill-py.sacramento.ca.us Tue May 21 12:10:04 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LJA4E27510 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 12:10:04 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LJA3b13033 for <6bone@ISI.EDU>; Tue, 21 May 2002 12:10:03 -0700 (PDT) Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 12:09:57 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <2B81403386729140A3A899A8B39B046405E087@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: X-MS-TNEF-Correlator: content-class: urn:content-classes:message Thread-Topic: [6bone] 6Bone registry entries when multihomed? X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Index: AcIA9kj9VOYc77/dTz20mwaRL1g4uwAA0M8g From: "Michel Py" To: "Pim van Pelt" Cc: <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4LJA4E27510 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Pim, >> Michel Py wrote: >> Why not having accurate information in the 6bone database? We are not >> talking about a xTLA peering with a private ASN, but about a site >> peering with a xTLA that can use remove-private-as. > Pim van Pelt wrote: > Can, but doesn't, as has been visible in the global routing > tables for many months now. This is the root of the problem, IMHO. > He may (naturally) do what he pleases, however he has been asked > by numerous people not to have his AS show up all around the place, > but he simply blames his uplinks for not filtering them out. Well, it is the role of an xTLA to make sure that whatever crap their customers feed them is not seen in the global routing table. To some extent, it's good that people do announce private ASNs, because it points out filtering flaws. > I might as well filter off those pTLAs that are not well > behaving then Have you contacted them? If someone forgot to put a filter, it's one thing. If they do it on purpose, I would filter these non-behaving pTLAs myself. Michel. From nicolas.deffayet-extml@ndsoftwaregroup.com Tue May 21 14:53:42 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LLrfE11716 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 14:53:41 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LLrcb03378 for <6bone@ISI.EDU>; Tue, 21 May 2002 14:53:40 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17AHZY-000KVv-00 for 6bone@ISI.EDU; Tue, 21 May 2002 23:53:36 +0200 Received: (qmail 14845 invoked from network); 21 May 2002 22:06:35 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 21 May 2002 22:06:35 -0000 From: "Nicolas DEFFAYET" To: "'Pim van Pelt'" , "'Michel Py'" Cc: , <6bone@ISI.EDU>, Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 23:53:18 +0200 Organization: NDSoftware Group Message-ID: <00b701c20111$eadb2f20$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020521183430.GF16534@bfib.colo.bit.nl> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Pim van Pelt > Sent: Tuesday, May 21, 2002 8:35 PM > To: Michel Py > Cc: itojun@iijlab.net; 6bone@ISI.EDU; peering@v6bone.de > Subject: Re: [6bone] 6Bone registry entries when multihomed? I don't like reply to a troll, but i reply for many reasons. > I normally don't engage in personal flames, but this has been > on my chest for a looong time. I'm sure other members of the > 6bone community will agree with me, so here goes (my 2 cents > worth of rant). > > Deffayet claims 'RIPE wont give him an AS' but this is only > logical as he does not operate an autonomous system, nor is > he a LIR, rather > two or three cablemodems at residential sites. First please respect me. I'm not your dog, call me Nicolas or Nicolas DEFFAYET or Mr DEFFAYET, not "DEFFAYET" I don't claim this. Have you read my mail ? Be a LIR is plained for my project... Have you create your network in one day ? I don't use "cablemodems at residential sites". It's the same if i tell that IPng.nl use 3 56k modems ! You are a troll expert :) I don't like liar. > AS65526 is giving transit to others, which is completely > ludicrous. This shows up in the looking glass at AS8954: > Network Path > * 3ffe:82a0::/28 15589 12337 15671 65526 7521 i > > Now apparently AS15671 is non-well behaved (therefor the CC > to their contact), and it is leaking this as-path into its peers. All routes sent my me, are in ALL case with community no-export. This is not possible (execept of ISP have bugy router who don't understand community). For information, community no-export = send routes to ibgp but NOT to other eBGP. I have shutdown the announcement of my routes to v6bone. > > Looking at the prefixes that AS15671 announces regularly, > Deffayet's aren't amongst them. This leads me to believe that > Deffayet is not using a private AS number to establish a > session with his uplinks (he has three), but simply to > circumvent the RIR policies which denied him an AS number > (for, I might add, obvious reasons!). I will get soon a public AS. But for respect the RIPE allocation rule, i need 2 transit IPv4. It's plained before for maximum the end of this year. > > Now I ask again: can you please clean up the mess you are making ? If you have problem with "my" private ASN: noc@ndsoftwarenet.com But it's very very rare because all my routes are sent with community no-export and i send all routes (transit) only to peer who request this to me. You can add filter if you want: ip as-path access-list private-asn-in deny _(6451[2-9]|645[2-9][0-9]|64[6-9][0-9][0-9]|65[0-4][0-9][0-9]|655[0-2][0 -9]|6553[0-5])_ ip as-path access-list private-asn-in permit .* Best Regards, Nicolas DEFFAYET From nicolas.deffayet-extml@ndsoftwaregroup.com Tue May 21 14:56:46 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LLukE13884 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 14:56:46 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LLuib04292 for <6bone@ISI.EDU>; Tue, 21 May 2002 14:56:45 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17AHcY-000KWi-00 for 6bone@ISI.EDU; Tue, 21 May 2002 23:56:42 +0200 Received: (qmail 15203 invoked from network); 21 May 2002 22:09:42 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 21 May 2002 22:09:42 -0000 From: "Nicolas DEFFAYET" To: "'Michel Py'" Cc: <6bone@ISI.EDU>, , Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 23:56:25 +0200 Organization: NDSoftware Group Message-ID: <00b801c20112$5a3a1430$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <2B81403386729140A3A899A8B39B046405E086@server2000.arneill-py.sacramento.ca.us> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Michel Py > Sent: Tuesday, May 21, 2002 8:56 PM > To: Nicolas DEFFAYET > Cc: 6bone@ISI.EDU; jens.gottbehuet@completel.de; randy@ipcenta.de > Subject: RE: [6bone] 6Bone registry entries when multihomed? > > > > Nicolas DEFFAYET wrote: > > Warning, remove-private-as don't drop route with private > ASN but only > > remove private ASN in AS path. > > Correct, combined with aggregation this is what your ISP is > supposed to do. Filtering private ASNs should not be > necessary if everyone configured things the way they are > supposed to, which is not the case. > > BGP table version is 29198, local router ID is 209.233.126.65 > Status codes: s suppressed, d damped, h history, * valid, > > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete > > Network Next Hop Metric LocPrf Weight Path > * 3FFE:82A0::/28 3FFE:B00:C18::8C > 0 10566 12337 15671 > 65526 7521 i > > The bottom line is that you should _not_ announce AS 7521 to > AS 15671. Also, AS 15671 should strip the private AS from the ASPATH. I think that completel's router don't understand community (read my reply to Pim for more information about that). Now, i don't send any routes to completel, i accept it only (a BGP view). Best Regards, Nicolas DEFFAYET From daniel@kewlio.net Tue May 21 15:12:42 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4LMCgE20955 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 15:12:42 -0700 (PDT) Received: from ambient.kewlio.net (root@ambient.kewlio.net [62.24.229.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4LMCeb09994 for <6bone@ISI.EDU>; Tue, 21 May 2002 15:12:41 -0700 (PDT) Received: from windoze (adsl-62-128-217-62-128-217.iomart.com [62.128.217.217] (may be forged)) by ambient.kewlio.net (kewlio.net mail server) with SMTP id g4LMCXsT094930; Tue, 21 May 2002 23:12:33 +0100 (BST) Message-ID: <001b01c20114$98d42990$611c08d9@windoze> Reply-To: "Daniel Austin" From: "Daniel Austin" To: "Nicolas DEFFAYET" Cc: "'Pim van Pelt'" , "'Michel Py'" , , <6bone@ISI.EDU>, References: <20020521230300.U93116-100000@ambient.kewlio.net> Subject: Re: [6bone] 6Bone registry entries when multihomed? Date: Tue, 21 May 2002 23:12:28 +0100 Organization: Kewlio.net Limited MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: And again from the correct address :-) ----- Original Message ----- From: "Daniel Austin (fxp0)" To: "Nicolas DEFFAYET" Cc: "'Pim van Pelt'" ; "'Michel Py'" ; ; <6bone@ISI.EDU>; Sent: Tuesday, May 21, 2002 11:05 PM Subject: RE: [6bone] 6Bone registry entries when multihomed? > Hiya, > > Nicolas peers with us, and his ASN is not exported to our upstream > providers. IPv6 is a new technology and people are going to use it > differently to IPv4 so why should be restrict them to the current ipv4 > requirements? > > If they want to use private ASN's then thats not a problem. If everyone > applies the correct filters everything is fine. > > > With Thanks, > > Daniel Austin, > kewlio.net Limited. > > > On Tue, 21 May 2002, Nicolas DEFFAYET wrote: > > > > -----Original Message----- > > > From: 6bone-admin@mailman.isi.edu > > > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Pim van Pelt > > > Sent: Tuesday, May 21, 2002 8:35 PM > > > To: Michel Py > > > Cc: itojun@iijlab.net; 6bone@ISI.EDU; peering@v6bone.de > > > Subject: Re: [6bone] 6Bone registry entries when multihomed? > > > > I don't like reply to a troll, but i reply for many reasons. > > > > > I normally don't engage in personal flames, but this has been > > > on my chest for a looong time. I'm sure other members of the > > > 6bone community will agree with me, so here goes (my 2 cents > > > worth of rant). > > > > > > Deffayet claims 'RIPE wont give him an AS' but this is only > > > logical as he does not operate an autonomous system, nor is > > > he a LIR, rather > > > two or three cablemodems at residential sites. > > > > First please respect me. > > I'm not your dog, call me Nicolas or Nicolas DEFFAYET or Mr DEFFAYET, > > not "DEFFAYET" > > > > I don't claim this. > > > > Have you read my mail ? > > Be a LIR is plained for my project... > > > > Have you create your network in one day ? > > > > I don't use "cablemodems at residential sites". > > It's the same if i tell that IPng.nl use 3 56k modems ! > > > > You are a troll expert :) > > > > I don't like liar. > > > > > > > AS65526 is giving transit to others, which is completely > > > ludicrous. This shows up in the looking glass at AS8954: > > > Network Path > > > * 3ffe:82a0::/28 15589 12337 15671 65526 7521 i > > > > > > Now apparently AS15671 is non-well behaved (therefor the CC > > > to their contact), and it is leaking this as-path into its peers. > > > > All routes sent my me, are in ALL case with community no-export. > > This is not possible (execept of ISP have bugy router who don't > > understand community). > > > > For information, community no-export = send routes to ibgp but NOT to > > other eBGP. > > > > I have shutdown the announcement of my routes to v6bone. > > > > > > > > Looking at the prefixes that AS15671 announces regularly, > > > Deffayet's aren't amongst them. This leads me to believe that > > > Deffayet is not using a private AS number to establish a > > > session with his uplinks (he has three), but simply to > > > circumvent the RIR policies which denied him an AS number > > > (for, I might add, obvious reasons!). > > > > I will get soon a public AS. > > But for respect the RIPE allocation rule, i need 2 transit IPv4. > > > > It's plained before for maximum the end of this year. > > > > > > > > Now I ask again: can you please clean up the mess you are making ? > > > > If you have problem with "my" private ASN: noc@ndsoftwarenet.com > > But it's very very rare because all my routes are sent with community > > no-export and i send all routes (transit) only to peer who request this > > to me. > > > > You can add filter if you want: > > > > ip as-path access-list private-asn-in deny > > _(6451[2-9]|645[2-9][0-9]|64[6-9][0-9][0-9]|65[0-4][0-9][0-9]|655[0-2][0 > > -9]|6553[0-5])_ > > ip as-path access-list private-asn-in permit .* > > > > > > Best Regards, > > > > Nicolas DEFFAYET > > > > _______________________________________________ > > 6bone mailing list > > 6bone@mailman.isi.edu > > http://mailman.isi.edu/mailman/listinfo/6bone > > > > From david@iprg.nokia.com Tue May 21 17:57:21 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4M0vLE16472 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 17:57:21 -0700 (PDT) Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4M0vKb24094 for <6bone@ISI.EDU>; Tue, 21 May 2002 17:57:20 -0700 (PDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA21037; Tue, 21 May 2002 17:57:12 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g4M0vBA16797; Tue, 21 May 2002 17:57:11 -0700 X-mProtect: <200205220057> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (4.22.78.79, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdE0LVWN; Tue, 21 May 2002 17:57:09 PDT Received: (from david@localhost) by iprg.nokia.com (8.11.2/8.11.2) id g4M0vFQ03685; Tue, 21 May 2002 17:57:15 -0700 Date: Tue, 21 May 2002 17:57:15 -0700 From: David Kessens To: Nicolas DEFFAYET Cc: 6bone@ISI.EDU Subject: Re: [6bone] 6Bone registry entries when multihomed? Message-ID: <20020521175715.A3637@iprg.nokia.com> References: <1648.1021993740@itojun.org> <008201c200e6$a4599e90$0103010a@lnet.fr.ndsoftwaregroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <008201c200e6$a4599e90$0103010a@lnet.fr.ndsoftwaregroup.com>; from nicolas.deffayet-extml@ndsoftwaregroup.com on Tue, May 21, 2002 at 06:43:31PM +0200 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Nicolas, On Tue, May 21, 2002 at 06:43:31PM +0200, Nicolas DEFFAYET wrote: > > Why remove/forbid private ASN (ipv6-site ? because a aut-num can't be > registered at this time) from 6bone whois ? 6bone whois is a test whois > database. Please don't spread this kind of misinformation about the server. The whois server is not a test server at all and is the official registry for the 6bone. We have very liberal policies in place for registration of information. That means that everybody who uses this information is well advised to use filters in order to distinguise some bad information from the good information. We are this liberal because we don't want to make the use of the registry a burden for the legitimate 6bone community. I can put in more restrictive policies if the community desires so. It's users like you who sometimes make me wonder whether I should ask the community to put such more restrictive policies in place. You might want to consider to be more careful in what you are doing on the 6bone and the work that you create for me with your continious changing objects and mail servers that never seem to work. There is serious people on the 6bone who want to work with ipv6. Your project is causing an enormous distraction for many people who want to find out about the real problems in deploying ipv6. You are welcome to participate, whether you are small or big. However, this participation comes with certain responsibilities. One of these responsibilities is that you take comments/concerns from other people seriously and fix issues when they arise. You clearly have a problem with private AS#'s leaking out and I would like to suggest that you try to resolve that with your providers instead of blaming other people for a problem that ultimately originates from your network. Thanks, David K. --- From dave@dave2.dave.tj Tue May 21 21:29:18 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4M4TIE06247 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 21:29:18 -0700 (PDT) Received: from mta5.srv.hcvlny.cv.net (mta5.srv.hcvlny.cv.net [167.206.5.31]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4M4TGb22222 for <6bone@isi.edu>; Tue, 21 May 2002 21:29:17 -0700 (PDT) Received: from dave2.dave.tj (ool-4351482a.dyn.optonline.net [67.81.72.42]) by mta2.srv.hcvlny.cv.net (iPlanet Messaging Server 5.0 Patch 2 (built Dec 14 2000)) with ESMTP id <0GWH00C95WGQDE@mta2.srv.hcvlny.cv.net> for 6bone@isi.edu; Wed, 22 May 2002 00:29:16 -0400 (EDT) Received: (from dave@localhost) by dave2.dave.tj (8.10.2/8.10.2) id g4M4OIH21102; Wed, 22 May 2002 04:24:18 +0000 (GMT) Date: Wed, 22 May 2002 00:24:17 -0400 (EDT) From: Dave Subject: Re: [6bone] unsubscribe In-reply-to: <8E8A6F537294EA4481D8821DCB2F22B75553@mail.DATAVOXin.net> To: Namal@datavox.net (RS Namal) Cc: 6bone@ISI.EDU Message-id: <200205220424.g4M4OIH21102@dave2.dave.tj> MIME-version: 1.0 X-Mailer: ELM [version 2.5 PL3] Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Try sending an email with the subject "unsubscribe" to <6bone-request@isi.edu>. That should work, now that 6bone is on real mailman (as opposed to their majordomo's attempts at fooling us into thinking it was mailman a week or so ago). - Dave RS Namal wrote: > > This is a multi-part message in MIME format. > > ------_=_NextPart_001_01C200E6.B428EDD6 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > Can somebody help me to unsubscribe from 6bone? I am trying various > ways, but yet unsuccessful. > > =20 > > > ------_=_NextPart_001_01C200E6.B428EDD6 > Content-Type: text/html; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > > > > charset=3Dus-ascii"> > > > > > > > > > > >
> >

style=3D'font-size:10.0pt; > font-family:Arial'>Can somebody help me to unsubscribe from 6bone? I am = > trying > various ways, but yet unsuccessful.

> >

style=3D'font-size:10.0pt; > font-family:Arial'> 

> >
> > > > > =00 > ------_=_NextPart_001_01C200E6.B428EDD6-- > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From nicolas.deffayet-extml@ndsoftwaregroup.com Wed May 22 05:21:31 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4MCLVE29033 for <6bone@mailman.isi.edu>; Wed, 22 May 2002 05:21:31 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4MCLQb22326 for <6bone@ISI.EDU>; Wed, 22 May 2002 05:21:27 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17AV7L-0002a3-00 for 6bone@ISI.EDU; Wed, 22 May 2002 14:21:23 +0200 Received: (qmail 19844 invoked from network); 22 May 2002 12:34:26 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 22 May 2002 12:34:26 -0000 From: "Nicolas DEFFAYET" To: "'David Kessens'" Cc: <6bone@ISI.EDU> Subject: RE: [6bone] 6Bone registry entries when multihomed? Date: Wed, 22 May 2002 14:20:59 +0200 Organization: NDSoftware Group Message-ID: <011e01c2018b$220ffbf0$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020521175715.A3637@iprg.nokia.com> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: David Kessens [mailto:david@IPRG.nokia.com] > Sent: Wednesday, May 22, 2002 2:57 AM > To: Nicolas DEFFAYET > Cc: 6bone@ISI.EDU > Subject: Re: [6bone] 6Bone registry entries when multihomed? > > Dear David, > On Tue, May 21, 2002 at 06:43:31PM +0200, Nicolas DEFFAYET wrote: > > > > I can put in more restrictive policies if the community > desires so. It's users like you who sometimes make me wonder > whether I should ask the community to put such more > restrictive policies in place. You might want to consider to > be more careful in what you are doing on the 6bone and the > work that you create for me with your continious changing > objects and mail servers that never seem to work. There is > serious people on the 6bone who want to work with ipv6. Your > project is causing an enormous distraction for many people > who want to find out about the real problems in deploying ipv6. I'm sorry if i create work for you. 6bone database is not fully automatic (except for mnter object who need manual intervention) ? I have decide this before this mail (i have remove ipv6-fr-cust and all user whois)): i don't create anymore individual whois for users of IPv6-FR project (it's not the same project that NDSoftware, IPv6-FR is a french project for the developement of IPv6 in France). I have do this because you have a lot of problem with mail servers of users and with more than 40 users i can't maint individual whois in good conditions. I don't think that you have problem with my mail servers because i have many MX checked my monitoring tool. I will now more pay attention to whois create/update/delete. > > You are welcome to participate, whether you are small or big. > However, this participation comes with certain > responsibilities. One of these responsibilities is that you > take comments/concerns from other people seriously and fix > issues when they arise. You clearly have a problem with > private AS#'s leaking out and I would like to suggest that > you try to resolve that with your providers instead of > blaming other people for a problem that ultimately originates > from your network. For information, i'm responsable of NDSoftware and IPv6-FR project, you (and all peoples) can contact me if you have problem with this projects, don't hesitate, i'm open to all requests (except troll like the Pim's troll) for fix my errors. I do very attention with my private ASN (all my routes are sent with community no-export) and i don't provide transit except if the peer ask me for it. "Dear Nicolas DEFFAYET, Peer is ok. BTW, please give me your full route. It seems disappear from yesterday. Thank you." I don't send anymore routes to v6bone (completel) because one of users of 6bone have report me a problem (see previous mails). I will apply this for each peer who reannonce my routes with my private ASN. Problem with it => don't annonces routes anymore If anyone find this policy bad, tell me. I wait your comments... Thanks Best Regards, Nicolas DEFFAYET From bmanning@ISI.EDU Wed May 22 09:13:19 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4MGDJE08223 for <6bone@mailman.isi.edu>; Wed, 22 May 2002 09:13:19 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g4MGDD919274; Wed, 22 May 2002 09:13:13 -0700 (PDT) From: Bill Manning Message-Id: <200205221613.g4MGDD919274@boreas.isi.edu> Subject: Re: [6bone] 6bone pTLA 3FFE:4009::/32 allocated to VERAT In-Reply-To: <5.1.0.14.0.20020521064954.02989c98@imap2.es.net> from Bob Fink at "May 21, 2 06:51:10 am" To: fink@es.net (Bob Fink) Date: Wed, 22 May 2002 09:13:13 -0700 (PDT) Cc: 6bone@ISI.EDU, awl@verat.net, hostmaster@ep.net X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: until then.... ;; QUESTION SECTION: ;9.0.0.4.e.f.f.3.ip6.int. IN NS ;; AUTHORITY SECTION: 9.0.0.4.e.f.f.3.ip6.int. 86400 IN NS noserver. % VERAT has been allocated pTLA 3FFE:4009::/32 having finished its 2-week % review period. % % % % % Note that it will take a short while for their pTLA inet6num entry to % appear in the 6bone registry as they have to create it themselves. However, % their registration is listed on: % % % % % [To create a reverse DNS registration for pTLAs, please send the prefix % allocated above, and a list of at least two authoritative nameservers, to % hostmaster@ep.net.] % % % Thanks, % % Bob % % _______________________________________________ % 6bone mailing list % 6bone@mailman.isi.edu % http://mailman.isi.edu/mailman/listinfo/6bone % -- --bill From michael@kjorling.com Wed May 22 11:01:14 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4MI1CE04344 for <6bone@mailman.isi.edu>; Wed, 22 May 2002 11:01:13 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4MI1Ab22047 for <6bone@isi.edu>; Wed, 22 May 2002 11:01:11 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4MI10w31733 for <6bone@isi.edu>; Wed, 22 May 2002 18:01:00 GMT Date: Wed, 22 May 2002 20:00:56 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: 6bone <6bone@ISI.EDU> Subject: Re: [6bone] 6bone pTLA 3FFE:4009::/32 allocated to VERAT In-Reply-To: <200205221613.g4MGDD919274@boreas.isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 22 2002 09:13 -0700, Bill Manning wrote: > until then.... > > ;; QUESTION SECTION: > ;9.0.0.4.e.f.f.3.ip6.int. IN NS > > ;; AUTHORITY SECTION: > 9.0.0.4.e.f.f.3.ip6.int. 86400 IN NS noserver. Wouldn't it be better to simply not put in any delegation information? That would give a quick NXDOMAIN response, instead of the resolver having to go off and ask the root servers about "noserver", only to find out it doesn't exist. Granted, negative caching will mitigate this problem, but why put unnecessary load on the root servers when it can be avoided? Also I'm not sure how exactly a NS pointing to a non-existent RR is handled. NXDOMAIN, or SERVFAIL? Might have to check, just for the heck of it... Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE869zbKqN7/Ypw4z4RApxIAJ9I8ihYbCoQ4NyGRv+FPhA4PFUu8wCgl7YS g6qeNUMl+9LLJqtKGaiAJXM= =mOM0 -----END PGP SIGNATURE----- From nicolas.deffayet-extml@ndsoftwaregroup.com Wed May 22 12:32:10 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4MJWAE19257 for <6bone@mailman.isi.edu>; Wed, 22 May 2002 12:32:10 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4MJW8b13840 for <6bone@ISI.EDU>; Wed, 22 May 2002 12:32:09 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17AbqA-0005P2-00 for 6bone@ISI.EDU; Wed, 22 May 2002 21:32:06 +0200 Received: (qmail 6059 invoked from network); 22 May 2002 19:45:12 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 22 May 2002 19:45:12 -0000 From: "Nicolas DEFFAYET" To: "'Michael Kjorling'" , "'6bone'" <6bone@ISI.EDU> Subject: RE: [6bone] 6bone pTLA 3FFE:4009::/32 allocated to VERAT Date: Wed, 22 May 2002 21:31:41 +0200 Organization: NDSoftware Group Message-ID: <019f01c201c7$4c999b10$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Michael Kjorling > Sent: Wednesday, May 22, 2002 8:01 PM > To: 6bone > Subject: Re: [6bone] 6bone pTLA 3FFE:4009::/32 allocated to VERAT > > On May 22 2002 09:13 -0700, Bill Manning wrote: > > > until then.... > > > > ;; QUESTION SECTION: > > ;9.0.0.4.e.f.f.3.ip6.int. IN NS > > > > ;; AUTHORITY SECTION: > > 9.0.0.4.e.f.f.3.ip6.int. 86400 IN NS noserver. > > Wouldn't it be better to simply not put in any delegation > information? That would give a quick NXDOMAIN response, > instead of the resolver having to go off and ask the root > servers about "noserver", only to find out it doesn't exist. > > Granted, negative caching will mitigate this problem, but why > put unnecessary load on the root servers when it can be avoided? > > Also I'm not sure how exactly a NS pointing to a non-existent > RR is handled. NXDOMAIN, or SERVFAIL? > > Might have to check, just for the heck of it... I think that it's a good idea to ask for nameservers in pTLA request. It's plained to do stats on nameserver of pTLA like the RIPE ? (http://www.ripe.net/ripencc/pub-services/stats/revdns/index.html) Best Regards, Nicolas DEFFAYET From michael@kjorling.com Wed May 22 13:14:42 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4MKEfE07331 for <6bone@mailman.isi.edu>; Wed, 22 May 2002 13:14:42 -0700 (PDT) Received: from varg.mcpoolen.se (varg.mcpoolen.se [213.88.238.204]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4MKEeb06235 for <6bone@isi.edu>; Wed, 22 May 2002 13:14:40 -0700 (PDT) Received: from localhost (IDENT:michael@localhost [127.0.0.1]) by varg.mcpoolen.se (8.11.6/8.11.6) with ESMTP id g4MKEcw03736 for <6bone@isi.edu>; Wed, 22 May 2002 20:14:38 GMT Date: Wed, 22 May 2002 22:14:34 +0200 (CDT) From: Michael Kjorling X-X-Sender: michael@varg.wolfpack To: 6bone <6bone@ISI.EDU> Subject: RE: [6bone] 6bone pTLA 3FFE:4009::/32 allocated to VERAT In-Reply-To: <019f01c201c7$4c999b10$0103010a@lnet.fr.ndsoftwaregroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On May 22 2002 21:31 +0200, Nicolas DEFFAYET wrote: > I think that it's a good idea to ask for nameservers in pTLA request. While I agree in principle, there is one problem with this. Without knowing the prefix allocated, setting up the name servers to serve it gets pretty tricky. I do think it would be a good idea to clearly state that reverse DNS _is_ required in either RFC 2772 or its successor, though. The problem is that without some way to enforce that, it gets nothing but a blow in the air. We don't need rules that are impossible or extremely hard to enforce beyond the "would you please do this" point - I think more or less everyone here can agree with that. Michael Kjörling - -- Michael Kjörling -- Programmer/Network administrator ^..^ Internet: michael@kjorling.com -- FidoNet: 2:204/254.4 \/ PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e ``And indeed people sometimes speak of man's "bestial" cruelty, but this is very unfair and insulting to the beasts: a beast can never be so cruel as a man, so ingeniously, so artistically cruel.'' (Ivan Karamazov, in Dostoyevsky's 'The Brothers Karamazov') -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Public key is at http://michael.kjorling.com/contact/pgp.html iD8DBQE86/wuKqN7/Ypw4z4RAgu0AKDSG1cAm23JkI0/A0vMjDBEUaC9ngCeMqQw NrOrymUKY+n+8OHRUPnrKhc= =OX5h -----END PGP SIGNATURE----- From ishida@netlab.nttdocomo.co.jp Mon May 20 17:01:29 2002 Received: from mail0.yrp.nttdocomo.co.jp (root@mail0.yrp.nttdocomo.co.jp [202.245.184.18]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4L01SE13609 for <6bone@mailman.isi.edu>; Mon, 20 May 2002 17:01:28 -0700 (PDT) Received: from NW-ISHIDA ([172.20.34.248]) by mail0.yrp.nttdocomo.co.jp (8.11.6/YRPHUB0-8820020412) with ESMTP id g4L01QD02510 for <6bone@mailman.isi.edu>; Tue, 21 May 2002 09:01:26 +0900 (JST) Date: Tue, 21 May 2002 09:05:54 +0900 From: To: 6bone@mailman.isi.edu Message-Id: <20020521090259.6A26.ISHIDA@netlab.nttdocomo.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.00.11 Subject: [6bone] Magic Packet with IPv6 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Dear all, I want to start my PC on other Ethernet with Magic Packet ( http://www.amd.com/us-en/Networking/NetworkingApplications/0,,50_2332_2627_2481,00.html ). What destination IPv6 address I use? If I send IPv4 packet to broadcast IPv4 address of other Ethernet, the router may send the packet with broad-cast MAC address. Then my PC's LAN controller catch the packet and my PC wake up. I want to do this with IPv6. ----------------- Ishida So Network Laboratories, NTT DoCoMo, Inc. From michel@arneill-py.sacramento.ca.us Wed May 22 20:45:16 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4N3jGE23239 for <6bone@mailman.isi.edu>; Wed, 22 May 2002 20:45:16 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4N3jFb21584 for <6bone@ISI.EDU>; Wed, 22 May 2002 20:45:15 -0700 (PDT) Subject: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Date: Wed, 22 May 2002 20:45:08 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <2B81403386729140A3A899A8B39B046406C75E@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-TNEF-Correlator: Thread-Topic: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Thread-Index: AcIBLDVWhtru+tyeQDabRUfzxq83JwA39oyw From: "Michel Py" To: <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4N3jGE23239 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: 6boner, My candid view on IPv6 multihoming, comments welcomed. Michel. +-----------------------------------------------+ | Roadmap to IPv6 multihoming: no PI addresses. | +-----------------------------------------------+ Assessment of the current IPv6 multihoming situation: ----------------------------------------------------- - Regardless of the availability of multihoming protocols, independence from the service provider is highly desired by multihomers. - The pressure is increasing on RIRs to allocate PI blocks. - RIRs have delayed PI allocation as it creates long-term known problems. - The current policies effectively prohibit multihoming for everyone but ISPs (even RIRs themselves can not use PI addresses). - It is clear at this time that PA addresses alone do not address today's needs. The current roadmap to IPv6 multihoming is: - Offer a short-term alternative that would prevent the deployment of PI addresses: "geo for now". - Finish developing a long-term, scalable solution: MHAP. - ISP multihoming remains unchanged. "geo for now" ------------- The idea is to create a low-ambition geographic aggregation model that can be adopted using today's technology, requires no changes to physical infrastructure and few changes to current operational practices. Current work includes making geo for now and MHAP compatible to the migration from the shorter-term geo for now to the longer-term MHAP smooth. Geo addresses are: - Allocated depending on the location of the site. - Allocated by RIRs or NIRs - Locally portable. - Globally unique. - Aggregatable. Regardless of the actual aggregation ratio achieved, geo addresses are always preferable to PI; PI addresses will never be aggregated, geo will some day. Therefore, no IPv6 PI addresses must be ever used in any situation and geo addresses must be used instead. In other words, PI addresses offers no hope of aggregation, geo addresses do. The choice between PI and geo is a no-brainer: geo. MHAP ---- This is currently a working document of the ipv6mh mailing list. The draft is relatively mature and an earlier form was submitted to the IETF a year ago (it has evolved since then). MHAP is a full-blown mid to long-term solution. MHAP Features: - Zero impact on the DFZ's routing table. The DFZ's routing table stays strongly aggregated. - Provides multihomed, provider-independent, /48 address space for any site. - Very large organizations that require more can get a /47 or bigger. - Scalable (4 billion multihomed sites, initial allocation). - Addresses are aggregated at geographic areas boundaries. - There is no need for Internet eXchanges at aggregation boundaries. - MHAP is transparent to hosts. No modification of existing stacks is required and end-to-end traffic is unchanged. - More than 90% of routers would not require modification. - Provides global load balancing. - Provides survivability of open sessions. - There is no MTU reduction. - Can be run on hardware available today. - Gradual migration, no "flag day". - IPv6 only protocol. - MHAP provides site multihoming. ISP multihoming is unchanged. MHAP Concepts: - Multihomed address space exists only at the edge. The end-to-end multihomed traffic is carried over aggregated PA address space in the core. - A site gets PA addresses from ISPs and multihomed provider-independent space from a registry. - The process of transforming multihomed traffic to PA and back is called aliasing and relies on the presence of rendezvous points and aggregators. - Rendezvous points and aggregators answer topology requests. They do not carry traffic. - There is a separation between the DFZ's routing table and the multihomed space routing tables. The entire multihomed space is represented by two aggregates in the DFZ's routing table. - The only multihomed traffic on backbones is topology requests and routing updates. - There are two types of multihomed addresses: o Centralized, portable, for large multinational organizations. o Geographical, portable only within a geographic area. - There is no centralized table for geographic addresses. - The routing table for centralized prefixes remains contained to rendezvous points. - No multihomed site receives full multihomed tables. All a multihomed site needs is the small DFZ's routing table. From fink@es.net Thu May 23 06:44:37 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NDibE15790 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 06:44:37 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NDibb21363 for <6bone@isi.edu>; Thu, 23 May 2002 06:44:37 -0700 (PDT) Received: from ([63.196.96.113]) by postal1.es.net (Postal Node 1) with SMTP id GQF37091; Thu, 23 May 2002 06:44:35 -0700 Message-Id: <5.1.0.14.0.20020523064231.02a89750@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 23 May 2002 06:43:30 -0700 To: 6BONE List <6bone@ISI.EDU> From: Bob Fink Cc: enric@satec.es (Enric Corominas), 6bone reverse DNS registration Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] 6bone pTLA 3FFE:400A::/32 allocated to SATEC Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: SATEC has been allocated pTLA 3FFE:400A::/32 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: [To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to hostmaster@ep.net.] Thanks, Bob From jorgen@hovland.cx Thu May 23 08:02:27 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NF2QE07543 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 08:02:27 -0700 (PDT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NF2Mb15685 for <6bone@ISI.EDU>; Thu, 23 May 2002 08:02:23 -0700 (PDT) Received: from hera (58.80-203-6.nextgentel.com [80.203.6.58]) by mail.broadpark.no (Postfix) with SMTP id B768C7D74; Thu, 23 May 2002 17:02:15 +0200 (MEST) Message-ID: <005701c2026a$d47b6240$0200000a@hera> From: =?iso-8859-1?Q?J=F8rgen_Hovland?= To: "Michel Py" , <6bone@ISI.EDU> References: <2B81403386729140A3A899A8B39B046406C75E@server2000.arneill-py.sacramento.ca.us> Subject: Re: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Date: Thu, 23 May 2002 17:02:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: I dont really think there is a problem. If everybody used ipv6 instead of ipv4 right now, we would probably have less prefixes than today. There are around 109327 ipv4 prefixes today, but only around 65000 as numbers. Im not sure really how big/the usage of a ipv6 /35 is if you compare it to a ipv4 /16. There are no lir's today with more than 1 real ipv6 prefix anyway? That would result in something like: number of asn's == number of prefixes wouldnt it? As you stated, the problem might begin with too many wanting a multihomed solution. Since becoming a LIR is not free (atleast not in europe/ripe), it would restrict itself. Small company's probably wont spend that ammount of money just to get a LIR membership. Its not worth it. Some enterprises do need multihoming: stockexchanges, banks etc. Only allowing isp's to be multihomed is crap. As long as the price for LIR membership is high enough, the problem is solved :-) I agree with the PI-address suggestion. They should drop it completely. Right now, I recieved an email from ripe. They are implementing a new global ipv6 policy. Im not familiar with it, but Im looking forward to read it. Maybe somebody knows whats it about? --------------- Dear Colleagues, We are pleased to announce that the RIPE NCC will implement the new Global IPv6 Policy on 1 July 2002. This policy has been agreed by the communities of all the Regional Internet Registries (RIRs). Before 1 July 2002 we will publish and announce the following as RIPE Documents: - Global IPv6 Policy Document - Initial IPv6 Allocation Request Form in the RIPE NCC Service Region - IPv6 End User Site Assignment Request Form in the RIPE NCC Service Region (for prefixes shorter than a /48) ------------------------------ Joergen Hovland WebOnline AS ----- Original Message ----- From: "Michel Py" To: <6bone@ISI.EDU> Sent: Thursday, May 23, 2002 5:45 AM Subject: [6bone] Roadmap to IPv6 multihoming: no PI addresses. > 6boner, > > My candid view on IPv6 multihoming, comments welcomed. > > Michel. > > +-----------------------------------------------+ > | Roadmap to IPv6 multihoming: no PI addresses. | > +-----------------------------------------------+ > > Assessment of the current IPv6 multihoming situation: > ----------------------------------------------------- > > - Regardless of the availability of multihoming protocols, independence > from the service provider is highly desired by multihomers. > - The pressure is increasing on RIRs to allocate PI blocks. > - RIRs have delayed PI allocation as it creates long-term known > problems. > - The current policies effectively prohibit multihoming for everyone but > ISPs (even RIRs themselves can not use PI addresses). > - It is clear at this time that PA addresses alone do not address > today's needs. > > The current roadmap to IPv6 multihoming is: > - Offer a short-term alternative that would prevent the deployment of PI > addresses: "geo for now". > - Finish developing a long-term, scalable solution: MHAP. > - ISP multihoming remains unchanged. > > > "geo for now" > ------------- > The idea is to create a low-ambition geographic aggregation model that > can be adopted using today's technology, requires no changes to physical > infrastructure and few changes to current operational practices. Current > work includes making geo for now and MHAP compatible to the migration > from the shorter-term geo for now to the longer-term MHAP smooth. > > Geo addresses are: > - Allocated depending on the location of the site. > - Allocated by RIRs or NIRs > - Locally portable. > - Globally unique. > - Aggregatable. > > Regardless of the actual aggregation ratio achieved, geo addresses are > always preferable to PI; PI addresses will never be aggregated, geo will > some day. > > Therefore, no IPv6 PI addresses must be ever used in any situation and > geo addresses must be used instead. > > In other words, PI addresses offers no hope of aggregation, geo > addresses do. The choice between PI and geo is a no-brainer: geo. > > > > MHAP > ---- > This is currently a working document of the ipv6mh mailing list. The > draft is relatively mature and an earlier form was submitted to the IETF > a year ago (it has evolved since then). MHAP is a full-blown mid to > long-term solution. > > > MHAP Features: > > - Zero impact on the DFZ's routing table. The DFZ's routing table stays > strongly aggregated. > - Provides multihomed, provider-independent, /48 address space for any > site. > - Very large organizations that require more can get a /47 or bigger. > - Scalable (4 billion multihomed sites, initial allocation). > - Addresses are aggregated at geographic areas boundaries. > - There is no need for Internet eXchanges at aggregation boundaries. > - MHAP is transparent to hosts. No modification of existing stacks is > required and end-to-end traffic is unchanged. > - More than 90% of routers would not require modification. > - Provides global load balancing. > - Provides survivability of open sessions. > - There is no MTU reduction. > - Can be run on hardware available today. > - Gradual migration, no "flag day". > - IPv6 only protocol. > - MHAP provides site multihoming. ISP multihoming is unchanged. > > > MHAP Concepts: > > - Multihomed address space exists only at the edge. The end-to-end > multihomed traffic is carried over aggregated PA address space in the > core. > - A site gets PA addresses from ISPs and multihomed provider-independent > space from a registry. > - The process of transforming multihomed traffic to PA and back is > called aliasing and relies on the presence of rendezvous points and > aggregators. > - Rendezvous points and aggregators answer topology requests. They do > not carry traffic. > - There is a separation between the DFZ's routing table and the > multihomed space routing tables. The entire multihomed space is > represented by two aggregates in the DFZ's routing table. > - The only multihomed traffic on backbones is topology requests and > routing updates. > - There are two types of multihomed addresses: > o Centralized, portable, for large multinational organizations. > o Geographical, portable only within a geographic area. > - There is no centralized table for geographic addresses. > - The routing table for centralized prefixes remains contained to > rendezvous points. > - No multihomed site receives full multihomed tables. All a multihomed > site needs is the small DFZ's routing table. > > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From michel@arneill-py.sacramento.ca.us Thu May 23 08:33:57 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NFXvE20688 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 08:33:57 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NFXub24914 for <6bone@ISI.EDU>; Thu, 23 May 2002 08:33:56 -0700 (PDT) Subject: RE: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Date: Thu, 23 May 2002 08:33:50 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <2B81403386729140A3A899A8B39B046405E095@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-TNEF-Correlator: Thread-Topic: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Thread-Index: AcICavJ9FRoPytWHSEi8ouKBfBFJIgAACGZA From: "Michel Py" To: =?iso-8859-1?Q?J=F8rgen_Hovland?= , <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4NFXvE20688 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Jørgen, > Jørgen Hovland wrote: > I dont really think there is a problem. If everybody used ipv6 instead > of ipv4 right now, we would probably have less prefixes than today. > There are around 109327 ipv4 prefixes today, but only around 65000 as > numbers. About ~12k ASNs are allocated today. > Im not sure really how big/the usage of a ipv6 /35 is if you compare > it to a ipv4 /16. There are no lir's today with more than 1 real ipv6 > prefix anyway? That would result in something like: number of asn's > == number of prefixes wouldnt it? We have made the same analysis, and it's close enough although a little optimistic (some will have both a 2001 prefix and a 3ffe); the issue here is that 64k ASNs are not going to last forever, see: http://search.ietf.org/internet-drafts/draft-ietf-idr-as4bytes-05.txt > Since becoming a LIR is not free (at least not in europe/ripe), it would > restrict itself. Small company's probably wont spend that ammount of > money just to get a LIR membership. Its not worth it. I have a problem with a system that favors the rich and the powerful. It is a legitimate demand for any size site to be multihomed, especially the small that uses cheesy technology. A large routing table favors big operators, because they are the only ones that can afford to buy the GSR or M160 that gets the job done. We can do better than this. > Right now, I recieved an email from ripe. They are implementing a new > global ipv6 policy. Im not familiar with it, but Im looking forward to > read it. Maybe somebody knows whats it about? ==> - IPv6 End User Site Assignment Request Form in the RIPE ==> NCC Service Region (for prefixes shorter than a /48) I have not seen this very form yet, regardless of its name this is the beginning of PI allocation. (Note that I support the new policy by lack of a better one). Michel. From Robert.Kiessling@de.easynet.net Thu May 23 09:18:36 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NGIaE12367 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 09:18:36 -0700 (PDT) Received: from smtp.de.easynet.net (smtp.de.easynet.net [194.24.208.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NGIZb15065 for <6bone@ISI.EDU>; Thu, 23 May 2002 09:18:35 -0700 (PDT) Received: from joseba.easynet.de (unknown [212.224.0.54]) by smtp.de.easynet.net (Postfix) with ESMTP id 0590611CD61; Thu, 23 May 2002 18:18:28 +0200 (CEST) To: "Michel Py" Cc: =?iso-8859-1?q?J=F8rgen?= Hovland , <6bone@ISI.EDU> Subject: Re: [6bone] Roadmap to IPv6 multihoming: no PI addresses. References: <2B81403386729140A3A899A8B39B046405E095@server2000.arneill-py.sacramento.ca.us> X-Ncc-RegID: de.easynet From: Robert Kiessling Date: 23 May 2002 17:28:41 +0000 In-Reply-To: <2B81403386729140A3A899A8B39B046405E095@server2000.arneill-py.sacramento.ca.us> Message-ID: Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: "Michel Py" writes: > ==> - IPv6 End User Site Assignment Request Form in the RIPE > ==> NCC Service Region (for prefixes shorter than a /48) > > I have not seen this very form yet, regardless of its name this is the beginning of PI allocation. Not at all. This is for very large sites for which an assignment of /48 is too small. It is still PA, without any signs of PI, apart from *possibly* the size of the netblock which *might* make it more likely to be accepted globally. But that is not under the RIRs' control. Robert From michel@arneill-py.sacramento.ca.us Thu May 23 13:10:40 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NKAcE24915 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 13:10:40 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NKAbb22393 for <6bone@ISI.EDU>; Thu, 23 May 2002 13:10:37 -0700 (PDT) Subject: RE: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Date: Thu, 23 May 2002 13:10:31 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <2B81403386729140A3A899A8B39B046405E097@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: content-class: urn:content-classes:message X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Topic: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Thread-Index: AcICdY8LH/9TyuD0Tp60EvtLBTvTqQAHDd2A From: "Michel Py" To: "Robert Kiessling" Cc: =?iso-8859-1?Q?J=F8rgen_Hovland?= , <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4NKAcE24915 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Robert, ==> - IPv6 End User Site Assignment Request Form in the RIPE ==> NCC Service Region (for prefixes shorter than a /48) > Robert Kiessling wrote: > Not at all. This is for very large sites for which an assignment of > /48 is too small. It is still PA, without any signs of PI, apart from > *possibly* the size of the netblock which *might* make it more likely > to be accepted globally. But that is not under the RIRs' control. Thanks for the precision. It would be interesting to follow up how many of these are allocated, as it makes little sense to me. If you need a /48, you have more than 64k subnets. It appears dangerous to me configuring a network that size with addresses that belongs to a LIR, even if you actually own the LIR. If my memory is correct, the feds forced WorldCom to sell CWnet a while ago, leaving some parts of MCI to renumber. Michel. From Robert.Kiessling@de.easynet.net Thu May 23 16:34:11 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NNYBE27897 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 16:34:11 -0700 (PDT) Received: from smtp.de.easynet.net (smtp.de.easynet.net [194.24.208.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NNYAb00680 for <6bone@ISI.EDU>; Thu, 23 May 2002 16:34:10 -0700 (PDT) Received: from joseba.easynet.de (unknown [212.224.0.54]) by smtp.de.easynet.net (Postfix) with ESMTP id A23B311CD61; Fri, 24 May 2002 01:34:04 +0200 (CEST) To: "Michel Py" Cc: <6bone@ISI.EDU> Subject: Re: [6bone] Roadmap to IPv6 multihoming: no PI addresses. References: <2B81403386729140A3A899A8B39B046405E097@server2000.arneill-py.sacramento.ca.us> X-Ncc-RegID: de.easynet From: Robert Kiessling Date: 24 May 2002 00:44:17 +0000 In-Reply-To: <2B81403386729140A3A899A8B39B046405E097@server2000.arneill-py.sacramento.ca.us> Message-ID: Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: "Michel Py" writes: > Thanks for the precision. It would be interesting to follow up how > many of these are allocated, as it makes little sense to me. Just look at the respective whois databases. > If you need a /48, you have more than 64k subnets. Right, if you make full use of them. But bear in mind that in IPv6 aggregation wins over conservation. A suitable hierarchy "wastes" a lot of address space. Thus the H ratio was chosen as a better approach to measure utilisation, taking into account aggregation and hierarchy, and in my understanding you wouldn't actually need 64k subnets to justify a larger assignment, but rather about 7k. > It appears dangerous to me configuring a network that size with > addresses that belongs to a LIR, even if you actually own the LIR. So you question the very principle of PA addresses. Well, I don't feel like arguing about that. Robert From nicolas.deffayet-extml@ndsoftwaregroup.com Thu May 23 16:56:16 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NNuFE07774 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 16:56:15 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NNuCb09659 for <6bone@isi.edu>; Thu, 23 May 2002 16:56:13 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17B2RC-000IvE-00 for 6bone@isi.edu; Fri, 24 May 2002 01:56:06 +0200 Received: (qmail 11974 invoked from network); 24 May 2002 00:09:23 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 24 May 2002 00:09:23 -0000 From: "Nicolas DEFFAYET" To: "Mailing-List 6bone" <6bone@ISI.EDU>, "Mailing-List Debian IPv6" , "Mailing-List IPv6 Users" , "Mailing-List USAGI" , "Mailing-List Zebra" Date: Fri, 24 May 2002 01:54:44 +0200 Organization: NDSoftware Group Message-ID: <005201c202b5$36be4310$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [6bone] IPv6 routing problem with zebra and kernel Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hello, First, sorry for cross-post but the problem is related to a lot of mailing-lists. I have a strange problem on one of my router: lacr1.us.ndsoftwarenet.net. I get "connect: Network is unreachable", when i try a traceroute or a connection from the router to a host on 6bone. The problem is random, because a destination www.kame.net can work but not www.6bone.net (for exemple) and after restart zebra www.6bone.net can work but not www.kame.net. Often, all destinations don't work. OS: Debian 3.0 (sid/unstable) with last update Kernel: 2.4.18 (i have try kernel 2.4.18 USAGI (last snapshot) and standard (from kernel.org) but same problem Zebra: 0.93 CVS (i have try 0.92a too but same problem) It's not the zebra configuration (zebra.conf, bgpd.conf), because all my routers have the same configuration. How i can fix this problem ? Any help are welcome. --- When a user, connected on router try traceroute: wireless:/etc/zebra# /usr/sbin/traceroute6 phenix.rootshell.be traceroute to phenix.rootshell.be (3ffe:8100:200:1fff::25) from 3ffe:81f1:3:2006::2, 30 hops max, 16 byte packets 1 tun6-0-lacr1.us.ndsoftwarenet.net (3ffe:81f1:3:2006::1) 118.109 ms !H 125.594 ms !H 119.42 ms !H wireless:/etc/zebra# --- When i try a traceroute from router: # traceroute6 www.6bone.net connect: Network is unreachable --- Kernel routing table, good route on the good interface: # route -A inet6 | grep 3ffe:b00::/24 3ffe:b00::/24 fe80::d55b:403 UG 1024 0 0 sit1 --- BGP is OK: lacr1.us.ndsoftwarenet.net> show ipv6 bgp 3ffe:b00::/24 BGP routing table entry for 3ffe:b00::/24 Paths: (2 available, best #1, table Default-IP-Routing-Table) Advertised to non peer-group peers: 3ffe:81f1:3:1000::2 10566 3ffe:81f1:1:2054::1 from 3ffe:81f1:1:2054::1 (213.91.4.3) (fe80::d55b:403) Origin incomplete, localpref 100, valid, internal, best Last update: Thu May 23 06:04:22 2002 2042 10566 3ffe:81f1:3:2004::2 from 3ffe:81f1:3:2004::2 (202.187.22.65) (fe80::cabb:1602) Origin incomplete, localpref 100, valid, external Last update: Thu May 23 06:04:20 2002 lacr1.us.ndsoftwarenet.net> --- Zebra routing table is OK: lacr1.us.ndsoftwarenet.net> show ipv6 route 3ffe:b00::/24 Routing entry for 3ffe:b00::/24 Known via "bgp", distance 200, metric 0, best Last update 00:06:35 ago * fe80::d55b:403, via sit1 lacr1.us.ndsoftwarenet.net> --- Zebra compiled with --enable-netlink zebra.log: 2002/05/23 06:06:26 ZEBRA: netlink-listen error: File exists, type=RTM_NEWROUTE(24), seq=742, pid=0 2002/05/23 06:06:26 ZEBRA: netlink-listen error: File exists, type=RTM_NEWROUTE(24), seq=743, pid=0 2002/05/23 06:14:20 ZEBRA: netlink_talk: ignoring message type 0x0019 2002/05/23 06:14:20 ZEBRA: netlink_talk: ignoring message type 0x0019 --- Zebra compiled with --disable-netlink zebra.log: 2002/05/23 06:15:13 ZEBRA: can't delete ipv6 route: No such process 2002/05/23 06:15:13 ZEBRA: can't delete ipv6 route: No such process 2002/05/23 06:15:13 ZEBRA: can't add ipv6 route: File exists 2002/05/23 06:15:13 ZEBRA: can't add ipv6 route: File exists --- Best Regards, Nicolas DEFFAYET From michel@arneill-py.sacramento.ca.us Thu May 23 16:56:43 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4NNugE07997 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 16:56:42 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4NNufb09676 for <6bone@ISI.EDU>; Thu, 23 May 2002 16:56:41 -0700 (PDT) Subject: RE: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Date: Thu, 23 May 2002 16:56:35 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <2B81403386729140A3A899A8B39B046405E09A@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: content-class: urn:content-classes:message X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Topic: [6bone] Roadmap to IPv6 multihoming: no PI addresses. Thread-Index: AcICsmj7VwkP9IzJQaCmldprFCbjAAAAPemA From: "Michel Py" To: "Robert Kiessling" Cc: <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4NNugE07997 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Robert, >> If you need a /48, you have more than 64k subnets. > Robert Kiessling wrote: > Right, if you make full use of them. But bear in mind that in > IPv6 aggregation wins over conservation. A suitable hierarchy > "wastes" a lot of address space. Thus the H ratio was chosen as a > better approach to measure utilisation, taking into account > aggregation and hierarchy, and in my understanding you wouldn't > actually need 64k subnets to justify a larger assignment, but > rather about 7k. Agree. For 65k actual subnets, we are talking about a /45 or so. >> It appears dangerous to me configuring a network that size with >> addresses that belongs to a LIR, even if you actually own the LIR. > So you question the very principle of PA addresses. You misunderstand me, I don't. It is one of the necessary building blocks. I question the business sense and timing of building today a 7k+ subnets network in the lack of a multihoming solution and by getting married to a provider. Michel. From Marc.Blanchet@viagenie.qc.ca Fri May 24 02:42:20 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4O9gKE14523 for <6bone@mailman.isi.edu>; Fri, 24 May 2002 02:42:20 -0700 (PDT) Received: from jazz.viagenie.qc.ca (jazz.viagenie.qc.ca [206.123.31.2]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4O9gJb17006 for <6bone@ISI.EDU>; Fri, 24 May 2002 02:42:19 -0700 (PDT) Received: from [192.168.31.8] (modemcable071.132-130-66.que.mc.videotron.ca [66.130.132.71]) by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id g4O9gG866492; Fri, 24 May 2002 05:42:18 -0400 (EDT) Date: Fri, 24 May 2002 05:41:31 -0400 From: Marc Blanchet To: Nicolas DEFFAYET , Mailing-List 6bone <6bone@ISI.EDU>, Mailing-List Debian IPv6 , Mailing-List IPv6 Users , Mailing-List USAGI , Mailing-List Zebra Message-ID: <153180000.1022233291@classic.viagenie.qc.ca> In-Reply-To: <005201c202b5$36be4310$0103010a@lnet.fr.ndsoftwaregroup.com> References: <005201c202b5$36be4310$0103010a@lnet.fr.ndsoftwaregroup.com> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g4O9gKE14523 Subject: [6bone] Re: IPv6 routing problem with zebra and kernel Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: just guessing: - might be just a problem of connexion time. - I would try traceroute -w with some higher number than the default and see if it is still the same issue. might be not the problem. Marc. -- vendredi, mai 24, 2002 01:54:44 +0200 Nicolas DEFFAYET wrote/a écrit: > Hello, > > First, sorry for cross-post but the problem is related to a lot of > mailing-lists. > > I have a strange problem on one of my router: > lacr1.us.ndsoftwarenet.net. > > I get "connect: Network is unreachable", when i try a traceroute or a > connection from the router to a host on 6bone. > The problem is random, because a destination www.kame.net can work but > not www.6bone.net (for exemple) and after restart zebra www.6bone.net > can work but not www.kame.net. Often, all destinations don't work. > > OS: Debian 3.0 (sid/unstable) with last update > Kernel: 2.4.18 (i have try kernel 2.4.18 USAGI (last snapshot) and > standard (from kernel.org) but same problem > Zebra: 0.93 CVS (i have try 0.92a too but same problem) > > It's not the zebra configuration (zebra.conf, bgpd.conf), because all my > routers have the same configuration. > > How i can fix this problem ? > > Any help are welcome. > > --- > > When a user, connected on router try traceroute: > > wireless:/etc/zebra# /usr/sbin/traceroute6 phenix.rootshell.be > traceroute to phenix.rootshell.be (3ffe:8100:200:1fff::25) from > 3ffe:81f1:3:2006::2, 30 hops max, 16 byte packets > 1 tun6-0-lacr1.us.ndsoftwarenet.net (3ffe:81f1:3:2006::1) 118.109 ms > !H 125.594 ms !H 119.42 ms !H > wireless:/etc/zebra# > > --- > > When i try a traceroute from router: > ># traceroute6 www.6bone.net > connect: Network is unreachable > > --- > > Kernel routing table, good route on the good interface: > ># route -A inet6 | grep 3ffe:b00::/24 > 3ffe:b00::/24 fe80::d55b:403 > UG 1024 0 0 sit1 > > --- > > BGP is OK: > > lacr1.us.ndsoftwarenet.net> show ipv6 bgp 3ffe:b00::/24 > BGP routing table entry for 3ffe:b00::/24 > Paths: (2 available, best #1, table Default-IP-Routing-Table) > Advertised to non peer-group peers: > 3ffe:81f1:3:1000::2 > 10566 > 3ffe:81f1:1:2054::1 from 3ffe:81f1:1:2054::1 (213.91.4.3) > (fe80::d55b:403) > Origin incomplete, localpref 100, valid, internal, best > Last update: Thu May 23 06:04:22 2002 > > 2042 10566 > 3ffe:81f1:3:2004::2 from 3ffe:81f1:3:2004::2 (202.187.22.65) > (fe80::cabb:1602) > Origin incomplete, localpref 100, valid, external > Last update: Thu May 23 06:04:20 2002 > > lacr1.us.ndsoftwarenet.net> > > --- > > Zebra routing table is OK: > > lacr1.us.ndsoftwarenet.net> show ipv6 route 3ffe:b00::/24 > Routing entry for 3ffe:b00::/24 > Known via "bgp", distance 200, metric 0, best > Last update 00:06:35 ago > * fe80::d55b:403, via sit1 > > lacr1.us.ndsoftwarenet.net> > > --- > > Zebra compiled with --enable-netlink > > zebra.log: > 2002/05/23 06:06:26 ZEBRA: netlink-listen error: File exists, > type=RTM_NEWROUTE(24), seq=742, pid=0 > 2002/05/23 06:06:26 ZEBRA: netlink-listen error: File exists, > type=RTM_NEWROUTE(24), seq=743, pid=0 > 2002/05/23 06:14:20 ZEBRA: netlink_talk: ignoring message type 0x0019 > 2002/05/23 06:14:20 ZEBRA: netlink_talk: ignoring message type 0x0019 > > --- > > Zebra compiled with --disable-netlink > > zebra.log: > 2002/05/23 06:15:13 ZEBRA: can't delete ipv6 route: No such process > 2002/05/23 06:15:13 ZEBRA: can't delete ipv6 route: No such process > 2002/05/23 06:15:13 ZEBRA: can't add ipv6 route: File exists > 2002/05/23 06:15:13 ZEBRA: can't add ipv6 route: File exists > > --- > > Best Regards, > > Nicolas DEFFAYET > > --------------------------------------------------------------------- > The IPv6 Users Mailing List > Unsubscribe by sending "unsubscribe users" to majordomo@ipv6.org > ------------------------------------------ Marc Blanchet Viagénie tel: +1-418-656-9254x225 ------------------------------------------ http://www.freenet6.net: IPv6 connectivity ------------------------------------------ http://www.normos.org: IETF(RFC,draft), IANA,W3C,... standards. ------------------------------------------ From nicolas.deffayet-extml@ndsoftwaregroup.com Fri May 24 04:00:08 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4OB08E03215 for <6bone@mailman.isi.edu>; Fri, 24 May 2002 04:00:08 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4OB05b06051 for <6bone@isi.edu>; Fri, 24 May 2002 04:00:07 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17BCnj-000Pao-00 for 6bone@isi.edu; Fri, 24 May 2002 13:00:03 +0200 Received: (qmail 25431 invoked from network); 24 May 2002 11:13:26 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 24 May 2002 11:13:26 -0000 From: "Nicolas DEFFAYET" To: "'Fabio Massimo Di Nitto'" Cc: "'Mailing-List 6bone'" <6bone@ISI.EDU>, "'Mailing-List Debian IPv6'" , "'Mailing-List IPv6 Users'" , "'Mailing-List USAGI'" , "'Mailing-List Zebra'" Date: Fri, 24 May 2002 12:58:38 +0200 Organization: NDSoftware Group Message-ID: <002801c20311$f661d810$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <3CEDBC7F.8070706@fabbione.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [6bone] RE: IPv6 routing problem with zebra and kernel Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: Fabio Massimo Di Nitto [mailto:fabbione@fabbione.net] > Sent: Friday, May 24, 2002 6:07 AM > To: Nicolas DEFFAYET > Cc: Mailing-List 6bone; Mailing-List Debian IPv6; > Mailing-List IPv6 Users; Mailing-List USAGI; Mailing-List Zebra > Subject: Re: IPv6 routing problem with zebra and kernel > Hi Fabio, > Nicolas DEFFAYET wrote: > > > > >Zebra compiled with --enable-netlink > > > Did you enable the netlink emulation in the kernel as well???? Same problem with or without netlink_dev. I reboot the machine and recompile zebra with and without netlink options after each change... > > A similar problem was discussed in one of the debian ml and > it seems that having netlink enable fix the problem but it > needs to be done both in the kernel and in zebra. Don't find this discussion on google. What's the list for i can search in the archive ? Best Regards, Nicolas DEFFAYET From nicolas.deffayet-extml@ndsoftwaregroup.com Fri May 24 04:17:02 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4OBH1E06953 for <6bone@mailman.isi.edu>; Fri, 24 May 2002 04:17:01 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4OBGxb12273 for <6bone@ISI.EDU>; Fri, 24 May 2002 04:17:00 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17BD46-000Pid-00 for 6bone@ISI.EDU; Fri, 24 May 2002 13:16:58 +0200 Received: (qmail 27434 invoked from network); 24 May 2002 11:30:12 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 24 May 2002 11:30:12 -0000 From: "Nicolas DEFFAYET" To: "'Roger Jorgensen'" Cc: "'Mailing-List 6bone'" <6bone@ISI.EDU>, "'Mailing-List Debian IPv6'" , "'Mailing-List IPv6 Users'" , "'Mailing-List USAGI'" , "'Mailing-List Zebra'" Subject: RE: [6bone] IPv6 routing problem with zebra and kernel Date: Fri, 24 May 2002 13:15:26 +0200 Organization: NDSoftware Group Message-ID: <002b01c20314$4e65aa30$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <5.1.0.14.0.20020524092750.038d7c40@213.46.233.213> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: Roger Jorgensen [mailto:rjorgensen@upctechnology.com] > Sent: Friday, May 24, 2002 9:29 AM > To: Nicolas DEFFAYET > Subject: Re: [6bone] IPv6 routing problem with zebra and kernel > > > How does your routing table look like (ip -6 ro with > iproute2) ? Is the via address right? > > A destination who work: # traceroute6 www.ipv6.chello.com traceroute to future.ipv6.chello.com (2001:730:0:1:a00:20ff:fec1:b1f0) from 3ffe:81f1:1:2054::2, 30 hops max, 16 byte packets 1 tun54-0-parcr1.fr.ndsoftwarenet.net (3ffe:81f1:1:2054::1) 200.536 ms 174.857 ms 164.169 ms 2 chello-gw-parcr1.fr.ndsoftwarenet.net (3ffe:81f1:1:2022::2) 196.507 ms 202.46 ms 192.882 ms 3 future.ipv6.chello.com (2001:730:0:1:a00:20ff:fec1:b1f0) 193.6 ms 194.294 ms 193.905 ms # ip -6 ro | grep 2001:730 2001:730::/35 via fe80::d55b:403 dev sit1 metric 1024 mtu 1480 advmss 1420 --- A destination who don't work: # traceroute6 www.ipv6.uni-muenster.de connect: Network is unreachable # ip -6 ro | grep 3ffe:400 unreachable 3ffe:400::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 Best Regards, Nicolas DEFFAYET From ali@ali.dnsalias.com Fri May 24 06:12:17 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4ODCHE04820 for <6bone@mailman.isi.edu>; Fri, 24 May 2002 06:12:17 -0700 (PDT) Received: from ali.dnsalias.com (pD9E68BFE.dip.t-dialin.net [217.230.139.254]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4ODCFb14067 for <6bone@ISI.EDU>; Fri, 24 May 2002 06:12:15 -0700 (PDT) Received: (from ali@localhost) by ali.dnsalias.com (8.11.0/8.11.0/ HP-NEW-NET 4.11 8.11.0-0.4) id g4ODCCA02662; Fri, 24 May 2002 15:12:12 +0200 Date: Fri, 24 May 2002 15:12:12 +0200 From: ali@ali.dnsalias.com Message-Id: <200205241312.g4ODCCA02662@ali.dnsalias.com> To: 6bone@ISI.EDU X-Mailer: WEBEMAIL 1.31 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------768076484109871907011644" Subject: [6bone] (no subject) Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: This is a MIME-encapsulated message. --------------768076484109871907011644 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit which ali@ali.dnsalias.com --------------768076484109871907011644-- From fabbione@fabbione.net Thu May 23 21:07:59 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4O47wE20973 for <6bone@mailman.isi.edu>; Thu, 23 May 2002 21:07:59 -0700 (PDT) Received: from trider-g7.fabbione.net (port5.ds1-sby.adsl.cybercity.dk [212.242.169.198]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4O47ub02293 for <6bone@isi.edu>; Thu, 23 May 2002 21:07:57 -0700 (PDT) Received: from diapolon.int.fabbione.net ([192.168.1.3] helo=fabbione.net) by trider-g7.fabbione.net with esmtp (Exim 3.35 #1 (Debian)) id 17B6MR-0003V9-00; Fri, 24 May 2002 06:07:27 +0200 Message-ID: <3CEDBC7F.8070706@fabbione.net> Date: Fri, 24 May 2002 06:07:27 +0200 From: Fabio Massimo Di Nitto User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020520 Debian/1.0rc2-3 X-Accept-Language: en MIME-Version: 1.0 To: Nicolas DEFFAYET CC: Mailing-List 6bone <6bone@ISI.EDU>, Mailing-List Debian IPv6 , Mailing-List IPv6 Users , Mailing-List USAGI , Mailing-List Zebra References: <005201c202b5$36be4310$0103010a@lnet.fr.ndsoftwaregroup.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [6bone] Re: IPv6 routing problem with zebra and kernel Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi Nicolas Nicolas DEFFAYET wrote: > >Zebra compiled with --enable-netlink > Did you enable the netlink emulation in the kernel as well???? A similar problem was discussed in one of the debian ml and it seems that having netlink enable fix the problem but it needs to be done both in the kernel and in zebra. Fabio From fabbione@fabbione.net Fri May 24 05:20:10 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4OCKAE21077 for <6bone@mailman.isi.edu>; Fri, 24 May 2002 05:20:10 -0700 (PDT) Received: from trider-g7.fabbione.net (port5.ds1-sby.adsl.cybercity.dk [212.242.169.198]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4OCK8b29203 for <6bone@isi.edu>; Fri, 24 May 2002 05:20:09 -0700 (PDT) Received: from diapolon.int.fabbione.net ([192.168.1.3] helo=fabbione.net) by trider-g7.fabbione.net with esmtp (Exim 3.35 #1 (Debian)) id 17BYeM-0000Mt-00; Sat, 25 May 2002 12:19:50 +0200 Message-ID: <3CEE2FE6.5060901@fabbione.net> Date: Fri, 24 May 2002 14:19:50 +0200 From: Fabio Massimo Di Nitto User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020520 Debian/1.0rc2-3 X-Accept-Language: en MIME-Version: 1.0 To: zebra@zebra.org CC: "'Mailing-List 6bone'" <6bone@ISI.EDU>, "'Mailing-List Debian IPv6'" , "'Mailing-List IPv6 Users'" , "'Mailing-List USAGI'" References: <002801c20311$f661d810$0103010a@lnet.fr.ndsoftwaregroup.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [6bone] Re: [zebra 13790] RE: IPv6 routing problem with zebra and kernel Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Nicolas DEFFAYET wrote: >Hi Fabio, > > >Don't find this discussion on google. >What's the list for i can search in the archive ? > > > As far as I remember was on debian-ipv6 or debian-devel. Regards Fabio From elisaudo@telegoias.com.br Tue May 28 18:33:52 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4T1XpE18030 for <6bone@mailman.isi.edu>; Tue, 28 May 2002 18:33:52 -0700 (PDT) Received: from goexchange.telegoias.com.br ([200.199.229.14]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4T1Xob11656 for <6bone@isi.edu>; Tue, 28 May 2002 18:33:50 -0700 (PDT) Received: from goexchange.telegoias.com.br ([10.62.16.28]) by goexchange.telegoias.com.br with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 28 May 2002 22:34:37 -0300 Received: by GOEXCHANGE.telegoias.com.br with Internet Mail Service (5.5.2653.19) id <20235H3C>; Tue, 28 May 2002 22:25:25 -0300 Message-ID: <976F547C242D554A82920C6606ACB2240185BBC2@GOEXCHANGE.telegoias.com.br> From: Elisaudo Sousa de Jesus To: "'6bone@ISI.EDU'" <6bone@ISI.EDU> Date: Tue, 28 May 2002 22:25:23 -0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [6bone] thesis about active network over ipv6 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, I'm writing a thesis about active network over ipv6. I found your e-mail on the internet. Could you give me some hints about papers, sites or books that i can find good information of these subject. Thanks very much! Elisaudo Sousa de Jesus elisaudo@telegoias.com.br From nicolas.deffayet-extml@ndsoftwaregroup.com Wed May 29 09:29:13 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4TGTCE18926 for <6bone@mailman.isi.edu>; Wed, 29 May 2002 09:29:12 -0700 (PDT) Received: from mail2.ndsoftware.net (ns3.ndsoftware.net [62.4.22.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4TGT9b15315 for <6bone@ISI.EDU>; Wed, 29 May 2002 09:29:11 -0700 (PDT) Received: from eth0-0-parnat1.fr.ndsoftware.net ([62.4.22.213] helo=mail.lnet.fr.ndsoftwaregroup.com) by mail2.ndsoftware.net with esmtp (Exim 4.01) id 17D6Jt-0009Gl-00 for 6bone@ISI.EDU; Wed, 29 May 2002 18:29:05 +0200 Received: (qmail 8633 invoked from network); 29 May 2002 16:43:22 -0000 Received: from wks1.lnet.fr.ndsoftwaregroup.com (HELO wks1) (10.1.3.1) by mail.localnet.ndsoftware.net with RC4-MD5 encrypted SMTP; 29 May 2002 16:43:22 -0000 From: "Nicolas DEFFAYET" To: "'Elisaudo Sousa de Jesus'" , <6bone@ISI.EDU> Subject: RE: [6bone] thesis about active network over ipv6 Date: Wed, 29 May 2002 18:28:50 +0200 Organization: NDSoftware Group Message-ID: <020801c2072d$eab3f460$0103010a@lnet.fr.ndsoftwaregroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <976F547C242D554A82920C6606ACB2240185BBC2@GOEXCHANGE.telegoias.com.br> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Elisaudo > Sousa de Jesus > Sent: Wednesday, May 29, 2002 3:25 AM > To: '6bone@ISI.EDU' > Subject: [6bone] thesis about active network over ipv6 > Hi, > I'm writing a thesis about active network over ipv6. I found > your e-mail on the internet. It's a mailing-list. > > Could you give me some hints about papers, sites or books > that i can find good information of these subject. > Have you try to search on this sites ? http://www.6bone.net http://www.hs247.com http://dmoz.org/Computers/Internet/Protocols/IP/IPng/ Best Regards, Nicolas DEFFAYET From ck@ns1.arch.bellsouth.net Wed May 29 09:45:51 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4TGjoE27298 for <6bone@mailman.isi.edu>; Wed, 29 May 2002 09:45:50 -0700 (PDT) Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4TGjob25291 for <6bone@ISI.EDU>; Wed, 29 May 2002 09:45:50 -0700 (PDT) Received: (from ck@localhost) by ns1.arch.bellsouth.net (goaway/goaway) id g4TGjsp13160; Wed, 29 May 2002 12:45:54 -0400 (EDT) Date: Wed, 29 May 2002 12:45:54 -0400 From: Christian Kuhtz To: Elisaudo Sousa de Jesus Cc: "'6bone@ISI.EDU'" <6bone@ISI.EDU> Subject: Re: [6bone] thesis about active network over ipv6 Message-ID: <20020529124554.D10249@ns1.arch.bellsouth.net> References: <976F547C242D554A82920C6606ACB2240185BBC2@GOEXCHANGE.telegoias.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <976F547C242D554A82920C6606ACB2240185BBC2@GOEXCHANGE.telegoias.com.br>; from Elisaudo Sousa de Jesus on Tue, May 28, 2002 at 10:25:23PM -0300 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: active network? care to explain what _exactly_ you mean by that? marketeers with their marketecture slides have screwed that word up quite nicely. On Tue, May 28, 2002 at 10:25:23PM -0300, Elisaudo Sousa de Jesus wrote: > Hi, > > I'm writing a thesis about active network over ipv6. I found your e-mail on > the internet. > > Could you give me some hints about papers, sites or books that i can find > good information of these subject. > > Thanks very much! > > Elisaudo Sousa de Jesus > elisaudo@telegoias.com.br > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone From dax@infres.enst.fr Wed May 29 10:13:32 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4THDWE10648 for <6bone@mailman.isi.edu>; Wed, 29 May 2002 10:13:32 -0700 (PDT) Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g4THDVb11629 for <6bone@ISI.EDU>; Wed, 29 May 2002 10:13:31 -0700 (PDT) Received: from horla.enst.fr (horla.enst.fr [137.194.161.1]) by infres.enst.fr (Postfix) with ESMTP id 3410F18AA; Wed, 29 May 2002 19:13:24 +0200 (MEST) Received: (from dax@localhost) by horla.enst.fr (8.10.2+Sun/8.10.2) id g4THDOl04787; Wed, 29 May 2002 19:13:24 +0200 (MEST) Date: Wed, 29 May 2002 19:13:24 +0200 From: Philippe Dax To: Christian Kuhtz Cc: Elisaudo Sousa de Jesus , "'6bone@ISI.EDU'" <6bone@ISI.EDU> Subject: Re: [6bone] thesis about active network over ipv6 Message-ID: <20020529171324.GA4589@horla.enst.fr> References: <976F547C242D554A82920C6606ACB2240185BBC2@GOEXCHANGE.telegoias.com.br> <20020529124554.D10249@ns1.arch.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020529124554.D10249@ns1.arch.bellsouth.net> User-Agent: Mutt/1.3.25i X-Organization: ENST X-WWW: http://www.infres.enst.fr/~dax/ X-Whois: whois -h whois.ripe.net PD97 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On 29/05, Christian Kuhtz wrote: | | active network? care to explain what _exactly_ you mean by that? | | marketeers with their marketecture slides have screwed that word up | quite nicely. From: http://nms.lcs.mit.edu/darpa-activenet/mission.html What is an active network? Active networks allow individual user, or groups of users, to inject customized programs into the nodes of the network. "Active" architectures enable a massive increase in the complexity and customization of the computation that is performed within the network, e.g., that is interposed between the communicating end points. See http://nms.lcs.mit.edu/darpa-activenet/ and http://ww.isi.edu/abone/ Philippe Dax -- | On Tue, May 28, 2002 at 10:25:23PM -0300, Elisaudo Sousa de Jesus wrote: | > Hi, | > | > I'm writing a thesis about active network over ipv6. I found your e-mail on | > the internet. | > | > Could you give me some hints about papers, sites or books that i can find | > good information of these subject. | > | > Thanks very much! | > | > Elisaudo Sousa de Jesus | > elisaudo@telegoias.com.br | > _______________________________________________ | > 6bone mailing list | > 6bone@mailman.isi.edu | > http://mailman.isi.edu/mailman/listinfo/6bone | _______________________________________________ | 6bone mailing list | 6bone@mailman.isi.edu | http://mailman.isi.edu/mailman/listinfo/6bone From fink@es.net Mon Jun 3 20:36:26 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g543aPE26631 for <6bone@mailman.isi.edu>; Mon, 3 Jun 2002 20:36:25 -0700 (PDT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g543aOb26901 for <6bone@isi.edu>; Mon, 3 Jun 2002 20:36:25 -0700 (PDT) Received: from ([63.196.96.113]) by postal3.es.net (Postal Node 3) with SMTP id GQF37091; Mon, 03 Jun 2002 20:36:14 -0700 Message-Id: <5.1.0.14.0.20020603203034.025ce748@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 03 Jun 2002 20:36:01 -0700 To: 6BONE List <6bone@ISI.EDU> From: Bob Fink Cc: Sanan Kurkulsatsanakit Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] pTLA request INET-TH - review closes 17 June 2002 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: 6bone Folk, INET-TH has requested a pTLA allocation and I find their request fully compliant with RFC2772. The open review period for this will close 17 June 2002. Please send your comments to me or the list. Thanks, Bob === >Date: Mon, 3 Jun 2002 09:11:28 +0700 (GMT+0700) >From: Sanan Kurkulsatsanakit >To: >cc: >Subject: pTLA prefix request > >Hi Bob, > >This is a pTLA prefix request from Internet Thailand Public Company >Limited. Please review and notify us for any update. > >Many thanks, >Sanan > > >================================================================================ > 1. The pTLA Applicant must have a minimum of three (3) months > qualifying experience as a 6Bone end-site or pNLA transit. During > the entire qualifying period the Applicant must be operationally > providing the following: > > a. Fully maintained, up to date, 6Bone Registry entries for their > ipv6-site inet6num, mntner, and person objects, including each > tunnel that the Applicant has. >-------------------------------------------------------------------------------- >We have 3 delegated 6bone prefix (/48) as following: >- 3FFE:B80:61F::/48 from FREENET6 >- 3FFE:B00:4050::/48 from VIAGENIE >- 3FFE:2900:1101::/48 from SPRINT > ><<< ipv6-site >>> >% RIPEdb(3.0.0b2) with ISI RPSL extensions > >ipv6-site: INET-TH >origin: AS4618 >descr: Internet Thailand Public Company Limited >country: TH >prefix: 3FFE:B80:61F::/48 >prefix: 3FFE:B00:4050::/48 >prefix: 3FFE:2900:1101::/48 >application: ping ipv6-gw66.inet.co.th >tunnel: IPv6 in IPv4 ipv6-gw66.inet.co.th -> www.freenet6.net >VIAGENIE STATIC >tunnel: IPv6 in IPv4 ipv6-gw66.inet.co.th -> rap.viagenie.qc.ca >VIAGENIE BGP4+ >tunnel: IPv6 in IPv4 ipv6-gw66.inet.co.th -> >sl-bb1v6-sj.sprintlink.net SPRINT BGP4+ >contact: BS5-6BONE >contact: INOC1-6BONE >remarks: ipv6-site is operational since 20011225 >mnt-by: MNT-INET >changed: snakk@inet.co.th 20011227 >changed: snakk@inet.co.th 20011229 >changed: snakk@inet.co.th 20020117 >changed: snakk@inet.co.th 20020129 >source: 6BONE > ><<< inet6num >>> >inet6num: 3FFE:B80:61F::/48 >netname: INET-TH >descr: Internet Thailand Public Company Limited >country: TH >admin-c: BS5-6BONE >tech-c: INOC1-6BONE >notify: noc@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20011225 >changed: snakk@inet.co.th 20011227 >source: 6BONE > >inet6num: 3FFE:B00:4050::/48 >netname: INET-TH >descr: Internet Thailand Public Company Limited >country: TH >admin-c: BS5-6BONE >tech-c: INOC1-6BONE >notify: ipv6@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20020529 >source: 6BONE > >inet6num: 3FFE:2900:1101::/48 >netname: INET-TH >descr: Internet Thailand Public Company Limited >country: TH >admin-c: BS5-6BONE >tech-c: INOC1-6BONE >notify: ipv6@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20020529 >source: 6BONE > > ><<< mntner >>> >% RIPEdb(3.0.0b2) with ISI RPSL extensions > >mntner: MNT-INET >descr: Maintainer of INET-TH 6bone objects >admin-c: BS16-AP >tech-c: CN2-TH >tech-c: SK13-AP >tech-c: SK26-TH >upd-to: noc@inet.co.th >auth: CRYPT-PW * >auth: CRYPT-PW * >remarks: This object is automatically converted from the RIPE181 >registry >mnt-by: MNT-INET >changed: snakk@inet.co.th 20010107 >changed: snakk@inet.co.th 20010108 >changed: auto-dbm@whois.6bone.net 20010117 >source: 6BONE > ><<< person >>> >% RIPEdb(3.0.0b2) with ISI RPSL extensions > >role: INET-TH Network Operation Center >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12 Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2640-0456 >e-mail: noc@inet.co.th >admin-c: BS5-6BONE >tech-c: SK2-6BONE >nic-hdl: INOC1-6BONE >remarks: This object is automatically converted from the RIPE181 >registry >notify: noc@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20010108 >changed: auto-dbm@whois.6bone.net 20010117 >changed: snakk@inet.co.th 20011225 >source: 6BONE > >person: Buncha Srisamanuwat >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12 Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2640-0456 >e-mail: athicha@inet.co.th >nic-hdl: BS5-6BONE >remarks: This object is automatically converted from the RIPE181 >registry >notify: athicha@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20010108 >changed: auto-dbm@whois.6bone.net 20010117 >changed: snakk@inet.co.th 20011225 >source: 6BONE > >person: Sanan Kurkulsatsanakit >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12 Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2640-0456 >e-mail: snakk@inet.co.th >nic-hdl: SK2-6BONE >remarks: This object is automatically converted from the RIPE181 >registry >notify: snakk@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20010108 >changed: auto-dbm@whois.6bone.net 20010117 >changed: snakk@inet.co.th 20011225 >source: 6BONE > >person: Chakrit Noisuwan >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12 Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2640-0456 >e-mail: chakrit@inet.co.th >nic-hdl: CN2-6BONE >notify: chakrit@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20011225 >changed: snakk@inet.co.th 20011225 >source: 6BONE > >person: Nattapong Jatupongpairoj >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12th Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2257-7275 >e-mail: jnatta@inet.co.th >nic-hdl: NJ2-6BONE >notify: jnatta@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20020521 >source: 6BONE > >person: Prasong Sakulwongwattana >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12th Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2257-7275 >e-mail: psongs@inet.co.th >nic-hdl: PS9-6BONE >notify: psongs@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20020521 >source: 6BONE > >person: Karaked Kedchumpol >address: Internet Thailand Public Company Limited >address: 108 Bangkok Thai Tower Bldg., 12th Fl., >address: Rangnam Rd., Rajdhevee, >address: Bangkok 10400, Thailand >phone: +66-2640-0345 >fax-no: +66-2257-7275 >e-mail: karaked@inet.co.th >nic-hdl: KK13-6BONE >notify: karaked@inet.co.th >mnt-by: MNT-INET >changed: snakk@inet.co.th 20020521 >source: 6BONE > >-------------------------------------------------------------------------------- > b. Fully maintained, and reliable, BGP4+ peering and connectivity > between the Applicant's boundary router and the appropriate > connection point into the 6Bone. This router must be IPv6 > pingable. This criteria is judged by members of the 6Bone > Operations Group at the time of the Applicant's pTLA request. >-------------------------------------------------------------------------------- >We have 2 BGP perring with SPRINT and VIAGENIE > >IPv6-Router#show ipv6 interface brief >Ethernet0 [up/up] > 3FFE:2900:1101:0:2B0:64FF:FEFC:E2E1 >Loopback0 [up/up] > unassigned >Tunnel11 [up/up] <--- SPRINT > 3FFE:2900:1100:1::2 >Tunnel99 [up/up] <--- VIAGENIE > 3FFE:B00:C18::99 > >IPv6-Router#show ip interface brief >Interface IP-Address OK? Method Status >Prot >ocol >Ethernet0 203.150.14.66 YES NVRAM up >up > >Loopback0 203.150.16.66 YES NVRAM up >up > >Tunnel11 unassigned YES NVRAM up >up <--- SPRINT > >Tunnel99 unassigned YES NVRAM up >up <--- VIAGENIE > >IPv6-Router#show bgp ipv6 summary >BGP router identifier 203.150.16.66, local AS number 4618 >BGP table version is 265470, main routing table version 265470 >225 network entries and 427 paths using 58061 bytes of memory >359 BGP path attribute entries using 21540 bytes of memory >348 BGP AS-PATH entries using 9812 bytes of memory >9 BGP community entries using 216 bytes of memory >0 BGP route-map cache entries using 0 bytes of memory >180 BGP filter-list cache entries using 2160 bytes of memory >213 received paths for inbound soft reconfiguration >BGP activity 56658/276904 prefixes, 219207/218780 paths, scan interval 15 >secs > >Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down >State/PfxRcd >3FFE:B00:C18::98 > 4 10566 746846 346002 265470 0 0 13:33:53 >0 <--- VIAGENIE >3FFE:2900:1100:1::1 > 4 6175 352396 171730 265470 0 0 1d02h >212 <--- SPRINT > >-------------------------------------------------------------------------------- > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. >-------------------------------------------------------------------------------- >The main DNS server is "rns1.v6.inet.co.th". >Our formal forward domain name for IPv6 is "v6.inet.co.th". >And we have DNS reverse (ip6.int) delegation from SPRINT >(3ffe:2900:1101::/48) only. > ># nslookup -type=soa v6.inet.co.th >v6.inet.co.th > origin = rns1.v6.inet.co.th > mail addr = hostmaster.inet.co.th > serial = 2002052803 > refresh = 21600 (6H) > retry = 7200 (2H) > expire = 604800 (1W) > minimum ttl = 43200 (12H) >v6.inet.co.th nameserver = rns1.v6.inet.co.th >rns1.v6.inet.co.th internet address = 203.150.14.111 >rns1.v6.inet.co.th IPv6 address = 3ffe:2900:1101:0:210:64ff:fe30:7cb9 > ># nslookup > > ls -d v6.inet.co.th >$ORIGIN v6.inet.co.th. >@ 12H IN SOA rns1 hostmaster.inet.co.th. ( > 2002052803 ; serial > 6H ; refresh > 2H ; retry > 1W ; expiry > 12H ) ; minimum > > 12H IN NS rns1 >FREENET6 12H IN AAAA 3ffe:b80:61f:: >SPRINT 12H IN AAAA 3ffe:2900:1101:: >VIAGENIE 12H IN AAAA 3ffe:b00:4050:: > >core-gw 12H IN A 203.150.14.66 > 12H IN AAAA 3ffe:2900:1101:0:2b0:64ff:fefc:e2e1 > >netcen 12H IN A 203.150.14.120 > 12H IN AAAA 3ffe:2900:1101:0:220:afff:fed3:6a4c >rns1 12H IN A 203.150.14.111 > 12H IN AAAA 3ffe:2900:1101:0:210:64ff:fe30:7cb9 >www 12H IN A 203.150.14.120 > 12H IN AAAA 3ffe:2900:1101:0:220:afff:fed3:6a4c > > ># dig -t any 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int @ns1.sprintv6.net > >; <<>> DiG 8.3 <<>> -t 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int @ns1.sprintv6.net >; (1 server found) >;; res options: init recurs defnam dnsrch >;; got answer: >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 >;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 2 >;; QUERY SECTION: >;; 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int, type = ANY, class = IN > >;; ANSWER SECTION: >1.0.1.1.0.0.9.2.e.f.f.3.ip6.int. 4H IN NS rns1.v6.inet.co.th. > >;; AUTHORITY SECTION: >9.2.e.f.f.3.ip6.int. 4H IN NS ns1.sprintv6.net. > >;; ADDITIONAL SECTION: >ns1.sprintv6.net. 4H IN A 63.167.40.5 >ns1.sprintv6.net. 4H IN AAAA 2001:440:1239:1001::2 > > >-------------------------------------------------------------------------------- > d. A fully maintained, and reliable, IPv6-accessible system > providing, at a mimimum, one or more web pages, describing the > Applicant's IPv6 services. This server must be IPv6 pingable. >-------------------------------------------------------------------------------- >Our common webpage for IPv6 is "http://www.v6.inet.co.th". >It can be IPv6 pingable. > ># ping6 www.v6.inet.co.th >PING6(56=40+8+8 bytes) 3ffe:2900:1101:0:220:afff:fed3:6a4c --> >3ffe:2900:1101:0:220:afff:fed3:6a4c > >16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=0 hlim=64 >time=0.32 ms >16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=1 hlim=64 >time=0.19 ms >16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=2 hlim=64 >time=0.186 ms >16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=3 hlim=64 >time=0.185 ms >16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=4 hlim=64 >time=0.189 ms > >--- www.v6.inet.co.th ping6 statistics --- >5 packets transmitted, 5 packets received, 0% packet loss >round-trip min/avg/max = 0.185/0.214/0.320 ms > >================================================================================ > 2. The pTLA Applicant MUST have the ability and intent to provide > "production-quality" 6Bone backbone service. Applicants must > provide a statement and information in support of this claim. > This MUST include the following: > > a. A support staff of two persons minimum, three preferable, with > person attributes registered for each in the ipv6-site object > for the pTLA applicant. >-------------------------------------------------------------------------------- >person: Buncha Srisamanuwat >notify: athicha@inet.co.th > >person: Sanan Kurkulsatsanakit >notify: snakk@inet.co.th > >person: Chakrit Noisuwan >notify: chakrit@inet.co.th > >person: Nattapong Jatupongpairoj >notify: jnatta@inet.co.th > >person: Prasong Sakulwongwattana >notify: psongs@inet.co.th > >person: Karaked Kedchumpol >notify: karaked@inet.co.th > >-------------------------------------------------------------------------------- > b. A common mailbox for support contact purposes that all support > staff have acess to, pointed to with a notify attribute in the > ipv6-site object for the pTLA Applicant. >-------------------------------------------------------------------------------- >The common mailbox for IPv6 in INET-TH is "ipv6@inet.co.th" > >ipv6-site: INET-TH >contact: INOC1-6BONE > >role: INET-TH Network Operation Center >e-mail: ipv6@inet.co.th >nic-hdl: INOC1-6BONE > >================================================================================ > 3. The pTLA Applicant MUST have a potential "user community" that > would be served by its becoming a pTLA, e.g., the Applicant is a > major provider of Internet service in a region, country, or focus > of interest. Applicant must provide a statement and information in > support this claim. >-------------------------------------------------------------------------------- >INET-TH is the most market-shared ISP of corporate customers in Thailand. >We are providing Internet Access Service for both Corporate and Individual >customers. We also provide Hosting, Co-location, Internet Data Center and >E-commerce Services. We are the first ISP in Thailand that became to >public >company limited. Our coverage is overall of Thailand 76 provinces last >year. > >As a 6BONE pTLA, we have a plan of testbed with our subscribers with >policy >of not charging services. We welcome whoever want to connect us with >6BONE prefix. > >We also plan to request IPv6 address space from APNIC within this year. >Then >we will provide our commercial services in IPv6. > >================================================================================ > 4. The pTLA Applicant MUST commit to abide by the current 6Bone > operational rules and policies as they exist at time of its > application, and agree to abide by future 6Bone backbone > operational rules and policies as they evolve by consensus of the > 6Bone backbone and user community. >-------------------------------------------------------------------------------- > >INET-TH commit and agree to the current and future 6BONE operational rules >and policies. > ><<< Internet Thailand Public Company Limited >>> From fink@es.net Tue Jun 4 05:37:00 2002 Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g54CaxE03068 for <6bone@mailman.isi.edu>; Tue, 4 Jun 2002 05:36:59 -0700 (PDT) Received: from ([63.196.96.113]) by postal3.es.net (Postal Node 3) with SMTP id GQF37091; Tue, 04 Jun 2002 05:36:55 -0700 Message-Id: <5.1.0.14.0.20020604053539.0239eff8@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 04 Jun 2002 05:36:51 -0700 To: 6BONE List <6bone@mailman.isi.edu> From: Bob Fink Cc: Sanan Kurkulsatsanakit Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] pTLA request INET-TH - review closes 17 June 2002 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: 6bone Folk, INET-TH has requested a pTLA allocation and I find their request fully compliant with RFC2772. The open review period for this will close 17 June 2002. Please send your comments to me or the list. Thanks, Bob === Date: Mon, 3 Jun 2002 09:11:28 +0700 (GMT+0700) From: Sanan Kurkulsatsanakit To: cc: Subject: pTLA prefix request Hi Bob, This is a pTLA prefix request from Internet Thailand Public Company Limited. Please review and notify us for any update. Many thanks, Sanan ================================================================================ 1. The pTLA Applicant must have a minimum of three (3) months qualifying experience as a 6Bone end-site or pNLA transit. During the entire qualifying period the Applicant must be operationally providing the following: a. Fully maintained, up to date, 6Bone Registry entries for their ipv6-site inet6num, mntner, and person objects, including each tunnel that the Applicant has. -------------------------------------------------------------------------------- We have 3 delegated 6bone prefix (/48) as following: - 3FFE:B80:61F::/48 from FREENET6 - 3FFE:B00:4050::/48 from VIAGENIE - 3FFE:2900:1101::/48 from SPRINT <<< ipv6-site >>> % RIPEdb(3.0.0b2) with ISI RPSL extensions ipv6-site: INET-TH origin: AS4618 descr: Internet Thailand Public Company Limited country: TH prefix: 3FFE:B80:61F::/48 prefix: 3FFE:B00:4050::/48 prefix: 3FFE:2900:1101::/48 application: ping ipv6-gw66.inet.co.th tunnel: IPv6 in IPv4 ipv6-gw66.inet.co.th -> www.freenet6.net VIAGENIE STATIC tunnel: IPv6 in IPv4 ipv6-gw66.inet.co.th -> rap.viagenie.qc.ca VIAGENIE BGP4+ tunnel: IPv6 in IPv4 ipv6-gw66.inet.co.th -> sl-bb1v6-sj.sprintlink.net SPRINT BGP4+ contact: BS5-6BONE contact: INOC1-6BONE remarks: ipv6-site is operational since 20011225 mnt-by: MNT-INET changed: snakk@inet.co.th 20011227 changed: snakk@inet.co.th 20011229 changed: snakk@inet.co.th 20020117 changed: snakk@inet.co.th 20020129 source: 6BONE <<< inet6num >>> inet6num: 3FFE:B80:61F::/48 netname: INET-TH descr: Internet Thailand Public Company Limited country: TH admin-c: BS5-6BONE tech-c: INOC1-6BONE notify: noc@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20011225 changed: snakk@inet.co.th 20011227 source: 6BONE inet6num: 3FFE:B00:4050::/48 netname: INET-TH descr: Internet Thailand Public Company Limited country: TH admin-c: BS5-6BONE tech-c: INOC1-6BONE notify: ipv6@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20020529 source: 6BONE inet6num: 3FFE:2900:1101::/48 netname: INET-TH descr: Internet Thailand Public Company Limited country: TH admin-c: BS5-6BONE tech-c: INOC1-6BONE notify: ipv6@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20020529 source: 6BONE <<< mntner >>> % RIPEdb(3.0.0b2) with ISI RPSL extensions mntner: MNT-INET descr: Maintainer of INET-TH 6bone objects admin-c: BS16-AP tech-c: CN2-TH tech-c: SK13-AP tech-c: SK26-TH upd-to: noc@inet.co.th auth: CRYPT-PW * auth: CRYPT-PW * remarks: This object is automatically converted from the RIPE181 registry mnt-by: MNT-INET changed: snakk@inet.co.th 20010107 changed: snakk@inet.co.th 20010108 changed: auto-dbm@whois.6bone.net 20010117 source: 6BONE <<< person >>> % RIPEdb(3.0.0b2) with ISI RPSL extensions role: INET-TH Network Operation Center address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12 Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2640-0456 e-mail: noc@inet.co.th admin-c: BS5-6BONE tech-c: SK2-6BONE nic-hdl: INOC1-6BONE remarks: This object is automatically converted from the RIPE181 registry notify: noc@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20010108 changed: auto-dbm@whois.6bone.net 20010117 changed: snakk@inet.co.th 20011225 source: 6BONE person: Buncha Srisamanuwat address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12 Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2640-0456 e-mail: athicha@inet.co.th nic-hdl: BS5-6BONE remarks: This object is automatically converted from the RIPE181 registry notify: athicha@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20010108 changed: auto-dbm@whois.6bone.net 20010117 changed: snakk@inet.co.th 20011225 source: 6BONE person: Sanan Kurkulsatsanakit address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12 Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2640-0456 e-mail: snakk@inet.co.th nic-hdl: SK2-6BONE remarks: This object is automatically converted from the RIPE181 registry notify: snakk@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20010108 changed: auto-dbm@whois.6bone.net 20010117 changed: snakk@inet.co.th 20011225 source: 6BONE person: Chakrit Noisuwan address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12 Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2640-0456 e-mail: chakrit@inet.co.th nic-hdl: CN2-6BONE notify: chakrit@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20011225 changed: snakk@inet.co.th 20011225 source: 6BONE person: Nattapong Jatupongpairoj address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12th Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2257-7275 e-mail: jnatta@inet.co.th nic-hdl: NJ2-6BONE notify: jnatta@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20020521 source: 6BONE person: Prasong Sakulwongwattana address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12th Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2257-7275 e-mail: psongs@inet.co.th nic-hdl: PS9-6BONE notify: psongs@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20020521 source: 6BONE person: Karaked Kedchumpol address: Internet Thailand Public Company Limited address: 108 Bangkok Thai Tower Bldg., 12th Fl., address: Rangnam Rd., Rajdhevee, address: Bangkok 10400, Thailand phone: +66-2640-0345 fax-no: +66-2257-7275 e-mail: karaked@inet.co.th nic-hdl: KK13-6BONE notify: karaked@inet.co.th mnt-by: MNT-INET changed: snakk@inet.co.th 20020521 source: 6BONE -------------------------------------------------------------------------------- b. Fully maintained, and reliable, BGP4+ peering and connectivity between the Applicant's boundary router and the appropriate connection point into the 6Bone. This router must be IPv6 pingable. This criteria is judged by members of the 6Bone Operations Group at the time of the Applicant's pTLA request. -------------------------------------------------------------------------------- We have 2 BGP perring with SPRINT and VIAGENIE IPv6-Router#show ipv6 interface brief Ethernet0 [up/up] 3FFE:2900:1101:0:2B0:64FF:FEFC:E2E1 Loopback0 [up/up] unassigned Tunnel11 [up/up] <--- SPRINT 3FFE:2900:1100:1::2 Tunnel99 [up/up] <--- VIAGENIE 3FFE:B00:C18::99 IPv6-Router#show ip interface brief Interface IP-Address OK? Method Status Prot ocol Ethernet0 203.150.14.66 YES NVRAM up up Loopback0 203.150.16.66 YES NVRAM up up Tunnel11 unassigned YES NVRAM up up <--- SPRINT Tunnel99 unassigned YES NVRAM up up <--- VIAGENIE IPv6-Router#show bgp ipv6 summary BGP router identifier 203.150.16.66, local AS number 4618 BGP table version is 265470, main routing table version 265470 225 network entries and 427 paths using 58061 bytes of memory 359 BGP path attribute entries using 21540 bytes of memory 348 BGP AS-PATH entries using 9812 bytes of memory 9 BGP community entries using 216 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 180 BGP filter-list cache entries using 2160 bytes of memory 213 received paths for inbound soft reconfiguration BGP activity 56658/276904 prefixes, 219207/218780 paths, scan interval 15 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 3FFE:B00:C18::98 4 10566 746846 346002 265470 0 0 13:33:53 0 <--- VIAGENIE 3FFE:2900:1100:1::1 4 6175 352396 171730 265470 0 0 1d02h 212 <--- SPRINT -------------------------------------------------------------------------------- c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) entries for the Applicant's router(s) and at least one host system. -------------------------------------------------------------------------------- The main DNS server is "rns1.v6.inet.co.th". Our formal forward domain name for IPv6 is "v6.inet.co.th". And we have DNS reverse (ip6.int) delegation from SPRINT (3ffe:2900:1101::/48) only. # nslookup -type=soa v6.inet.co.th v6.inet.co.th origin = rns1.v6.inet.co.th mail addr = hostmaster.inet.co.th serial = 2002052803 refresh = 21600 (6H) retry = 7200 (2H) expire = 604800 (1W) minimum ttl = 43200 (12H) v6.inet.co.th nameserver = rns1.v6.inet.co.th rns1.v6.inet.co.th internet address = 203.150.14.111 rns1.v6.inet.co.th IPv6 address = 3ffe:2900:1101:0:210:64ff:fe30:7cb9 # nslookup > ls -d v6.inet.co.th $ORIGIN v6.inet.co.th. @ 12H IN SOA rns1 hostmaster.inet.co.th. ( 2002052803 ; serial 6H ; refresh 2H ; retry 1W ; expiry 12H ) ; minimum 12H IN NS rns1 FREENET6 12H IN AAAA 3ffe:b80:61f:: SPRINT 12H IN AAAA 3ffe:2900:1101:: VIAGENIE 12H IN AAAA 3ffe:b00:4050:: core-gw 12H IN A 203.150.14.66 12H IN AAAA 3ffe:2900:1101:0:2b0:64ff:fefc:e2e1 netcen 12H IN A 203.150.14.120 12H IN AAAA 3ffe:2900:1101:0:220:afff:fed3:6a4c rns1 12H IN A 203.150.14.111 12H IN AAAA 3ffe:2900:1101:0:210:64ff:fe30:7cb9 www 12H IN A 203.150.14.120 12H IN AAAA 3ffe:2900:1101:0:220:afff:fed3:6a4c # dig -t any 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int @ns1.sprintv6.net ; <<>> DiG 8.3 <<>> -t 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int @ns1.sprintv6.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 2 ;; QUERY SECTION: ;; 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int, type = ANY, class = IN ;; ANSWER SECTION: 1.0.1.1.0.0.9.2.e.f.f.3.ip6.int. 4H IN NS rns1.v6.inet.co.th. ;; AUTHORITY SECTION: 9.2.e.f.f.3.ip6.int. 4H IN NS ns1.sprintv6.net. ;; ADDITIONAL SECTION: ns1.sprintv6.net. 4H IN A 63.167.40.5 ns1.sprintv6.net. 4H IN AAAA 2001:440:1239:1001::2 -------------------------------------------------------------------------------- d. A fully maintained, and reliable, IPv6-accessible system providing, at a mimimum, one or more web pages, describing the Applicant's IPv6 services. This server must be IPv6 pingable. -------------------------------------------------------------------------------- Our common webpage for IPv6 is "http://www.v6.inet.co.th". It can be IPv6 pingable. # ping6 www.v6.inet.co.th PING6(56=40+8+8 bytes) 3ffe:2900:1101:0:220:afff:fed3:6a4c --> 3ffe:2900:1101:0:220:afff:fed3:6a4c 16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=0 hlim=64 time=0.32 ms 16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=1 hlim=64 time=0.19 ms 16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=2 hlim=64 time=0.186 ms 16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=3 hlim=64 time=0.185 ms 16 bytes from 3ffe:2900:1101:0:220:afff:fed3:6a4c, icmp_seq=4 hlim=64 time=0.189 ms --- www.v6.inet.co.th ping6 statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.185/0.214/0.320 ms ================================================================================ 2. The pTLA Applicant MUST have the ability and intent to provide "production-quality" 6Bone backbone service. Applicants must provide a statement and information in support of this claim. This MUST include the following: a. A support staff of two persons minimum, three preferable, with person attributes registered for each in the ipv6-site object for the pTLA applicant. -------------------------------------------------------------------------------- person: Buncha Srisamanuwat notify: athicha@inet.co.th person: Sanan Kurkulsatsanakit notify: snakk@inet.co.th person: Chakrit Noisuwan notify: chakrit@inet.co.th person: Nattapong Jatupongpairoj notify: jnatta@inet.co.th person: Prasong Sakulwongwattana notify: psongs@inet.co.th person: Karaked Kedchumpol notify: karaked@inet.co.th -------------------------------------------------------------------------------- b. A common mailbox for support contact purposes that all support staff have acess to, pointed to with a notify attribute in the ipv6-site object for the pTLA Applicant. -------------------------------------------------------------------------------- The common mailbox for IPv6 in INET-TH is "ipv6@inet.co.th" ipv6-site: INET-TH contact: INOC1-6BONE role: INET-TH Network Operation Center e-mail: ipv6@inet.co.th nic-hdl: INOC1-6BONE ================================================================================ 3. The pTLA Applicant MUST have a potential "user community" that would be served by its becoming a pTLA, e.g., the Applicant is a major provider of Internet service in a region, country, or focus of interest. Applicant must provide a statement and information in support this claim. -------------------------------------------------------------------------------- INET-TH is the most market-shared ISP of corporate customers in Thailand. We are providing Internet Access Service for both Corporate and Individual customers. We also provide Hosting, Co-location, Internet Data Center and E-commerce Services. We are the first ISP in Thailand that became to public company limited. Our coverage is overall of Thailand 76 provinces last year. As a 6BONE pTLA, we have a plan of testbed with our subscribers with policy of not charging services. We welcome whoever want to connect us with 6BONE prefix. We also plan to request IPv6 address space from APNIC within this year. Then we will provide our commercial services in IPv6. ================================================================================ 4. The pTLA Applicant MUST commit to abide by the current 6Bone operational rules and policies as they exist at time of its application, and agree to abide by future 6Bone backbone operational rules and policies as they evolve by consensus of the 6Bone backbone and user community. -------------------------------------------------------------------------------- INET-TH commit and agree to the current and future 6BONE operational rules and policies. <<< Internet Thailand Public Company Limited >>> From bmanning@ISI.EDU Thu Jun 6 11:18:29 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g56IITE08075 for <6bone@mailman.isi.edu>; Thu, 6 Jun 2002 11:18:29 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g56IISa02140 for 6bone; Thu, 6 Jun 2002 11:18:28 -0700 (PDT) From: Bill Manning Message-Id: <200206061818.g56IISa02140@boreas.isi.edu> To: 6bone@ISI.EDU Date: Thu, 6 Jun 2002 11:18:28 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [6bone] random walk? Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: both nodes in LA. very impressive.... ---------------------------------------------------- traceroute6 to lime.ep.net (2001:478:6::1) from 3ffe:0:1::c620:242, 30 hops max, 12 byte packets 1 3ffe:0:1::1 9.531 ms * 0.498 ms 2 3ffe:c00:8023:e::1 11.849 ms 11.881 ms 11.392 ms 3 london1-manchester1-gw.ipv6.kewlio.net 219.342 ms edt-cisco.ipv6.edisontel. it 193.543 ms 193.373 ms 4 3ffe:2900:1:5::2 727.936 ms 3ffe:800::fffb:0:0:6 164.302 ms 166.069 ms 5 gate.ipv6.wanadoo.be 181.536 ms 290.697 ms * 6 2001:768:e:1::2 357.994 ms 3ffe:c00:8023:c::1 213.895 ms 213.377 ms 7 3ffe:81d0:ffff:2::23 487.803 ms 2001:288:3b0::c 708.252 ms 2001:288:3b0::1 e 402.871 ms 8 3ffe:8320:1::25 1028.21 ms london1-manchester1-gw.ipv6.kewlio.net 460.173 ms 459.098 ms 9 2001:780::b 449.21 ms 3ffe:c00:8023:25::1 264.226 ms 251.315 ms 10 3ffe:c00:8023:25::2 330.116 ms * 335.899 ms 11 3ffe:c00:8023:25::1 492.054 ms 401.806 ms 420.531 ms 12 3ffe:c00:8023:25::2 412.062 ms 809.992 ms 608.478 ms 13 3ffe:c00:8023:25::1 607.878 ms 415.899 ms 492.083 ms 14 * 3ffe:c00:8023:25::1 488.384 ms 551.468 ms 15 3ffe:c00:8023:25::2 564.566 ms 564.617 ms 567.17 ms 16 3ffe:c00:8023:25::1 577.971 ms 568.394 ms 571.052 ms 17 3ffe:c00:8023:25::2 647.445 ms 650.442 ms 653.109 ms 18 3ffe:c00:8023:25::1 642.521 ms 643.35 ms 3ffe:8260:fd:6::1 1278.51 ms !A 19 grnet-hurricane.ipv6.grnet.gr 2778.35 ms 2001:780::b 1757.16 ms 3ffe:c00:8 023:1e::2 2009.55 ms 20 2001:780::b 2096.76 ms 2091.27 ms 2084.79 ms 21 3ffe:c00:8023:1e::2 2222.58 ms 1922.16 ms 1659.08 ms 22 2001:478:ffff::1e 1655.09 ms 1648.34 ms 1631.33 ms 23 3ffe:c00:8023:1e::2 1842.8 ms 1824.69 ms 1794.77 ms 24 2001:780::b 1288.24 ms 1411.98 ms 1417.64 ms 25 2001:478:ffff::1e 1415.71 ms 1284.05 ms 1279.68 ms 26 2001:780::b 1391.3 ms 2001:478:ffff::1e 1487.08 ms 1696.65 ms 27 2001:470:1fff:2::5 1878.89 ms 1874.68 ms 1890.85 ms 28 2001:780::b 1910.57 ms 1931.28 ms 1912.06 ms 29 2001:470:1fff:2::5 1962.74 ms 3ffe:c00:8023:24::2 2586.11 ms 2593.85 ms 30 3ffe:c00:8023:24::1 2662.59 ms 2650.47 ms 2587.02 ms -- "When in doubt, Twirl..." -anon From mail@thomas--schaefer.de Thu Jun 6 12:34:47 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g56JYkE11318 for <6bone@mailman.isi.edu>; Thu, 6 Jun 2002 12:34:46 -0700 (PDT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g56JYib18977 for <6bone@isi.edu>; Thu, 6 Jun 2002 12:34:45 -0700 (PDT) Received: from fwd06.sul.t-online.de by mailout10.sul.t-online.com with smtp id 17G31u-0002wx-07; Thu, 06 Jun 2002 21:34:42 +0200 Received: from witz (520065784698-0001@[217.228.223.31]) by fmrl06.sul.t-online.com with esmtp id 17G31k-0wJBz6C; Thu, 6 Jun 2002 21:34:32 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Thomas Schaefer To: 6bone@ISI.EDU Subject: Re: [6bone] random walk? Date: Thu, 6 Jun 2002 21:34:28 +0200 X-Mailer: KMail [version 1.4] References: <200206061818.g56IISa02140@boreas.isi.edu> In-Reply-To: <200206061818.g56IISa02140@boreas.isi.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200206062134.28910.mail@thomas--schaefer.de> X-Sender: 520065784698-0001@t-dialin.net Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: 6. Juni 2002 20:18 wrote Bill Manning: > very impressive.... > from a different point of view: host:~ # traceroute6 2001:478:6::1 traceroute to 2001:478:6::1 (2001:478:6::1) from 3ffe:b80:d17:1:2a0:ccff:fe20:5d7c, 30 hops max, 16 byte packets 1 3ffe:b80:d17:1::1 (3ffe:b80:d17:1::1) 0.87 ms 0.577 ms 0.567 ms 2 3ffe:b80:2:95f3::1 (3ffe:b80:2:95f3::1) 365.829 ms 361.016 ms 375.314 ms 3 2001:780::b (2001:780::b) 814.896 ms 358.293 ms 353.315 ms 4 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 492.258 ms 461.492 ms * 5 3ffe:b00:c18::3 (3ffe:b00:c18::3) 561.88 ms 560.234 ms 578.585 ms 6 2001:780::b (2001:780::b) 571.196 ms 570.055 ms 570.962 ms 7 * 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 650.221 ms 660.813 ms 8 3ffe:b00:c18::3 (3ffe:b00:c18::3) 778.641 ms 779.591 ms 776.91 ms 9 * * 2001:780::b (2001:780::b) 775.771 ms 10 * 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 857.956 ms 874.645 ms 11 3ffe:b00:c18::3 (3ffe:b00:c18::3) 1028.26 ms 1004.38 ms 1054.79 ms 12 2001:780::b (2001:780::b) 1042.59 ms 993.64 ms 999.804 ms 13 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 1098.09 ms 1082.68 ms 1116.46 ms 14 3ffe:b00:c18::3 (3ffe:b00:c18::3) 1222.71 ms 1217.99 ms 1196.03 ms 15 2001:780::b (2001:780::b) 1270.78 ms 1207.47 ms 1198.48 ms 16 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 1323.21 ms 1286.93 ms 1308.19 ms 17 3ffe:b00:c18::3 (3ffe:b00:c18::3) 1416.23 ms 1422.7 ms 1437.84 ms 18 2001:780::b (2001:780::b) 1414.32 ms 1413.82 ms 1445.82 ms 19 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 1520.97 ms 1629.09 ms 1555.38 ms 20 * 3ffe:b00:c18::3 (3ffe:b00:c18::3) 1627.2 ms 1667.6 ms ... host:~ # ping6 2001:478:6::1 PING 2001:478:6::1(2001:478:6::1) from 3ffe:b80:d17:1:2a0:ccff:fe20:5d7c : 56 data bytes From 3ffe:b00:c18::6b icmp_seq=1 Time exceeded: Hop limitFrom 3ffe:b00:c18::6b icmp_seq=2 Time exceeded: Hop limitFrom 3ffe:b00:c18::6b icmp_seq=3 Time exceeded: Hop limit --- 2001:478:6::1 ping statistics --- 8 packets transmitted, 0 received, +3 errors, 100% loss, time 7042ms Regards, Thomas Schäfer From jorgen@hovland.cx Thu Jun 6 13:22:05 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g56KM5E02668 for <6bone@mailman.isi.edu>; Thu, 6 Jun 2002 13:22:05 -0700 (PDT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g56KLxb11693; Thu, 6 Jun 2002 13:22:04 -0700 (PDT) Received: from hera (58.80-203-6.nextgentel.com [80.203.6.58]) by mail.broadpark.no (Postfix) with SMTP id 840117D07; Thu, 6 Jun 2002 22:21:52 +0200 (MEST) Message-ID: <012301c20d97$cc3f52c0$0200000a@hera> From: =?iso-8859-1?Q?J=F8rgen_Hovland?= To: "Bill Manning" , <6bone@ISI.EDU> References: <200206061818.g56IISa02140@boreas.isi.edu> Subject: Re: [6bone] random walk? Date: Thu, 6 Jun 2002 22:21:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: It is most likely due to flapping and people using default-routes. Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure Origin codes: i - IGP, e - EGP, ? - incomplete Network From Flaps Duration Reuse Path * 2001:478::/35 2001:750:E::A 1 00:01:55 15589 8954 4554 * 3FFE:82B0:0:1:1 1 00:01:54 24765 109 4554 Joergen Hovland ----- Original Message ----- From: "Bill Manning" To: <6bone@ISI.EDU> Sent: Thursday, June 06, 2002 8:18 PM Subject: [6bone] random walk? > both nodes in LA. > very impressive.... > > ---------------------------------------------------- > > traceroute6 to lime.ep.net (2001:478:6::1) from 3ffe:0:1::c620:242, 30 hops max, > 12 byte packets > 1 3ffe:0:1::1 9.531 ms * 0.498 ms > 2 3ffe:c00:8023:e::1 11.849 ms 11.881 ms 11.392 ms > 3 london1-manchester1-gw.ipv6.kewlio.net 219.342 ms edt-cisco.ipv6.edisontel. > it 193.543 ms 193.373 ms > 4 3ffe:2900:1:5::2 727.936 ms 3ffe:800::fffb:0:0:6 164.302 ms 166.069 ms > 5 gate.ipv6.wanadoo.be 181.536 ms 290.697 ms * > 6 2001:768:e:1::2 357.994 ms 3ffe:c00:8023:c::1 213.895 ms 213.377 ms > 7 3ffe:81d0:ffff:2::23 487.803 ms 2001:288:3b0::c 708.252 ms 2001:288:3b0::1 > e 402.871 ms > 8 3ffe:8320:1::25 1028.21 ms london1-manchester1-gw.ipv6.kewlio.net 460.173 > ms 459.098 ms > 9 2001:780::b 449.21 ms 3ffe:c00:8023:25::1 264.226 ms 251.315 ms > 10 3ffe:c00:8023:25::2 330.116 ms * 335.899 ms > 11 3ffe:c00:8023:25::1 492.054 ms 401.806 ms 420.531 ms > 12 3ffe:c00:8023:25::2 412.062 ms 809.992 ms 608.478 ms > 13 3ffe:c00:8023:25::1 607.878 ms 415.899 ms 492.083 ms > 14 * 3ffe:c00:8023:25::1 488.384 ms 551.468 ms > 15 3ffe:c00:8023:25::2 564.566 ms 564.617 ms 567.17 ms > 16 3ffe:c00:8023:25::1 577.971 ms 568.394 ms 571.052 ms > 17 3ffe:c00:8023:25::2 647.445 ms 650.442 ms 653.109 ms > 18 3ffe:c00:8023:25::1 642.521 ms 643.35 ms 3ffe:8260:fd:6::1 1278.51 ms !A > 19 grnet-hurricane.ipv6.grnet.gr 2778.35 ms 2001:780::b 1757.16 ms 3ffe:c00:8 > 023:1e::2 2009.55 ms > 20 2001:780::b 2096.76 ms 2091.27 ms 2084.79 ms > 21 3ffe:c00:8023:1e::2 2222.58 ms 1922.16 ms 1659.08 ms > 22 2001:478:ffff::1e 1655.09 ms 1648.34 ms 1631.33 ms > 23 3ffe:c00:8023:1e::2 1842.8 ms 1824.69 ms 1794.77 ms > 24 2001:780::b 1288.24 ms 1411.98 ms 1417.64 ms > 25 2001:478:ffff::1e 1415.71 ms 1284.05 ms 1279.68 ms > 26 2001:780::b 1391.3 ms 2001:478:ffff::1e 1487.08 ms 1696.65 ms > 27 2001:470:1fff:2::5 1878.89 ms 1874.68 ms 1890.85 ms > 28 2001:780::b 1910.57 ms 1931.28 ms 1912.06 ms > 29 2001:470:1fff:2::5 1962.74 ms 3ffe:c00:8023:24::2 2586.11 ms 2593.85 ms > 30 3ffe:c00:8023:24::1 2662.59 ms 2650.47 ms 2587.02 ms > > -- > "When in doubt, Twirl..." -anon > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From jeroen@unfix.org Thu Jun 6 15:14:20 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g56MEJE01200 for <6bone@mailman.isi.edu>; Thu, 6 Jun 2002 15:14:20 -0700 (PDT) Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g56MEHb16589; Thu, 6 Jun 2002 15:14:18 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 7860A3187; Fri, 7 Jun 2002 00:14:10 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 05EDF316A; Fri, 7 Jun 2002 00:13:50 +0200 (CEST) From: "Jeroen Massar" To: "=?iso-8859-1?Q?'J=F8rgen_Hovland'?=" , "'Bill Manning'" , <6bone@ISI.EDU> Subject: RE: [6bone] random walk? Date: Fri, 7 Jun 2002 00:13:50 +0200 Organization: Unfix Message-ID: <000a01c20da7$740e7800$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <012301c20d97$cc3f52c0$0200000a@hera> X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g56MEJE01200 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Jørgen Hovland wrote: > It is most likely due to flapping and people using default-routes. > > Status codes: s suppressed, d damped, h history, * valid, > best, i - > internal, > r RIB-failure > Origin codes: i - IGP, e - EGP, ? - incomplete > > Network From Flaps Duration Reuse Path > * 2001:478::/35 2001:750:E::A 1 00:01:55 > 15589 8954 4554 > * 3FFE:82B0:0:1:1 1 00:01:54 > 24765 109 4554 jeroen@noc:~$ traceroute6 2001:478:6::1 traceroute to 2001:478:6::1 (2001:478:6::1) from 3ffe:4007:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets 1 fe0.breda.ipv6.concepts-ict.net (3ffe:4007:1:1::1) 0.488 ms 0.385 ms 0.346 ms 2 se2.ams-ix.ipv6.concepts-ict.net (3ffe:4007:0:10::1) 3.559 ms 3.576 ms 3.746 ms 3 ams-ix.sara.xs4all.net (2001:7f8:1::a500:3265:1) 4.085 ms 4.741 ms 4.111 ms 4 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 4.25 ms 4.107 ms 4.125 ms 5 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 161.881 ms 161.794 ms * 6 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 168.316 ms !H * 161.958 ms !H @Intouch (www.ipng.nl/bgp/ :) EP-NET ISI-LAP 2001:0478::/35 3.5% 0.0% view http://www.ipng.nl/bgp/history/35-EP-NET.html : 90.3% ( 130 / 144 ) ISI-LAP 8.3% ( 12 / 144 ) SURFNET - BELNET-BE - BELBONE-BE - 4589 - CYBERNET - REGIO-DE - SPACENET-D - ISI-LAP 0.7% ( 1 / 144 ) CERN - EDISONTEL - 12337 - REGIO-DE - SPACENET-D - ISI-LAP 0.7% ( 1 / 144 ) CISCO - ITESM - XS4ALL-NL - OXYGEN - SPRINT - ISI-LAP ISI-LAP doesn't nicely connect to you but are announcing it... btw... QWEST-IPV6 has an unstability rating of 57.6% here... which is quite high imho, nothing bad but not quite nice either ;) btw2: check the list at http://dmoz.org/Computers/Internet/Protocols/IP/IPng/IPv6_Route_Views/ to check where it could go wrong. btw3: Nice to see ep.net going v6 when are the servers following ? :) Greets, Jeroen From pim@ipng.nl Sun Jun 9 10:22:52 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g59HMpE12297 for <6bone@mailman.isi.edu>; Sun, 9 Jun 2002 10:22:52 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g59HMob22774 for <6bone@isi.edu>; Sun, 9 Jun 2002 10:22:51 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 1CCA58C2A; Sun, 9 Jun 2002 17:22:47 +0000 (GMT) Date: Sun, 9 Jun 2002 19:22:47 +0200 From: Pim van Pelt To: 6bone@ISI.EDU Message-ID: <20020609172247.GA2781@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Subject: [6bone] ifconfig and EUI-64 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi guys, Does anyone know why exactly the ifconfig programs for the BSDs, Linux and most probably Solaris are not able to autoconfigure their own addresses, by not using the RS/RA schema, but a local autoconfiguration such as the Cisco IOS: interface FastEthernet0/0 ipv6 enable ipv6 address 2001:7b8:4:1234::/64 eui-64 ! which will let the fa0/0 device figure out its own address using the lower order 64 bits of its linklocal address in the specified prefix. This behavior is missing in the Unix world and I for one would like to see it implemented. Anybody against this ? groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From ww@GROOVY.NET Sun Jun 9 12:06:36 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g59J6aE28898 for <6bone@mailman.isi.edu>; Sun, 9 Jun 2002 12:06:36 -0700 (PDT) Received: from ANAPHORA.GROOVY.NET (ANAPHORA.GROOVY.NET [205.189.139.196]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g59J6Zb08328 for <6bone@ISI.EDU>; Sun, 9 Jun 2002 12:06:35 -0700 (PDT) Received: by ANAPHORA.GROOVY.NET (Postfix, from userid 101) id EAD6813A; Sun, 9 Jun 2002 15:06:30 -0400 (EDT) Date: Sun, 9 Jun 2002 15:06:30 -0400 From: ww@GROOVY.NET To: Pim van Pelt Cc: 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 Message-ID: <20020609150630.A18427@GROOVY.NET> References: <20020609172247.GA2781@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020609172247.GA2781@bfib.colo.bit.nl>; from pim@ipng.nl on Sun, Jun 09, 2002 at 07:22:47PM +0200 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Sun, Jun 09, 2002 at 07:22:47PM +0200, Pim van Pelt wrote: > > which will let the fa0/0 device figure out its own address using the > lower order 64 bits of its linklocal address in the specified prefix. > > This behavior is missing in the Unix world and I for one would like to > see it implemented. Anybody against this ? There was a discussion about this some time ago on the NetBSD tech-net mailing list. The debate centered on whether it was better to have this functionality in the ifconfig binary or in some sort of script that would call ifconfig after calculating the lower order 64 bits. The problem with the latter is that it might assume that /usr is mounted which may not be true until after networking has been configured. I can't think of any very strong argument about why what you suggest should not be implemented within ifconfig(8). Cheers, Will From jeroen@unfix.org Sun Jun 9 12:56:25 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g59JuPE07800 for <6bone@mailman.isi.edu>; Sun, 9 Jun 2002 12:56:25 -0700 (PDT) Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g59JuOb14208 for <6bone@ISI.EDU>; Sun, 9 Jun 2002 12:56:24 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 97E093188; Sun, 9 Jun 2002 21:56:20 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 1346C316A; Sun, 9 Jun 2002 21:56:12 +0200 (CEST) From: "Jeroen Massar" To: , "'Pim van Pelt'" Cc: <6bone@ISI.EDU> Subject: RE: [6bone] ifconfig and EUI-64 Date: Sun, 9 Jun 2002 21:56:12 +0200 Organization: Unfix Message-ID: <000c01c20fef$b5a53a20$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020609150630.A18427@GROOVY.NET> Importance: Normal X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: ww@GROOVY.NET wrote: > On Sun, Jun 09, 2002 at 07:22:47PM +0200, Pim van Pelt wrote: > > > > which will let the fa0/0 device figure out its own address using the > > lower order 64 bits of its linklocal address in the specified prefix. > > > > This behavior is missing in the Unix world and I for one would like to > > see it implemented. Anybody against this ? > > There was a discussion about this some time ago on the NetBSD > tech-net mailing list. The debate centered on whether it was > better to have this functionality in the ifconfig binary or > in some sort of script that would call ifconfig after calculating > the lower order 64 bits. The problem with the latter is that it > might assume that /usr is mounted which may not be true until > after networking has been configured. > > I can't think of any very strong argument about why what you > suggest should not be implemented within ifconfig(8). FreeBSD 4.2 had the /etc/rc.network6 init script setup so that it would check for a prefixcmd_enable="YES" and if that was true it would use the prefix from ipv6_prefix_ and do a 'prefix ' which sets up an anycast address, after which, the system (read: kernel) knows how to autoconfig that device. Unfortunatly for some odd reason this 'feature' was taken from newer (4.4+) FreeBSD's. The 'prefix' command is still there but the rc.network6 script is now used, the prefix command is completely ignored. As this comes from the KAME upstream they probably know the reason why that happened? Greets, Jeroen PS: snippets from the 'prefix' manpage: DESCRIPTION prefix is used to assign an prefix to a network interface and/or renum- bering network interface prefixes. prefix must be used at boot time to define the network prefix of each interface present on a machine; it may also be used at a later time to renumbering multiple interface's prefixes and other prefix related parameters. prefix is router-only command, so you must do following to use it. % sysctl -w net.inet6.ip6.forwarding=1 If net.inet6.ip6.forwarding is set to 0, prefix command fails by EPERM error. HISTORY The prefix command first appeared in WIDE/KAME IPv6 protocol stack kit. IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack was initially integrated into FreeBSD 4.0 From hansolofalcon@worldnet.att.net Sun Jun 9 13:08:40 2002 Received: from mtiwmhc22.worldnet.att.net (mtiwmhc22.worldnet.att.net [204.127.131.47]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g59K8dE09647 for <6bone@mailman.isi.edu>; Sun, 9 Jun 2002 13:08:39 -0700 (PDT) Received: from who ([12.88.82.42]) by mtiwmhc22.worldnet.att.net (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020609200833.EKKV13408.mtiwmhc22.worldnet.att.net@who> for <6bone@mailman.isi.edu>; Sun, 9 Jun 2002 20:08:33 +0000 From: "Gregg C Levine" To: "6bone Mail List" <6bone@mailman.isi.edu> Subject: RE: [6bone] ifconfig and EUI-64 Date: Sun, 9 Jun 2002 16:07:20 -0400 Message-ID: <000001c20ff1$4373e940$2a52580c@who> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020609150630.A18427@GROOVY.NET> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g59K8dE09647 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hello from Gregg C Levine Pim, I am in total agreement with you on this. Both distributions of Linux which I run here, do support IPv6, but do it strangely. I am inclined to keep an open mind here, on what preference happens. The strange thing I found with NetBSD is that during the installation process it wanted to autoconfig an IPv6 address, then things broke down because my system wasn't being properly configured for that version. FreeBSD on the other hand did want to, but I told it to not do that. And back to Linux, I'll spare you folks my complaints on that problem grouping. ------------------- Gregg C Levine hansolofalcon@worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."  Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda ) > -----Original Message----- > From: 6bone-admin@mailman.isi.edu [mailto:6bone-admin@mailman.isi.edu] On > Behalf Of ww@GROOVY.NET > Sent: Sunday, June 09, 2002 3:07 PM > To: Pim van Pelt > Cc: 6bone@ISI.EDU > Subject: Re: [6bone] ifconfig and EUI-64 > > On Sun, Jun 09, 2002 at 07:22:47PM +0200, Pim van Pelt wrote: > > > > which will let the fa0/0 device figure out its own address using the > > lower order 64 bits of its linklocal address in the specified prefix. > > > > This behavior is missing in the Unix world and I for one would like to > > see it implemented. Anybody against this ? > > There was a discussion about this some time ago on the NetBSD > tech-net mailing list. The debate centered on whether it was > better to have this functionality in the ifconfig binary or > in some sort of script that would call ifconfig after calculating > the lower order 64 bits. The problem with the latter is that it > might assume that /usr is mounted which may not be true until > after networking has been configured. > > I can't think of any very strong argument about why what you > suggest should not be implemented within ifconfig(8). > > Cheers, > Will > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone From aangel@transa.infoarc.sodaknet.com Sun Jun 9 16:22:07 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g59NM7E09358 for <6bone@mailman.isi.edu>; Sun, 9 Jun 2002 16:22:07 -0700 (PDT) Received: from transa.infoarc.sodaknet.com (root@12-245-236-234.client.attbi.com [12.245.236.234]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g59NM5b20518 for <6bone@isi.edu>; Sun, 9 Jun 2002 16:22:06 -0700 (PDT) Received: from transa.infoarc.sodaknet.com (aangel@localhost [127.0.0.1]) by transa.infoarc.sodaknet.com (8.12.3/8.11.6) with ESMTP id g59NLpJ8056313 for <6bone@isi.edu>; Sun, 9 Jun 2002 19:21:51 -0400 (EDT) (envelope-from aangel@transa.infoarc.sodaknet.com) Received: (from aangel@localhost) by transa.infoarc.sodaknet.com (8.12.3/8.12.3/Submit) id g59NLp7q056312; Sun, 9 Jun 2002 19:21:51 -0400 (EDT) Subject: [Fwd: Re: [6bone] ifconfig and EUI-64] From: Aaron Angel To: 6bone@ISI.EDU Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 09 Jun 2002 19:21:51 -0400 Message-Id: <1023664911.56010.21.camel@transa.infoarc.sodaknet.com> Mime-Version: 1.0 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Ehk; forgot to Cc: the list. -----Forwarded Message----- > From: Aaron Angel > To: Pim van Pelt > Subject: Re: [6bone] ifconfig and EUI-64 > Date: 09 Jun 2002 19:21:08 -0400 > > On Sun, 2002-06-09 at 13:22, Pim van Pelt wrote: > > Hi guys, > > > > Does anyone know why exactly the ifconfig programs for the BSDs, Linux > > and most probably Solaris are not able to autoconfigure their own > > addresses, by not using the RS/RA schema, but a local autoconfiguration > > such as the Cisco IOS: > > > The KAME stack comes with rtsol and rtsold; the former sends > solicitations once, the latter is a daemonized version. > > As far as Linux goes (or anything supported, for that matter), > distributions which use INRIA support it in ifconfig with the eui64 > keyword...exactly how, I'm not sure; I don't use it. From Francis.Dupont@enst-bretagne.fr Tue Jun 11 00:56:41 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5B7ueE08067 for <6bone@mailman.isi.edu>; Tue, 11 Jun 2002 00:56:40 -0700 (PDT) Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5B7ubb14699 for <6bone@ISI.EDU>; Tue, 11 Jun 2002 00:56:39 -0700 (PDT) Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1]) by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id g5B7tfX27880; Tue, 11 Jun 2002 09:55:41 +0200 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id JAA16809; Tue, 11 Jun 2002 09:55:41 +0200 (MET DST) Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id g5B7teT98855; Tue, 11 Jun 2002 09:55:40 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200206110755.g5B7teT98855@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Pim van Pelt cc: 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 In-reply-to: Your message of Sun, 09 Jun 2002 19:22:47 +0200. <20020609172247.GA2781@bfib.colo.bit.nl> Date: Tue, 11 Jun 2002 09:55:40 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: In your previous mail you wrote: Does anyone know why exactly the ifconfig programs for the BSDs, Linux and most probably Solaris are not able to autoconfigure their own addresses, by not using the RS/RA schema, but a local autoconfiguration such as the Cisco IOS: => note that Ciscos are usually routers so can't use RS/RA. interface FastEthernet0/0 ipv6 enable ipv6 address 2001:7b8:4:1234::/64 eui-64 ! which will let the fa0/0 device figure out its own address using the lower order 64 bits of its linklocal address in the specified prefix. => EUI-64 should be from the MAC address not from the link-local address but I agree the intended behavior is not well reflected by the name. This behavior is missing in the Unix world and I for one would like to see it implemented. Anybody against this ? => I like to have this and the possibility to explicitely set the link-local address too. Regards Francis.Dupont@enst-bretagne.fr From Francis.Dupont@enst-bretagne.fr Tue Jun 11 01:01:30 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5B81UE08750 for <6bone@mailman.isi.edu>; Tue, 11 Jun 2002 01:01:30 -0700 (PDT) Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5B81Tb15753 for <6bone@ISI.EDU>; Tue, 11 Jun 2002 01:01:29 -0700 (PDT) Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1]) by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id g5B81EX28548; Tue, 11 Jun 2002 10:01:14 +0200 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA16888; Tue, 11 Jun 2002 10:01:14 +0200 (MET DST) Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id g5B81DT98888; Tue, 11 Jun 2002 10:01:14 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200206110801.g5B81DT98888@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Aaron Angel cc: 6bone@ISI.EDU Subject: Re: [Fwd: Re: [6bone] ifconfig and EUI-64] In-reply-to: Your message of 09 Jun 2002 19:21:51 EDT. <1023664911.56010.21.camel@transa.infoarc.sodaknet.com> Date: Tue, 11 Jun 2002 10:01:13 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: In your previous mail you wrote: > As far as Linux goes (or anything supported, for that matter), > distributions which use INRIA support it in ifconfig with the eui64 > keyword...exactly how, I'm not sure; I don't use it. => I can answer, from man ifconfig: eui64 (inet6 only) The real IPv6 address is computed by replacing the last 64 bytes of the given address with the Interface Identifier. For a point-to-point interface, if a destination address is given and has a null Interface Identifier part, the Interface Identifi- er part of this destination address is filled by the Interface Identifier part of the link-local destination address (which must be present). The interface ID is picked up from the (first) link-local address and if there is none from the link-layer address. There is a provision for point-to-point links (i.e. set the peer interface ID too). The last versions perform this in ifconfig itself but you can implement the same idea in the kernel or in a script. Thanks Francis.Dupont@enst-bretagne.fr From pim@ipng.nl Tue Jun 11 01:58:15 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5B8wEE21947 for <6bone@mailman.isi.edu>; Tue, 11 Jun 2002 01:58:15 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5B8wCb27330 for <6bone@ISI.EDU>; Tue, 11 Jun 2002 01:58:13 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 146278C2A; Tue, 11 Jun 2002 08:58:10 +0000 (GMT) Date: Tue, 11 Jun 2002 10:58:10 +0200 From: Pim van Pelt To: Aaron Angel Cc: 6bone@ISI.EDU Subject: Re: [Fwd: Re: [6bone] ifconfig and EUI-64] Message-ID: <20020611085810.GB26532@bfib.colo.bit.nl> References: <1023664911.56010.21.camel@transa.infoarc.sodaknet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1023664911.56010.21.camel@transa.infoarc.sodaknet.com> User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Sun, Jun 09, 2002 at 07:21:51PM -0400, Aaron Angel wrote: | Ehk; forgot to Cc: the list. Aaron, Thanks for the remarks but I was specifically stating that I wish _not_ to use the Router Discovery protocol on a host. Let us say that our box is a router itself, then we would like to set the interface addresses in the global scope implicitly by specifying something like: # ifconfig gx0 inet6 2001:7b8:3:1234:: -prefixlen 64 -eui64 Which would make the box calculate the lower order 64 bits via the MAC address (thanks, Francis) in stead of having the user set it explicitly. Your rtsol/rtsold (and the standard Linux/Windows behavior) have nothing to do with this. I should check out the INRIA comment though, thanks for that hint! groet, Pim | | -----Forwarded Message----- | | > From: Aaron Angel | > To: Pim van Pelt | > Subject: Re: [6bone] ifconfig and EUI-64 | > Date: 09 Jun 2002 19:21:08 -0400 | > | > On Sun, 2002-06-09 at 13:22, Pim van Pelt wrote: | > > Hi guys, | > > | > > Does anyone know why exactly the ifconfig programs for the BSDs, Linux | > > and most probably Solaris are not able to autoconfigure their own | > > addresses, by not using the RS/RA schema, but a local autoconfiguration | > > such as the Cisco IOS: | > > | > The KAME stack comes with rtsol and rtsold; the former sends | > solicitations once, the latter is a daemonized version. | > | > As far as Linux goes (or anything supported, for that matter), | > distributions which use INRIA support it in ifconfig with the eui64 | > keyword...exactly how, I'm not sure; I don't use it. | | _______________________________________________ | 6bone mailing list | 6bone@mailman.isi.edu | http://mailman.isi.edu/mailman/listinfo/6bone -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From dwaddington@lucent.com Tue Jun 11 06:23:11 2002 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5BDNAE25952 for <6bone@mailman.isi.edu>; Tue, 11 Jun 2002 06:23:10 -0700 (PDT) Received: from scummy.research.bell-labs.com (H-135-104-2-10.research.bell-labs.com [135.104.2.10]) by dirty.research.bell-labs.com (8.12.2/8.12.2) with ESMTP id g5BDNI6R054327; Tue, 11 Jun 2002 09:23:18 -0400 (EDT) Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com [135.180.160.8]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id g5BDN2k52136; Tue, 11 Jun 2002 09:23:03 -0400 (EDT) Received: from cupid (cupid [135.180.144.140]) by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with SMTP id JAA01655; Tue, 11 Jun 2002 09:22:59 -0400 (EDT) From: "Daniel G Waddington" To: <6bone@mailman.isi.edu>, Date: Tue, 11 Jun 2002 09:18:08 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [6bone] Public Announcement - Bell Labs IPv6 Probing Experiments Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: PUBLIC ANNOUNCEMENT - BELL LABS IPv6 PROBING EXPERIMENTS To all 6Bone users and network administrators: Bell Laboratories, NJ, is currently performing experiments in IPv6 network topology discovery that involves sending a number of source routed IPv6 probe packets (from 3ffe:2900:c00c:1102:210:5aff:fe9e:9e3b) into the 6Bone network. This is purely a research experiment aimed at collecting router topology information about the 6Bone network. The data that we are collecting from the network will hopefully help us, and the rest of the IPv6 community, to better understand the nature of large scale IPv6 deployment (e.g. effects of tunnelling on routing infrastructure). Some of you may already have noticed that we have been dispatching probes on and off for the last 3 months on to the 6Bone network. Since this is an experimental infrastructure overseen by the IETF, the results will be made publically available to the IETF community in the coming months on www.ipv6.bell-labs.com. If you do not wish to be part of this experiment, then given your router addresses we can eliminate you from the search space. However, we can assure you that probe traffic will be kept to a minimum and that once we have a complete set of data, the experiments will be performed less frequently. Please do not hesitate to contact me if you have any further questions or issues to raise on this matter. Sincerely Yours, Daniel G. Waddington Networking Research Lab Bell Laboratories, Lucent Technologies From itojun@itojun.org Tue Jun 11 07:37:25 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5BEbPE18682 for <6bone@mailman.isi.edu>; Tue, 11 Jun 2002 07:37:25 -0700 (PDT) Received: from starfruit.itojun.org ([209.115.217.214]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5BEbOb09001 for <6bone@ISI.EDU>; Tue, 11 Jun 2002 07:37:24 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by starfruit.itojun.org (Postfix) with ESMTP id 9A3AD7B9; Tue, 11 Jun 2002 23:36:46 +0900 (JST) To: Francis Dupont Cc: Pim van Pelt , 6bone@ISI.EDU In-reply-to: Francis.Dupont's message of Tue, 11 Jun 2002 09:55:40 +0200. <200206110755.g5B7teT98855@givry.rennes.enst-bretagne.fr> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] ifconfig and EUI-64 From: Jun-ichiro itojun Hagino Date: Tue, 11 Jun 2002 23:36:46 +0900 Message-Id: <20020611143646.9A3AD7B9@starfruit.itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >=> I like to have this and the possibility to explicitely set the link-local >address too. you can always remove then add. itojun From kre@munnari.OZ.AU Wed Jun 12 00:50:16 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5C7oGE27666 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 00:50:16 -0700 (PDT) Received: from delta.cs.mu.OZ.AU (96-1.nat.psu.ac.th [202.28.96.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5C7oCb26631 for <6bone@ISI.EDU>; Wed, 12 Jun 2002 00:50:13 -0700 (PDT) Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id g5C7ir718606; Wed, 12 Jun 2002 14:44:53 +0700 (ICT) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Robert Elz To: Francis Dupont cc: Pim van Pelt , 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 In-Reply-To: <200206110755.g5B7teT98855@givry.rennes.enst-bretagne.fr> References: <200206110755.g5B7teT98855@givry.rennes.enst-bretagne.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jun 2002 14:44:53 +0700 Message-ID: <18604.1023867893@munnari.OZ.AU> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Date: Tue, 11 Jun 2002 09:55:40 +0200 From: Francis Dupont Message-ID: <200206110755.g5B7teT98855@givry.rennes.enst-bretagne.fr> | => I like to have this Me too. | and the possibility to explicitely set the link-local address too. Doesn't everyone already allow that? (Some of my systems have a whole bunch of link local addresses assigned to various interfaces - after all, there are 2^64 to choose from on every link, and no nets I use have nearly that many connected hosts, so each host can have lots...) What I want, which is maybe what you meant, is the ability to explicitly set the IID, from which the link-local, and global (and site-local...) addresses are computed. That is so when a new prefix appears in a RA, the new address will automatically be generated using the IID I specified (which is why simply specifying the whole address doesn't work). kre From Francis.Dupont@enst-bretagne.fr Wed Jun 12 05:14:43 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5CCEhE27326 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 05:14:43 -0700 (PDT) Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5CCEbb29398 for <6bone@ISI.EDU>; Wed, 12 Jun 2002 05:14:42 -0700 (PDT) Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1]) by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id g5CC7vX13693; Wed, 12 Jun 2002 14:07:57 +0200 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id OAA05905; Wed, 12 Jun 2002 14:07:57 +0200 (MET DST) Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id g5CC7uT06279; Wed, 12 Jun 2002 14:07:57 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200206121207.g5CC7uT06279@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Robert Elz cc: Pim van Pelt , 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 In-reply-to: Your message of Wed, 12 Jun 2002 14:44:53 +0700. <18604.1023867893@munnari.OZ.AU> Date: Wed, 12 Jun 2002 14:07:56 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: In your previous mail you wrote: | and the possibility to explicitely set the link-local address too. Doesn't everyone already allow that? => no, for instance in KAME you have to recompile the kernel with "options IP6_AUTO_LINKLOCAL=0"... What I want, which is maybe what you meant, is the ability to explicitly set the IID, from which the link-local, and global (and site-local...) addresses are computed. => on a reasonable system to set the link-local address or the IID are equivalent. That is so when a new prefix appears in a RA, the new address will automatically be generated using the IID I specified (which is why simply specifying the whole address doesn't work). => the subject of this thread is the extension of this to the ifconfig command. Thanks Francis.Dupont@enst-bretagne.fr From kre@munnari.OZ.AU Wed Jun 12 08:11:52 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5CFBpE22472 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 08:11:51 -0700 (PDT) Received: from ratree.psu.ac.th ([202.28.96.5]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5CFBob12137 for <6bone@ISI.EDU>; Wed, 12 Jun 2002 08:11:50 -0700 (PDT) Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98]) by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id g5CFBDM04168; Wed, 12 Jun 2002 22:11:16 +0700 (ICT) Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id g5CF8fs20787; Wed, 12 Jun 2002 22:08:43 +0700 (ICT) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Robert Elz To: Francis Dupont cc: Pim van Pelt , 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 In-Reply-To: <200206121207.g5CC7uT06279@givry.rennes.enst-bretagne.fr> References: <200206121207.g5CC7uT06279@givry.rennes.enst-bretagne.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jun 2002 22:08:41 +0700 Message-ID: <20785.1023894521@munnari.OZ.AU> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Date: Wed, 12 Jun 2002 14:07:56 +0200 From: Francis Dupont Message-ID: <200206121207.g5CC7uT06279@givry.rennes.enst-bretagne.fr> | => no, for instance in KAME you have to recompile the kernel with | "options IP6_AUTO_LINKLOCAL=0"... Then what you mean isn't what you said, I use KAME, and I have lots of link local addresses, and I never knew that option existed. I suspect that what you mean is "not automatically generate a link local based upon the IID" but that's a different thing to "explicitly set the link local address". | => on a reasonable system to set the link-local address or the IID are | equivalent. Only if you make the assumption that there is only one link-local address. That's not a reasonable assumption I don't think. There's no reason not to have several. eg: In general I prefer regular auto-config'd addresses (EUI-64 and all that in the IID). But for debugging (ping of the address, etc) it is nice if they also have nice easy to use LL addresses, like fe80::1 fe80::2 and such, so I just go assign those. It can also be convenient to have fe80::a.b.c.d where a.b.c.d is the IPv4 address assigned to the interface, as that's then a real easy way to match things, and know which is which (from the ancient past, I tend to simply know what IPv4 addr applies to every system around). But I want only one IID for the interface - which one of those should the kernel pick, if it was to treat them as equivalent. | => the subject of this thread is the extension of this to the ifconfig | command. Yes, I know, what I would like to be able to do is ifconfig interface inet6 iid 77 and if I do that before anything else has enabled IPv6 on the interface, it should simply use "77" (which would be a hex string with an arbitrary number of :'s up to 5, with an implied (maybe required explicit) leading ::) when it first enabled the interface and configures its first link local. Being able to specify "prefix xxx::" I would also like. The "iid" is mostly for hosts, "prefix" for routers (iid for routers too, but specifying both iid and prefix is just the same as specifying the whole address on a router, which doesn't get more prefixes from RAs). kre From Francis.Dupont@enst-bretagne.fr Wed Jun 12 10:18:06 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5CHI2E19483 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 10:18:06 -0700 (PDT) Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5CHI0b21381 for <6bone@ISI.EDU>; Wed, 12 Jun 2002 10:18:01 -0700 (PDT) Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1]) by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id g5CHBTC08313; Wed, 12 Jun 2002 19:11:29 +0200 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id TAA11194; Wed, 12 Jun 2002 19:11:30 +0200 (MET DST) Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id g5CHBTT07971; Wed, 12 Jun 2002 19:11:30 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200206121711.g5CHBTT07971@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Robert Elz cc: Pim van Pelt , 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 In-reply-to: Your message of Wed, 12 Jun 2002 22:08:41 +0700. <20785.1023894521@munnari.OZ.AU> Date: Wed, 12 Jun 2002 19:11:29 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: In your previous mail you wrote: | => no, for instance in KAME you have to recompile the kernel with | "options IP6_AUTO_LINKLOCAL=0"... Then what you mean isn't what you said, I use KAME, and I have lots of link local addresses, and I never knew that option existed. => this option is not documented but gives a way to disable the automatic (i.e. out of control) generation of a link-local address when an interface comes up. I suspect that what you mean is "not automatically generate a link local based upon the IID" but that's a different thing to "explicitly set the link local address". => this is a matter of wording: my idea is the IID doesn't exist by itself. And I assume that to have a link-local address is equivalent to have IPv6 enabled on the interface. | => on a reasonable system to set the link-local address or the IID are | equivalent. Only if you make the assumption that there is only one link-local address. That's not a reasonable assumption I don't think. There's no reason not to have several. => but there is no need to have several too... eg: In general I prefer regular auto-config'd addresses (EUI-64 and all that in the IID). => I agree but I'd like to have the control for the rare cases where something else is better. But for debugging (ping of the address, etc) it is nice if they also have nice easy to use LL addresses, like fe80::1 fe80::2 and such, so I just go assign those. It can also be convenient to have fe80::a.b.c.d where a.b.c.d is the IPv4 address assigned to the interface, as that's then a real easy way to match things, and know which is which (from the ancient past, I tend to simply know what IPv4 addr applies to every system around). => when cut&paste is not available fe80::1, ..., are very convenient. But I want only one IID for the interface - which one of those should the kernel pick, if it was to treat them as equivalent. => this is the point we disagree: I want only one link-local for the interface and the (unique) IID is taken from the link-local. I don't believe the result will be very different but this is not exactly the same thing. | => the subject of this thread is the extension of this to the ifconfig | command. Yes, I know, what I would like to be able to do is ifconfig interface inet6 iid 77 and if I do that before anything else has enabled IPv6 on the interface, it should simply use "77" (which would be a hex string with an arbitrary number of :'s up to 5, with an implied (maybe required explicit) leading ::) when it first enabled the interface and configures its first link local. Being able to specify "prefix xxx::" I would also like. The "iid" is mostly for hosts, "prefix" for routers (iid for routers too, but specifying both iid and prefix is just the same as specifying the whole address on a router, which doesn't get more prefixes from RAs). => I write this "ifconfig interface inet6 fe80::77/64" and "ifconfig interface inet6 xxx::/plen eui64 alias". As I've said our disagreement is only about details... Regards Francis.Dupont@enst-bretagne.fr PS: for an obscure reason KAME /etc/rc.network6 script supports full addresses and prefixes but in the wrong order... From jeroen@unfix.org Wed Jun 12 10:21:14 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5CHLEE20718 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 10:21:14 -0700 (PDT) Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5CHLDb23476 for <6bone@ISI.EDU>; Wed, 12 Jun 2002 10:21:13 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 7F1A33186; Wed, 12 Jun 2002 19:21:09 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 83CB4316A; Wed, 12 Jun 2002 19:21:05 +0200 (CEST) From: "Jeroen Massar" To: <6bone@ISI.EDU> Cc: Date: Wed, 12 Jun 2002 19:21:05 +0200 Organization: Unfix Message-ID: <001701c21235$8900e8a0$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Subject: [6bone] 3FFE:6700::/32 - Another pTLA space hijack Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: jeroen@purgatory:~$ whois 3FFE:6700::/32 inet6num: 3FFE:6700::/32 netname: AZURVP-V6 descr: AzurVP Network. None profit organisation. country: FR admin-c: AD5-6BONE tech-c: AD5-6BONE mnt-by: MNT-AZURVP changed: a_dailliez@yahoo.fr 20020611 source: 6BONE person: Amaury DAILLIEZ address: 506 chemin des ecoliers phone: +33614912547 nic-hdl: AD5-6BONE url: http://www.azurvp.net mnt-by: MNT-AZURVP changed: a_dailliez@yahoo.fr 20020605 source: 6BONE This is the second time some 'entity' has simply chosen to steal some address space. Previous time went unseen when (also some french entity) though to hijack 3ffe:6777::/32. They replied with "I didn't saw the rules concerning the pTLA spaces" which could also be read as "I didn't know I couldn't just take this cool castle, I didn't saw a sign when I went in". Could the 3ffe://16 object be protected with mnt-lower's to the real pTLA holders ? "Look mummy I got a /32 on the internet all for myself", but then written in leet... Greets, Jeroen From michel@arneill-py.sacramento.ca.us Wed Jun 12 10:43:36 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5CHhZE00869 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 10:43:35 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5CHhYb07287 for <6bone@ISI.EDU>; Wed, 12 Jun 2002 10:43:34 -0700 (PDT) Subject: RE: [6bone] 3FFE:6700::/32 - Another pTLA space hijack Date: Wed, 12 Jun 2002 10:43:28 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <2B81403386729140A3A899A8B39B046405E0FC@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Topic: [6bone] 3FFE:6700::/32 - Another pTLA space hijack Thread-Index: AcISNkDIPTut0AQsRjuO9ygJ/00ydgAAUoag content-class: urn:content-classes:message From: "Michel Py" To: "Jeroen Massar" , <6bone@ISI.EDU> Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g5CHhZE00869 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: The one thing that bugs me is that I don't even see what this kind of behavior achieves. Not only nobody will route it, but now he's on the blacklist. Maybe we should have an age verification system and not allow 14 year-old to register /32s. Amaury, nettoies tes merdes de la base de données, merci. Michel. -----Original Message----- From: Jeroen Massar [mailto:jeroen@unfix.org] Sent: Wednesday, June 12, 2002 10:21 AM To: 6bone@ISI.EDU Cc: a_dailliez@yahoo.fr Subject: [6bone] 3FFE:6700::/32 - Another pTLA space hijack jeroen@purgatory:~$ whois 3FFE:6700::/32 inet6num: 3FFE:6700::/32 netname: AZURVP-V6 descr: AzurVP Network. None profit organisation. country: FR admin-c: AD5-6BONE tech-c: AD5-6BONE mnt-by: MNT-AZURVP changed: a_dailliez@yahoo.fr 20020611 source: 6BONE person: Amaury DAILLIEZ address: 506 chemin des ecoliers phone: +33614912547 nic-hdl: AD5-6BONE url: http://www.azurvp.net mnt-by: MNT-AZURVP changed: a_dailliez@yahoo.fr 20020605 source: 6BONE This is the second time some 'entity' has simply chosen to steal some address space. Previous time went unseen when (also some french entity) though to hijack 3ffe:6777::/32. They replied with "I didn't saw the rules concerning the pTLA spaces" which could also be read as "I didn't know I couldn't just take this cool castle, I didn't saw a sign when I went in". Could the 3ffe://16 object be protected with mnt-lower's to the real pTLA holders ? "Look mummy I got a /32 on the internet all for myself", but then written in leet... Greets, Jeroen _______________________________________________ 6bone mailing list 6bone@mailman.isi.edu http://mailman.isi.edu/mailman/listinfo/6bone From fink@es.net Wed Jun 12 19:28:26 2002 Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5D2SPE11072 for <6bone@mailman.isi.edu>; Wed, 12 Jun 2002 19:28:25 -0700 (PDT) Received: from ([63.196.96.113]) by postal2.es.net (Postal Node 2) with SMTP id GQF37091; Wed, 12 Jun 2002 19:28:22 -0700 Message-Id: <5.1.0.14.0.20020612190531.02a62e90@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 12 Jun 2002 19:27:47 -0700 To: a_dailliez@yahoo.fr From: Bob Fink Cc: 6BONE List <6bone@mailman.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] Illegal registry of 3FFE:6700::/32 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Amaury DAILLIEZ, You are in violation of 6bone address allocation rules and general 6bone policy. Please reply to me immediately so I can at least understand your motivation for this, and hopefully you can maintain your future reputation with the 6bone/ipv6 community. Whatever your response, however, I have deleted your inet6num entry for 3FFE:6700::/32 as it is a hijacking of unallocated space. Depending on your reply, I will decided whether to delete your mntner and person objects as well. Also note that no 6bone pTLA is likely to peer with you, nor should be willing to do so, given the unauthorized nature of your inet6num entry and its prefix range. Hoping to hear from you, Bob Fink === >From: "Jeroen Massar" >To: <6bone@ISI.EDU> >Cc: >Subject: [6bone] 3FFE:6700::/32 - Another pTLA space hijack >Date: Wed, 12 Jun 2002 19:21:05 +0200 > >jeroen@purgatory:~$ whois 3FFE:6700::/32 > >inet6num: 3FFE:6700::/32 >netname: AZURVP-V6 >descr: AzurVP Network. None profit organisation. >country: FR >admin-c: AD5-6BONE >tech-c: AD5-6BONE >mnt-by: MNT-AZURVP >changed: a_dailliez@yahoo.fr 20020611 >source: 6BONE > >person: Amaury DAILLIEZ >address: 506 chemin des ecoliers >phone: +33614912547 >nic-hdl: AD5-6BONE >url: http://www.azurvp.net >mnt-by: MNT-AZURVP >changed: a_dailliez@yahoo.fr 20020605 >source: 6BONE > > >This is the second time some 'entity' has simply chosen to steal some >address space. >Previous time went unseen when (also some french entity) though to >hijack 3ffe:6777::/32. >They replied with "I didn't saw the rules concerning the pTLA spaces" >which could also be >read as "I didn't know I couldn't just take this cool castle, I didn't >saw a sign when I went in". > >Could the 3ffe://16 object be protected with mnt-lower's to the real >pTLA holders ? > >"Look mummy I got a /32 on the internet all for myself", but then >written in leet... > >Greets, > Jeroen > >_______________________________________________ >6bone mailing list >6bone@mailman.isi.edu >http://mailman.isi.edu/mailman/listinfo/6bone From kre@munnari.OZ.AU Thu Jun 13 03:28:21 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DASLE03015 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 03:28:21 -0700 (PDT) Received: from ratree.psu.ac.th ([202.28.96.5]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5DASKb27544 for <6bone@ISI.EDU>; Thu, 13 Jun 2002 03:28:20 -0700 (PDT) Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98]) by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id g5DARcM00364; Thu, 13 Jun 2002 17:27:38 +0700 (ICT) Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id g5DAP4s23513; Thu, 13 Jun 2002 17:25:11 +0700 (ICT) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Robert Elz To: Francis Dupont cc: Pim van Pelt , 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 In-Reply-To: <200206121711.g5CHBTT07971@givry.rennes.enst-bretagne.fr> References: <200206121711.g5CHBTT07971@givry.rennes.enst-bretagne.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Jun 2002 17:25:04 +0700 Message-ID: <23511.1023963904@munnari.OZ.AU> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Date: Wed, 12 Jun 2002 19:11:29 +0200 From: Francis Dupont Message-ID: <200206121711.g5CHBTT07971@givry.rennes.enst-bretagne.fr> | => this option is not documented but gives a way to disable the | automatic (i.e. out of control) generation of a link-local address | when an interface comes up. Thanks for the explanation, that's what I guessed when you mentioned it. | => this is a matter of wording: my idea is the IID doesn't exist by itself. That's something with which I disagree then, as I believe it does, though certainly it is a minor point. | And I assume that to have a link-local address is equivalent to have IPv6 | enabled on the interface. Yes I would treat those two as being essentially the same, no IPv6 operating interface should ever be without a LL address. | => but there is no need to have several too... No, it isn't required (except perhaps for a node acting as a proxy for another node - wouldn't a VRRP router need to take over the LL address of the router it is pretending to be, and wouldn't a HA need to at least act as if it owns the addresses of mobile nodes?) But there's a difference between not being required (if it never is) and not being useful. I see no reason to forbid multiple LL addresses for a node. | => this is the point we disagree: I want only one link-local for the | interface and the (unique) IID is taken from the link-local. Yes, that's where we disagree. | I don't believe the result will be very different but this is not exactly | the same thing. Not very different, we both want the same functionality, I just want a little more generality than you do. Also, if I decide that fe80::1 is the one and only LL addr for an interface, that doesn't mean that I want 3ffe:abcd::1 to necessarily be the global address assigned - in many cases I'd still like that one to be EUI-64 based. So, I really would prefer to separate the issues of assigning a LL address, and setting the IID that should be used to auto-configure addresses. | As I've said our disagreement is only about details... Almost, but not quite. | PS: for an obscure reason KAME /etc/rc.network6 script supports full | addresses and prefixes but in the wrong order... I use KAME as incorporated into NetBSD, which has no such script, (IPv6 stuff is handled along with IPv4 stuff in /etc/rc.d/network) so I'm afraid I can't quite follow that reference. kre From fink@es.net Thu Jun 13 07:28:56 2002 Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DESuE04250 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 07:28:56 -0700 (PDT) Received: from ([63.196.96.113]) by postal2.es.net (Postal Node 2) with SMTP id GQF37091; Thu, 13 Jun 2002 07:28:52 -0700 Message-Id: <5.1.0.14.0.20020613072453.0293b1d8@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 13 Jun 2002 07:27:59 -0700 To: 6BONE List <6bone@mailman.isi.edu> From: Bob Fink Cc: Bartosz Waszak Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] pTLA request ICPNET-PL - review closes 27 June 2002 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: 6bone Folk, ICPNET-PL has requested a pTLA allocation and I find their request fully compliant with RFC2772. The open review period for this will close 27 June 2002. Please send your comments to me or the list. Thanks, Bob === >Date: Thu, 13 Jun 2002 09:50:16 +0200 >From: Bartosz Waszak >To: Bob Fink >Subject: pTLA Request for ICPNET (AS13110), resubmit > >Hello! > >Here we present our corrected application for a 6Bone pTLA. > >RFC 2772: > >7. Guidelines for 6Bone pTLA sites > > > > The following rules apply to qualify for a 6Bone pTLA allocation. > > It should be recognized that holders of 6Bone pTLA allocations are > > expected to provide production quality backbone network services > > for the 6Bone. > > > > 1. The pTLA Applicant must have a minimum of three (3) months > > qualifying experience as a 6Bone end-site or pNLA transit. During > > the entire qualifying period the Applicant must be operationally > > providing the following: > >We have about 6 months experience as a 6bone end-site. > > > a. Fully maintained, up to date, 6Bone Registry entries for their > > ipv6-site inet6num, mntner, and person objects, including each > > tunnel that the Applicant has. > >ipv6-site: ICPNET-PL >origin: AS13110 >descr: Internet Cable Provider (major broadband service in country) >country: PL >prefix: 3FFE:8010:7:11::/64 >prefix: 3FFE:8010:7:F00::/56 >prefix: 3FFE:8320:2:5::/64 >application: ping ontario.ipv6.icpnet.pl >application: www www.ipv6.icpnet.pl >application: smtp ontario.ipv6.icpnet.pl >application: ftp ftp.ipv6.icpnet.pl >tunnel: IPv6 in IPv4 ontario.ipv6.icpnet.pl -> 6bone-gw.6bone.pl >ICM-PL BGP4+ >tunnel: IPv6 in IPv4 ontario.ipv6.icpnet.pl -> ipv6-gw.man.poznan.pl >POZMAN BGP4+ >tunnel: IPv6 in IPv4 ontario.ipv6.icpnet.pl -> >nautilus.ipv6.icpnet.pl ICPNET STATIC >tunnel: IPv6 in IPv4 ontario.ipv6.icpnet.pl -> chaos.wmid.amu.edu.pl >UNDEFINE BGP4+ >contact: IS2-6BONE >remarks: joined projects: SCIFI (operational since Sep 2000) and UNISOFT >notify: ipv6@ipv6.icpnet.pl >mnt-by: MNT-SCIFI >changed: waszi@ipv6.icpnet.pl 20020611 >source: 6BONE > >inet6num: 3FFE:8010:7:F00::/56 >netname: ICPNET-PL >descr: Internet Cable Provider >country: PL >admin-c: BW3-6BONE >tech-c: IS2-6BONE >remarks: ICPNET, pilot project for transition Cable Modem access to ipv6 >notify: ipv6@ipv6.icpnet.pl >mnt-by: MNT-SCIFI >changed: waszi@ipv6.icpnet.pl 20020611 >source: 6BONE > >inet6num: 3FFE:8010:7:11::/64 >netname: ICPNET-PL >descr: Internet Cable Provider >country: PL >admin-c: BW3-6BONE >tech-c: IS2-6BONE >remarks: ICPNET, pilot project for transition Cable Modem access to ipv6 >notify: ipv6@ipv6.icpnet.pl >mnt-by: MNT-SCIFI >changed: waszi@ipv6.icpnet.pl 20020611 >source: 6BONE > >inet6num: 3FFE:8320:2:5::/64 >netname: ICPNET-PL >descr: Internet Cable Provider >country: PL >admin-c: BW3-6BONE >tech-c: IS2-6BONE >remarks: ICPNET, pilot project for transition Cable Modem access to ipv6 >notify: ipv6@ipv6.icpnet.pl >mnt-by: MNT-SCIFI >changed: waszi@ipv6.icpnet.pl 20020611 >source: 6BONE > >role: ICP Staff >address: ul. Owsiana 17 >address: 61-666 Poznan >address: POLAND >e-mail: ipv6@ipv6.icpnet.pl >admin-c: BW3-6BONE >tech-c: KP4-6BONE >nic-hdl: IS2-6BONE >mnt-by: MNT-SCIFI >changed: waszi@ipv6.icpnet.pl 20020611 >source: 6BONE > >person: Bartosz Waszak >address: ul. Owsiana 17 >address: 61-666 Poznan >address: POLAND >phone: +48618280132 >e-mail: waszi@ipv6.icpnet.pl >nic-hdl: BW3-6BONE >url: http://www.ipv6.icpnet.pl/ >notify: waszi@ipv6.icpnet.pl >changed: waszi@ipv6.icpnet.pl 20020603 >source: 6BONE > >person: Krzysztof Palicki >address: ul. Owsiana 17 >address: 61-666 Poznan >address: POLAND >phone: +48618280132 >e-mail: chris@poczta.icpnet.pl >nic-hdl: KP4-6BONE >url: http://www.ipv6.icpnet.pl/ >notify: chris@poczta.icpnet.pl >changed: chris@poczta.icpnet.pl 20020612 >source: 6BONE > > > b. Fully maintained, and reliable, BGP4+ peering and connectivity > > between the Applicant's boundary router and the appropriate > > connection point into the 6Bone. This router must be IPv6 > > pingable. This criteria is judged by members of the 6Bone > > Operations Group at the time of the Applicant's pTLA request. > >We have three BGP4+ peerings, and some static tunnels + native IPv6 >connections. > >BGP router identifier 62.21.98.6, local AS number 13110 >451 BGP AS-PATH entries >7 BGP community entries > >Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ >Up/Down State/PfxRcd > >ICM: >3ffe:8010:7:11::1 > 4 8664 32644 5793 0 0 0 01:02:02 217 > >AMUWMID: >3ffe:8010:7:6a00::3e > 4 58502 4991 1295 0 0 0 21:22:09 217 > >POZMAN: >3ffe:8320:1::30 4 9112 15817 10549 0 0 0 01w0d05h 211 > >router is pingable via IPv6: >[root@voyager /]# ping6 ontario.ipv6.icpnet.pl >PING ontario.ipv6.icpnet.pl(3ffe:8320:2:5:2::1) 56 data bytes >64 bytes from 3ffe:8320:2:5:2::1: icmp_seq=1 ttl=63 time=8.792 msec >64 bytes from 3ffe:8320:2:5:2::1: icmp_seq=2 ttl=63 time=7.087 msec > > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > > entries for the Applicant's router(s) and at least one host > > system. > >We maintain DNS entries for ipv6.icpnet.pl and for 3ffe:8010:7:f00::/56 > >Our primary DNS server for IPv6 is: ontario.icpnet.pl >Secondary: ww2.icpnet.pl > >;; global options: printcmd >ipv6.icpnet.pl. 600 IN SOA ontario.icpnet.pl. >hostmaster.ontario.icpnet.pl. 2002061101 10800 600 604800 86400 >ipv6.icpnet.pl. 600 IN NS ww2.icpnet.pl. >ipv6.icpnet.pl. 600 IN NS ontario.icpnet.pl. >ipv6.icpnet.pl. 600 IN MX 0 voyager.ipv6.icpnet.pl. >ipv6.icpnet.pl. 600 IN MX 10 ontario.ipv6.icpnet.pl. >z-portal-gw.amuwmid-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11:2::1 >ftp.ipv6.icpnet.pl. 600 IN CNAME ontario.ipv6.icpnet.pl. >z-voyager-gw.icm-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11::1 >z-portal-gw.icpnet-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::c >z-voyager-gw.icpnet-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::a >irc.ipv6.icpnet.pl. 600 IN CNAME ontario.ipv6.icpnet.pl. >z-portal-gw.ktnet-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::1 >localhost.ipv6.icpnet.pl. 600 IN A 127.0.0.1 >nautilus.ipv6.icpnet.pl. 600 IN A 62.21.3.239 >nautilus.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8320:2:5:1::2 >news.ipv6.icpnet.pl. 600 IN CNAME ontario.ipv6.icpnet.pl. >ontario.ipv6.icpnet.pl. 600 IN A 62.21.98.6 >ontario.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8320:2:5:2::1 >z-portal-gw.pbern-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::7 >z-portal-gw.pollus-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::5 >z-amuwmid-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11:2:: >z-icpnet-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::d >z-ktnet-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed:: >z-pbern-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::6 >z-pollus-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::4 >z-thelema-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::2 >z-undefine-gw.portal-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::8 >z-portal-gw.thelema-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::3 >z-portal-gw.undefine-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::9 >voyager.ipv6.icpnet.pl. 600 IN A 62.21.3.1 >voyager.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8320:2:5:1::1 >z-icm-gw.voyager-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:11::2 >z-icpnet-gw.voyager-gw.ipv6.icpnet.pl. 600 IN AAAA 3ffe:8010:7:f00:feed::b >www.ipv6.icpnet.pl. 600 IN CNAME ontario.ipv6.icpnet.pl. >ipv6.icpnet.pl. 600 IN SOA ontario.icpnet.pl. >hostmaster.ontario.icpnet.pl. 2002061101 10800 600 604800 86400 >;; Query time: 23 msec >;; SERVER: 62.21.98.6#53(ontario.icpnet.pl) >;; WHEN: Wed Jun 12 21:03:10 2002 >;; XFR size: 36 records > >$ORIGIN . >$TTL 600 ; 10 minutes >f.0.7.0.0.0.0.1.0.8.e.f.f.3.ip6.int IN SOA dns.portalcafe.pl. >root\@scifi.eu.org. ( > 2002051806 ; serial > 10800 ; refresh (3 hours) > 600 ; retry (10 minutes) > 604800 ; expire (1 week) > 86400 ; minimum (1 day) > ) > NS dns.portalcafe.pl. > NS voyager.ipv6.icpnet.pl. >$ORIGIN f.0.7.0.0.0.0.1.0.8.e.f.f.3.ip6.int. >$ORIGIN 0.0.0.0.0.0.0.0.0.0.0.d.e.e.f.0.0.f.0.7.0.0.0.0.1.0.8.e.f.f.3.ip6.int. >0 PTR z-ktnet-gw.portal-gw.ipv6.icpnet.pl. >1 PTR z-portal-gw.ktnet-gw.ipv6.icpnet.pl. >2 PTR z-thelema-gw.portal-gw.ipv6.icpnet.pl. >3 PTR z-portal-gw.thelema-gw.ipv6.icpnet.pl. >4 PTR z-pollus-gw.portal-gw.ipv6.icpnet.pl. >5 PTR z-portal-gw.pollus-gw.ipv6.icpnet.pl. >6 PTR z-pbern-gw.portal-gw.ipv6.icpnet.pl. >7 PTR z-portal-gw.pbern-gw.ipv6.icpnet.pl. >8 PTR z-undefine-gw.portal-gw.ipv6.icpnet.pl. >9 PTR z-portal-gw.undefine-gw.ipv6.icpnet.pl. >a PTR z-voyager-gw.icpnet-gw.ipv6.icpnet.pl. >b PTR z-icpnet-gw.voyager-gw.ipv6.icpnet.pl. >c PTR z-portal-gw.icpnet-gw.ipv6.icpnet.pl. >d PTR z-icpnet-gw.portal-gw.ipv6.icpnet.pl. > > > d. A fully maintained, and reliable, IPv6-accessible system > > providing, at a mimimum, one or more web pages, describing the > > Applicant's IPv6 services. This server must be IPv6 pingable. > >Our new IPv6 Accessible web page is under construction. >Currently on http://www.ipv6.icpnet.pl/ is info about how >to contact with us. > > > 2. The pTLA Applicant MUST have the ability and intent to provide > > "production-quality" 6Bone backbone service. Applicants must > > provide a statement and information in support of this claim. > > This MUST include the following: > > > > a. A support staff of two persons minimum, three preferable, with > > person attributes registered for each in the ipv6-site object > > for the pTLA applicant. > >person: Bartosz Waszak >e-mail: waszi@ipv6.icpnet.pl >nic-hdl: BW3-6BONE > >person: Krzysztof Palicki >e-mail: chris@poczta.icpnet.pl >nic-hdl: KP4-6BONE > > > b. A common mailbox for support contact purposes that all support > > staff have acess to, pointed to with a notify attribute in the > > ipv6-site object for the pTLA Applicant. > >ipv6@ipv6.icpnet.pl > >This address is configured as a "e-mail" attribute in the "role" object. > > > 3. The pTLA Applicant MUST have a potential "user community" that > > would be served by its becoming a pTLA, e.g., the Applicant is a > > major provider of Internet service in a region, country, or focus > > of interest. Applicant must provide a statement and information in > > support this claim. > >ICP is providing internet access by cable modems or directly to >our backbone by Ethernet. We have about 10'000 users, >so we are in Poland one of the major ISPs. > > > 4. The pTLA Applicant MUST commit to abide by the current 6Bone > > operational rules and policies as they exist at time of its > > application, and agree to abide by future 6Bone backbone > > operational rules and policies as they evolve by consensus of the > > 6Bone backbone and user community. > >We agree to abide by the rules as they exist now and as they may evolve in >the future. > > > When an Applicant seeks to receive a pTLA allocation, it will apply > > to the 6Bone Operations Group (see section 8 below) by providing to > > the Group information in support of its claims that it meets the > > criteria above. > > > >8. 6Bone Operations Group > > > > The 6Bone Operations Group is the group in charge of monitoring and > > policing adherence to the current rules. Membership in the 6Bone > > Operations Group is mandatory for, and restricted to, sites > > connected to the 6Bone. > > > > The 6Bone Operations Group is currently defined by those members of > > the existing 6Bone mailing list who represent sites participating in > > the 6Bone. Therefore it is incumbent on relevant site contacts to > > join the 6Bone mailing list. Instructions on how to join the list > > are maintained on the 6Bone web site at < http://www.6bone.net>. > >Regards > >-- >Bartosz Waszak >Internet Cable Provider Sp. z o.o. >(http://www.icpnet.pl/) From rvdp@kirk.rvdp.org Thu Jun 13 16:12:48 2002 Received: from kirk.rvdp.org (node147c0.a2000.nl [24.132.71.192]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5DNClE13480 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 16:12:47 -0700 (PDT) Received: from kirk.rvdp.org (localhost [IPv6:::1]) by kirk.rvdp.org (8.12.3/8.12.3) with ESMTP id g5DNCj2Z039019 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 01:12:45 +0200 (CEST) (envelope-from rvdp@kirk.rvdp.org) Received: (from rvdp@localhost) by kirk.rvdp.org (8.12.3/8.12.3/Submit) id g5DNCjFj039018 for 6bone@mailman.isi.edu; Fri, 14 Jun 2002 01:12:45 +0200 (CEST) Date: Fri, 14 Jun 2002 01:12:45 +0200 From: Ronald van der Pol To: 6bone@mailman.isi.edu Message-ID: <20020613231245.GA36510@rvdp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.99i Subject: [6bone] problem with ftp.netbsd.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: I cannot ftp to ftp.bsd.org: spock$ ftp ftp.netbsd.org Connected to ftp.netbsd.org. Tcpdump shows (spock is 2001:610:508:1001:260:1dff:fef6:7ff9): 00:37:02.458730 2001:610:508:1001:260:1dff:fef6:7ff9.1310 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: S [tcp sum ok] 3384697445:3384697445(0) win 57344 (len 40, hlim 64) 00:37:02.764566 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21 > 2001:610:508:1001:260:1dff:fef6:7ff9.1310: S [tcp sum ok] 131386982:131386982(0) ack 3384697446 win 32768 (len 40, hlim 54) 00:37:02.764799 2001:610:508:1001:260:1dff:fef6:7ff9.1310 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: . [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:37:10.547821 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:38:14.548802 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:39:18.549774 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:40:22.550736 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:41:26.551704 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:42:30.552678 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) 00:43:34.553613 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: R [tcp sum ok] 2:2(0) ack 1 win 58548 (len 20, hlim 64) Several people have informed me that they can reach ftp.netbsd.org over IPv6. I am thinking about a routing problem from ftp.netbsd.org towards me, but on the other hand the tcpdump above shows I do get one packet from ftp.netbsd.org in the handshaking phase. I tried this on freebsd-stable, netbsd-current and netbsd 1.5.3 with the same result. 'ftp -4 ftp.netbsd.org' is working fine. v6 ftp to other v6 ftp servers is also working, so no firewall issues. Traceroute is also working: spock$ traceroute6 -q 1 -l ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:610:508:1001:260:1dff:fef6:7ff9, 30 hops max, 12 byte packets 1 kirk (2001:610:508:1001:220:afff:fec6:4faa) 3.201 ms 2 surrogate.ipv6.surfnet.nl (2001:610:508:1000::1) 7.9 ms 3 surfnet-bv.Amsterdam.ipv6.surf.net (2001:610:0:2001::1) 13.627 ms 4 PO4-0.CR2.Amsterdam1.surf.net (2001:610:16:3048::49) 16.897 ms 5 PO0-0.BR2.Amsterdam1.surf.net (2001:610:16:6004::6) 15.136 ms 6 ams-ix.sara.xs4all.net (2001:7f8:1::a500:3265:1) 13.938 ms 7 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 12.436 ms 8 3ffe:1280:1001:1::1 (3ffe:1280:1001:1::1) 382.62 ms 9 3ffe:80a::1 (3ffe:80a::1) 203.762 ms 10 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 204.275 ms 11 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 306.499 ms Any suggestions what could be wrong here? rvdp PS This is quite annoying because I have the same problem with www.netbsd.org and I use mozilla-1.0. From jeroen@unfix.org Thu Jun 13 17:14:57 2002 Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E0EtE14952 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 17:14:56 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 569FE3186; Fri, 14 Jun 2002 02:14:52 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id C6DCA3148; Fri, 14 Jun 2002 02:14:44 +0200 (CEST) From: "Jeroen Massar" To: "'Ronald van der Pol'" , <6bone@mailman.isi.edu> Subject: RE: [6bone] problem with ftp.netbsd.org Date: Fri, 14 Jun 2002 02:14:44 +0200 Organization: Unfix Message-ID: <000b01c21338$7d28fe10$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020613231245.GA36510@rvdp.org> X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > -----Original Message----- > From: 6bone-admin@mailman.isi.edu > [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Ronald van der Pol > Sent: Friday, 14 June 2002 01:13 > To: 6bone@mailman.isi.edu > Subject: [6bone] problem with ftp.netbsd.org > > > I cannot ftp to ftp.bsd.org: > > spock$ ftp ftp.netbsd.org > Connected to ftp.netbsd.org. > > > Tcpdump shows (spock is 2001:610:508:1001:260:1dff:fef6:7ff9): > 8<---------------- jeroen@purgatory:~$ telnet -6 www.netbsd.org 80 Trying 3ffe:8050:201:1860:290:27ff:feab:19a7... Connected to www.netbsd.org. Escape character is '^]'. GET / HTTP/1.1 Host: www.netbsd.org ----------->8 wait wait wait, but no reply :( > Several people have informed me that they can reach ftp.netbsd.org over IPv6. HTTP has the same problem. > I am thinking about a routing > problem from ftp.netbsd.org towards me, > but on the other hand the tcpdump above shows I do get one packet from > ftp.netbsd.org in the handshaking phase. I even get a connect ;) > I tried this on freebsd-stable, netbsd-current and netbsd 1.5.3 with the same result. > Any suggestions what could be wrong here? Then again I am probably behind the same uplink (IPng/Intouch :) So it could still be between the netherlands and the US.... Greets, Jeroen From randy@psg.com Thu Jun 13 17:21:49 2002 Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E0LmE17612 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 17:21:49 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 4.04) id 17IeqV-000IXb-00; Thu, 13 Jun 2002 17:21:43 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jeroen Massar" Cc: "'Ronald van der Pol'" , <6bone@mailman.isi.edu> Subject: RE: [6bone] problem with ftp.netbsd.org References: <20020613231245.GA36510@rvdp.org> <000b01c21338$7d28fe10$420d640a@unfix.org> Message-Id: Date: Thu, 13 Jun 2002 17:21:43 -0700 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: % ping6 ftp.netbsd.org PING6(56=40+8+8 bytes) 2001:418:1:0:2e0:18ff:fe02:6ec9 --> 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea 16 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, icmp_seq=0 hlim=59 time=33.077 ms 16 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, icmp_seq=1 hlim=59 time=32.97 ms 16 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, icmp_seq=2 hlim=59 time=32.597 ms % uname -a FreeBSD roam.psg.com 4.6-RC FreeBSD 4.6-RC #18: Fri May 24 14:09:23 PDT 2002 6 From itojun@itojun.org Thu Jun 13 17:51:12 2002 Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E0pBE29162 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 17:51:12 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id DEDDB4B25; Fri, 14 Jun 2002 09:51:07 +0900 (JST) To: Ronald van der Pol Cc: 6bone@mailman.isi.edu In-reply-to: Ronald.vanderPol's message of Fri, 14 Jun 2002 01:12:45 +0200. <20020613231245.GA36510@rvdp.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] problem with ftp.netbsd.org From: itojun@iijlab.net Date: Fri, 14 Jun 2002 09:51:07 +0900 Message-ID: <3827.1024015867@itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >I cannot ftp to ftp.bsd.org: >Several people have informed me that they can reach ftp.netbsd.org over >IPv6. > >I am thinking about a routing problem from ftp.netbsd.org towards me, >but on the other hand the tcpdump above shows I do get one packet from >ftp.netbsd.org in the handshaking phase. > >I tried this on freebsd-stable, netbsd-current and netbsd 1.5.3 with the >same result. > >Any suggestions what could be wrong here? there seems to be some config mistake within ISI (who hosts tp.netbsd.org), regarding to link MTU setting of tunnel interface. i heard that they have changed the config so it should be better now. (at least, it is much better for me) i myself have experienced it before - Juniper sets tunnel interface MTU to infinity, and KAME uses 1280. itojun From jeroen@unfix.org Thu Jun 13 17:55:50 2002 Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E0tnE00562 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 17:55:49 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 9ACCC3186; Fri, 14 Jun 2002 02:55:46 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 9EEAA316A; Fri, 14 Jun 2002 02:55:39 +0200 (CEST) From: "Jeroen Massar" To: "'Randy Bush'" Cc: "'Ronald van der Pol'" , <6bone@mailman.isi.edu> Subject: RE: [6bone] problem with ftp.netbsd.org Date: Fri, 14 Jun 2002 02:55:39 +0200 Organization: Unfix Message-ID: <001301c2133e$33f85cd0$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Randy Bush [mailto:randy@psg.com] wrote: > % ping6 ftp.netbsd.org > PING6(56=40+8+8 bytes) 2001:418:1:0:2e0:18ff:fe02:6ec9 --> > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea > 16 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, > icmp_seq=0 hlim=59 time=33.077 ms > 16 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, > icmp_seq=1 hlim=59 time=32.97 ms > 16 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, > icmp_seq=2 hlim=59 time=32.597 ms > > % uname -a > FreeBSD roam.psg.com 4.6-RC FreeBSD 4.6-RC #18: Fri May 24 > 14:09:23 PDT 2002 6 I got some of those too, they will syn/ack but no data :( tunnelserver.ipng.nl: 8<-------------------- jeroen@tunnelserver:~$ traceroute6 ftp6.netbsd.org traceroute6 to ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:6e0::250:4ff:fe4a:7708, 30 hops max, 16 byte packets 1 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 1.75 ms 0.411 ms 0.388 ms 2 3ffe:1280:1001:1::1 (3ffe:1280:1001:1::1) 298.968 ms * 315.534 ms 3 3ffe:80a::1 (3ffe:80a::1) 159.079 ms 159.268 ms 158.932 ms 4 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 160.742 ms 160.487 ms 159.343 ms 5 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 159.866 ms 159.95 ms 160.722 ms jeroen@tunnelserver:~$ ping6 ftp6.netbsd.org PING ftp6.netbsd.org(ftp6.netbsd.org) 56 data bytes 64 bytes from ftp6.netbsd.org: icmp_seq=0 time=160.3 ms 64 bytes from ftp6.netbsd.org: icmp_seq=1 time=349.0 ms 64 bytes from ftp6.netbsd.org: icmp_seq=2 time=197.7 ms 64 bytes from ftp6.netbsd.org: icmp_seq=3 time=202.2 ms 64 bytes from ftp6.netbsd.org: icmp_seq=4 time=206.6 ms 64 bytes from ftp6.netbsd.org: icmp_seq=5 time=210.5 ms --- ftp6.netbsd.org ping6 statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 160.3/221.0/349.0 ms jeroen@tunnelserver:~$ uname -a Linux tunnelserver 2.4.17ipng #1 Fri Jan 25 14:54:39 CET 2002 i586 unknown jeroen@tunnelserver:~$ telnet ftp6.netbsd.org 21 Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... Connected to ftp6.netbsd.org. Escape character is '^]'. -------------------->8 It will connect, but nothing more, something is dropping packets I think. Unfortunatly these boxes all take the same route over amsterdam.intouch (2001:6e0::2) so the problem could be behind that box, though I don't think it's that one as I kinda trust it :) Odd thing: connecting to port 80 on the ftp6.netbsd.org doesn't get refused. Is this thing a v6 loadbalancer ? :) Greets, Jeroen From itojun@itojun.org Thu Jun 13 18:13:43 2002 Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E1DgE06483 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 18:13:42 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 8B6D74B24 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 10:13:40 +0900 (JST) To: 6bone@mailman.isi.edu In-reply-to: itojun's message of Fri, 14 Jun 2002 09:51:07 +0900. <3827.1024015867@itojun.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] problem with ftp.netbsd.org From: itojun@iijlab.net Date: Fri, 14 Jun 2002 10:13:40 +0900 Message-ID: <4065.1024017220@itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > there seems to be some config mistake within ISI (who hosts s/ISI/ISC/ itojun From darko@hytron.net Thu Jun 13 18:18:02 2002 Received: from hytron.hytron.net (root@pcp01177798pcs.shlb1201.mi.comcast.net [68.60.225.208]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E1I2E07064 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 18:18:02 -0700 (PDT) Received: from localhost (darko@localhost) by hytron.hytron.net (8.11.4/8.11.4) with ESMTP id g5E1Hvv10386; Thu, 13 Jun 2002 21:17:57 -0400 Date: Thu, 13 Jun 2002 21:17:57 -0400 (EDT) From: Darko To: Ronald van der Pol cc: <6bone@mailman.isi.edu> Subject: Re: [6bone] problem with ftp.netbsd.org In-Reply-To: <20020613231245.GA36510@rvdp.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Try nslookup -q=AAAA ftp.bsd.org You will see that there is no AAAA record for that host, therefore you cannot use IPv6 to reach it. Darko On Fri, 14 Jun 2002, Ronald van der Pol wrote: > Date: Fri, 14 Jun 2002 01:12:45 +0200 > From: Ronald van der Pol > To: 6bone@mailman.isi.edu > Subject: [6bone] problem with ftp.netbsd.org > > I cannot ftp to ftp.bsd.org: > > spock$ ftp ftp.netbsd.org > Connected to ftp.netbsd.org. > > > Tcpdump shows (spock is 2001:610:508:1001:260:1dff:fef6:7ff9): > > 00:37:02.458730 2001:610:508:1001:260:1dff:fef6:7ff9.1310 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: S [tcp sum ok] 3384697445:3384697445(0) win 57344 (len 40, hlim 64) > 00:37:02.764566 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21 > 2001:610:508:1001:260:1dff:fef6:7ff9.1310: S [tcp sum ok] 131386982:131386982(0) ack 3384697446 win 32768 (len 40, hlim 54) > 00:37:02.764799 2001:610:508:1001:260:1dff:fef6:7ff9.1310 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: . [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:37:10.547821 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:38:14.548802 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:39:18.549774 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:40:22.550736 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:41:26.551704 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:42:30.552678 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: F [tcp sum ok] 1:1(0) ack 1 win 58548 (len 32, hlim 64) > 00:43:34.553613 2001:610:508:1001:260:1dff:fef6:7ff9.1308 > 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea.21: R [tcp sum ok] 2:2(0) ack 1 win 58548 (len 20, hlim 64) > > Several people have informed me that they can reach ftp.netbsd.org over > IPv6. > > I am thinking about a routing problem from ftp.netbsd.org towards me, > but on the other hand the tcpdump above shows I do get one packet from > ftp.netbsd.org in the handshaking phase. > > I tried this on freebsd-stable, netbsd-current and netbsd 1.5.3 with the > same result. > > 'ftp -4 ftp.netbsd.org' is working fine. v6 ftp to other v6 ftp servers > is also working, so no firewall issues. Traceroute is also working: > spock$ traceroute6 -q 1 -l ftp.netbsd.org > traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:610:508:1001:260:1dff:fef6:7ff9, 30 hops max, 12 byte packets > 1 kirk (2001:610:508:1001:220:afff:fec6:4faa) 3.201 ms > 2 surrogate.ipv6.surfnet.nl (2001:610:508:1000::1) 7.9 ms > 3 surfnet-bv.Amsterdam.ipv6.surf.net (2001:610:0:2001::1) 13.627 ms > 4 PO4-0.CR2.Amsterdam1.surf.net (2001:610:16:3048::49) 16.897 ms > 5 PO0-0.BR2.Amsterdam1.surf.net (2001:610:16:6004::6) 15.136 ms > 6 ams-ix.sara.xs4all.net (2001:7f8:1::a500:3265:1) 13.938 ms > 7 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 12.436 ms > 8 3ffe:1280:1001:1::1 (3ffe:1280:1001:1::1) 382.62 ms > 9 3ffe:80a::1 (3ffe:80a::1) 203.762 ms > 10 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 204.275 ms > 11 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 306.499 ms > > Any suggestions what could be wrong here? > > rvdp > > PS This is quite annoying because I have the same problem with > www.netbsd.org and I use mozilla-1.0. > _______________________________________________ > 6bone mailing list > 6bone@mailman.isi.edu > http://mailman.isi.edu/mailman/listinfo/6bone > From tony@lava.net Thu Jun 13 18:45:40 2002 Received: from babingka.lava.net (babingka.lava.net [64.65.64.26]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E1jcE14779 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 18:45:40 -0700 (PDT) Received: from malasada.lava.net ([64.65.64.17]) (1151 bytes) by babingka.lava.net; Thu, 13 Jun 2002 15:45:31 -1000 (HST) via sendmail [esmtp] id for <6bone@mailman.isi.edu> Date: Thu, 13 Jun 2002 15:45:30 -1000 (HST) From: Antonio Querubin To: Darko cc: Ronald van der Pol , <6bone@mailman.isi.edu> Subject: Re: [6bone] problem with ftp.netbsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Thu, 13 Jun 2002, Darko wrote: > Try nslookup -q=AAAA ftp.bsd.org > You will see that there is no AAAA record for that host, therefore you > cannot use IPv6 to reach it. True enough but the problem was/is with ftp.netbsd.org, not ftp.bsd.org. % host -a ftp.netbsd.org Trying null domain rcode = 0 (Success), ancount=2 The following answer is not verified as authentic by the server: ftp.netbsd.org 3600 IN A 204.152.184.75 ftp.netbsd.org 3600 IN AAAA 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea From tlangdon@atctraining.com.au Thu Jun 13 19:50:34 2002 Received: from atc-mail-db.atctraining.com.au (gw2.atctraining.com.au [210.8.174.5]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E2oXE02721 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 19:50:33 -0700 (PDT) Received: by atc-mail-db.atctraining.com.au with Internet Mail Service (5.5.2448.0) id ; Fri, 14 Jun 2002 12:50:28 +1000 Message-ID: From: Tony Langdon To: "'Darko'" , Ronald van der Pol Cc: 6bone@mailman.isi.edu Subject: RE: [6bone] problem with ftp.netbsd.org Date: Fri, 14 Jun 2002 12:50:18 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g5E2oXE02721 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Try nslookup -q=AAAA ftp.bsd.org > You will see that there is no AAAA record for that host, therefore you > cannot use IPv6 to reach it. Hmm, the site was ftp.netbsd.org,which does have IPv6 address. ; <<>> DiG 9.2.0 <<>> ftp.netbsd.org any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40363 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 6 ;; QUESTION SECTION: ;ftp.netbsd.org. IN ANY ;; ANSWER SECTION: ftp.netbsd.org. 3594 IN A 204.152.184.75 ftp.netbsd.org. 3594 IN AAAA 3ffe:8050:201:1860:2a0:c9ff:feed :b7ea ..... Now for a ping... [root@ipv6gw1 rc.d]# ping6 ftp.netbsd.org PING ftp.netbsd.org(3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 56 data bytes 64 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea: icmp_seq=2 ttl=58 time=410 ms 64 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea: icmp_seq=3 ttl=58 time=430 ms 64 bytes from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea: icmp_seq=4 ttl=58 time=420 ms FTP connection worked fine for me also, no dramas [root@ipv6gw1 rc.d]# ftp 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea Connected to 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea (3ffe:8050:201:1860:2a0:c9ff: feed:b7ea). 220 ftp6.netbsd.org FTP server (NetBSD-ftpd 20020201) ready. Name (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea:root): anonymous 331 Guest login ok, type your name as password. Password: Also worked by name on IPv6 --- Outgoing mail has been scanned for Viruses. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.370 / Virus Database: 205 - Release Date: 5/06/2002 This correspondence is for the named person’s use only. It may contain confidential or legally privileged information or both. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any opinions expressed in this message are those of the individual sender. From jeroen@unfix.org Thu Jun 13 19:58:18 2002 Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E2wHE04032 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 19:58:17 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id E8C493186; Fri, 14 Jun 2002 04:58:14 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 30E7D316A; Fri, 14 Jun 2002 04:58:11 +0200 (CEST) From: "Jeroen Massar" To: , "'Ronald van der Pol'" Cc: <6bone@mailman.isi.edu> Subject: RE: [6bone] problem with ftp.netbsd.org Date: Fri, 14 Jun 2002 04:58:11 +0200 Organization: Unfix Message-ID: <001b01c2134f$523033b0$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <3827.1024015867@itojun.org> X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: itojun@iijlab.net wrote: > >I cannot ftp to ftp.bsd.org: > >Several people have informed me that they can reach ftp.netbsd.org over IPv6. > > > >I am thinking about a routing problem from ftp.netbsd.org towards me, > >but on the other hand the tcpdump above shows I do get one packet from > >ftp.netbsd.org in the handshaking phase. > > > >I tried this on freebsd-stable, netbsd-current and netbsd 1.5.3 with the > >same result. > > > >Any suggestions what could be wrong here? > > there seems to be some config mistake within ISI (who hosts > tp.netbsd.org), regarding to link MTU setting of tunnel interface. > i heard that they have changed the config so it should be better now. > (at least, it is much better for me) > > i myself have experienced it before - Juniper sets tunnel interface MTU > to infinity, and KAME uses 1280. Let's try again from purgatory.unfix.org: 8<-------------------------- jeroen@purgatory:~$ telnet www.jp.freebsd.org 21 Trying 3ffe:501:185b:101:2a0:24ff:fe57:e561... Connected to www.jp.freebsd.org. Escape character is '^]'. 220 tortoise.jp.freebsd.org FTP server (Version 6.00) ready. ^] telnet> q Connection closed. jeroen@purgatory:~$ telnet ftp6.netbsd.org 21 Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... Connected to ftp6.netbsd.org. Escape character is '^]'. -------------------------->8 Still no response back :( Greets, Jeroen From stuart@tech.org Thu Jun 13 20:51:19 2002 Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E3pIE01813 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 20:51:18 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5E3pCk01953 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 20:51:12 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206140351.g5E3pCk01953@lo.tech.org> To: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Date: Thu, 13 Jun 2002 20:51:12 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: If anyone is still having problems with TCP sessions to/from ftp.netbsd.org, please send me traceroutes. Thanks, Stephen From mail@thomas--schaefer.de Thu Jun 13 23:36:02 2002 Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E6a1E11684 for <6bone@mailman.isi.edu>; Thu, 13 Jun 2002 23:36:01 -0700 (PDT) Received: from fwd00.sul.t-online.de by mailout09.sul.t-online.com with smtp id 17Ikgf-0002TU-03; Fri, 14 Jun 2002 08:35:57 +0200 Received: from witz (520065784698-0001@[217.228.221.82]) by fmrl00.sul.t-online.com with esmtp id 17Ikgd-2JKKUSC; Fri, 14 Jun 2002 08:35:55 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Thomas Schaefer To: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Date: Fri, 14 Jun 2002 08:35:52 +0200 User-Agent: KMail/1.4.1 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200206140835.52758.mail@thomas--schaefer.de> X-Sender: 520065784698-0001@t-dialin.net Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Am Freitag, 14. Juni 2002 03:45 schrieb Antonio Querubin: > On Thu, 13 Jun 2002, Darko wrote: > > Try nslookup -q=AAAA ftp.bsd.org > > You will see that there is no AAAA record for that host, therefore you > > cannot use IPv6 to reach it. > > True enough but the problem was/is with ftp.netbsd.org, not ftp.bsd.org. > > And now it seems to work very well: ----------------------------------------------- thomas@witz:~> nslookup -query=any ftp.netbsd.org Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 212.185.252.201 Address: 212.185.252.201#53 Name: ftp.netbsd.org Address: 204.152.184.75 ftp.netbsd.org has AAAA address 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea thomas@witz:~> ftp 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea Connected to 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea. 220 ftp6.netbsd.org FTP server (NetBSD-ftpd 20020201) ready. Name (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea:thomas): anonymous 331 Guest login ok, type your name as password. Password: 230- Welcome to FTP.NetBSD.ORG Located in Palo Alto, CA, USA , , /( )` Home of \ \___ / | 100Mb Connectivity Courtesy of the FREE /- _ `-/ ' Internet Software Consortium MULTIPLATFORM (/\/ \ \ /\ NetBSD 1.5.2 OS / / | ` \ \ O O ) / | +--- Currently Supported Platforms ----+ \ `-^--'`< ' | DEC ALPHA, (STRONG)ARM32, ATARI, | \ (_.) _ ) / |BEBOX, COMMODORE AMIGA & MACROSYSTEMS | `.___/` / | DRACO, HP 300, INTEL x86, APPLE | `-----' / | MACINTOSH(68k & PPC, iMAC, G3, G4), | <----. __ / __ \ | MOTOROLA MVME68k, NEWS (68k & MIPS), | <----|====O)))==) \) /==== | NeXT, PC532, PMAX, POWERPC, SUN | <----' `--' `.__,' \ | SPARC(64), SUN 3/3X, DEC VAX, X68k | | | +--------------------------------------+ \ / MORE ARE UNDER DEVELOPMENT ______( (_ / \_____ (FL) ,' ,-----' | \ ALL FTP TRANSFERS AND COMMANDS ARE LOGGED. `--{__________) \/ 230- EXPORT NOTICE Please note that portions of this FTP site contain cryptographic software controlled under the Export Administration Regulations (EAR). None of this software may be downloaded or otherwise exported or re-exported into (or to a national or resident of) Cuba, Iraq, Libya, Sudan, North Korea, Iran, Syria or any other country to which the U.S. has embargoed goods. By downloading or using said software, you are agreeing to the foregoing and you are representing and warranting that you are not located in, under the control of, or a national or resident of any such country or on any such list. 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> ls -la 229 Entering Extended Passive Mode (|||49196|) 150 Opening ASCII mode data connection for '/bin/ls'. total 10984 drwxr-xr-x 9 0 wheel 512 Dec 13 1999 . drwxr-xr-x 9 0 wheel 512 Dec 13 1999 .. -rw-r--r-- 1 0 wheel 611 Jun 6 2000 .message drwxr-xr-x 2 0 wheel 512 Jul 17 1999 archive dr-xr-xr-x 2 0 wheel 512 Apr 17 2001 bin drwxr-xr-x 2 0 wheel 512 Dec 25 1997 etc d--x--x--x 4 0 wheel 512 Feb 4 16:25 hidden drwx-----T 2 234 netbsd 512 Jul 16 1999 lost+found -rw-rw-r-- 1 234 netbsd 5582055 Jun 12 19:58 ls-lRA.gz drwxr-xr-x 6 0 wheel 512 Jun 20 1999 pub dr-xr-xr-x 2 0 wheel 512 Dec 25 1997 usr 226 Transfer complete. ftp> bye 221- Data traffic for this session was 0 bytes in 0 files. Total traffic for this session was 3633 bytes in 1 transfer. 221 Thank you for using the FTP service on ftp6.netbsd.org. thomas@witz:~> ---------------------------------------------------------------- Regards, Thomas Schäfer From rvdp@kirk.rvdp.org Fri Jun 14 00:16:45 2002 Received: from kirk.rvdp.org (node147c0.a2000.nl [24.132.71.192]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E7GiE21141 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 00:16:44 -0700 (PDT) Received: from kirk.rvdp.org (localhost [IPv6:::1]) by kirk.rvdp.org (8.12.3/8.12.3) with ESMTP id g5E7Gg2Z042264; Fri, 14 Jun 2002 09:16:42 +0200 (CEST) (envelope-from rvdp@kirk.rvdp.org) Received: (from rvdp@localhost) by kirk.rvdp.org (8.12.3/8.12.3/Submit) id g5E7GgEu042263; Fri, 14 Jun 2002 09:16:42 +0200 (CEST) Date: Fri, 14 Jun 2002 09:16:42 +0200 From: Ronald van der Pol To: Kimmo Suominen Cc: Ronald van der Pol , 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Message-ID: <20020614071642.GB36510@rvdp.org> References: <20020613231245.GA36510@rvdp.org> <20020614010018.1ACFA7E13@beowulf.gw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020614010018.1ACFA7E13@beowulf.gw.com> User-Agent: Mutt/1.3.99i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Thu, Jun 13, 2002 at 21:00:18 -0400, Kimmo Suominen wrote: > An MTU mismatch was identified and corrected earlier today. Ah, thanks. Now I understand what is happening. > Please try again now, and let me know how it goes. It does not work yet: bones.rvdp.org$ ftp ftp.netbsd.org Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... Connected to ftp.netbsd.org. 421 Service not available, remote server timed out. Connection closed ftp> > I can currently get a successful ftp session connected from > 3ffe:26ff:10:8003:260:8ff:fe61:f82d, but the connection just > times out from 3ffe:2900:b00c:2:250:4ff:feac:7981, like this > > beowulf:~> ftp ftp.netbsd.org > Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... > Connected to ftp.netbsd.org. > > 421 Service not available, remote server timed out. Connection closed > > The tunnel experiencing the problem is via Sprint. Does anybody have access to ftp.netbsd.org to try to ping6 from it with various fragment sizes? rvdp From simon@limmat.switch.ch Fri Jun 14 02:14:57 2002 Received: from babar.switch.ch (babar.switch.ch [130.59.4.2]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5E9EuE18481 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 02:14:56 -0700 (PDT) Received: (from leinen@localhost) by babar.switch.ch (8.11.6+Sun/8.11.6) id g5E9Ehr24859; Fri, 14 Jun 2002 11:14:43 +0200 (MEST) X-Authentication-Warning: babar.switch.ch: leinen set sender to simon@limmat.switch.ch using -f To: itojun@iijlab.net Cc: Ronald van der Pol , 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org References: <3827.1024015867@itojun.org> X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPdz,@ttmwYVO7l`6OXXYR` From: Simon Leinen In-Reply-To: <3827.1024015867@itojun.org> Date: 14 Jun 2002 11:14:43 +0200 Message-ID: Lines: 63 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.90 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >>>>> On Fri, 14 Jun 2002 09:51:07 +0900, itojun@iijlab.net said: > there seems to be some config mistake within ISI (who hosts > tp.netbsd.org), regarding to link MTU setting of tunnel > interface. i heard that they have changed the config so it > should be better now. (at least, it is much better for me) Yes, but that shouldn't matter early on in the FTP session - the first packets are all quite small. By the way, for me it works fine from a Solaris 8 machine, although the problem may simply have been fixed in the meantime. I'm appending tcpdump output from a complete session. > i myself have experienced it before - Juniper sets tunnel > interface MTU to infinity, and KAME uses 1280. -- Simon Leinen simon@babar.switch.ch SWITCH http://www.switch.ch/misc/leinen/ Computers hate being anthropomorphized. 10:30:42.770049 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: S [tcp sum ok] 3717258812:3717258812(0) win 32805 (len 44, hlim 60) 10:30:42.967472 ftp6.netbsd.org.ftp > babar.switch.ch.41522: S [tcp sum ok] 4094757220:4094757220(0) ack 3717258813 win 32768 (len 40, hlim 56) 10:30:42.967502 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 1 win 32844 (len 32, hlim 60) 10:30:43.328349 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 1:63(62) ack 1 win 33120 [flowlabel 0xf4865] (len 94, hlim 56) 10:30:43.328382 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 63 win 32844 (len 32, hlim 60) 10:30:46.236393 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: P [tcp sum ok] 1:11(10) ack 63 win 32844 (len 42, hlim 60) 10:30:46.432911 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 63:112(49) ack 11 win 33120 [flowlabel 0xf4865] (len 81, hlim 56) 10:30:46.524524 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 112 win 32844 (len 32, hlim 60) 10:30:48.130238 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: P [tcp sum ok] 11:33(22) ack 112 win 32844 (len 54, hlim 60) 10:30:48.430036 ftp6.netbsd.org.ftp > babar.switch.ch.41522: . [tcp sum ok] ack 33 win 33120 [flowlabel 0xf4865] (len 32, hlim 56) 10:30:48.471005 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 112:118(6) ack 33 win 33120 [flowlabel 0xf4865] (len 38, hlim 56) 10:30:48.564520 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 118 win 32844 (len 32, hlim 60) 10:30:48.585777 ftp6.netbsd.org.ftp > babar.switch.ch.41522: . [tcp sum ok] 118:1326(1208) ack 33 win 33120 [flowlabel 0xf4865] (len 1240, hlim 56) 10:30:48.684532 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 1326 win 32844 (len 32, hlim 60) 10:30:48.886186 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 1326:1762(436) ack 33 win 33120 [flowlabel 0xf4865] (len 468, hlim 56) 10:30:48.984524 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 1762 win 32844 (len 32, hlim 60) 10:30:49.184436 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 1762:2491(729) ack 33 win 33120 [flowlabel 0xf4865] (len 761, hlim 56) 10:30:49.284539 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 2491 win 32844 (len 32, hlim 60) 10:30:50.446337 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: P [tcp sum ok] 33:39(6) ack 2491 win 32844 (len 38, hlim 60) 10:30:50.642775 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 2491:2539(48) ack 39 win 33120 [flowlabel 0xf4865] (len 80, hlim 56) 10:30:50.643278 babar.switch.ch.41523 > ftp6.netbsd.org.49202: S [tcp sum ok] 3014599293:3014599293(0) win 32805 (len 44, hlim 60) 10:30:50.734548 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 2539 win 32844 (len 32, hlim 60) 10:30:50.838925 ftp6.netbsd.org.49202 > babar.switch.ch.41523: S [tcp sum ok] 823416627:823416627(0) ack 3014599294 win 32768 (len 40, hlim 56) 10:30:50.838956 babar.switch.ch.41523 > ftp6.netbsd.org.49202: . [tcp sum ok] ack 1 win 32844 (len 32, hlim 60) 10:30:50.839146 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: P [tcp sum ok] 39:45(6) ack 2539 win 32844 (len 38, hlim 60) 10:30:51.039516 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 2539:2594(55) ack 45 win 33120 [flowlabel 0xf4865] (len 87, hlim 56) 10:30:51.134569 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 2594 win 32844 (len 32, hlim 60) 10:30:51.385422 ftp6.netbsd.org.49202 > babar.switch.ch.41523: F [tcp sum ok] 516:516(0) ack 1 win 33120 [flowlabel 0xf4866] (len 32, hlim 56) 10:30:51.385451 babar.switch.ch.41523 > ftp6.netbsd.org.49202: . [tcp sum ok] ack 1 win 32844 (len 32, hlim 60) 10:30:51.386884 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 2594:2618(24) ack 45 win 33120 [flowlabel 0xf4865] (len 56, hlim 56) 10:30:51.389623 ftp6.netbsd.org.49202 > babar.switch.ch.41523: P [tcp sum ok] 1:516(515) ack 1 win 33120 [flowlabel 0xf4866] (len 547, hlim 56) 10:30:51.389735 babar.switch.ch.41523 > ftp6.netbsd.org.49202: . [tcp sum ok] ack 517 win 32844 (len 32, hlim 60) 10:30:51.393974 babar.switch.ch.41523 > ftp6.netbsd.org.49202: F [tcp sum ok] 1:1(0) ack 517 win 32844 (len 32, hlim 60) 10:30:51.484554 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 2618 win 32844 (len 32, hlim 60) 10:30:51.587775 ftp6.netbsd.org.49202 > babar.switch.ch.41523: . [tcp sum ok] ack 2 win 33120 [flowlabel 0xf4866] (len 32, hlim 56) 10:30:52.120699 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: P [tcp sum ok] 45:51(6) ack 2618 win 32844 (len 38, hlim 60) 10:30:52.320393 ftp6.netbsd.org.ftp > babar.switch.ch.41522: P [tcp sum ok] 2618:2624(6) ack 51 win 33120 [flowlabel 0xf4865] (len 38, hlim 56) 10:30:52.322111 ftp6.netbsd.org.ftp > babar.switch.ch.41522: FP [tcp sum ok] 2624:2810(186) ack 51 win 33120 [flowlabel 0xf4865] (len 218, hlim 56) 10:30:52.322233 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: . [tcp sum ok] ack 2811 win 32844 (len 32, hlim 60) 10:30:52.322846 babar.switch.ch.41522 > ftp6.netbsd.org.ftp: F [tcp sum ok] 51:51(0) ack 2811 win 32844 (len 32, hlim 60) 10:30:52.518550 ftp6.netbsd.org.ftp > babar.switch.ch.41522: . [tcp sum ok] ack 52 win 33120 [flowlabel 0xf4865] (len 32, hlim 56) From pim@ipng.nl Fri Jun 14 11:13:37 2002 Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EIDXE18130 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 11:13:36 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 3D8148C2A; Fri, 14 Jun 2002 18:13:31 +0000 (GMT) Date: Fri, 14 Jun 2002 20:13:31 +0200 From: Pim van Pelt To: Stephen Stuart Cc: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Message-ID: <20020614181331.GC2270@bfib.colo.bit.nl> References: <200206140351.g5E3pCk01953@lo.tech.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206140351.g5E3pCk01953@lo.tech.org> User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Thu, Jun 13, 2002 at 08:51:12PM -0700, Stephen Stuart wrote: | If anyone is still having problems with TCP sessions to/from | ftp.netbsd.org, please send me traceroutes. The MTU and tunnel setttings are unrelated. A TCP handshake uses Syn/SynAck/Ack packets without payload so these should be around 50 bytes. Stephen, I still cannot reach the site, from various Dutch ISPs, such as SURFnet (AS1103), Intouch (AS8954), BIT (AS12859) and Concepts (AS12871). A typical traceroute for AS12859 would be: [HoG] /hog.mnt/vol2/rsync/bfib/www$ traceroute6 ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:7b8:3:17:2a0:24ff:fe56:6a60, 30 hops max, 12 byte packets 1 dapje.ipv6.network.bit.nl 1.169 ms 1.117 ms 1 ms 2 c7206.sara.ams-ix.ipv6.network.bit.nl 10.336 ms 9.678 ms 10.765 ms 3 ams-ix.sara.xs4all.net 10.653 ms 13.089 ms 11.801 ms 4 Gi1-2.BR1.Amsterdam1.surf.net 13.195 ms * 10.898 ms 5 nikhef.ams-ix.ipv6.intouch.net 9.658 ms 9.855 ms 9.633 ms 6 3ffe:800::fffb:0:0:5 168.34 ms 169.399 ms * 7 3ffe:800::fff9:0:0:2 343.838 ms 278.082 ms 189.127 ms 8 3ffe:8050:ffff::fffd 181.536 ms 178.031 ms 179.648 ms 9 ftp6.netbsd.org 178.405 ms 182.943 ms 179.327 ms And directly from AS8954 (intouch.net): pim@tunnelserver:~$ traceroute6 ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:6e0::250:4ff:fe4a:7708, 30 hops max, 16 byte packets 1 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 0.522 ms 0.423 ms 0.389 ms 2 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 159.983 ms * 158.36 ms 3 3ffe:800::fff9:0:0:2 (3ffe:800::fff9:0:0:2) 167.842 ms 167.723 ms 167.985 ms 4 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 169.695 ms 169.222 ms 169.645 ms 5 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 169.245 ms 169.039 ms 169.31 ms As Ronald has also witnessed, I see Syn, then SynAck, then I send Ack and the line goes dead (does this Ack ever reach the ftp6 server?). It also raises another point, which I find quite odd. I will mail about this later. groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From pim@ipng.nl Fri Jun 14 11:17:28 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EIHSE20050 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 11:17:28 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5EIHRb06023 for <6bone@isi.edu>; Fri, 14 Jun 2002 11:17:27 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 430778C2A; Fri, 14 Jun 2002 18:17:24 +0000 (GMT) Date: Fri, 14 Jun 2002 20:17:24 +0200 From: Pim van Pelt To: 6bone@ISI.EDU Message-ID: <20020614181724.GD2270@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Subject: [6bone] BGP routing 'these days' Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: hi, When I traced to the NetBSD site just now, I saw that my path to them is kind of odd. At AMS-IX, several parties peer with each other, they normally would send a full view to each other on the native IPv6 peering point. Now I wonder why it is that a packet from my network to NetBSD, goes over several of these parties: 2 c7206.sara.ams-ix.ipv6.network.bit.nl, to 3 ams-ix.sara.xs4all.net, to 4 Gi1-2.BR1.Amsterdam1.surf.net, to 5 nikhef.ams-ix.ipv6.intouch.net, to The AS path for this would be AS12859 AS3265 AS1103 AS8954 And I am dead sure that AS12859 peers with AS8954 directly, and they both exchange full views. The localpref on these routes is 100 in both cases. Anybody want to guess why this transits AS3265 and AS1103 nevertheless ? :) groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From stuart@tech.org Fri Jun 14 12:17:25 2002 Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EJHME24095 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 12:17:24 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5EJHDk05423; Fri, 14 Jun 2002 12:17:13 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206141917.g5EJHDk05423@lo.tech.org> To: Pim van Pelt cc: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-reply-to: Your message of "Fri, 14 Jun 2002 20:13:31 +0200." <20020614181331.GC2270@bfib.colo.bit.nl> Date: Fri, 14 Jun 2002 12:17:13 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > On Thu, Jun 13, 2002 at 08:51:12PM -0700, Stephen Stuart wrote: > | If anyone is still having problems with TCP sessions to/from > | ftp.netbsd.org, please send me traceroutes. > > The MTU and tunnel setttings are unrelated. A TCP handshake uses > Syn/SynAck/Ack packets without payload so these should be around 50 > bytes. I understand that. ISC receives routes from two sources: peers on the PAIX Palo Alto switch fabric, and a tunnel to ISI. I would like to determine if the people having problems share some property relating to that, like "people who still report problems all show the ISI tunnel in their traceroute." > Stephen, I still cannot reach the site, from various Dutch ISPs, such as > SURFnet (AS1103), Intouch (AS8954), BIT (AS12859) and Concepts > (AS12871). [traceroutes] The traceroutes you sent were helpful, as they all show the ISI tunnel in the traceroute. The problem showed up as the result of two variables in our network changing: our Palo Alto router changed from Cisco to Juniper, and our Redwood City router changed from Cisco to FreeBSD/zebra (this is not to be taken as a reflection on Cisco, the change was necessary for other reasons). To further comment on your observation regarding TCP - yes, the handshake is small, and in an environment where MTU mismatch would cause problems with larger packet sizes, a TCP session would tend to start and then hang, as the window size ramps up and datagram sizes approach interface MTU size. As was correctly noted by itojun, when the *interior* tunnel MTU sizes did not match, everyone suffered (including the iBGP session between the routers); when the MTUs were aligned in the manner that itojun noted (the Juniper was brought down to FreeBSD's setting) connectivity for some improved. Remaining problems *seem* to have the ISI tunnel in common. Interface MTU size on the tunnel interface toward the ISI router has now been matched, just as with the interior tunnel interface. > As Ronald has also witnessed, I see Syn, then SynAck, then I send Ack > and the line goes dead (does this Ack ever reach the ftp6 server?). That is an excellent question. I am not a member of the NetBSD development team, and I do not have access to their box to determine conclusively whether the ack really gets there. I can run tcpdump on the router immediately upstream to see if it is attempting to deliver it. If someone still having issues would like to coordinate a debugging session to look at that, please contact me privately. Stephen From stuart@tech.org Fri Jun 14 12:24:18 2002 Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EJOHE26731 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 12:24:17 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5EJO9k05478; Fri, 14 Jun 2002 12:24:09 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206141924.g5EJO9k05478@lo.tech.org> To: "Jeroen Massar" cc: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-reply-to: Your message of "Fri, 14 Jun 2002 04:58:11 +0200." <001b01c2134f$523033b0$420d640a@unfix.org> Date: Fri, 14 Jun 2002 12:24:09 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > Let's try again from purgatory.unfix.org: ftp.netbsd.org's path to purgatory.unfix.org traverses the ISC-ISI tunnel mentioned in my recent mail. Stephen From kim@tac.nyc.ny.us Fri Jun 14 12:49:18 2002 Received: from beowulf.gw.com (postfix@beowulf.gw.com [204.80.150.34]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EJnHE05545 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 12:49:17 -0700 (PDT) Received: from beowulf.gw.com (localhost [127.0.0.1]) by beowulf.gw.com (Postfix) with ESMTP id 388177E10; Fri, 14 Jun 2002 15:49:16 -0400 (EDT) To: Stephen Stuart Cc: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-Reply-To: <200206141917.g5EJHDk05423@lo.tech.org> from Stephen Stuart on Fri, 14 Jun 2002 12:17:13 -0700 References: <200206141917.g5EJHDk05423@lo.tech.org> X-Attribution: Kim MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25709.1024084156.1@beowulf.gw.com> Date: Fri, 14 Jun 2002 15:49:16 -0400 From: Kimmo Suominen Message-Id: <20020614194916.388177E10@beowulf.gw.com> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: The problem still exists for me. Below are the traceroutes for each direction and tcpdumps of an attempt. The tcpdump was a bit odd -- I kept seeing packets from beowulf to the ftp server even after I killed the ftp process (and I didn't see any other ftp processes on the machine). + Kim beowulf:~> ftp ftp.netbsd.org Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... Connected to ftp.netbsd.org. 421 Service not available, remote server timed out. Connection closed ftp> ^D beowulf:~> traceroute6 -q1 -w2 ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 3ffe:2900:b00c:2:250:4ff:feac:7981, 30 hops max, 12 byte packets 1 dit 0.57 ms 2 sl-bb1v6-rly-t-48.sprintv6.net 24.104 ms 3 2001:440:1239:1007::2 79.704 ms 4 2001:440:1239:1007::2 79.998 ms 5 3ffe:800::fff9:0:0:2 102.131 ms 6 3ffe:800::fff9:0:0:2 100.058 ms 7 ftp6.netbsd.org 103.044 ms nbftp:~> traceroute6 -q1 -w2 beowulf.gw.com traceroute6 to beowulf.gw.com (3ffe:2900:b00c:2:250:4ff:feac:7981) from 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea, 30 hops max, 12 byte packets 1 3ffe:8050:201:1860:200:f8ff:fe02:9a03 0.554 ms 2 3ffe:8050:ffff::fffe 1.624 ms 3 3ffe:800::fff9:0:0:1 11.548 ms 4 2001:478:ffff::a 21.554 ms 5 2001:440:1239:1007::1 22.501 ms 6 3ffe:2900:b:7::2 103.124 ms 7 3ffe:2900:b:7::2 101.241 ms 8 beowulf.gw.com 102.321 ms beowulf:~# tcpdump -i ex0 ip6 host ftp.netbsd.org tcpdump: listening on ex0 15:43:00.489420 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: S 3455727996:3455727996(0) win 16384 [flowlabel 0x3ef7f] 15:43:00.590674 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: S 3623584296:3623584296(0) ack 3455727997 win 32768 15:43:00.590852 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: . ack 1 win 16384 [flowlabel 0x3ef7f] 15:43:12.350259 beowulf.gw.com.49385 > ftp6.netbsd.org.ftp: F 450414700:450414700(0) ack 1762195173 win 16384 [flowlabel 0x3ef7d] 15:44:00.602554 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 15:44:01.602081 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 15:44:03.602073 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 15:44:07.602303 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 15:44:15.602535 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 15:44:16.352526 beowulf.gw.com.49385 > ftp6.netbsd.org.ftp: F 0:0(0) ack 1 win 16384 [flowlabel 0x3ef7d] 15:44:31.603116 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 15:45:03.604328 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] ^C 1085 packets received by filter 0 packets dropped by kernel nbftp:~# tcpdump -i fxp0 ip6 host beowulf.gw.com tcpdump: listening on fxp0 12:43:00.374725 ftp6.netbsd.org.ftp > beowulf.gw.com.49385: FP 1762195173:1762195272(99) ack 450414701 win 33120 [flowlabel 0xf496c] 12:43:00.534959 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: S 3455727996:3455727996(0) win 16384 [flowlabel 0x3ef7f] 12:43:00.535158 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: S 3623584296:3623584296(0) ack 3455727997 win 32768 12:43:00.634521 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: . ack 1 win 16384 [flowlabel 0x3ef7f] 12:43:00.657402 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: P 1:63(62) ack 1 win 33120 [flowlabel 0xf496d] 12:43:01.374715 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: P 1:63(62) ack 1 win 33120 [flowlabel 0xf496d] 12:43:03.374581 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: P 1:63(62) ack 1 win 33120 [flowlabel 0xf496d] 12:43:07.374813 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: P 1:63(62) ack 1 win 33120 [flowlabel 0xf496d] 12:43:12.394908 beowulf.gw.com.49385 > ftp6.netbsd.org.ftp: F 0:0(0) ack 0 win 16384 [flowlabel 0x3ef7d] 12:43:12.394995 ftp6.netbsd.org.ftp > beowulf.gw.com.49385: . ack 1 win 33120 [flowlabel 0xf496c] 12:43:15.374745 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: P 1:63(62) ack 1 win 33120 [flowlabel 0xf496d] 12:43:31.374797 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: P 1:63(62) ack 1 win 33120 [flowlabel 0xf496d] 12:44:00.646781 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:44:00.646872 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: . ack 2 win 33120 [flowlabel 0xf496d] 12:44:00.647275 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: FP 63:100(37) ack 2 win 33120 [flowlabel 0xf496d] 12:44:01.646876 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:44:01.646966 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: . ack 2 win 33120 [flowlabel 0xf496d] 12:44:03.374476 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: FP 1:100(99) ack 2 win 33120 [flowlabel 0xf496d] 12:44:03.646448 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:44:03.646523 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: . ack 2 win 33120 [flowlabel 0xf496d] 12:44:04.374417 ftp6.netbsd.org.ftp > beowulf.gw.com.49385: FP 0:99(99) ack 1 win 33120 [flowlabel 0xf496c] 12:44:07.647571 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:44:07.647649 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: . ack 2 win 33120 [flowlabel 0xf496d] 12:44:15.646881 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:44:15.646961 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: FP 1:100(99) ack 2 win 33120 [flowlabel 0xf496d] 12:44:16.396892 beowulf.gw.com.49385 > ftp6.netbsd.org.ftp: F 0:0(0) ack 0 win 16384 [flowlabel 0x3ef7d] 12:44:16.396983 ftp6.netbsd.org.ftp > beowulf.gw.com.49385: . ack 1 win 33120 [flowlabel 0xf496c] 12:44:31.648395 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:44:31.648548 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: . ack 2 win 33120 [flowlabel 0xf496d] 12:45:03.648837 beowulf.gw.com.49386 > ftp6.netbsd.org.ftp: F 1:1(0) ack 1 win 16384 [flowlabel 0x3ef7f] 12:45:03.648911 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: . ack 2 win 33120 [flowlabel 0xf496d] 12:45:08.373946 ftp6.netbsd.org.ftp > beowulf.gw.com.49385: FP 0:99(99) ack 1 win 33120 [flowlabel 0xf496c] 12:45:19.373862 ftp6.netbsd.org.ftp > beowulf.gw.com.49386: FP 1:100(99) ack 2 win 33120 [flowlabel 0xf496d] 12:45:20.399057 beowulf.gw.com.49385 > ftp6.netbsd.org.ftp: F 0:0(0) ack 0 win 16384 [flowlabel 0x3ef7d] 12:45:20.399138 ftp6.netbsd.org.ftp > beowulf.gw.com.49385: . ack 1 win 33120 [flowlabel 0xf496c] ^C 250449 packets received by filter 0 packets dropped by kernel | From: Stephen Stuart | Date: Fri, 14 Jun 2002 12:17:13 -0700 | | Remaining problems *seem* to have the ISI tunnel in common. Interface | MTU size on the tunnel interface toward the ISI router has now been | matched, just as with the interior tunnel interface. From gnea@garson.org Fri Jun 14 12:57:02 2002 Received: from garson.sd.timebender.com (mail@roc-24-93-23-118.rochester.rr.com [24.93.23.118]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EJv1E07662 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 12:57:02 -0700 (PDT) Received: from gnea by garson.sd.timebender.com with local (Exim 3.35 #1 (Debian)) id 17Ix69-0000kA-00 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 15:51:05 -0400 Date: Fri, 14 Jun 2002 15:51:04 -0400 From: Scott Prader To: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Message-ID: <20020614195104.GA2498@gnea.net> References: <200206140835.52758.mail@thomas--schaefer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206140835.52758.mail@thomas--schaefer.de> User-Agent: Mutt/1.3.28i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Indeed, the following from a Debian (unstable release) setup through freenet6: [gnea@garson] [~] telnet -6 ftp6.netbsd.org 21 Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... Connected to ftp6.netbsd.org. Escape character is '^]'. 220 ftp6.netbsd.org FTP server (NetBSD-ftpd 20020201) ready. user anonymous 331 Guest login ok, type your name as password. pass gnea@garson.org 230- Welcome to FTP.NetBSD.ORG Located in Palo Alto, CA, USA , , /( )` -----------yada! [gnea@garson] [~] traceroute6 ftp6.netbsd.org traceroute to ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 3ffe:b80:2:9109::2, 30 hops max, 16 byte packets 1 3ffe:b80:2:9109::1 (3ffe:b80:2:9109::1) 236.375 ms 177.293 ms 149.612 ms 2 3ffe:8000:ffff:b::2 (3ffe:8000:ffff:b::2) 95.14 ms 206.992 ms 98.79 ms 3 3ffe:b00:c18::6b (3ffe:b00:c18::6b) 218.926 ms 252.254 ms 191.161 ms 4 paix-tunnel.fmt.ipv6.he.net (3ffe:81d0:ffff:1::1) 172.006 ms 231.26 ms 191.508 ms 5 paix-v6.isc.org (3ffe:80a::1) 212.827 ms 254.686 ms 219.655 ms 6 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 286.989 ms 199.393 ms 285.002 ms 7 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 246.178 ms 274.975 ms 316.906 ms -----------yada! lftp seems to work to connect, but as soon as i attempt an ls, it segfaults: [gnea@garson] [~] grep dns .lftprc set dns:order inet6 inet [gnea@garson] [~] lftp lftp :~> o ftp6.netbsd.org lftp ftp6.netbsd.org:~> cd . cd ok, cwd=/ lftp ftp6.netbsd.org:/> ls Segmentation fault [gnea@garson] [~] I'll need to sit down and debug this later or see if there is a new version around the corner which fixes that, it's not a very big concern at this point in time. OTOH, it could be a malformed option set in .lftprc * Thomas Schaefer (mail@thomas--schaefer.de) cobbled forth: > And now it seems to work very well: > ----------------------------------------------- > thomas@witz:~> nslookup -query=any ftp.netbsd.org > Note: nslookup is deprecated and may be removed from future releases. > Consider using the `dig' or `host' programs instead. Run nslookup with > the `-sil[ent]' option to prevent this message from appearing. > Server: 212.185.252.201 > Address: 212.185.252.201#53 > > Name: ftp.netbsd.org > Address: 204.152.184.75 > ftp.netbsd.org has AAAA address 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea .oO Gnea [gnea at garson dot org] Oo. .oO url [http://gnea.net] Oo. "You can tune a filesystem, but you can't tune a fish." -Kirk McKusick From rogerj@student.uit.no Fri Jun 14 14:24:14 2002 Received: from mux2.uit.no (mux2.uit.no [129.242.5.252]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5ELOCE08720 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 14:24:13 -0700 (PDT) Received: from oddbit.student.uit.no (IDENT:root@oddbit.student.uit.no [129.242.80.22]) by mux2.uit.no (8.12.3/8.12.3/Mux) with ESMTP id g5ELO98o036114; Fri, 14 Jun 2002 23:24:09 +0200 (CEST) Received: from trinket.student.uit.no (IDENT:rogerj@trinket.student.uit.no [129.242.80.24]) by oddbit.student.uit.no (8.9.3/8.9.3) with ESMTP id XAA08535; Fri, 14 Jun 2002 23:24:09 +0200 Date: Fri, 14 Jun 2002 23:26:38 +0200 (CEST) From: Roger Jorgensen To: Stephen Stuart cc: Pim van Pelt , <6bone@mailman.isi.edu> Subject: Re: [6bone] problem with ftp.netbsd.org In-Reply-To: <200206141917.g5EJHDk05423@lo.tech.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: : ok X-Scanned-By: MIMEDefang 2.12 (www dot roaringpenguin dot com slash mimedefang) Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Fri, 14 Jun 2002, Stephen Stuart wrote: > > On Thu, Jun 13, 2002 at 08:51:12PM -0700, Stephen Stuart wrote: > > | If anyone is still having problems with TCP sessions to/from > > | ftp.netbsd.org, please send me traceroutes. > > > > The MTU and tunnel setttings are unrelated. A TCP handshake uses > > Syn/SynAck/Ack packets without payload so these should be around 50 > > bytes. > > I understand that. > > ISC receives routes from two sources: peers on the PAIX Palo Alto > switch fabric, and a tunnel to ISI. I would like to determine if the > people having problems share some property relating to that, like > "people who still report problems all show the ISI tunnel in their > traceroute." I've tried it from several machines, and sites and they all use the same route: 2 2001:730::1:2f (2001:730::1:2f) 157.299 ms 156.369 ms 155.876 ms 3 paix-tunnel.fmt.ipv6.he.net (3ffe:81d0:ffff:1::1) 161.154 ms 158.577 ms 159.025 ms 4 3ffe:80a::1 (3ffe:80a::1) 351.493 ms 231.817 ms 224.404 ms 5 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 173.924 ms 169.901 ms 169.360 ms 6 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 169.013 ms * 169.903 ms zero problems for any of them, except two solaris boxes that couldn't connect at all to ftp.netbsd.org. However, those two solaris boxes worked fine when I ftp'ed to ftp.pasta.cs.uit.no (3ffe:2a00:100:3001::2) ... ------------------------------ Roger Jorgensen | IRC: James_B rogerj@stud.cs.uit.no | - IPv6 is The Key! http://www.jorgensen.no | roger@jorgensen.no ------------------------------------------------------- From stuart@tech.org Fri Jun 14 15:27:45 2002 Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EMRiE10293 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 15:27:45 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5EMRbk06200; Fri, 14 Jun 2002 15:27:37 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206142227.g5EMRbk06200@lo.tech.org> To: Kimmo Suominen cc: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-reply-to: Your message of "Fri, 14 Jun 2002 15:49:16 EDT." <20020614194916.388177E10@beowulf.gw.com> Date: Fri, 14 Jun 2002 15:27:37 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > The problem still exists for me. > > Below are the traceroutes for each direction and tcpdumps of an attempt. I have a traceroute running on the router to watch for beowulf.gw.com; please try an FTP session again. > The tcpdump was a bit odd -- I kept seeing packets from beowulf to the > ftp server even after I killed the ftp process (and I didn't see any > other ftp processes on the machine). Probably just trying to tidy up the closed TCP session. Stephen From stuart@tech.org Fri Jun 14 15:29:18 2002 Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5EMTIE11185 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 15:29:18 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5EMTCk06224; Fri, 14 Jun 2002 15:29:12 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206142229.g5EMTCk06224@lo.tech.org> To: Kimmo Suominen cc: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-reply-to: Your message of "Fri, 14 Jun 2002 15:27:37 PDT." Date: Fri, 14 Jun 2002 15:29:12 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > > The problem still exists for me. > > > > Below are the traceroutes for each direction and tcpdumps of an attempt. > > I have a traceroute running on the router to watch for beowulf.gw.com; > please try an FTP session again. Sigh. s/traceroute/tcpdump/. Stephen From fink@es.net Fri Jun 14 16:46:31 2002 Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5ENkUE17955 for <6bone@mailman.isi.edu>; Fri, 14 Jun 2002 16:46:30 -0700 (PDT) Received: from ([63.196.96.113]) by postal1.es.net (Postal Node 1) with SMTP id GQF37091; Fri, 14 Jun 2002 16:46:27 -0700 Message-Id: <5.1.0.14.0.20020614164056.02a68148@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 14 Jun 2002 16:46:18 -0700 To: 6BONE List <6bone@mailman.isi.edu> From: Bob Fink Cc: Amaury DAILLIEZ Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] recent illegal inet6num registry Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: I just wanted to conclude this particular illegal inet6num registry with a report that after discussing it with Mr. Amaury Dailliez, who is the Technical Manager of AzurVP Network France, I am convinced this was just an honest mistake of someone trying to figure out how to setup a legitimate inet6num entry. He is quite embarrassed about it and says he has never used the prefix in any way. Anyway, the bogus entry is removed and I believe we should treat Mr. Dailliez as a citizen of the 6bone in good standing. I certainly believe he is. Thanks, Bob Fink From fink@es.net Sat Jun 15 00:02:25 2002 Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5F72PE20798 for <6bone@mailman.isi.edu>; Sat, 15 Jun 2002 00:02:25 -0700 (PDT) Received: from ([63.196.96.113]) by postal2.es.net (Postal Node 2) with SMTP id GQF37091; Sat, 15 Jun 2002 00:02:21 -0700 Message-Id: <5.1.0.14.0.20020614235339.02a74488@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 15 Jun 2002 00:02:18 -0700 To: 6BONE List <6bone@mailman.isi.edu> From: Bob Fink Cc: "Ferdinando Porcu" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] pTLA request EURNETCITY - review closes 28 June 2002 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: 6bone Folk, EURNETCITY has requested a pTLA allocation and I find their request fully compliant with RFC2772. The open review period for this will close 28 June 2002. Please send your comments to me or the list. Thanks, Bob === >From: "Ferdinando Porcu" >To: >Subject: pTLA request for EURNetCity (AS20794) >Date: Wed, 12 Jun 2002 18:21:08 +0200 > >Hi Bob and 6bone members, > >On behalf of EURNetCity, I would like to submit our application for a pTLA. > >1. The pTLA Applicant must have a minimum of three (3) months > qualifying experience as a 6Bone end-site or pNLA transit. > >We are connected to the 6bone since Feb 2002 with a /48 from VIAGENIE. > >During the entire qualifying period the Applicant must be operationally >providing the following: > >a. Fully maintained, up to date, 6Bone Registry entries for their >ipv6-site inet6num, mntner, and person objects, including each >tunnel that the Applicant has. > >Our records on the 6bone database are up to date. >http://whois.6bone.net/cgi-bin/whois?eurnet-mnt >http://whois.6bone.net/cgi-bin/whois?eurnetcity > >b. Fully maintained, and reliable, BGP4+ peering and connectivity >between the Applicant's boundary router and the appropriate >connection point into the 6Bone. This router must be IPv6 >pingable. This criteria is judged by members of the 6Bone >Operations Group at the time of the Applicant's pTLA request. > >We have currently 3 BGP4+ peering sessions (CSELT and >RMNet) on a Juniper M10 Router > >c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) >entries for the Applicant's router(s) and at least one host >system. > >DNS server : dns.ipv6.eurnetcity.net - 3ffe:b80:731:1:2d0:b7ff:feaa:9bbb > >d. A fully maintained, and reliable, IPv6-accessible system >providing, at a mimimum, one or more web pages, describing the >Applicant's IPv6 services. This server must be IPv6 pingable. > >IPv6 Web server is at: http://www.ipv6.eurnetcity.net and is pingable > >2. The pTLA Applicant MUST have the ability and intent to provide > "production-quality" 6Bone backbone service. Applicants must > provide a statement and information in support of this claim. > This MUST include the following: > > a. A support staff of two persons minimum, three preferable, with > person attributes registered for each in the ipv6-site object > for the pTLA applicant. > >We have a mail entry to the group of technical people at: >network@eurnetcity.net >Tech persons on charge of IPv6 support are: >http://whois.6bone.net/cgi-bin/whois?FP4-6BONE >http://whois.6bone.net/cgi-bin/whois?FA3-6BONE > > b. A common mailbox for support contact purposes that all support > staff have acess to, pointed to with a notify attribute in the > ipv6-site object for the pTLA Applicant. > >The staff has access to the common mailbox: network@eurnetcity.net >3. The pTLA Applicant MUST have a potential "user community" that > would be served by its becoming a pTLA, e.g., the Applicant is a > major provider of Internet service in a region, country, or focus > of interest. Applicant must provide a statement and information in > support this claim. > >Eurnetcity will serve business and residential users in Rome Area for >broadband services such as >VoD, VoIP and internet traffic using his optical metro network to deliver >it. >We are actually offering our commercial services through PSTN and ISDN >dialup, dedicated lines, ADSL lines and colocation. >Our users base is about 1000 home-users and 100 enterprises > >4. The pTLA Applicant MUST commit to abide by the current 6Bone > operational rules and policies as they exist at time of its > application, and agree to abide by future 6Bone backbone > operational rules and policies as they evolve by consensus of the > 6Bone backbone and user community. > >We fully agree to all current and future operational rules and policies. > >When an Applicant seeks to receive a pTLA allocation, it will apply >to the 6Bone Operations Group (see section 8 below) by providing to >the Group information in support of its claims that it meets the >criteria above. > > >Best regards, >-- > >---------------------------------------------------------------- >Ferdinando Porcu > >Eurnetcity S.p.A. >Eurnetcity e' una iniziativa di Eur S.p.A. e Gruppo Acea >Resp. Servizi IP >Via Ciro il Grande, 16 >00144 ROMA > >Tel. +39.(0)6.5425.2268 >Fax +39.(0)6.5425.2055 >http://www.eurnetcity.it >http://www.eurnetcity.net >fporcu@eurnetcity.net >---------------------------------------------------------------------------- >------------------------------ >This communication contains information which is confidential and >may also privileged. It is for the exclusive use of the indented >recipient(s). If you are not the intended recipient(s), please note >that any distribution, copying or use of this communication or the >information in it is stricly prohibited. If you have received this >communication in error, please notify the sender immediately >and then destroy any copies of it. >---------------------------------------------------------------------------- >----------------- From pim@ipng.nl Sat Jun 15 01:35:50 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5F8ZoE06255 for <6bone@mailman.isi.edu>; Sat, 15 Jun 2002 01:35:50 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5F8Znb02876 for <6bone@isi.edu>; Sat, 15 Jun 2002 01:35:49 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 910508C2A; Sat, 15 Jun 2002 08:35:46 +0000 (GMT) Date: Sat, 15 Jun 2002 10:35:46 +0200 From: Pim van Pelt To: 6bone@ISI.EDU Message-ID: <20020615083546.GA24977@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Subject: [6bone] whois and mnt-lower Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi What are the current thoughts of the WHOIS database maintainers (and its software engineers) on the insertion of a maintained object for the 3ffe::/16 (or even 0::/0) range, and delegate mnt-lower to each company that received a pTLA allocation. This will take care of the problem Jeroen mentioned, and the apparent honest mistake Amaury's engineering team made. I for one would very much like to see this database cleaned up a bit more. groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From fink@es.net Sat Jun 15 08:02:04 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5FF23E10637 for <6bone@mailman.isi.edu>; Sat, 15 Jun 2002 08:02:03 -0700 (PDT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5FF23b09712 for <6bone@ISI.EDU>; Sat, 15 Jun 2002 08:02:03 -0700 (PDT) Received: from ([63.196.96.113]) by postal2.es.net (Postal Node 2) with SMTP id GQF37091; Sat, 15 Jun 2002 08:02:01 -0700 Message-Id: <5.1.0.14.0.20020615075623.02a33a60@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 15 Jun 2002 08:01:58 -0700 To: Pim van Pelt , 6bone@ISI.EDU From: Bob Fink Subject: Re: [6bone] whois and mnt-lower In-Reply-To: <20020615083546.GA24977@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Pim, At 10:35 AM 6/15/2002 +0200, Pim van Pelt wrote: >Hi > >What are the current thoughts of the WHOIS database maintainers (and its >software engineers) on the insertion of a maintained object for the >3ffe::/16 (or even 0::/0) range, and delegate mnt-lower to each company >that received a pTLA allocation. > >This will take care of the problem Jeroen mentioned, and the apparent >honest mistake Amaury's engineering team made. > >I for one would very much like to see this database cleaned up a bit >more. There has been a 3FFE::/16 inet6num for the 6bone for some time (see below). We have not wanted to get into extended discussions, about what you suggest above, on the list to avoid attracting overmuch interest, however, David and I are discussing various approaches (including yours) and will eventually let the list know what's reasonable for us to do. Thanks, Bob === % RIPEdb(3.0.0b2) with ISI RPSL extensions inet6num: 3FFE::/16 netname: 6BONE descr: Test Address Space for the 6bone country: AR AT AU BE BG BR CA CM CN CZ DE DK EE ES FI FR GB GR HK HU IE IN IT JP KR KZ LT MX MY NL NO NZ PL PT RO RU SE SG SI SK TW UA US UY ZA admin-c: RLF1-6BONE tech-c: BM2-6BONE tech-c: DK13-RIPE rev-srv: ns.isi.edu rev-srv: imag.imag.fr remarks: contact RLF1-6BONE for allocation of a pTLA contact BM2-6BONE for reverse delegations contact DK13-RIPE for issues regarding the 6bone registry changed netname to 6bone remarks: This object is automatically converted from the RIPE181 registry mnt-by: RLF1-6BONE changed: davidk@ISI.EDU 19970908 changed: rlfink@lbl.gov 19970909 changed: fink@es.net 20000521 changed: fink@es.net 20000712 changed: auto-dbm@whois.6bone.net 20010117 source: 6BONE ipv6-site: 6BONE origin: AS293 descr: IETF NGTRANS Working Group IPv6 Testbed prefix: 3FFE::/16 contact: RLF1-6BONE remarks: This object is automatically converted from the RIPE181 registry url: http://www.6bone.net notify: fink@es.net mnt-by: RLF1-6BONE changed: fink@es.net 20001128 changed: auto-dbm@whois.6bone.net 20010117 source: 6BONE person: Robert L. Fink address: ESnet - Lawrence Berkeley National Laboratory phone: +1 510 486 5692 e-mail: fink@es.net nic-hdl: RLF1-6BONE remarks: change to my esnet email address remarks: This object is automatically converted from the RIPE181 registry notify: fink@es.net mnt-by: RLF1-6BONE changed: fink@es.net 19991206 changed: fink@es.net 20000521 changed: auto-dbm@whois.6bone.net 20010117 source: 6BONE person: Bill Manning address: po 12317, mdr, ca. usa phone: +1.310.322.8102 e-mail: bmanning@isi.edu nic-hdl: BM2-6BONE remarks: This object is automatically converted from the RIPE181 registry notify: bmanning@isi.edu changed: bmanning@isi.edu 19970401 changed: auto-dbm@whois.6bone.net 20010117 source: 6BONE -end From rvdp@kirk.rvdp.org Mon Jun 17 01:56:48 2002 Received: from kirk.rvdp.org (node147c0.a2000.nl [24.132.71.192]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5H8ulE08767 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 01:56:47 -0700 (PDT) Received: (from rvdp@localhost) by kirk.rvdp.org (8.11.6/8.11.6) id g5H8uXD07368; Mon, 17 Jun 2002 10:56:33 +0200 (CEST) Date: Mon, 17 Jun 2002 10:56:33 +0200 From: Ronald van der Pol To: Stephen Stuart Cc: Pim van Pelt , 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Message-ID: <20020617085633.GB1463@rvdp.org> References: <20020614181331.GC2270@bfib.colo.bit.nl> <200206141917.g5EJHDk05423@lo.tech.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206141917.g5EJHDk05423@lo.tech.org> User-Agent: Mutt/1.4i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Fri, Jun 14, 2002 at 12:17:13 -0700, Stephen Stuart wrote: > If someone still having issues would like to coordinate a > debugging session to look at that, please contact me privately. It is working for me now, but the path has changed. It used to be: spock$ traceroute6 -q 1 -l ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:610:508:1001:260:1dff:fef6:7ff9, 30 hops max, 12 byte packets 1 kirk (2001:610:508:1001:220:afff:fec6:4faa) 3.201 ms 2 surrogate.ipv6.surfnet.nl (2001:610:508:1000::1) 7.9 ms 3 surfnet-bv.Amsterdam.ipv6.surf.net (2001:610:0:2001::1) 13.627 ms 4 PO4-0.CR2.Amsterdam1.surf.net (2001:610:16:3048::49) 16.897 ms 5 PO0-0.BR2.Amsterdam1.surf.net (2001:610:16:6004::6) 15.136 ms 6 ams-ix.sara.xs4all.net (2001:7f8:1::a500:3265:1) 13.938 ms 7 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 12.436 ms 8 3ffe:1280:1001:1::1 (3ffe:1280:1001:1::1) 382.62 ms 9 3ffe:80a::1 (3ffe:80a::1) 203.762 ms 10 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 204.275 ms 11 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 306.499 ms Which did not work. Now it works with the path: bones.rvdp.org$ traceroute6 -q1 -l ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 2001:610:508:1001:202:2dff:fe0f:7d1, 64 hops max, 12 byte packets 1 2001:610:508:1001::1 (2001:610:508:1001::1) 5.074 ms 2 surrogate.ipv6.surfnet.nl (2001:610:508:1000::1) 41.915 ms 3 surfnet-bv.Amsterdam.ipv6.surf.net (2001:610:0:2001::1) 20.911 ms 4 PO4-0.CR2.Amsterdam2.surf.net (2001:610:16:5048::49) 35.221 ms 5 Gi0-0.AR1.Amsterdam2.surf.net (2001:610:16:5060::62) 38.964 ms 6 3ffe:2200:0:8000::1 (3ffe:2200:0:8000::1) 150.217 ms 7 aads-tunnel.fmt.ipv6.he.net (3ffe:81d0:ffff:1::3) 222.045 ms 8 paix-tunnel.fmt.ipv6.he.net (3ffe:81d0:ffff:1::1) 230.037 ms 9 3ffe:80a::1 (3ffe:80a::1) 212.591 ms 10 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 233.241 ms 11 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 255.217 ms bones.rvdp.org$ Notice the last three hops of the path are the same: 9 3ffe:80a::1 (3ffe:80a::1) 203.762 ms 10 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 204.275 ms 11 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 306.499 ms rvdp From kim@tac.nyc.ny.us Mon Jun 17 05:36:48 2002 Received: from beowulf.gw.com (postfix@beowulf.gw.com [204.80.150.34]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HCalE00596 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 05:36:47 -0700 (PDT) Received: from beowulf.gw.com (localhost [127.0.0.1]) by beowulf.gw.com (Postfix) with ESMTP id 5395C7E57; Mon, 17 Jun 2002 08:36:46 -0400 (EDT) To: Ronald van der Pol Cc: Stephen Stuart , Pim van Pelt , 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-Reply-To: <20020617085633.GB1463@rvdp.org> from Ronald van der Pol on Mon, 17 Jun 2002 10:56:33 +0200 References: <20020614181331.GC2270@bfib.colo.bit.nl> <200206141917.g5EJHDk05423@lo.tech.org> <20020617085633.GB1463@rvdp.org> X-Attribution: Kim MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19539.1024317406.1@beowulf.gw.com> Date: Mon, 17 Jun 2002 08:36:46 -0400 From: Kimmo Suominen Message-Id: <20020617123646.5395C7E57@beowulf.gw.com> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Same thing here -- connecting works fine, but the path has switched to go through he.net. + Kim | From: Ronald van der Pol | Date: Mon, 17 Jun 2002 10:56:33 +0200 | | On Fri, Jun 14, 2002 at 12:17:13 -0700, Stephen Stuart wrote: | | > If someone still having issues would like to coordinate a | > debugging session to look at that, please contact me privately. | | It is working for me now, but the path has changed. It used to be: [...snip...] From jon@jons.org Mon Jun 17 06:22:25 2002 Received: from vile.com (nexus.vile.com [199.79.161.2]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HDMOE10740 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 06:22:24 -0700 (PDT) Received: (qmail 10640 invoked from network); 17 Jun 2002 13:22:11 -0000 Received: from unknown (HELO exodus) (199.79.161.25) by mail.vile.com with SMTP; 17 Jun 2002 13:22:11 -0000 From: "Jon Christopherson" To: "'Kimmo Suominen'" , "'Ronald van der Pol'" Cc: "'Stephen Stuart'" , "'Pim van Pelt'" , <6bone@mailman.isi.edu> Subject: RE: [6bone] problem with ftp.netbsd.org Date: Mon, 17 Jun 2002 06:22:04 -0700 Message-ID: <000001c21601$fc255a80$19a14fc7@exodus> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020617123646.5395C7E57@beowulf.gw.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: All Looks good from my end as well: ~ >traceroute6 -q1 -l ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 3ffe:c00:803d:2::2, 30 hops max, 12 byte packets 1 enigma (3ffe:c00:803d:2::1) 0.408 ms 2 3ffe:c00:8023:46::1 (3ffe:c00:8023:46::1) 28.688 ms 3 paix-tunnel.fmt.ipv6.he.net (3ffe:81d0:ffff:1::1) 39.49 ms 4 3ffe:80a::1 (3ffe:80a::1) 43.152 ms 5 3ffe:8050:ffff::fffd (3ffe:8050:ffff::fffd) 42.99 ms 6 ftp6.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) 42.044 ms Thanks! -jon -----Original Message----- From: 6bone-admin@mailman.isi.edu [mailto:6bone-admin@mailman.isi.edu] On Behalf Of Kimmo Suominen Sent: Monday, June 17, 2002 5:37 AM To: Ronald van der Pol Cc: Stephen Stuart; Pim van Pelt; 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org Same thing here -- connecting works fine, but the path has switched to go through he.net. + Kim | From: Ronald van der Pol | Date: Mon, 17 Jun 2002 10:56:33 +0200 | | On Fri, Jun 14, 2002 at 12:17:13 -0700, Stephen Stuart wrote: | | > If someone still having issues would like to coordinate a | > debugging session to look at that, please contact me privately. | | It is working for me now, but the path has changed. It used to be: [...snip...] _______________________________________________ 6bone mailing list 6bone@mailman.isi.edu http://mailman.isi.edu/mailman/listinfo/6bone From jeroen@unfix.org Mon Jun 17 07:25:52 2002 Received: from purgatory.unfix.org (postfix@cust.92.136.adsl.cistron.nl [195.64.92.136]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HEPpE28723 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 07:25:51 -0700 (PDT) Received: from localhost (localhost [::ffff:127.0.0.1]) by purgatory.unfix.org (Postfix) with ESMTP id 2E82D316B; Mon, 17 Jun 2002 16:25:48 +0200 (CEST) Received: from HELL (hell.unfix.org [::ffff:10.100.13.66]) by purgatory.unfix.org (Postfix) with ESMTP id 42C043209; Mon, 17 Jun 2002 16:25:20 +0200 (CEST) From: "Jeroen Massar" To: "'Ronald van der Pol'" , "'Stephen Stuart'" Cc: "'Pim van Pelt'" , <6bone@mailman.isi.edu> Subject: RE: [6bone] problem with ftp.netbsd.org Date: Mon, 17 Jun 2002 16:25:20 +0200 Organization: Unfix Message-ID: <001b01c2160a$d0c683b0$420d640a@unfix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020617085633.GB1463@rvdp.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS @ purgatory.unfix.org Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Ronald van der Pol wrote: > On Fri, Jun 14, 2002 at 12:17:13 -0700, Stephen Stuart wrote: > > > If someone still having issues would like to coordinate a > > debugging session to look at that, please contact me privately. > Now going over he.net for me also. 8<------------------ jeroen@purgatory:~$ traceroute6 ftp.netbsd.org traceroute6 to ftp.netbsd.org (3ffe:8050:201:1860:2a0:c9ff:feed:b7ea) from 3ffe:8114:1000::27, 30 hops max, 12 byte packets 1 tunnel-026.ipng.nl 19.711 ms 18.527 ms 18.866 ms 2 Amsterdam.core.ipv6.intouch.net 19.779 ms 19.829 ms 19.759 ms 3 3ffe:c00:8023:1f::1 158.658 ms 159.031 ms 158.896 ms 4 paix-tunnel.fmt.ipv6.he.net 187.316 ms 184.295 ms 179.761 ms 5 paix-v6.isc.org 175.072 ms 179.622 ms 183.888 ms 6 3ffe:8050:ffff::fffd 182.342 ms 198.789 ms 207.795 ms 7 ftp6.netbsd.org 213.099 ms 224.759 ms 212.57 ms ------------------>8 And it now nicely works: 8<------------------ jeroen@purgatory:~$ telnet ftp.netbsd.org 21 Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea... Connected to ftp.netbsd.org. Escape character is '^]'. 220 ftp6.netbsd.org FTP server (NetBSD-ftpd 20020201) ready. ^] telnet> q ------------------>8 :) Greets, Jeroen From fink@es.net Mon Jun 17 07:25:56 2002 Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HEPtE28767 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 07:25:55 -0700 (PDT) Received: from ([63.196.96.113]) by postal1.es.net (Postal Node 1) with SMTP id GQF37091; Mon, 17 Jun 2002 07:25:52 -0700 Message-Id: <5.1.0.14.0.20020617071847.02982598@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 17 Jun 2002 07:25:38 -0700 To: 6BONE List <6bone@mailman.isi.edu> From: Bob Fink Cc: Sanan Kurkulsatsanakit Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [6bone] 6bone pTLA 3FFE:400B::/32 allocated to INET-TH Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: INET-TH has been allocated pTLA 3FFE:400B::/32 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: [To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to hostmaster@ep.net.] Thanks, Bob From todd@shadow.fries.net Mon Jun 17 08:11:39 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HFBcE14654 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 08:11:38 -0700 (PDT) Received: from fries.net (root@ns0.fries.net [206.30.141.10]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HFBbb13845 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 08:11:37 -0700 (PDT) Received: from shadow.fries.net (todd@localhost.fries.net [127.0.0.1]) by fries.net (8.12.1/8.12.1) with ESMTP id g5HFATep004813 (version=TLSv1/SSLv3 cipher=EDH-DSS-DES-CBC3-SHA bits=168 verify=NO); Mon, 17 Jun 2002 10:10:29 -0500 (CDT) Received: (from todd@localhost) by shadow.fries.net (8.12.1/8.12.1/Submit) id g5HFAP9W021987; Mon, 17 Jun 2002 10:10:25 -0500 (CDT) Date: Mon, 17 Jun 2002 10:10:25 -0500 From: "Todd T. Fries" To: Paul Aitken Cc: tapas.das@teleweb.net.in, 6bone@ISI.EDU Message-ID: <20020617151025.GA27722@fries.net> Reply-To: todd@fries.net References: <3CD3F2B3.2000107@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CD3F2B3.2000107@cisco.com> User-Agent: Mutt/1.3.99i X-PGP-Fingerprint: B6 3B 70 46 BC 0F 8C DD 14 D4 C7 D1 47 F6 23 FA X-URL: http://todd.fries.net X-tra-email: todd@fries.net, toddf@acm.org, todd@openbsd.org, toddfries@yahoo.com X-IM: toddfries@AIM, toddfries@Yahoo, 115268457@ICQ, {toddfries,fr[1i]es}@*.irc.fries.net Subject: [6bone] Re: Got one IPV6 address from Freenet6 but not working. Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Fwiw, itojun has recently found a problem with kdelibs that disabled getaddrinfo for most systems due to an absent memset in the configure script. Currently, this is fixed in the OpenBSD ports tree and the current cvs repository, but unfortunately not before 3.0.1 went out. -- Todd Fries .. todd@fries.net (last updated $ToddFries: signature.p,v 1.2 2002/03/19 15:10:18 todd Exp $) Penned by Paul Aitken on Sat, May 04, 2002 at 03:39:47PM +0100, we have: | Tapas, | | >I have got a IPV6 address from Freenet6. I can also ping to few of the | >IPV6 address, but when I goto www.kame.net i don't see the dancing | >turtle also at the end of the page it says "you are using IPv4",can | >somebody explain me why is this happening. | | Most likely your DNS is resolving www.kame.net into an IPv4 address. Use | a browser that supports IPv6 and a DNS server that supports AAAA records. | | Cheers. | -- | Paul Aitken | IPv6 Development, Cisco Systems Ltd, Edinburgh, Scotland. EH6 6LX | From stuart@tech.org Mon Jun 17 09:37:35 2002 Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HGbXE28412 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 09:37:34 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5HGbSk18582 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 09:37:28 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206171637.g5HGbSk18582@lo.tech.org> To: 6bone@mailman.isi.edu Subject: Re: [6bone] problem with ftp.netbsd.org In-reply-to: Your message of "Mon, 17 Jun 2002 16:25:20 +0200." <001b01c2160a$d0c683b0$420d640a@unfix.org> Date: Mon, 17 Jun 2002 09:37:28 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Late on Friday I depref'd from and prepended toward ISI (from ISC). That shifted the traffic to/from ISC's PAIX peers (like the nice folks at Hurricane Electric). Stephen From ww@GROOVY.NET Mon Jun 17 09:46:06 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HGk5E03316 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 09:46:05 -0700 (PDT) Received: from ANAPHORA.GROOVY.NET (ANAPHORA.GROOVY.NET [205.189.139.196]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HGk5b28522 for <6bone@isi.edu>; Mon, 17 Jun 2002 09:46:05 -0700 (PDT) Received: by ANAPHORA.GROOVY.NET (Postfix, from userid 101) id 3FD9511B; Mon, 17 Jun 2002 12:45:59 -0400 (EDT) Date: Mon, 17 Jun 2002 12:45:59 -0400 From: ww@GROOVY.NET To: 6bone@ISI.EDU Message-ID: <20020617124559.A13931@GROOVY.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: [6bone] Exchange Point Addresses Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Hi, At the Toronto Internet Exchange (TORIX) we've been talking about making it possible to peer natively over IPv6. The problem is getting addresses for the exchange -- RIPE seems to have a clear policy (they'll hand out a /64), but ARIN doesn't appear to. It would not be appropriate to use addresses from one of the providers at the exchange since TORIX has been, since its inception, provider neutral and we'd like to keep it that way. Any suggestions or pointers to how to go about acquiring some numbers for the exchange would be appreciated. Thanks, -w -- Will Waites ww@groovy.net From pim@ipng.nl Mon Jun 17 11:18:47 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HIIkE20595 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 11:18:46 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HIIib19482 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 11:18:45 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id DF1528C2B; Mon, 17 Jun 2002 18:18:41 +0000 (GMT) Date: Mon, 17 Jun 2002 20:18:41 +0200 From: Pim van Pelt To: ww@GROOVY.NET Cc: 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses Message-ID: <20020617181841.GA5259@bfib.colo.bit.nl> References: <20020617124559.A13931@GROOVY.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020617124559.A13931@GROOVY.NET> User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, Jun 17, 2002 at 12:45:59PM -0400, ww@GROOVY.NET wrote: | Hi, | | At the Toronto Internet Exchange (TORIX) we've been talking about | making it possible to peer natively over IPv6. The problem is | getting addresses for the exchange -- RIPE seems to have a clear | policy (they'll hand out a /64), but ARIN doesn't appear to. It | would not be appropriate to use addresses from one of the providers | at the exchange since TORIX has been, since its inception, | provider neutral and we'd like to keep it that way. They give out a (non-aggregatable) /48, which is IMO almost 100% pointless (not a /64 like you mentioned). | Any suggestions or pointers to how to go about acquiring some | numbers for the exchange would be appreciated. As with your collegues at AMS-IX (NL), you will simply be left out in the cold. When you approach a registry with a remark like you just made, you will be told that you are no more special than any other company that wishes to have their own globally routable space (call it PI, call it TLA). At current, at least in the region I am active in (RIPE), IXPs cannot obtain address space without becoming dependant on a member. By the way, neither can the RIR itself. groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From stuart@tech.org Mon Jun 17 12:02:35 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HJ2ZE15121 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 12:02:35 -0700 (PDT) Received: from lo.tech.org (lo.tech.org [204.152.187.102]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HJ2Yb21311 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 12:02:34 -0700 (PDT) Received: from tech.org (localhost [127.0.0.1]) by lo.tech.org (8.11.6/8.11.6) with ESMTP id g5HJ2Ok19154; Mon, 17 Jun 2002 12:02:26 -0700 (PDT) (envelope-from stuart@tech.org) Message-Id: <200206171902.g5HJ2Ok19154@lo.tech.org> To: ww@GROOVY.NET cc: 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses In-reply-to: Your message of "Mon, 17 Jun 2002 12:45:59 EDT." <20020617124559.A13931@GROOVY.NET> Date: Mon, 17 Jun 2002 12:02:24 -0700 From: Stephen Stuart Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: > At the Toronto Internet Exchange (TORIX) we've been talking about > making it possible to peer natively over IPv6. The problem is > getting addresses for the exchange -- RIPE seems to have a clear > policy (they'll hand out a /64), but ARIN doesn't appear to. It > would not be appropriate to use addresses from one of the providers > at the exchange since TORIX has been, since its inception, > provider neutral and we'd like to keep it that way. Did you speak to anyone at ARIN about micro-allocations for exchange point use? Stephen From Robert.Kiessling@de.easynet.net Mon Jun 17 12:09:54 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HJ9sE17682 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 12:09:54 -0700 (PDT) Received: from smtp.de.easynet.net (smtp.de.easynet.net [194.24.208.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HJ9rb26523 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 12:09:53 -0700 (PDT) Received: from joseba.easynet.de (unknown [212.224.0.54]) by smtp.de.easynet.net (Postfix) with ESMTP id 63FCC11CDDA; Mon, 17 Jun 2002 21:09:44 +0200 (CEST) To: Pim van Pelt Cc: ww@GROOVY.NET, 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses References: <20020617124559.A13931@GROOVY.NET> <20020617181841.GA5259@bfib.colo.bit.nl> X-Ncc-RegID: de.easynet From: Robert Kiessling Date: 17 Jun 2002 20:20:56 +0000 In-Reply-To: <20020617181841.GA5259@bfib.colo.bit.nl> Message-ID: Lines: 55 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Pim van Pelt writes: > On Mon, Jun 17, 2002 at 12:45:59PM -0400, ww@GROOVY.NET wrote: > | At the Toronto Internet Exchange (TORIX) we've been talking about > | making it possible to peer natively over IPv6. The problem is > | getting addresses for the exchange -- RIPE seems to have a clear > | policy (they'll hand out a /64), but ARIN doesn't appear to. It > | would not be appropriate to use addresses from one of the providers > | at the exchange since TORIX has been, since its inception, > | provider neutral and we'd like to keep it that way. > They give out a (non-aggregatable) /48, which is IMO almost 100% > pointless (not a /64 like you mentioned). It fulfils exactly what it's made for: to provide neutral, provider-independent IPv6 addresses for the exchange mesh. There was and is a need for this, so it's far from "100% useless". > | Any suggestions or pointers to how to go about acquiring some > | numbers for the exchange would be appreciated. > > As with your collegues at AMS-IX (NL), you will simply be left out in > the cold. No, you're not. You can receive address space for the exchange mesh. There is no need for these addresses to be routable. Addresses for other services like web page, NTP etc. is a different story altogether. > When you approach a registry with a remark like you just > made, you will be told that you are no more special than any other > company that wishes to have their own globally routable space (call it > PI, call it TLA). Indeed. You are implying that the secondary services offered by exchange points are so important that they justify a different allocation policy. This in turn implies that you want to introduce PI to IPv6, which so far does not exist (TLA, sTLA are *not* PI, they clearly are PA). There is a clear consencus that this is not desirable. > At current, at least in the region I am active in (RIPE), IXPs cannot > obtain address space without becoming dependant on a member. By the > way, neither can the RIR itself. They can obtain address space like everone else. They just cannot get "PI" space, that is globally routable addresses not bound to an upstream. Of course they are free to fulil the requirements for an allocation, which is essentially to become a LIR and expect 200 customer assignments. Robert From pim@ipng.nl Mon Jun 17 12:31:08 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HJV7E25945 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 12:31:07 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HJV6b10888 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 12:31:07 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 931D58C2B; Mon, 17 Jun 2002 19:31:05 +0000 (GMT) Date: Mon, 17 Jun 2002 21:31:05 +0200 From: Pim van Pelt To: Robert Kiessling Cc: Pim van Pelt , ww@GROOVY.NET, 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses Message-ID: <20020617193105.GB5405@bfib.colo.bit.nl> References: <20020617124559.A13931@GROOVY.NET> <20020617181841.GA5259@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, Jun 17, 2002 at 08:20:56PM +0000, Robert Kiessling wrote: | Pim van Pelt writes: | | > On Mon, Jun 17, 2002 at 12:45:59PM -0400, ww@GROOVY.NET wrote: | > | At the Toronto Internet Exchange (TORIX) we've been talking about | > | making it possible to peer natively over IPv6. The problem is | > | getting addresses for the exchange -- RIPE seems to have a clear | > | policy (they'll hand out a /64), but ARIN doesn't appear to. It | > | would not be appropriate to use addresses from one of the providers | > | at the exchange since TORIX has been, since its inception, | > | provider neutral and we'd like to keep it that way. | > They give out a (non-aggregatable) /48, which is IMO almost 100% | > pointless (not a /64 like you mentioned). | | It fulfils exactly what it's made for: to provide neutral, | provider-independent IPv6 addresses for the exchange mesh. There was | and is a need for this, so it's far from "100% useless". Hi Robert, Sitelocal will do fine for these things. If you can't route it, I don't see the point in having it allocated from the 2000::/3 aggregate. I would find fec0::/10 addresses in the peering mesh useful. We have seen (in practice) that not having globally routable peering meshes, potentially breaks Path MTU discovery. This can happen when all the hops to the endpoint are larger than the one used on the shared medium, making the last box before the shared medium hop generate a message to the originating host that the MTU should be set to its value. Some router implementations drop any packets from sources which they do not have a route to in their FIB. | > | Any suggestions or pointers to how to go about acquiring some | > | numbers for the exchange would be appreciated. | > | > As with your collegues at AMS-IX (NL), you will simply be left out in | > the cold. | | No, you're not. You can receive address space for the exchange | mesh. There is no need for these addresses to be routable. See above. | Addresses for other services like web page, NTP etc. is a different | story altogether. It's the story I was actually referring to in my original comment. | > When you approach a registry with a remark like you just | > made, you will be told that you are no more special than any other | > company that wishes to have their own globally routable space (call it | > PI, call it TLA). | | Indeed. | | You are implying that the secondary services offered by exchange | points are so important that they justify a different allocation | policy. This in turn implies that you want to introduce PI to IPv6, | which so far does not exist (TLA, sTLA are *not* PI, they clearly are | PA). Please don't put words in my mouth. I am not implying that I would like to have PI space in IPv6, on the contrary. | There is a clear consencus that this is not desirable. I consent to not having PI, I do not consent to having the 2001:7f8::/32 superblock with /48 allocations for peering meshes. | > At current, at least in the region I am active in (RIPE), IXPs cannot | > obtain address space without becoming dependant on a member. By the | > way, neither can the RIR itself. | | They can obtain address space like everone else. They just cannot get | "PI" space, that is globally routable addresses not bound to an | upstream. Of course they are free to fulil the requirements for an | allocation, which is essentially to become a LIR and expect 200 | customer assignments. This would be lying to the RIR, and that type of behavior is being actively promoted these days, for example at RIPE42, where RIPE joined the other two RIRs with the new allocation policies. For an IXP, which will not offer downstream customers connectivity via their AS, it would not be feasable to request an IPv6 allocation from the RIR in saying that they would have a business case for 200 customer allocations (which would be their members). Most independant IXPs I know of (although I admit that I do not know of many :-), are member associations, which will not be able to make a case at their RIR to meet the 200 potential end-sites criterium. So either they lie, or they break their independence by becoming a customer with one (or several) of their members. As much as I do not think that an IXP is a more special pig than other pigs, I also do not think that they should be bending the rules and forcing themselves into awkward positions to obtain address space. Oh, did I mention that the RIRs themselves face exactly the same problem ? groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From pekkas@netcore.fi Mon Jun 17 13:18:59 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HKIwE16962 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 13:18:58 -0700 (PDT) Received: from netcore.fi (netcore.fi [193.94.160.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HKIvb09500 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 13:18:57 -0700 (PDT) Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id g5HKIZ006128; Mon, 17 Jun 2002 23:18:35 +0300 Date: Mon, 17 Jun 2002 23:18:35 +0300 (EEST) From: Pekka Savola To: Pim van Pelt cc: ww@GROOVY.NET, <6bone@ISI.EDU> Subject: Re: [6bone] Exchange Point Addresses In-Reply-To: <20020617181841.GA5259@bfib.colo.bit.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Pim, ww, Please note that IX allocation is not meant to be "globally routable". If you accept that, you can get IXP allocation, at least in RIPE region. Many IX's don't really need that (they only want addresses for e.g. switch fabrics or p-t-p addresses, not for services). IX, depending on how you build it, could have any kind of addressing you want. You could do private peerings and use addresses from either party. But that is very bothersome if the technique is based on broadcast medium, like Gigabit Ethernet. On Mon, 17 Jun 2002, Pim van Pelt wrote: > On Mon, Jun 17, 2002 at 12:45:59PM -0400, ww@GROOVY.NET wrote: > | Hi, > | > | At the Toronto Internet Exchange (TORIX) we've been talking about > | making it possible to peer natively over IPv6. The problem is > | getting addresses for the exchange -- RIPE seems to have a clear > | policy (they'll hand out a /64), but ARIN doesn't appear to. It > | would not be appropriate to use addresses from one of the providers > | at the exchange since TORIX has been, since its inception, > | provider neutral and we'd like to keep it that way. > They give out a (non-aggregatable) /48, which is IMO almost 100% > pointless (not a /64 like you mentioned). > > | Any suggestions or pointers to how to go about acquiring some > | numbers for the exchange would be appreciated. > > As with your collegues at AMS-IX (NL), you will simply be left out in > the cold. When you approach a registry with a remark like you just > made, you will be told that you are no more special than any other > company that wishes to have their own globally routable space (call it > PI, call it TLA). > > At current, at least in the region I am active in (RIPE), IXPs cannot > obtain address space without becoming dependant on a member. By the > way, neither can the RIR itself. > > groet, > Pim > > -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From bmanning@ISI.EDU Mon Jun 17 13:38:17 2002 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HKcGE27307 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 13:38:16 -0700 (PDT) Received: (from bmanning@localhost) by boreas.isi.edu (8.11.6/8.11.2) id g5HKc8N09094; Mon, 17 Jun 2002 13:38:08 -0700 (PDT) From: Bill Manning Message-Id: <200206172038.g5HKc8N09094@boreas.isi.edu> Subject: Re: [6bone] Exchange Point Addresses In-Reply-To: <20020617124559.A13931@GROOVY.NET> from "ww@GROOVY.NET" at "Jun 17, 2 12:45:59 pm" To: ww@GROOVY.NET Date: Mon, 17 Jun 2002 13:38:08 -0700 (PDT) Cc: 6bone@ISI.EDU X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: you may wish to talk with Joe Abley. you may also wish to review www.ep.net % Hi, % % At the Toronto Internet Exchange (TORIX) we've been talking about % making it possible to peer natively over IPv6. The problem is % getting addresses for the exchange -- RIPE seems to have a clear % policy (they'll hand out a /64), but ARIN doesn't appear to. It % would not be appropriate to use addresses from one of the providers % at the exchange since TORIX has been, since its inception, % provider neutral and we'd like to keep it that way. % % Any suggestions or pointers to how to go about acquiring some % numbers for the exchange would be appreciated. % % Thanks, % -w % -- % Will Waites % ww@groovy.net % _______________________________________________ % 6bone mailing list % 6bone@mailman.isi.edu % http://mailman.isi.edu/mailman/listinfo/6bone % -- --bill From Robert.Kiessling@de.easynet.net Mon Jun 17 14:04:34 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HL4XE10957 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 14:04:34 -0700 (PDT) Received: from smtp.de.easynet.net (smtp.de.easynet.net [194.24.208.3]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HL4Wb04339 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 14:04:32 -0700 (PDT) Received: from joseba.easynet.de (unknown [212.224.0.54]) by smtp.de.easynet.net (Postfix) with ESMTP id 1AD0111CDBF; Mon, 17 Jun 2002 23:04:26 +0200 (CEST) To: Pim van Pelt Cc: ww@GROOVY.NET, 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses References: <20020617124559.A13931@GROOVY.NET> <20020617181841.GA5259@bfib.colo.bit.nl> <20020617193105.GB5405@bfib.colo.bit.nl> X-Ncc-RegID: de.easynet From: Robert Kiessling Date: 17 Jun 2002 22:15:39 +0000 In-Reply-To: <20020617193105.GB5405@bfib.colo.bit.nl> Message-ID: Lines: 53 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Pim van Pelt writes: > | It fulfils exactly what it's made for: to provide neutral, > | provider-independent IPv6 addresses for the exchange mesh. There was > | and is a need for this, so it's far from "100% useless". > > Sitelocal will do fine for these things. If you can't route it, I don't > see the point in having it allocated from the 2000::/3 aggregate. I > would find fec0::/10 addresses in the peering mesh useful. Three things spring to my mind: 1. reverse DNS is not possible with site-local addresses 2. with site-local addresses on IXP LAN, a router is in two different local domains, with possible nasty interactions between the two "site local" domains 3. missing traceroutes hops through IPX LANs with site-local addresses > We have seen (in practice) that not having globally routable peering > meshes, potentially breaks Path MTU discovery. Then you see something I've never seen. RFC1918 addresses pose problems to PMTUD, that's true, but for different reasons. > Some router implementations drop any packets from sources which they do > not have a route to in their FIB. Which implementations do this? Even if you have such an implementation, you'd just need to nullroute the allocation from which IXP addresses are taken. > This would be lying to the RIR, and that type of behavior is being > actively promoted these days, [...] I didn't want to suggest to lie, but to honestly fulfil the criteria. > | There is a clear consencus that this is not desirable. > I consent to not having PI, I do not consent to having the 2001:7f8::/32 > superblock with /48 allocations for peering meshes. What would be your suggestion then? Giving routable blocks to IXPs which do not do end-user assignments *is* PI. > Oh, did I mention that the RIRs themselves face exactly the same problem ? You mentioned it. Still I fail see why this a problem. If it was, then is would be a problem not just for IXPs and RIPE, but for many other organsations too. IXPs and RIPE are not special in this respect. Robert From ww@GROOVY.NET Mon Jun 17 14:07:30 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HL7TE13146 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 14:07:30 -0700 (PDT) Received: from EPANAPHORA.GROOVY.NET ([205.189.139.147]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HL7Tb06393 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 14:07:29 -0700 (PDT) Received: by EPANAPHORA.GROOVY.NET (Postfix, from userid 101) id 3AFC027BEB; Mon, 17 Jun 2002 17:07:27 -0400 (EDT) Date: Mon, 17 Jun 2002 17:07:27 -0400 From: ww@GROOVY.NET To: Pim van Pelt Cc: 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses Message-ID: <20020617170727.A6406@GROOVY.NET> References: <20020617124559.A13931@GROOVY.NET> <20020617181841.GA5259@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020617181841.GA5259@bfib.colo.bit.nl>; from pim@ipng.nl on Mon, Jun 17, 2002 at 08:18:41PM +0200 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, Jun 17, 2002 at 08:18:41PM +0200, Pim van Pelt wrote: > > They give out a (non-aggregatable) /48, which is IMO almost 100% > pointless (not a /64 like you mentioned). My source for this was http://www.ripe.net/ripencc/mem-services/registration/ipv6/eix-interim.html "Since the address space does not need to be routable globally and an IXP is expected to only have one subnet, a /64 (64 bits of address space) will be assigned in most cases." Perhaps this does not reflect their actual policy. In any case if the addresses are not globally routeable, we might as well use site-local ones. It would befar better to use globally routeable addresses for exactly the reasons you point out -- i.e. path MTU discovery. Perhaps it is not impossible that a certain number of small exchange point blocks be allowed to leak unaggregated into the global routing table -- I suspect that the number of such blocks would be bounded above by 10000 or so (say about 300 countries in the world with on average 10 major cities, each with an internet exchange or two). It's clearly feasable technically, but less than elegant. > As with your collegues at AMS-IX (NL), you will simply be left out in > the cold. When you approach a registry with a remark like you just > made, you will be told that you are no more special than any other > company that wishes to have their own globally routable space (call it > PI, call it TLA). Which is unfortunate, since we don't really fit into their categories. In reality, TORIX is a couple of ethernet switches that live in shared physical space graciously donated by the managers of the local telco hotel. It is not a company, it is a shared community resource. And it has run into problems in the past being tied for one reason or another to a particular member of the exchage. So, what to do? ;) The way that ARIN seems to have tentatively addressed the issue is by trying to turn regional exchanges (a label which could reasonably be applied to TORIX since most of the ISPs in Ontario peer there) into sub-TLA registries for the region (http://www.arin.net/library/guidelines/ipv6_rir.txt section 4.2.3.1) which, I believe, is more responsibility than we would be willing to take on. They also have a RIPE-like policy proposal which doesn't appear to have been looked at in about a year and a half: http://www.arin.net/policy/2001_3.html Cheers, -w -- Will Waites ww@groovy.net From pekkas@netcore.fi Mon Jun 17 14:11:50 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HLBnE15264 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 14:11:49 -0700 (PDT) Received: from netcore.fi (netcore.fi [193.94.160.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HLBmb09318 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 14:11:48 -0700 (PDT) Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id g5HLBbm06720; Tue, 18 Jun 2002 00:11:37 +0300 Date: Tue, 18 Jun 2002 00:11:36 +0300 (EEST) From: Pekka Savola To: Pim van Pelt cc: Robert Kiessling , , <6bone@ISI.EDU> Subject: Re: [6bone] Exchange Point Addresses In-Reply-To: <20020617193105.GB5405@bfib.colo.bit.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, 17 Jun 2002, Pim van Pelt wrote: > On Mon, Jun 17, 2002 at 08:20:56PM +0000, Robert Kiessling wrote: > | Pim van Pelt writes: > | > | > On Mon, Jun 17, 2002 at 12:45:59PM -0400, ww@GROOVY.NET wrote: > | > | At the Toronto Internet Exchange (TORIX) we've been talking about > | > | making it possible to peer natively over IPv6. The problem is > | > | getting addresses for the exchange -- RIPE seems to have a clear > | > | policy (they'll hand out a /64), but ARIN doesn't appear to. It > | > | would not be appropriate to use addresses from one of the providers > | > | at the exchange since TORIX has been, since its inception, > | > | provider neutral and we'd like to keep it that way. > | > They give out a (non-aggregatable) /48, which is IMO almost 100% > | > pointless (not a /64 like you mentioned). > | > | It fulfils exactly what it's made for: to provide neutral, > | provider-independent IPv6 addresses for the exchange mesh. There was > | and is a need for this, so it's far from "100% useless". > Hi Robert, > > Sitelocal will do fine for these things. If you can't route it, I don't > see the point in having it allocated from the 2000::/3 aggregate. I > would find fec0::/10 addresses in the peering mesh useful. Reverse DNS won't work nicely with traceroute w/ site-locals, though. How significant this is, is another question.. > Some router implementations drop any packets from sources which they do > not have a route to in their FIB. Broken implementations, or those using unicast RPF I guess. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From ww@GROOVY.NET Mon Jun 17 14:18:50 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HLIoE18337 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 14:18:50 -0700 (PDT) Received: from EPANAPHORA.GROOVY.NET ([205.189.139.147]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HLInb13955 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 14:18:49 -0700 (PDT) Received: by EPANAPHORA.GROOVY.NET (Postfix, from userid 101) id B816127BEB; Mon, 17 Jun 2002 17:18:48 -0400 (EDT) Date: Mon, 17 Jun 2002 17:18:48 -0400 From: ww@GROOVY.NET To: Pim van Pelt Cc: 6bone@ISI.EDU Subject: Re: [6bone] ifconfig and EUI-64 Message-ID: <20020617171848.A6505@GROOVY.NET> References: <20020609172247.GA2781@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020609172247.GA2781@bfib.colo.bit.nl>; from pim@ipng.nl on Sun, Jun 09, 2002 at 07:22:47PM +0200 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Sun, Jun 09, 2002 at 07:22:47PM +0200, Pim van Pelt wrote: > > Does anyone know why exactly the ifconfig programs for the BSDs, Linux > and most probably Solaris are not able to autoconfigure their own > addresses, by not using the RS/RA schema, but a local autoconfiguration > such as the Cisco IOS: NetBSD-current now supports this :) i.e. ifconfig hme0 inet6 3ffe:1cdc:0:1234:: eui64 Cheers, -w From ww@GROOVY.NET Mon Jun 17 14:35:10 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HLZAE29002 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 14:35:10 -0700 (PDT) Received: from EPANAPHORA.GROOVY.NET ([205.189.139.147]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HLZ7b25214 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 14:35:09 -0700 (PDT) Received: by EPANAPHORA.GROOVY.NET (Postfix, from userid 101) id 9263027BEB; Mon, 17 Jun 2002 17:35:06 -0400 (EDT) Date: Mon, 17 Jun 2002 17:35:06 -0400 From: ww@GROOVY.NET To: Robert Kiessling Cc: Pim van Pelt , 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses Message-ID: <20020617173506.B6505@GROOVY.NET> References: <20020617124559.A13931@GROOVY.NET> <20020617181841.GA5259@bfib.colo.bit.nl> <20020617193105.GB5405@bfib.colo.bit.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from Robert.Kiessling@de.easynet.net on Mon, Jun 17, 2002 at 10:15:39PM +0000 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, Jun 17, 2002 at 10:15:39PM +0000, Robert Kiessling wrote: > > > We have seen (in practice) that not having globally routable peering > > meshes, potentially breaks Path MTU discovery. > > Then you see something I've never seen. RFC1918 addresses pose > problems to PMTUD, that's true, but for different reasons. What are the different reasons? I would think that using any non-unique addresses (RFC1918 or site-local IPv6) would cause similar problems. Unique but non globally routeable addresses should be ok though (pace RPF), no? -w From itojun@itojun.org Mon Jun 17 15:23:55 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HMNsE23323 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 15:23:54 -0700 (PDT) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HMNrb21210 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 15:23:53 -0700 (PDT) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 4AD6B4B24; Tue, 18 Jun 2002 07:23:48 +0900 (JST) To: ww@GROOVY.NET Cc: 6bone@ISI.EDU In-reply-to: ww's message of Mon, 17 Jun 2002 12:45:59 -0400. <20020617124559.A13931@GROOVY.NET> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: [6bone] Exchange Point Addresses From: itojun@iijlab.net Date: Tue, 18 Jun 2002 07:23:48 +0900 Message-Id: <20020617222348.4AD6B4B24@coconut.itojun.org> Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: >At the Toronto Internet Exchange (TORIX) we've been talking about >making it possible to peer natively over IPv6. The problem is >getting addresses for the exchange -- RIPE seems to have a clear >policy (they'll hand out a /64), but ARIN doesn't appear to. It >would not be appropriate to use addresses from one of the providers >at the exchange since TORIX has been, since its inception, >provider neutral and we'd like to keep it that way. > >Any suggestions or pointers to how to go about acquiring some >numbers for the exchange would be appreciated. at NSPIXP2 and NSPIXP6, we are using /64 block from WIDE (2001:200::/35). WIDE is operating these exchanges so it was a natural choice. another option is to use link-local address only on IX segment. draft-kato-bgp-ipv6-link-local-01.txt cisco and zebra are at least capable of doing it. traceroute doesn't really have problem, as many of the routers i know of do not do strict strong-host model. itojun From michel@arneill-py.sacramento.ca.us Mon Jun 17 15:43:14 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5HMhEE01909 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 15:43:14 -0700 (PDT) Received: from server2000.arneill-py.sacramento.ca.us (adsl-209-233-126-65.dsl.scrm01.pacbell.net [209.233.126.65]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5HMhDb01632 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 15:43:13 -0700 (PDT) Subject: RE: [6bone] Exchange Point Addresses Date: Mon, 17 Jun 2002 15:43:07 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <2B81403386729140A3A899A8B39B046405E119@server2000.arneill-py.sacramento.ca.us> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-TNEF-Correlator: content-class: urn:content-classes:message Thread-Topic: [6bone] Exchange Point Addresses Thread-Index: AcIWLHEXX4GL7SheRcSSn1jb8AFVMAAI0jqg From: "Michel Py" To: "Pim van Pelt" , Cc: <6bone@ISI.EDU> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by gamma.isi.edu id g5HMhEE01909 Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: Pim and 6boners, > Pim van Pelt wrote: > As with your collegues at AMS-IX (NL), you will simply be left > out in the cold. When you approach a registry with a remark like > you just made, you will be told that you are no more special than > any other company that wishes to have their own globally routable > space (call it PI, call it TLA). > At current, at least in the region I am active in (RIPE), IXPs > cannot obtain address space without becoming dependant on a member. > By the way, neither can the RIR itself. The ipv6mh list is working hard to provide you with geographical addresses so you don't stay in the cold too long. An example is available here: http://arneill-py.sacramento.ca.us/ipv6mh/geov6.txt I welcome the 6bone community's comments on this. This test is about proposed allocation only, the protocols and practices are still cooking. Michel. From pim@ipng.nl Mon Jun 17 23:17:46 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5I6HjE24774 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 23:17:45 -0700 (PDT) Received: from bfib.ipng.nl (postfix@bfib.colo.bit.nl [193.109.122.62]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5I6Hib07266 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 23:17:44 -0700 (PDT) Received: by bfib.ipng.nl (Postfix, from userid 863) id 68B6E8C2B; Tue, 18 Jun 2002 06:17:42 +0000 (GMT) Date: Tue, 18 Jun 2002 08:17:42 +0200 From: Pim van Pelt To: Michel Py Cc: Pim van Pelt , ww@GROOVY.NET, 6bone@ISI.EDU Subject: Re: [6bone] Exchange Point Addresses Message-ID: <20020618061742.GC26448@bfib.colo.bit.nl> References: <2B81403386729140A3A899A8B39B046405E119@server2000.arneill-py.sacramento.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2B81403386729140A3A899A8B39B046405E119@server2000.arneill-py.sacramento.ca.us> User-Agent: Mutt/1.3.25i Sender: 6bone-admin@mailman.isi.edu Errors-To: 6bone-admin@mailman.isi.edu X-BeenThere: 6bone@mailman.isi.edu X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Archive: On Mon, Jun 17, 2002 at 03:43:07PM -0700, Michel Py wrote: | Pim and 6boners, | | > Pim van Pelt wrote: | > As with your collegues at AMS-IX (NL), you will simply be left | > out in the cold. When you approach a registry with a remark like | > you just made, you will be told that you are no more special than | > any other company that wishes to have their own globally routable | > space (call it PI, call it TLA). | > At current, at least in the region I am active in (RIPE), IXPs | > cannot obtain address space without becoming dependant on a member. | > By the way, neither can the RIR itself. | | The ipv6mh list is working hard to provide you with geographical | addresses so you don't stay in the cold too long. An example is | available here: | http://arneill-py.sacramento.ca.us/ipv6mh/geov6.txt I browsed through this allocation document. Nice work! What are the aggregation policies with these networks ? I see that the smallest allocation to cities would be /32. Who would announce for example the NL-Amsterdam block 2346:7600::/29 ? If it is anybody other than AS1200, in the case of AMS-IX, then they would be dependent on that particular AS (and most probably, the member operating that AS). Can you point me to a document that explains how this will solve the dependency issue raised ? Thanks, groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From pekkas@netcore.fi Mon Jun 17 23:54:18 2002 Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g5I6sIE03603 for <6bone@mailman.isi.edu>; Mon, 17 Jun 2002 23:54:18 -0700 (PDT) Received: from netcore.fi (netcore.fi [193.94.160.1]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g5I6sHb20407 for <6bone@ISI.EDU>; Mon, 17 Jun 2002 23:54:17 -070