From dykang@snad.ncsl.nist.gov Wed Jul 1 16:19:14 1998 From: dykang@snad.ncsl.nist.gov (Deukyoon Kang) Date: Wed, 01 Jul 1998 11:19:14 -0400 Subject: FYI : Libpcapv6 release Message-ID: <359A5372.D0A9B662@snad.ncsl.nist.gov> I'm glad to announce that Libpcapv6(=extended version of Libpcap for IPv6) is released. You can obtain regarding information and download it from 'http://dutch.antd.nist.gov/~dykang/pcapv6.html'. Note that Libpcapv6 is still experimental. Regards. Deukyoon. ----------------------------------------------------- Member of Technical Staff Protocol Engineering Team, Korea Telecom ----------------------------------------------------- Guest Researcher Internetworking Technology Group, National Institute of Standards and Technology ----------------------------------------------------- From pdesai@wins.hrl.com Wed Jul 1 22:18:50 1998 From: pdesai@wins.hrl.com (Priyank) Date: Wed, 01 Jul 1998 14:18:50 -0700 Subject: -> connecting point to 6bone. Message-ID: <359AA7BA.9800B41E@wins.hrl.com> Hi! I am looking for a connecting point to 6bone. Priyank Desai From yjchui@ms.chttl.com.tw Thu Jul 2 04:05:43 1998 From: yjchui@ms.chttl.com.tw (Yann-Ju Chu) Date: Thu, 02 Jul 1998 11:05:43 +0800 Subject: How to get IPv4 nodes in IPv6-over-IPv4 tunnels Message-ID: <359AF907.ABC1CCB9@ms.chttl.com.tw> This is a multi-part message in MIME format. --------------9EF0C017559AE86F2A348BD8 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Hi, If I want to trace the IPv6 routers in the path, I can use traceroute(v6). However, If there is tunnel built in the path, the tool can not find any information. Is there any means (or protocol) to find any tunnel in a v6 path and the IPv4 routers in the tunnel? Chu --------------9EF0C017559AE86F2A348BD8 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline >From sjchen@ms.chttl.com.tw Tue Mar 3 16:30 EAT 1998 Received: from [10.144.2.104] by brain with SMTP (1.37.109.8/16.2) id AA16397; Tue, 3 Mar 1998 16:30:35 +0800 Return-Path: Received: from sjc.chttl.com.tw ([10.144.166.133] (may be forged)) by ms.chttl.com.tw (8.8.6/8.8.6) with ESMTP id QAA12890 for ; Tue, 3 Mar 1998 16:28:31 +0800 (CST) Message-Id: <34FBC009.B69C80B1@ms.chttl.com.tw> Date: Tue, 03 Mar 1998 16:32:10 +0800 From: sjchen Organization: Telecommunication Labs. X-Mailer: Mozilla 4.0 [en] (Win95; I) Mime-Version: 1.0 To: yjchui@ms.chttl.com.tw Subject: [Fwd: Majordomo results: subscribe aatn] X-Priority: 3 (Normal) Content-Type: multipart/mixed; boundary="------------DEB3A5B2E925936923C50218" This is a multi-part message in MIME format. --------------DEB3A5B2E925936923C50218 Content-Type: text/plain; charset=us-ascii Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit --------------DEB3A5B2E925936923C50218 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from gate.chttl.com.tw (firewall.chttl.com.tw [10.144.5.250]) by ms.chttl.com.tw (8.8.6/8.8.6) with ESMTP id KAA26960 for ; Tue, 10 Feb 1998 10:24:49 +0800 (CST) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by gate.chttl.com.tw (8.8.6/8.8.6) with ESMTP id KAA04401 for ; Tue, 10 Feb 1998 10:26:49 +0800 (CST) Received: from alpha.zk3.dec.com (ralpha.zk3.dec.com [16.140.64.6]) by mail11.digital.com (8.8.8/8.8.8/WV1.0c) with SMTP id VAA11147 for ; Mon, 9 Feb 1998 21:26:36 -0500 (EST) Received: by alpha.zk3.dec.com (5.65v4.0/1.1.8.2/18Feb95-1123AM) id AA18565; Mon, 9 Feb 1998 21:26:36 -0500 Date: Mon, 9 Feb 1998 21:26:36 -0500 Message-Id: <199802100226.AA18565@alpha.zk3.dec.com> To: sjchen@ms.chttl.com.tw From: Majordomo@alpha.zk3.dec.com Subject: Majordomo results: subscribe aatn Reply-To: Majordomo@alpha.zk3.dec.com Content-Type: text -- >>>> subscribe aatn sjchen@ms.chttl.com.tw Your request to Majordomo: subscribe aatn sjchen@ms.chttl.com.tw has been forwarded to the owner of the "aatn" list for approval. This could be for any of several reasons: You might have asked to subscribe to a "closed" list, where all new additions must be approved by the list owner. You might have asked to subscribe or unsubscribe an address other than the one that appears in the headers of your mail message. When the list owner approves your request, you will be notified. If you have any questions about the policy of the list owner, please contact "aatn-approval". Thanks! Majordomo >>>> --------------DEB3A5B2E925936923C50218-- --------------9EF0C017559AE86F2A348BD8-- From brian@hursley.ibm.com Thu Jul 2 09:22:25 1998 From: brian@hursley.ibm.com (Brian E Carpenter) Date: Thu, 02 Jul 1998 09:22:25 +0100 Subject: Another prototype Message-ID: <359B4341.C9A7F668@hursley.ibm.com> Please excuse this piece of advertising, but in case anybody wants to put their S/390 on the 6bone, see the second half of http://www.software.ibm.com/enetwork/commserver/downloads/demos/demo_csos390.html Brian From yjchui@ms.chttl.com.tw Thu Jul 2 09:21:53 1998 From: yjchui@ms.chttl.com.tw (Yann-Ju Chu) Date: Thu, 02 Jul 1998 16:21:53 +0800 Subject: How to get IPv4 nodes in IPv6-over-IPv4 tunnel Message-ID: <359B4321.CB6A65DE@ms.chttl.com.tw> Hi, If I want to trace the IPv6 routers in the path, I can use traceroute(v6). However, If there is tunnel built in the path, the tool can not find any information. Is there any means (or protocol) to find any tunnel in a v6 path and the IPv4 routers in the tunnel? Chu From grant@wcug.wwu.edu Thu Jul 2 20:40:43 1998 From: grant@wcug.wwu.edu (Grant Miller) Date: Thu, 2 Jul 1998 12:40:43 -0700 (PDT) Subject: No response from a pTLA admin? Message-ID: I am having trouble getting a response from the admin of the NWNET pTLA. Either he doesn't work there anymore and didn't pass the torch to someone else, or has dropped of the face of the Earth. Suggestions on how to proceed in this situation would be appreciated. --Grant Miller grant@wcug.wwu.edu From rlfink@lbl.gov Thu Jul 2 23:14:17 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 02 Jul 1998 15:14:17 -0700 Subject: -> connecting point to 6bone. In-Reply-To: <359AA7BA.9800B41E@wins.hrl.com> Message-ID: <1312730038-481478428@cnrmail.lbl.gov> Priyank, At 02:18 PM 7/1/98 -0700, Priyank wrote: >Hi! > >I am looking for a connecting point to 6bone. What works best is to follow the steps in the "joining the 6bone" web page at: http://www.6bone.net/6bone_hookup.html This will end up having you do the work to figure out what is the "best" point of attachment for your site, and then to contact that site directly. Thanks, Bob From rlfink@lbl.gov Thu Jul 2 23:17:10 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 02 Jul 1998 15:17:10 -0700 Subject: No response from a pTLA admin? In-Reply-To: Message-ID: <1312729865-481488830@cnrmail.lbl.gov> Grant, At 12:40 PM 7/2/98 -0700, Grant Miller wrote: > >I am having trouble getting a response from the admin of the NWNET pTLA. >Either he doesn't work there anymore and didn't pass the torch to someone >else, or has dropped of the face of the Earth. > >Suggestions on how to proceed in this situation would be appreciated. Look on the NWNET web pages at www.nwnet.net and contact their NOC folk. Let me know what they say. If they don't want to support it/you, then you may have to move to another pTLA and I'll have to see if they want me to deassign their pTLA at NWNET. Thanks, Bob From pdesai@wins.hrl.com Fri Jul 3 00:20:28 1998 From: pdesai@wins.hrl.com (Priyank) Date: Thu, 02 Jul 1998 16:20:28 -0700 Subject: Request for a tunnel connection. Message-ID: <359C15BC.9ED8B34B@wins.hrl.com> Hi!, - I am looking for a connecting point to 6bone. - Location : Malibu, California, USA - Company : HRL Laboratories. - Purpose : Experimental Research. - How R We connected : T1 connection through TGI Cerfnet. Thanks, Regards, Priyank From bmanning@ISI.EDU Fri Jul 3 01:01:50 1998 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 2 Jul 1998 17:01:50 -0700 (PDT) Subject: No response from a pTLA admin? In-Reply-To: from "Grant Miller" at Jul 2, 98 12:40:43 pm Message-ID: <199807030001.RAA02005@zephyr.isi.edu> > > > I am having trouble getting a response from the admin of the NWNET pTLA. > Either he doesn't work there anymore and didn't pass the torch to someone > else, or has dropped of the face of the Earth. > > Suggestions on how to proceed in this situation would be appreciated. > > > --Grant Miller grant@wcug.wwu.edu > Try Alf Farnham alfj@nw.verio.net -- --bill From bmanning@ISI.EDU Fri Jul 3 13:50:06 1998 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 3 Jul 1998 05:50:06 -0700 (PDT) Subject: Request for a tunnel connection. In-Reply-To: <359C15BC.9ED8B34B@wins.hrl.com> from "Priyank" at Jul 2, 98 04:20:28 pm Message-ID: <199807031250.FAA10013@zephyr.isi.edu> > > Hi!, > > - I am looking for a connecting point to 6bone. > > - Location : Malibu, California, USA > > - Company : HRL Laboratories. > > - Purpose : Experimental Research. > > - How R We connected : T1 connection through TGI Cerfnet. > > Thanks, > > Regards, > > Priyank > I'll be happy to work with you on this request. -- --bill From bmanning@ISI.EDU Fri Jul 3 13:50:06 1998 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 3 Jul 1998 05:50:06 -0700 (PDT) Subject: Request for a tunnel connection. In-Reply-To: <359C15BC.9ED8B34B@wins.hrl.com> from "Priyank" at Jul 2, 98 04:20:28 pm Message-ID: <199807031250.FAA10013@zephyr.isi.edu> > > Hi!, > > - I am looking for a connecting point to 6bone. > > - Location : Malibu, California, USA > > - Company : HRL Laboratories. > > - Purpose : Experimental Research. > > - How R We connected : T1 connection through TGI Cerfnet. > > Thanks, > > Regards, > > Priyank > I'll be happy to work with you on this request. -- --bill From bmanning@ISI.EDU Fri Jul 3 13:50:06 1998 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 3 Jul 1998 05:50:06 -0700 (PDT) Subject: Request for a tunnel connection. In-Reply-To: <359C15BC.9ED8B34B@wins.hrl.com> from "Priyank" at Jul 2, 98 04:20:28 pm Message-ID: <199807031250.FAA10013@zephyr.isi.edu> > > Hi!, > > - I am looking for a connecting point to 6bone. > > - Location : Malibu, California, USA > > - Company : HRL Laboratories. > > - Purpose : Experimental Research. > > - How R We connected : T1 connection through TGI Cerfnet. > > Thanks, > > Regards, > > Priyank > I'll be happy to work with you on this request. -- --bill From bmanning@ISI.EDU Fri Jul 3 13:50:06 1998 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 3 Jul 1998 05:50:06 -0700 (PDT) Subject: Request for a tunnel connection. In-Reply-To: <359C15BC.9ED8B34B@wins.hrl.com> from "Priyank" at Jul 2, 98 04:20:28 pm Message-ID: <199807031250.FAA10013@zephyr.isi.edu> > > Hi!, > > - I am looking for a connecting point to 6bone. > > - Location : Malibu, California, USA > > - Company : HRL Laboratories. > > - Purpose : Experimental Research. > > - How R We connected : T1 connection through TGI Cerfnet. > > Thanks, > > Regards, > > Priyank > I'll be happy to work with you on this request. -- --bill From bmanning@ISI.EDU Fri Jul 3 13:50:06 1998 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 3 Jul 1998 05:50:06 -0700 (PDT) Subject: Request for a tunnel connection. In-Reply-To: <359C15BC.9ED8B34B@wins.hrl.com> from "Priyank" at Jul 2, 98 04:20:28 pm Message-ID: <199807031250.FAA10013@zephyr.isi.edu> > > Hi!, > > - I am looking for a connecting point to 6bone. > > - Location : Malibu, California, USA > > - Company : HRL Laboratories. > > - Purpose : Experimental Research. > > - How R We connected : T1 connection through TGI Cerfnet. > > Thanks, > > Regards, > > Priyank > I'll be happy to work with you on this request. -- --bill From h_elashkar@ieee.org Sun Jul 5 19:20:54 1998 From: h_elashkar@ieee.org (Hossam El-Ashkar) Date: Sun, 5 Jul 1998 21:20:54 +0300 Subject: No subject Message-ID: <000b01bda841$af952650$031979a3@semsem.cn4.ml.org> This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BDA85A.CB493EE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have a very strange situation. I have an NT station and a Solaris = station, both with IPv6. The Solaris station has generated the automatic = address and is working perfectly with it. The NT station has generated = many new interfaces with 2 different addresses types. One which uses the = eui-64, another which is backward compatible with v4 address ( = fe80::ipv4). Also, it generated another one which is( ::ipv4). below is = the output of the 'ipv6 if' command. However, neither of these addresses are working. One is pinging from = the inside but not from the outside ( ::163.121.25.3), another from the = outside but not from the inside(from the Solaris, not from another = NTv6).=20 Does anyone have an explanation for that??? -------------------------------------------------------------------------= ------- Hossam El-Ashkar h_elashkar@ieee.org = -------------------------------------------------------------------------= ------------------------ OUTPUT of " ipv6 if" command on NT: D:\>ipv6 if Interface 4: link-level address: 00-00-c0-38-5d-d8 preferred address fe80::200:c0ff:fe38:5dd8/10, infinite/infinite link MTU 1500 (true link MTU 1500) current hop limit 128 reachable time 30ms (base 30ms) retransmission interval 1s DAD transmits 1 Interface 3: link-level address: 163.121.25.3 preferred address fe80::a379:1903/10, infinite/infinite link MTU 1480 (true link MTU 1480) current hop limit 128 reachable time 38094ms (base 30000ms) retransmission interval 1s DAD transmits 1 Interface 2: link-level address: 0.0.0.0 preferred address ::163.121.25.3/96, infinite/infinite link MTU 1480 (true link MTU 1480) current hop limit 128 reachable time 0ms (base 0ms) retransmission interval 0s DAD transmits 0 Interface 1: link-level address: preferred address ::1/0, infinite/infinite link MTU 1460 (true link MTU 0) current hop limit 1 reachable time 0ms (base 0ms) retransmission interval 0s DAD transmits 0 ------=_NextPart_000_0008_01BDA85A.CB493EE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    I have a very = strange=20 situation. I have an NT station and a Solaris station, both with IPv6. = The=20 Solaris station has generated the automatic address and is working = perfectly=20 with it. The NT station has generated many new interfaces with 2 = different=20 addresses types. One which uses the eui-64, another which is backward = compatible=20 with v4 address ( fe80::ipv4). Also, it generated another one which is( = ::ipv4).=20 below is the output of the 'ipv6 if' command.
    However, neither = of these=20 addresses are working. One is pinging from the inside but not from the = outside (=20 ::163.121.25.3), another from the outside but not from the inside(from = the=20 Solaris, not from another NTv6).
    Does anyone have = an=20 explanation for that???
Hossam El-Ashkar
h_elashkar@ieee.org
----------------------------------------------------------------= ---------------------------------
OUTPUT of " ipv6 if" command on = NT:
 
D:\>ipv6 if
Interface 4:
  link-level = address:=20 00-00-c0-38-5d-d8
    preferred address=20 fe80::200:c0ff:fe38:5dd8/10, infinite/infinite
  link MTU 1500 = (true=20 link MTU 1500)
  current hop limit 128
  reachable time = 30ms=20 (base 30ms)
  retransmission interval 1s
  DAD transmits = 1
Interface 3:
  link-level address:=20 163.121.25.3
    preferred address fe80::a379:1903/10, = infinite/infinite
  link MTU 1480 (true link MTU 1480)
  = current=20 hop limit 128
  reachable time 38094ms (base 30000ms)
 =20 retransmission interval 1s
  DAD transmits 1
Interface = 2:
 =20 link-level address: 0.0.0.0
    preferred address=20 ::163.121.25.3/96, infinite/infinite
  link MTU 1480 (true link = MTU=20 1480)
  current hop limit 128
  reachable time 0ms (base = 0ms)
  retransmission interval 0s
  DAD transmits = 0
Interface=20 1:
  link-level address:
    preferred address = ::1/0,=20 infinite/infinite
  link MTU 1460 (true link MTU 0)
  = current=20 hop limit 1
  reachable time 0ms (base 0ms)
  = retransmission=20 interval 0s
  DAD transmits 0
 
 
------=_NextPart_000_0008_01BDA85A.CB493EE0-- From richdr@microsoft.com Tue Jul 7 15:43:10 1998 From: richdr@microsoft.com (Richard Draves) Date: Tue, 7 Jul 1998 07:43:10 -0700 Subject: 07/06/98 6Bone Routing Report Message-ID: <4D0A23B3F74DD111ACCD00805F31D81005832569@red-msg-50.dns.microsoft.com> What's happening with 6bone routing? I received several truncated reports over the weekend, and now a report showing a big jump in routing instability? Rich > -----Original Message----- > From: owner-6bone-routing-report@merit.edu > [mailto:owner-6bone-routing-report@merit.edu] > Sent: Monday, July 06, 1998 11:15 PM > To: 6bone-routing-report@merit.edu > Subject: 07/06/98 6Bone Routing Report > > > See http://www.merit.edu/ipma for a more detailed report on routing > problems and recommendations on ways service providers can limit the > spread of invalid routing information. > Send comments and questions to ipma-support@merit.edu > > To unsubscribe from this list, send mail to > 6bone-routing-report-request@merit.edu. > A hypermail archive is available at > http://www.merit.net/mail.archives/html/6bone-routing-report/ > > Also see http://www.caida.org for more information about Internet > statistics collection research efforts. > > --------------------------------------------- > This report is for 07/06/98, peering with > VIAGENIE (AS10566) CISCO (AS109) CICNET (AS1225) ANSNET > (AS1673) WIDE (AS2500) TELEBIT (AS3263) NUS-IRDU (AS7610) > --------------------------------------------- > > Size of 6Bone Routing Table: > Max = 112, Min = 0, Average = 37 > 49 Unique Autonomous System (AS) numbers > > BGP4+ Traffic Summary: > Announcements = 105470 Withdraws = 16613 Unique Routes = 94 > > Non-6Bone Prefixes (outside of 3ffe::/16): > -------------------------------- > 0000::/0 path 10566 7610 237 1225 1312 (LORE/VT) > 1000::/4 path 10566 5408 1752 3185 786 1717 5623 5609 48 (NRL/INNER) > 1800::/4 path 7610 10566 237 1225 2914 (NWNET) > 3000::/7 path 10566 7610 237 1225 1312 (LORE/VT) > 3fff:ff00::/24 path 7610 10566 237 109 1673 237 1225 1275 > 1717 137 (INFN-CNAF) > 5f00:4700::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > 5f00:6d00::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > 5f01:7800::/32 path 1225 (CICNET) > 5f04:c500:cb26:1100::/64 path 10566 5408 559 2547 1103 1673 > 237 109 (CISCO) > 5f06:8900::/32 path 1673 (ANSNET) > 5f0b:4f00::/32 path 10566 5408 559 2547 1103 1673 237 109 2895 (INR) > 5f0d:e900:ce9c:9400::/64 path 1225 (CICNET) > 5f0f:8800::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > 5f10:8800::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > 5f10:ffff::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > 5f11:b600::/32 path 10566 5408 559 2547 1103 1673 237 109 > 4534 (NETGOD/LAB/IXA) > 5f11:d000:cca2:e400::/64 path 10566 5408 559 2547 1103 1673 > 237 109 (CISCO) > ffff:ff00::/24 path 109 1673 5609 1849 1752 (BT-LABS) > > Poorly Aggregated Prefixes (>24): > -------------------------------- > UIO (3ffe:2a00::/24) had 6 route(s) > 3ffe:2a00:200:1003::/64 path 1673 5609 1849 1752 224 (UIO) > 3ffe:2a00:200:1004::/64 path 1673 5609 1849 1752 224 (UIO) > 3ffe:2a00:200:1005::/64 path 1673 5609 1849 1752 224 (UIO) > 3ffe:2a00:200:1010::/64 path 1673 5609 1849 1752 224 (UIO) > 3ffe:2a00:1ff:f002::/64 path 1673 5609 1849 1752 224 (UIO) > 3ffe:2a00:200:1002::/64 path 1673 5609 1849 1752 224 (UIO) > > CISCO (3ffe:c00::/24) had 3 route(s) > 3ffe:c00:8004:1::/80 path 1673 5609 4555 109 8176 () > 3ffe:c00:800a::/48 path 1673 5609 4555 109 4534 (NETGOD/LAB/IXA) > 3ffe:c00:8004::/48 path 1673 5609 4555 109 8176 () > > ETRI (3ffe:2e00::/24) had 3 route(s) > 3ffe:2e00::ffff:ffff:ffff:ffff/128 path 109 4555 1849 786 > 1717 1103 1673 237 1225 5609 48 7081 10566 237 3559 (ETRI) > 3ffe:2e00:0:ffff:ffff:ffff:ffff:ffff/128 path 109 4555 > 1849 786 1717 1103 1673 237 1225 5609 48 7081 10566 237 3559 (ETRI) > 3ffe:2e00::1/128 path 1225 5609 5623 1890 1849 1752 48 > 7081 10566 237 3559 (ETRI) > > JANET (3ffe:2100::/24) had 3 route(s) > 3ffe:2101:0:ffff::2/127 path 1225 5609 48 1752 (BT-LABS) > 3ffe:2101:0:ffff:ffff:ffff:ffff:fffe/127 path 1225 1275 > 1103 2839 5609 1673 237 10566 5408 1752 (BT-LABS) > 3ffe:2101::/48 path 1225 5609 48 1752 3185 (ULANC) > > UUNET-UK (3ffe:1100::/24) had 2 route(s) > 3ffe:1100:0:c01::/64 path 1673 5609 5623 559 5408 1752 (BT-LABS) > 3ffe:1108:40a::/48 path 1225 1275 8319 5539 (SPACENET-DE) > > INFN-CNAF (3ffe:2300::/24) had 2 route(s) > 3ffe:23ff::/32 path 1673 5609 1225 237 10566 7081 48 1752 > 5408 8253 (DUTHNET) > 3ffe:23f0::/28 path 1673 5609 1849 1752 5408 8253 (DUTHNET) > > BT-LABS (3ffe:2c00::/24) had 2 route(s) > 3ffe:2c00:0:ffff::4/127 path 1673 5609 1849 1752 224 (UIO) > 3ffe:2c00:0:ffff:ffff:ffff:ffff:fffe/127 path 1225 1275 > 1103 2839 5609 1673 237 10566 5408 1752 224 (UIO) > > NRL (3ffe:f00::/24) had 2 route(s) > 3ffe:f01:0:ffff::c/126 path 1225 48 1752 (BT-LABS) > 3ffe:f01:0:ffff::d/126 path 1225 5609 1849 1752 (BT-LABS) > > GRNET (3ffe:2d00::/24) had 2 route(s) > 3ffe:2d00:3::/48 path 1673 5609 1849 1752 5408 8643 (UOA) > 3ffe:2dff:ffff::/48 path 1225 1275 1717 559 2547 1103 > 5623 1849 2839 5609 1673 237 10566 5408 8643 (UOA) > > SURFNET (3ffe:600::/24) had 2 route(s) > 3ffe:604:2::/48 path 1673 5609 5623 559 2547 1103 1891 > (VUB-ULB/DIGITAL-BE) > 3ffe:608:1::/48 path 1225 (CICNET) > > TEST-TLA-6BONE (3ffe::/16) had 2 route(s) > 3ffe:ffff:ffff:ffff::/64 path 109 4555 1849 786 1717 1103 > 1673 237 10566 5408 1752 224 (UIO) > 3ffe:ffff:ffff::/48 path 1225 1275 1717 1835 2839 5609 > 1673 237 10566 5408 1752 3185 (ULANC) > > UL (3ffe:1b00::/24) had 1 route(s) > 3ffe:1b01::/32 path 1673 5609 5623 559 1930 (RCCN) > > JOIN (3ffe:400::/24) had 1 route(s) > 3ffe:400:1c0::/48 path 1225 5609 48 8319 (REGIO-DE) > > SWITCH (3ffe:2000::/24) had 1 route(s) > 3ffe:2024:1000::/36 path 1673 5609 5623 559 1930 (RCCN) > > UNI-C (3ffe:1400::/24) had 1 route(s) > 3ffe:1402:1:1::/64 path 1225 5609 1849 5539 1273 (ECRC) > > WIDE (3ffe:500::/24) had 1 route(s) > 3ffe:501:0:1800::/56 path 1673 5609 1225 237 7610 2500 (WIDE) > > INR (3ffe:2400::/24) had 1 route(s) > 3ffe:2401::/32 path 1673 5609 4555 109 2895 2854 (STC-IPNG) > > VIAGENIE (3ffe:b00::/24) had 1 route(s) > 3ffe:b00:1800::/40 path 1673 5609 1225 237 10566 8111 () > > The Top Five Most Active Prefixes: > ---------------------------------- > 1. ANSNET (3ffe:d00::/24) had 30383 BGP+ updates (1120 unique aspaths) > 1225 5609 1673 (1019) > 2500 33 5609 1673 (983) > 109 4555 5609 1673 (892) > 1225 1275 1103 2839 5609 1673 (785) > 2500 109 4555 5609 1673 (663) > 109 1673 (569) > 2500 109 1673 (503) > 109 33 5609 1673 (478) > 109 5623 33 5609 1673 (389) > 10566 5408 559 5623 2839 5609 1673 (335) > 1225 1275 1103 1673 (304) > ...Truncated... > > 2. SWISSCOM (3ffe:1e00::/24) had 3601 BGP+ updates (10 unique aspaths) > 1673 5609 5623 3303 (1838) > 1225 5609 5623 3303 (926) > 1225 1275 559 3303 (787) > 10566 5408 559 3303 (11) > 7610 10566 5408 559 3303 (10) > 109 4555 5609 5623 3303 (7) > 2500 33 5609 5623 3303 (6) > 2500 109 4555 5609 5623 3303 (4) > 109 33 5609 5623 3303 (2) > 10566 7081 48 5609 5623 3303 (1) > > 3. NRL (3ffe:f01:0:ffff::c/126) had 2317 BGP+ updates (5 > unique aspaths) > 1673 5609 1849 1752 (1613) > 1225 5609 1849 1752 (695) > 10566 5408 1752 (6) > 1225 5609 48 1752 (2) > 1225 48 1752 (1) > > 4. SICS (3ffe:200::/24) had 2265 BGP+ updates (17 unique aspaths) > 1673 5609 2839 (1836) > 109 4555 5609 1849 2839 (107) > 109 1673 5609 2839 (97) > 2500 33 5609 1849 2839 (90) > 2500 109 1673 5609 2839 (88) > 10566 5408 559 5623 2839 (11) > 2500 109 4555 5609 2839 (5) > 109 4555 5609 2839 (5) > 2500 33 5609 2839 (5) > 1673 5609 1849 2839 (4) > 1225 1275 1103 2839 (3) > ...Truncated... > > 5. DIGITAL-BE (3ffe:604:2::/48) had 1964 BGP+ updates (21 > unique aspaths) > 1673 5609 5623 559 2547 1103 1891 (1742) > 1673 5609 2839 5623 559 2547 1103 1891 (97) > 10566 5408 559 2547 1103 1891 (13) > 1225 5609 5623 559 2547 1103 1891 (13) > 1225 1275 559 2547 1103 1891 (11) > 7610 10566 5408 559 2547 1103 1891 (11) > 2500 109 4555 5609 5623 559 2547 1103 1891 (8) > 1225 1275 1717 559 2547 1103 1891 (8) > 109 4555 5609 5623 559 2547 1103 1891 (7) > 2500 109 1673 5609 5623 559 2547 1103 1891 (3) > 109 1673 5609 5623 559 2547 1103 1891 (3) > ...Truncated... > From shilpa@cse.iitb.ernet.in Tue Jul 7 17:00:20 1998 From: shilpa@cse.iitb.ernet.in (Shilpa Ashok Deshpande) Date: Tue, 7 Jul 1998 21:30:20 +0530 (IST) Subject: Request for a tunnel connection. In-Reply-To: <199807031250.FAA10013@zephyr.isi.edu> Message-ID: Hi! - I am looking for a connecting point to 6bone. - Location : IIT Powai, Mumbai, INDIA - Purpose : For M.Tech. Project Thanks, Regards, Shilpa ---------------------------------- Ms. Shilpa Deshpande. M.Tech. CS, IIT Powai, Mumbai, INDIA email: shilpa@cse.iitb.ernet.in ---------------------------------- From Marc.Blanchet@viagenie.qc.ca Tue Jul 7 17:27:39 1998 From: Marc.Blanchet@viagenie.qc.ca (Marc Blanchet) Date: Tue, 07 Jul 1998 12:27:39 -0400 Subject: I-D ACTION:draft-blanchet-ipaddressalloc-00.txt Message-ID: <3.0.5.32.19980707122739.00adba50@mail.viagenie.qc.ca> Hi, a first cut of a draft on an allocation scheme. Comments appreciated. Regards, Marc. ---------------------------------------------------------------------------- ------------------------------- A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A flexible allocation scheme for IP addresses (IPv4 and IPv6) Author(s) : M. Blanchet Filename : draft-blanchet-ipaddressalloc-00.txt Pages : 5 Date : 06-Jul-98 This draft presents an IP address allocation scheme that enables the IP allocator (the organisation that allocates addresses) to postpone the final decision of prefix length by keeping space between allocated bits of the different parts of the IP address. This enables the allocator to change the different part lengths of the prefix (TLA, subTLA, SLA, ...) even after allocated spaces. This scheme is applicable to both IPv4 and IPv6 but is envisionned mainly for IPv6 where the address space is larger and more flexible. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-blanchet-ipaddressalloc-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-blanchet-ipaddressalloc-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-blanchet-ipaddressalloc-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <19980706163222.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-blanchet-ipaddressalloc-00.txt ----------------------------------------------------------- Marc Blanchet | Marc.Blanchet@viagenie.qc.ca Viagénie inc. | http://www.viagenie.qc.ca 3107 des hôtels | tél.: 418-656-9254 Ste-Foy, Québec | fax.: 418-656-0183 Canada, G1W 4W5 | radio: VA2-JAZ ------------------------------------------------------------ pgp :57 86 A6 83 D3 A8 58 32 F7 0A BB BD 5F B2 4B A7 ------------------------------------------------------------ Auteur du livre TCP/IP Simplifié, Éditions Logiques, 1997 ------------------------------------------------------------ From masaki@merit.edu Tue Jul 7 20:10:22 1998 From: masaki@merit.edu (Masaki Hirabaru) Date: Tue, 07 Jul 1998 15:10:22 -0400 Subject: 07/06/98 6Bone Routing Report In-Reply-To: Your message of "Tue, 07 Jul 1998 07:43:10 PDT." <4D0A23B3F74DD111ACCD00805F31D81005832569@red-msg-50.dns.microsoft.com> Message-ID: <199807071910.PAA10600@merit.edu> Hi. Richard and 6bone folks, Our 6bone routing data collection has not been working from 2pm on July 2 to 11am on July 6 due to the NFS server down. So, the 6bone routing reports issued on July 3rd though Today (July 7th) have been empty or incomplete. About routing instability, our collected data says there has been considerable instability from 9pm Yesterday to 2am Today (EDT). I'd think that this was not affected by our reporting system malfunctioning. Masaki > From: Richard Draves > To: "'6bone'" <6bone@ISI.EDU> > Subject: RE: 07/06/98 6Bone Routing Report > Date: Tue, 7 Jul 1998 07:43:10 -0700 > X-Mailer: Internet Mail Service (5.5.2328.0) > Sender: owner-6bone@ISI.EDU > Precedence: bulk > > What's happening with 6bone routing? I received several truncated reports > over the weekend, and now a report showing a big jump in routing > instability? > > Rich > > > -----Original Message----- > > From: owner-6bone-routing-report@merit.edu > > [mailto:owner-6bone-routing-report@merit.edu] > > Sent: Monday, July 06, 1998 11:15 PM > > To: 6bone-routing-report@merit.edu > > Subject: 07/06/98 6Bone Routing Report > > > > > > See http://www.merit.edu/ipma for a more detailed report on routing > > problems and recommendations on ways service providers can limit the > > spread of invalid routing information. > > Send comments and questions to ipma-support@merit.edu > > > > To unsubscribe from this list, send mail to > > 6bone-routing-report-request@merit.edu. > > A hypermail archive is available at > > http://www.merit.net/mail.archives/html/6bone-routing-report/ > > > > Also see http://www.caida.org for more information about Internet > > statistics collection research efforts. > > > > --------------------------------------------- > > This report is for 07/06/98, peering with > > VIAGENIE (AS10566) CISCO (AS109) CICNET (AS1225) ANSNET > > (AS1673) WIDE (AS2500) TELEBIT (AS3263) NUS-IRDU (AS7610) > > --------------------------------------------- > > > > Size of 6Bone Routing Table: > > Max = 112, Min = 0, Average = 37 > > 49 Unique Autonomous System (AS) numbers > > > > BGP4+ Traffic Summary: > > Announcements = 105470 Withdraws = 16613 Unique Routes = 94 > > > > Non-6Bone Prefixes (outside of 3ffe::/16): > > -------------------------------- > > 0000::/0 path 10566 7610 237 1225 1312 (LORE/VT) > > 1000::/4 path 10566 5408 1752 3185 786 1717 5623 5609 48 (NRL/INNER) > > 1800::/4 path 7610 10566 237 1225 2914 (NWNET) > > 3000::/7 path 10566 7610 237 1225 1312 (LORE/VT) > > 3fff:ff00::/24 path 7610 10566 237 109 1673 237 1225 1275 > > 1717 137 (INFN-CNAF) > > 5f00:4700::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > > 5f00:6d00::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > > 5f01:7800::/32 path 1225 (CICNET) > > 5f04:c500:cb26:1100::/64 path 10566 5408 559 2547 1103 1673 > > 237 109 (CISCO) > > 5f06:8900::/32 path 1673 (ANSNET) > > 5f0b:4f00::/32 path 10566 5408 559 2547 1103 1673 237 109 2895 (INR) > > 5f0d:e900:ce9c:9400::/64 path 1225 (CICNET) > > 5f0f:8800::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > > 5f10:8800::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > > 5f10:ffff::/32 path 10566 5408 559 2547 1103 1673 237 109 (CISCO) > > 5f11:b600::/32 path 10566 5408 559 2547 1103 1673 237 109 > > 4534 (NETGOD/LAB/IXA) > > 5f11:d000:cca2:e400::/64 path 10566 5408 559 2547 1103 1673 > > 237 109 (CISCO) > > ffff:ff00::/24 path 109 1673 5609 1849 1752 (BT-LABS) > > > > Poorly Aggregated Prefixes (>24): > > -------------------------------- > > UIO (3ffe:2a00::/24) had 6 route(s) > > 3ffe:2a00:200:1003::/64 path 1673 5609 1849 1752 224 (UIO) > > 3ffe:2a00:200:1004::/64 path 1673 5609 1849 1752 224 (UIO) > > 3ffe:2a00:200:1005::/64 path 1673 5609 1849 1752 224 (UIO) > > 3ffe:2a00:200:1010::/64 path 1673 5609 1849 1752 224 (UIO) > > 3ffe:2a00:1ff:f002::/64 path 1673 5609 1849 1752 224 (UIO) > > 3ffe:2a00:200:1002::/64 path 1673 5609 1849 1752 224 (UIO) > > > > CISCO (3ffe:c00::/24) had 3 route(s) > > 3ffe:c00:8004:1::/80 path 1673 5609 4555 109 8176 () > > 3ffe:c00:800a::/48 path 1673 5609 4555 109 4534 (NETGOD/LAB/IXA) > > 3ffe:c00:8004::/48 path 1673 5609 4555 109 8176 () > > > > ETRI (3ffe:2e00::/24) had 3 route(s) > > 3ffe:2e00::ffff:ffff:ffff:ffff/128 path 109 4555 1849 786 > > 1717 1103 1673 237 1225 5609 48 7081 10566 237 3559 (ETRI) > > 3ffe:2e00:0:ffff:ffff:ffff:ffff:ffff/128 path 109 4555 > > 1849 786 1717 1103 1673 237 1225 5609 48 7081 10566 237 3559 (ETRI) > > 3ffe:2e00::1/128 path 1225 5609 5623 1890 1849 1752 48 > > 7081 10566 237 3559 (ETRI) > > > > JANET (3ffe:2100::/24) had 3 route(s) > > 3ffe:2101:0:ffff::2/127 path 1225 5609 48 1752 (BT-LABS) > > 3ffe:2101:0:ffff:ffff:ffff:ffff:fffe/127 path 1225 1275 > > 1103 2839 5609 1673 237 10566 5408 1752 (BT-LABS) > > 3ffe:2101::/48 path 1225 5609 48 1752 3185 (ULANC) > > > > UUNET-UK (3ffe:1100::/24) had 2 route(s) > > 3ffe:1100:0:c01::/64 path 1673 5609 5623 559 5408 1752 (BT-LABS) > > 3ffe:1108:40a::/48 path 1225 1275 8319 5539 (SPACENET-DE) > > > > INFN-CNAF (3ffe:2300::/24) had 2 route(s) > > 3ffe:23ff::/32 path 1673 5609 1225 237 10566 7081 48 1752 > > 5408 8253 (DUTHNET) > > 3ffe:23f0::/28 path 1673 5609 1849 1752 5408 8253 (DUTHNET) > > > > BT-LABS (3ffe:2c00::/24) had 2 route(s) > > 3ffe:2c00:0:ffff::4/127 path 1673 5609 1849 1752 224 (UIO) > > 3ffe:2c00:0:ffff:ffff:ffff:ffff:fffe/127 path 1225 1275 > > 1103 2839 5609 1673 237 10566 5408 1752 224 (UIO) > > > > NRL (3ffe:f00::/24) had 2 route(s) > > 3ffe:f01:0:ffff::c/126 path 1225 48 1752 (BT-LABS) > > 3ffe:f01:0:ffff::d/126 path 1225 5609 1849 1752 (BT-LABS) > > > > GRNET (3ffe:2d00::/24) had 2 route(s) > > 3ffe:2d00:3::/48 path 1673 5609 1849 1752 5408 8643 (UOA) > > 3ffe:2dff:ffff::/48 path 1225 1275 1717 559 2547 1103 > > 5623 1849 2839 5609 1673 237 10566 5408 8643 (UOA) > > > > SURFNET (3ffe:600::/24) had 2 route(s) > > 3ffe:604:2::/48 path 1673 5609 5623 559 2547 1103 1891 > > (VUB-ULB/DIGITAL-BE) > > 3ffe:608:1::/48 path 1225 (CICNET) > > > > TEST-TLA-6BONE (3ffe::/16) had 2 route(s) > > 3ffe:ffff:ffff:ffff::/64 path 109 4555 1849 786 1717 1103 > > 1673 237 10566 5408 1752 224 (UIO) > > 3ffe:ffff:ffff::/48 path 1225 1275 1717 1835 2839 5609 > > 1673 237 10566 5408 1752 3185 (ULANC) > > > > UL (3ffe:1b00::/24) had 1 route(s) > > 3ffe:1b01::/32 path 1673 5609 5623 559 1930 (RCCN) > > > > JOIN (3ffe:400::/24) had 1 route(s) > > 3ffe:400:1c0::/48 path 1225 5609 48 8319 (REGIO-DE) > > > > SWITCH (3ffe:2000::/24) had 1 route(s) > > 3ffe:2024:1000::/36 path 1673 5609 5623 559 1930 (RCCN) > > > > UNI-C (3ffe:1400::/24) had 1 route(s) > > 3ffe:1402:1:1::/64 path 1225 5609 1849 5539 1273 (ECRC) > > > > WIDE (3ffe:500::/24) had 1 route(s) > > 3ffe:501:0:1800::/56 path 1673 5609 1225 237 7610 2500 (WIDE) > > > > INR (3ffe:2400::/24) had 1 route(s) > > 3ffe:2401::/32 path 1673 5609 4555 109 2895 2854 (STC-IPNG) > > > > VIAGENIE (3ffe:b00::/24) had 1 route(s) > > 3ffe:b00:1800::/40 path 1673 5609 1225 237 10566 8111 () > > > > The Top Five Most Active Prefixes: > > ---------------------------------- > > 1. ANSNET (3ffe:d00::/24) had 30383 BGP+ updates (1120 unique aspaths) > > 1225 5609 1673 (1019) > > 2500 33 5609 1673 (983) > > 109 4555 5609 1673 (892) > > 1225 1275 1103 2839 5609 1673 (785) > > 2500 109 4555 5609 1673 (663) > > 109 1673 (569) > > 2500 109 1673 (503) > > 109 33 5609 1673 (478) > > 109 5623 33 5609 1673 (389) > > 10566 5408 559 5623 2839 5609 1673 (335) > > 1225 1275 1103 1673 (304) > > ...Truncated... > > > > 2. SWISSCOM (3ffe:1e00::/24) had 3601 BGP+ updates (10 unique aspaths) > > 1673 5609 5623 3303 (1838) > > 1225 5609 5623 3303 (926) > > 1225 1275 559 3303 (787) > > 10566 5408 559 3303 (11) > > 7610 10566 5408 559 3303 (10) > > 109 4555 5609 5623 3303 (7) > > 2500 33 5609 5623 3303 (6) > > 2500 109 4555 5609 5623 3303 (4) > > 109 33 5609 5623 3303 (2) > > 10566 7081 48 5609 5623 3303 (1) > > > > 3. NRL (3ffe:f01:0:ffff::c/126) had 2317 BGP+ updates (5 > > unique aspaths) > > 1673 5609 1849 1752 (1613) > > 1225 5609 1849 1752 (695) > > 10566 5408 1752 (6) > > 1225 5609 48 1752 (2) > > 1225 48 1752 (1) > > > > 4. SICS (3ffe:200::/24) had 2265 BGP+ updates (17 unique aspaths) > > 1673 5609 2839 (1836) > > 109 4555 5609 1849 2839 (107) > > 109 1673 5609 2839 (97) > > 2500 33 5609 1849 2839 (90) > > 2500 109 1673 5609 2839 (88) > > 10566 5408 559 5623 2839 (11) > > 2500 109 4555 5609 2839 (5) > > 109 4555 5609 2839 (5) > > 2500 33 5609 2839 (5) > > 1673 5609 1849 2839 (4) > > 1225 1275 1103 2839 (3) > > ...Truncated... > > > > 5. DIGITAL-BE (3ffe:604:2::/48) had 1964 BGP+ updates (21 > > unique aspaths) > > 1673 5609 5623 559 2547 1103 1891 (1742) > > 1673 5609 2839 5623 559 2547 1103 1891 (97) > > 10566 5408 559 2547 1103 1891 (13) > > 1225 5609 5623 559 2547 1103 1891 (13) > > 1225 1275 559 2547 1103 1891 (11) > > 7610 10566 5408 559 2547 1103 1891 (11) > > 2500 109 4555 5609 5623 559 2547 1103 1891 (8) > > 1225 1275 1717 559 2547 1103 1891 (8) > > 109 4555 5609 5623 559 2547 1103 1891 (7) > > 2500 109 1673 5609 5623 559 2547 1103 1891 (3) > > 109 1673 5609 5623 559 2547 1103 1891 (3) > > ...Truncated... > > From Y.Adamopoulos@noc.ntua.gr Wed Jul 8 10:31:14 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Wed, 8 Jul 1998 12:31:14 +0300 Subject: KAME stack Message-ID: <19980708123114.B25004@noc.ntua.gr> Hi, I want to know experiences with the KAME stack, if anyone on the 6bone uses it before I try to work with it on NetBSD/pmax ;-) -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From h_elashkar@ieee.org Wed Jul 8 15:35:58 1998 From: h_elashkar@ieee.org (Hossam El-Ashkar) Date: Wed, 8 Jul 1998 17:35:58 +0300 Subject: NT strangness Message-ID: <000a01bdaa7d$d7dd2430$031979a3@semsem.cn4.ml.org> Thank you Richard, and mike. I have configured the automatic tunnel interface on the Solaris. They are both working well now ( the NT speaks to Solaris and vice versa).... I am very sorry to have caused so much debate, but there are a lot of addresses types in v6 that I got confused. I only have one more question and a request. The question is, what is the usefulness of the Carpenter/Jung draft compatible address? does it allow the v4 only hosts to speak to v6, or what? And the request is that I want to join the 6bone, can any one give me a tunnel? Thank you again. ---------------------------------------------------------------------------- ---- Hossam El-Ashkar h_elashkar@ieee.org From richdr@microsoft.com Wed Jul 8 17:43:07 1998 From: richdr@microsoft.com (Richard Draves) Date: Wed, 8 Jul 1998 09:43:07 -0700 Subject: NT strangness Message-ID: <4D0A23B3F74DD111ACCD00805F31D81005832587@red-msg-50.dns.microsoft.com> > The question is, what is the usefulness of the > Carpenter/Jung draft > compatible address? does it allow the v4 only hosts to speak > to v6, or what? The Carpenter/Jung 6-over-4 draft does not allow v4 only hosts to speak to v6. (That's what translators do. Several groups are also working on translators. For example see http://www.cs.washington.edu/research/networking/napt/.) 6-over-4 doesn't use any special type of address, that's one of the great things about it. Like configured & automatic tunnels, 6-over-4 is a way of transmitting v6 packets over a v4 network by encapsulating them in v4 packets. Unlike configured & automatic tunnels, 6-over-4 treats the v4 network as a real link layer, with link-local addresses, Neighbor Discovery, etc. Here's a scenario where 6-over-4 is incredibly useful: Suppose you have a campus network with many v4-only routers. The campus network supports v4 multicast across the campus. Sprinkled around the campus are v6 machines (which also support v4) that you want to connect to the 6bone, but for whatever reason (availability, cost, time, stability) you haven't yet upgraded the campus routers to support v6. What to do? One solution is to manually setup a network of configured tunnels between all the v6 machines on a campus and a campus gateway to the 6bone. There's a lot of effort here to create and maintain all the configured tunnels. Every new v6 machine on campus requires additional work. A much better solution is to use 6-over-4 to connect all the campus v6 machines to the campus 6bone gateway. Because the campus v4 network is a virtual link layer for v6, you can use stateless autoconfiguration. New v6 machines on campus will automatically discover the 6bone gateway and configure themselves with global 6bone addresses! The only configured tunnel that you need to create & maintain is between the campus 6bone gateway and the 6bone backbone. The only caveat is that the campus v4 network must support v4 multicast. Rich From qv@3com.com Wed Jul 8 22:56:51 1998 From: qv@3com.com (Quaizar Vohra) Date: Wed, 8 Jul 1998 14:56:51 -0700 (PDT) Subject: Looking for some BGP4+ peers Message-ID: <199807082156.OAA01849@lookout.nsd.3com.com> Hi, I am looking for a couple or more of backbone nodes to create tunnels and BGP4+ peering. This is mainly for testing our BGP4+ implementation and there a few 3Com customers who did like to join 6bone via our core node. 3Com has a pTLA prefix assigned to it. Lately I haven't been following the 6bone mailing list and might be unware of the changes in operational practises for backbone nodes. Is there a place I can find the requirements for becoming a backbone node or can someone please summarize them. All I remember is that apart from having a pTLA prefix, one has to host a couple of IPv6 DNS Servers, and be able to run BGP4+. Also for people running BGP4+, is there a consensus on whether the NEXT_HOP attribute is mandatory in BGP4+ or not. As for running BGP4+ just for exchanging IPv6 routes, the IPv4 NEXT_HOP attribute doesn't seem to serve any purpose. What is the operational experience. Looking forward to your replies. Thanks Quaizar From rlfink@lbl.gov Thu Jul 9 00:23:16 1998 From: rlfink@lbl.gov (Bob Fink) Date: Wed, 08 Jul 1998 16:23:16 -0700 Subject: Looking for some BGP4+ peers In-Reply-To: <199807082156.OAA01849@lookout.nsd.3com.com> Message-ID: <1312207499-512913901@cnrmail.lbl.gov> Quaizar, At 02:56 PM 7/8/98 -0700, Quaizar Vohra wrote: ... > I am looking for a couple or more of backbone nodes to create >tunnels and BGP4+ peering. This is mainly for testing our BGP4+ >implementation and there a few 3Com customers who did like to join >6bone via our core node. 3Com has a pTLA prefix assigned to it. > > Lately I haven't been following the 6bone mailing list and >might be unware of the changes in operational practises for backbone >nodes. Is there a place I can find the requirements for becoming >a backbone node or can someone please summarize them. All I remember >is that apart from having a pTLA prefix, one has to host a couple >of IPv6 DNS Servers, and be able to run BGP4+. Take a look at the 6bone home page, and go to the pointer on 6bone Routing Practice and related policies Bob From h_elashkar@ieee.org Thu Jul 9 12:08:47 1998 From: h_elashkar@ieee.org (Hossam El-Ashkar) Date: Thu, 9 Jul 1998 14:08:47 +0300 Subject: No subject Message-ID: <000b01bdab29$fe23f4a0$031979a3@semsem.cn4.ml.org> This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BDAB43.174A0F50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am trying to use the snoop you offer with the 5.3 release with = filtering but I cannot. Can you tell me how to configure it to capture = the packets addresses to a certain MAC address?? Also, the file it generates seems to be incompatible with the other = snoops. Can it be exported some how. I need to see the results more = visually!!! Thanx. -------------------------------------------------------------------------= ------- Hossam El-Ashkar h_elashkar@ieee.org =20 ------=_NextPart_000_0008_01BDAB43.174A0F50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
    I am trying to use the snoop you = offer with=20 the 5.3 release with filtering but I cannot. Can you tell me how to = configure it=20 to capture the packets addresses to a certain MAC address??
    Also, the file it generates seems = to be=20 incompatible with the other snoops. Can it be exported some how. I need = to see=20 the results more visually!!!
    Thanx.
Hossam El-Ashkar
h_elashkar@ieee.org
 
------=_NextPart_000_0008_01BDAB43.174A0F50-- From itojun@itojun.org Mon Jul 13 04:17:04 1998 From: itojun@itojun.org (Jun-ichiro itojun Itoh) Date: Mon, 13 Jul 1998 12:17:04 +0900 Subject: KAME stack References: <19980708123114.B25004@noc.ntua.gr> Message-ID: <24206.900299824@coconut.itojun.org> >I want to know experiences with the KAME stack, if anyone on the 6bone uses >it before I try to work with it on NetBSD/pmax ;-) NOTE: it looks that my reply does not reach to 6bone mailing list, maybe due to From: line. If any of you received two of this email please ignore this. Most of the UNIX-based routers in 6bone-jp (Japan 6bone) implements KAME stack. We (kame team) do not have experience with NetBSD/pmax, however, it should work with just a tiny modification into sys/arch/pmax/somewhere. (calling ip6intr() from software interrupt routine) jun-ichiro itojun itoh itojun@kame.net From itojun@itojun.org Mon Jul 13 04:17:38 1998 From: itojun@itojun.org (Jun-ichiro itojun Itoh) Date: Mon, 13 Jul 1998 12:17:38 +0900 Subject: KAME stack In-Reply-To: itojun's message of Mon, 13 Jul 1998 12:17:04 JST. <24206.900299824@coconut.itojun.org> Message-ID: <24224.900299858@coconut.itojun.org> > Most of the UNIX-based routers in 6bone-jp (Japan 6bone) implements > KAME stack. We (kame team) do not have experience with NetBSD/pmax, > however, it should work with just a tiny modification into > sys/arch/pmax/somewhere. (calling ip6intr() from software interrupt > routine) see http://www.kame.net/ and http://www.v6.wide.ad.jp/ for more info. thanks, itojun From boos@cscoms.com Tue Jul 14 03:12:33 1998 From: boos@cscoms.com (Booskorn Tanasomboonkit) Date: Tue, 14 Jul 1998 09:12:33 +0700 Subject: KAME stack References: <24224.900299858@coconut.itojun.org> Message-ID: <35AABE91.95352526@cscoms.com> Dear Sirs, Can anyone help me get out of this mailing list pls forward procedure Thank you in advance Booskorn Jun-ichiro itojun Itoh wrote: > > Most of the UNIX-based routers in 6bone-jp (Japan 6bone) implements > > KAME stack. We (kame team) do not have experience with NetBSD/pmax, > > however, it should work with just a tiny modification into > > sys/arch/pmax/somewhere. (calling ip6intr() from software interrupt > > routine) > > see http://www.kame.net/ and http://www.v6.wide.ad.jp/ for more info. > thanks, > > itojun From bmanning@ISI.EDU Tue Jul 14 14:33:57 1998 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Tue, 14 Jul 1998 06:33:57 -0700 (PDT) Subject: BOUNCE 6bone@zephyr.isi.edu: Non-member submission from [Nagaishi Tutomu ] (fwd) Message-ID: <199807141333.AA24795@zed.isi.edu> NTT would like to be considered for pTLA assignment. Forwarded message: > To: owner-6bone@ISI.EDU > From: owner-6bone@ISI.EDU > Subject: BOUNCE 6bone@zephyr.isi.edu: Non-member submission from [Nagaishi Tutomu ] > > >From 6bone-owner@ISI.EDU Tue Jul 14 03:25:32 1998 > Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) > by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id DAA28174 > for <6bone@zephyr.isi.edu>; Tue, 14 Jul 1998 03:25:32 -0700 (PDT) > Received: from tama3.tas.ntt.co.jp (tama3.tas.ntt.co.jp [192.68.248.40]) > by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id DAA09339 > for <6bone@isi.edu>; Tue, 14 Jul 1998 03:25:29 -0700 (PDT) > Received: from nttmail.ecl.ntt.co.jp (nttmail.tas.ntt.co.jp [192.68.248.11]) > by tama3.tas.ntt.co.jp (8.8.8/3.6W/tama3) with ESMTP id TAA07774; > Tue, 14 Jul 1998 19:25:27 +0900 (JST) > Received: from nttslb.slab.ntt.co.jp > by nttmail.ecl.ntt.co.jp (8.8.8/3.6W/nttmail) with ESMTP id TAA14969; > Tue, 14 Jul 1998 19:25:25 +0900 (JST) > Received: by nttslb.slab.ntt.co.jp (8.8.8+2.7Wbeta7/3.4W4/mx) with SMTP > id TAA17209; Tue, 14 Jul 1998 19:25:22 +0900 (JST) > Message-Id: <199807141025.TAA17209@nttslb.slab.ntt.co.jp> > X-Sender: nagaishi@nttslb.slab.ntt.co.jp > X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3-Jr2 (32) > Date: Tue, 14 Jul 1998 19:25:22 +0900 > To: RLFink@lbl.gov > From: Nagaishi Tutomu > Subject: Request for pTLA for NTT Software Labs. > Cc: 6bone@ISI.EDU > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > > Dear Bob, > > > I am writing to you because NTT Software Laboratories would like to become > one of the 6bone backbone sites. Below I give a short outline of NTT and > show how we meet the criteria for pTLA assignment in the Internet Draft > [Alain Durand]. > > I hope that after studying these responses, you will assign a pTLA to us. > If you do, we will expand our 6bone connectivity service. > > Regards, > > > Tsutomu Nagaishi > Researcher > NTT Software Laboratories > > > ***OUR ORGANIZATION*** > > Nippon Telegraph and Telephone Corporation (NTT) is the largest > communication carrier in Japan. NTT's Software Laboratories handle research > and development of networks and their application layer. > > Further information about NTT is available at http://www.ntt.co.jp/. > > ------------------------------------------------------------------ > Evidence of meeting criteria > > >> 1. Must have experience with IPv6 in the 6bone, at least as a leaf site, > >>and preferably as an NLA transit under a pTLA. > > We have been experimenting with 6bone connectivity: > - leaf site (3FFE:0501:0412/48) under 6bone JP-pTLA since 1997. > - leaf site (3FFE:1200:3002/48) under DEC CA/US-pTLA since 1997. > - NLA network (3FFE:0503:/32) under 6bone JP-pTLA since December > 1997. > > We have assigned one address prefix for multiple sites below our NLA and > are now providing transit service for 6bone connectivity. > > We have already provided information about the NLA transit experiment > (e.g., the registry of connection sites). The URL for this information is > http://www.nttv6.net. > > >> 2. Must have the ability and intent to provide "production-like" 6bone > >> backbone service to provide a robust and operationally reliable 6bone > >> backbone. > > NTT already has an ISP business division. Furthermore, in NTT Software > Laboratories we have been experimenting with 6bone connectivity. Therefore, > NTT has the skills needed to provide a "production-like" 6bone backbone > service. > > >> 3. Must have a potential "user community" that would be served by becoming > >> a pTLA, e.g., the requester is a major player in a region, country or focus > >> of interest. > > NTT is a major player in Japan and therefore has a large potential user > community. > > >> 4. Must commit to abide by whatever the 6bone backbone operational rules > >> and policies are (currently there are no formal ones, but the Alain Duran > >> draft is a start in trying to define some). > > We will commit to abide by the 6bone backbone operational rules and > policies. > > > Reference > > [Alain Durand] Alain Durand, "6Bone Routing Practice", May 1998, > "Guidelines for 6Bone pTLA sites", p. 5-6. > > -- "When in doubt, Twirl..." -anon From rlfink@lbl.gov Tue Jul 14 17:28:23 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 14 Jul 1998 09:28:23 -0700 Subject: Fwd: Request for pTLA for NTT Software Labs. Message-ID: <1311713991-542602313@cnrmail.lbl.gov> 6bone list: Tsutomu Nagaishi of NTT has requested a pTLA for NTT (see request form below). I would like to respond to this request by the 28th of July, so please send me your comments on this request by closs of business on July 27. Thanks, Bob ====================================== >Date: Tue, 14 Jul 1998 19:25:22 +0900 >To: RLFink@lbl.gov >From: Nagaishi Tutomu >Subject: Request for pTLA for NTT Software Labs. >Cc: 6bone@isi.edu > >Dear Bob, > > >I am writing to you because NTT Software Laboratories would like to become >one of the 6bone backbone sites. Below I give a short outline of NTT and >show how we meet the criteria for pTLA assignment in the Internet Draft >[Alain Durand]. > >I hope that after studying these responses, you will assign a pTLA to us. >If you do, we will expand our 6bone connectivity service. > >Regards, > > >Tsutomu Nagaishi >Researcher >NTT Software Laboratories > > >***OUR ORGANIZATION*** > >Nippon Telegraph and Telephone Corporation (NTT) is the largest >communication carrier in Japan. NTT's Software Laboratories handle research >and development of networks and their application layer. > >Further information about NTT is available at http://www.ntt.co.jp/. > >------------------------------------------------------------------ >Evidence of meeting criteria > >>> 1. Must have experience with IPv6 in the 6bone, at least as a leaf site, >>>and preferably as an NLA transit under a pTLA. > > We have been experimenting with 6bone connectivity: > - leaf site (3FFE:0501:0412/48) under 6bone JP-pTLA since 1997. > - leaf site (3FFE:1200:3002/48) under DEC CA/US-pTLA since 1997. > - NLA network (3FFE:0503:/32) under 6bone JP-pTLA since December > 1997. > > We have assigned one address prefix for multiple sites below our NLA and >are now providing transit service for 6bone connectivity. > > We have already provided information about the NLA transit experiment >(e.g., the registry of connection sites). The URL for this information is >http://www.nttv6.net. > >>> 2. Must have the ability and intent to provide "production-like" 6bone >>> backbone service to provide a robust and operationally reliable 6bone >>> backbone. > > NTT already has an ISP business division. Furthermore, in NTT Software >Laboratories we have been experimenting with 6bone connectivity. Therefore, >NTT has the skills needed to provide a "production-like" 6bone backbone >service. > >>> 3. Must have a potential "user community" that would be served by becoming >>> a pTLA, e.g., the requester is a major player in a region, country or focus >>> of interest. > > NTT is a major player in Japan and therefore has a large potential user >community. > >>> 4. Must commit to abide by whatever the 6bone backbone operational rules >>> and policies are (currently there are no formal ones, but the Alain Duran >>> draft is a start in trying to define some). > > We will commit to abide by the 6bone backbone operational rules and >policies. > > >Reference > >[Alain Durand] Alain Durand, "6Bone Routing Practice", May 1998, > "Guidelines for 6Bone pTLA sites", p. 5-6. > From Y.Adamopoulos@noc.ntua.gr Wed Jul 15 16:34:11 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Wed, 15 Jul 1998 18:34:11 +0300 Subject: private ASNs and cisco IOS Message-ID: <19980715183411.B5384@noc.ntua.gr> Does anyone on the 6bone now make use of private ASNs with cisco boxes? -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From rlfink@lbl.gov Wed Jul 15 17:13:10 1998 From: rlfink@lbl.gov (Bob Fink) Date: Wed, 15 Jul 1998 09:13:10 -0700 Subject: INTEROP pTLA released Message-ID: <1311628504-547744999@cnrmail.lbl.gov> The INTEROP pTLA has been released. not assigned 3FFE:1800::/24 http://www.6bone.net/6bone_pTLA_list.html Thanks, Bob From peterdd@gto.net.om Wed Jul 15 19:41:21 1998 From: peterdd@gto.net.om (peter dawson) Date: Wed, 15 Jul 1998 22:41:21 +0400 Subject: IPv6 Address allocation Message-ID: <35ACF7D1.DEF33A44@gto.net.om> I happened to come across this bit of info on the home IPng home pages and have a question. IPng supports addresses which are four times the number of bits as IPv4 addresses (128 vs. 32). This is 4 Billion times 4 Billion (2^^96) times the size of the IPv4 address space (2^^32). This works out to be: 340,282,366,920,938,463,463,374,607,431,768,211,456 Approximately fifteen percent of the address space is initially allocated. The remaining 85% is reserved for future use. Now my question .... 15% of 4 billion times 4 billion is an awfull lot of IP address space which has been allocated ... for what reasons has these allocations taken place and how will they be used ?? /pete From map@stacken.kth.se Thu Jul 16 00:35:05 1998 From: map@stacken.kth.se (Magnus Ahltorp) Date: 16 Jul 1998 01:35:05 +0200 Subject: IPv6 Address allocation In-Reply-To: peter dawson's message of Wed, 15 Jul 1998 22:41:21 +0400 References: <35ACF7D1.DEF33A44@gto.net.om> Message-ID: > Now my question .... 15% of 4 billion times 4 billion is an awfull > lot of IP address space which has been allocated ... for what > reasons has these allocations taken place and how will they be used It is not only a matter of the number of addresses that can be in use. A lot of addresses has to be wasted to make routing efficient. For example, it is impractical to route at something other than bit boundaries, i.e. the significant part of the address (at a specific router) is the n left bits of the address (indicated with /n after the address). To make the routing feasible, routing must also be hierarchical. This means that there is a top level routing and routing levels beneath that. In the 6bone, the top level routing is performed by the backbone routers as you can see on the various diagrams on the 6bone web site. Hierarchical routing waste even more addresses, since every routing level must have well defined bit boundaries, or to put it in another way, the address is divided into smaller parts. If you look in the Internet draft draft-ietf-ipngwg-addr-arch-v2-06.txt, their suggestion is to have 3 bits for format prefix, 13 bits for TLA (Top-level aggregation identifier), 8 bits reserved, 24 bits NLA (Next-level aggregation identifier), 16 bits for intra-site routing and 64 bits for an interface identifier. This adds up to 128 bits. /Magnus map@stacken.kth.se From Y.Adamopoulos@noc.ntua.gr Thu Jul 16 13:23:33 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Thu, 16 Jul 1998 15:23:33 +0300 Subject: alternative drawing of 6bone tunnels between pTLAs Message-ID: <19980716152333.A29664@noc.ntua.gr> Hi all, Take a look at http://ajax.noc.ntua.gr/~adamo/6bone.gif It displays the tunnels between pTLAs from data drawn out of ftp://ftp.isi.edu/6bone/6bone.db.gz Not as good as the one at 6bone.net site, but something done using Graphviz ;-) -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From rlfink@lbl.gov Thu Jul 16 14:39:55 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 16 Jul 1998 06:39:55 -0700 Subject: alternative drawing of 6bone tunnels between pTLAs In-Reply-To: <19980716152333.A29664@noc.ntua.gr> Message-ID: <1311551229-552393599@cnrmail.lbl.gov> Yiorgos, At 03:23 PM 7/16/98 +0300, Yiorgos Adamopoulos wrote: >Hi all, > >Take a look at http://ajax.noc.ntua.gr/~adamo/6bone.gif > >It displays the tunnels between pTLAs from data drawn out of >ftp://ftp.isi.edu/6bone/6bone.db.gz > >Not as good as the one at 6bone.net site, but something done using Graphviz I like it. Has a certain elegance of free form. Are you going to produce it regularly or was it one time? Thanks, Bob From Y.Adamopoulos@noc.ntua.gr Thu Jul 16 15:22:27 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Thu, 16 Jul 1998 17:22:27 +0300 Subject: alternative drawing of 6bone tunnels between pTLAs In-Reply-To: <1311551229-552393599@cnrmail.lbl.gov>; from Bob Fink on Thu, Jul 16, 1998 at 06:39:55AM -0700 References: <19980716152333.A29664@noc.ntua.gr> <1311551229-552393599@cnrmail.lbl.gov> Message-ID: <19980716172227.C17489@noc.ntua.gr> On Thu, Jul 16, 1998 at 06:39:55AM -0700, Bob Fink wrote: > > Are you going to produce it regularly or was it one time? > I am going to improve the script (so as to show routing protocols) and run it regularly. How often does ftp://ftp.isi.edu/6bone.db.gz gets updated? -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From rlfink@lbl.gov Thu Jul 16 15:41:49 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 16 Jul 1998 07:41:49 -0700 Subject: alternative drawing of 6bone tunnels between pTLAs In-Reply-To: <19980716172227.C17489@noc.ntua.gr> References: <1311551229-552393599@cnrmail.lbl.gov> <19980716152333.A29664@noc.ntua.gr> <1311551229-552393599@cnrmail.lbl.gov> Message-ID: <1311547583-552612909@cnrmail.lbl.gov> Yiorgos, At 05:22 PM 7/16/98 +0300, Yiorgos Adamopoulos wrote: >On Thu, Jul 16, 1998 at 06:39:55AM -0700, Bob Fink wrote: >> >> Are you going to produce it regularly or was it one time? >> > >I am going to improve the script (so as to show routing protocols) and run it >regularly. How often does ftp://ftp.isi.edu/6bone.db.gz gets updated? I believe it is daily. David Kessens can tell us for sure. When you finish up, please let me know, and I'll put a pointer to it on the 6bone web page. Thanks, Bob From Y.Adamopoulos@noc.ntua.gr Thu Jul 16 16:02:30 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Thu, 16 Jul 1998 18:02:30 +0300 Subject: alternative drawing of 6bone tunnels between pTLAs In-Reply-To: <1311547583-552612909@cnrmail.lbl.gov>; from Bob Fink on Thu, Jul 16, 1998 at 07:41:49AM -0700 References: <1311551229-552393599@cnrmail.lbl.gov> <19980716152333.A29664@noc.ntua.gr> <1311551229-552393599@cnrmail.lbl.gov> <19980716172227.C17489@noc.ntua.gr> <1311547583-552612909@cnrmail.lbl.gov> Message-ID: <19980716180230.B26370@noc.ntua.gr> On Thu, Jul 16, 1998 at 07:41:49AM -0700, Bob Fink wrote: > > When you finish up, please let me know, and I'll put a pointer to it on the 6bone web page. > I am also interested in bug-reports (ie. tunnels between pTLAs than do not show and such). I already had one bug report from CAIRN. -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From seb_col@yahoo.com Thu Jul 16 16:22:24 1998 From: seb_col@yahoo.com (Sébastien Col) Date: Thu, 16 Jul 1998 08:22:24 -0700 (PDT) Subject: IPv6 Address allocation Message-ID: <19980716152224.19107.rocketmail@send1a.yahoomail.com> peter dawson wrote: ... for what reasons has these allocations taken place and how will they be used ?? **It is for the toasters!** _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From Y.Adamopoulos@noc.ntua.gr Thu Jul 16 17:48:25 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Thu, 16 Jul 1998 19:48:25 +0300 Subject: how to use private ASs on 6bone? Message-ID: <19980716194825.A13712@noc.ntua.gr> Hi all, GRNET has customers who in the IPv4 feed use private ASNs. Now we want to use private ASNs for the IPv6 feeds. In collaboration with one of out customers we tried this using AS 65001 but I was unable to remove 65001 from the AS path list. Has anyone else implemented private ASNs like this on the 6bone? the remove-private-AS command does not seem to work on our cisco for BGP4+ (IPv6 addresses). -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From davidk@ISI.EDU Thu Jul 16 18:38:47 1998 From: davidk@ISI.EDU (David Kessens) Date: Thu, 16 Jul 1998 17:38:47 +0000 Subject: alternative drawing of 6bone tunnels between pTLAs In-Reply-To: <19980716172227.C17489@noc.ntua.gr>; from Yiorgos Adamopoulos on Thu, Jul 16, 1998 at 05:22:27PM +0300 References: <19980716152333.A29664@noc.ntua.gr> <1311551229-552393599@cnrmail.lbl.gov> <19980716172227.C17489@noc.ntua.gr> Message-ID: <19980716173847.A29538@ISI.EDU> Yiorgos, On Thu, Jul 16, 1998 at 05:22:27PM +0300, Yiorgos Adamopoulos wrote: > On Thu, Jul 16, 1998 at 06:39:55AM -0700, Bob Fink wrote: > > > > Are you going to produce it regularly or was it one time? > > I am going to improve the script (so as to show routing protocols) and run it > regularly. How often does ftp://ftp.isi.edu/6bone.db.gz gets updated? It's updated daily, somewhere between 00:00-1:00am pacific time. The best source for the file is: ftp://whois.6bone.net/6bone/6bone.db.gz The file is stored at other locations too, for ease of use and fall back purposes in case of failures. Note that you can check for '# EOF' at the end of the file to make sure that you got the complete file. David K. --- From rrockell@sprint.net Thu Jul 16 20:42:31 1998 From: rrockell@sprint.net (Robert Rockell) Date: Thu, 16 Jul 1998 15:42:31 -0400 (EDT) Subject: Soliciting for peers Message-ID: Wanted to solicit if anyone is interested in getting a peering going. I have a /32 (3ffe:2900) and a 7200 with lots-o-ram. Please write rrockell@sprint.net and copy chall@sprint.net if interested This is strictly a non-supported offer, and is independant of Sprinltink Operations (sort of a pet project for some of us). Thanks Rob Rockell Sprintlink Internet Service Center Operations Engineering 703-689-6322 1-800-724-3329, PIN 385-8833 From raphael@icu.ac.kr Fri Jul 17 05:03:40 1998 From: raphael@icu.ac.kr (Raphael Lee) Date: Fri, 17 Jul 1998 13:03:40 +0900 Subject: BGP4+ for Linux IPv6 Message-ID: <001301bdb137$e7ce0c40$2e32fe81@raphael.etri.re.kr> Hello.. This is Raphael Lee in ICU, Korea. I installed Linux Red-Hat 5.0 to PC, and.. deployed IPv6.(kernel 2.1.102) I success to 6bone-kr router.. but..it had two problems.. I want to deploy BGP4+. So, I installed 'mrtd(Merit) binary for linux 2.1.102' . but.. it is not work.. and.. I tried to install 'mrtd source version' but.. it had many compile errors. and.. I tried to install 'gated - IPv6' but.. it is working on FreeBSD. I tried to fix 'gated source' and.. configuration.. but.. It doesn't work... Who knows BGP4+ program for linux 2.1.102 ? or How to install 'mrtd' for linux 2.1.102? Of course, I read all for their "installation guide". I wait... your answer.. See you.. From Y.Adamopoulos@noc.ntua.gr Fri Jul 17 15:57:35 1998 From: Y.Adamopoulos@noc.ntua.gr (Yiorgos Adamopoulos) Date: Fri, 17 Jul 1998 17:57:35 +0300 Subject: alternative drawing of 6bone tunnels between pTLAs In-Reply-To: ; from Simon Leinen on Fri, Jul 17, 1998 at 04:44:38PM +0200 References: <1311551229-552393599@cnrmail.lbl.gov> <19980716152333.A29664@noc.ntua.gr> <1311551229-552393599@cnrmail.lbl.gov> <19980716172227.C17489@noc.ntua.gr> <1311547583-552612909@cnrmail.lbl.gov> <19980716180230.B26370@noc.ntua.gr> Message-ID: <19980717175735.B19994@noc.ntua.gr> On Fri, Jul 17, 1998 at 04:44:38PM +0200, Simon Leinen wrote: > The only problem I have with it is that the nodes are laid out with > very little concern about geographic or (IPv4-) topological distance. I could give it a shot, but: The drawing algorithm is not mine ;-) It is the algorithm that ``dot'' uses to produce graphs. All I do is parse the 6bone.db file and find out the tunnels that exist between pTLAs. Then I feed them to ``dot'' like: graph G { "GRNET" -- "EWD-3COM" "GRNET" -- "SWITCH" : : } I'll see what I can do to put some GIS on the graph ;-) -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE From masaki@merit.edu Fri Jul 17 22:17:50 1998 From: masaki@merit.edu (Masaki Hirabaru) Date: Fri, 17 Jul 1998 17:17:50 -0400 Subject: BGP4+ for Linux IPv6 In-Reply-To: Your message of "Fri, 17 Jul 1998 13:03:40 +0900." <001301bdb137$e7ce0c40$2e32fe81@raphael.etri.re.kr> Message-ID: <199807172117.RAA26735@merit.edu> Hi Raphael, The binary of MRT for Linux 2.1.102 was built on Slackware with my own kernel configuration, so it may or may not run on your Linux box. The snapshot of MRT source code I'm preparing now will run on Redhat 5.1 but will depend on what kind of IPv6 libc you use. In general, questions specific to MRT would go to its users' mailling-list . I'm afraid that IPv6 Gated available from INRIA doesn't run on Linux. I think that you now know that IPv6 API related to socket has been standardized, but other IPv6 extension to routing and network interface API depend on platforms. Thanks, Masaki MRT Project Merit Network, Inc. > Message-ID: <001301bdb137$e7ce0c40$2e32fe81@raphael.etri.re.kr> > From: "Raphael Lee" > To: <6bone@ISI.EDU> > Subject: BGP4+ for Linux IPv6 > Date: Fri, 17 Jul 1998 13:03:40 +0900 > X-Priority: 3 > X-MSMail-Priority: Normal > X-Mailer: Microsoft Outlook Express 4.72.2106.4 > X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 > Sender: owner-6bone@ISI.EDU > Precedence: bulk > > Hello.. This is Raphael Lee in ICU, Korea. > I installed Linux Red-Hat 5.0 to PC, and.. deployed IPv6.(kernel 2.1.102) > I success to 6bone-kr router.. > > but..it had two problems.. > I want to deploy BGP4+. > So, I installed 'mrtd(Merit) binary for linux 2.1.102' . but.. it is not > work.. > and.. I tried to install 'mrtd source version' but.. it had many compile > errors. > and.. I tried to install 'gated - IPv6' but.. it is working on FreeBSD. > I tried to fix 'gated source' and.. configuration.. but.. It doesn't work... > > Who knows BGP4+ program for linux 2.1.102 ? > or How to install 'mrtd' for linux 2.1.102? > Of course, I read all for their "installation guide". > > I wait... your answer.. > > See you.. > > > From rlfink@lbl.gov Thu Jul 23 21:37:23 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 23 Jul 1998 13:37:23 -0700 Subject: ngtrans meeting times for August IETF Message-ID: <1310921451-590278862@cnrmail.lbl.gov> Just received confirmations from the IETF Secretariat: >This is to confirm two one hour slots for NGTRANS as follows: > > > Tuesday, August 25 at 1300- 1400 > other groups scheudled at that time: dasl, swap-BOF, manet, malloc > Tuesday, August 25 at 1415-1515 > other groups scheduled at that time: ircext-BOF, sieve-BOF, manet, > ipsec, malloc Bob From rrockell@sprint.net Mon Jul 27 15:15:55 1998 From: rrockell@sprint.net (Robert Rockell) Date: Mon, 27 Jul 1998 10:15:55 -0400 (EDT) Subject: BGP oddity Message-ID: having trouble with an IGP bgp4+ peering routes are showing up as B 3FFE:2C00::0/24 [200/4] via 3FFE:C00:E:1::1, Null, 00:00:00/never instead of having the interface listed, they are "nulled" -running cisco 0501 code, and this is an IGP peering. Anyone run into this? All peers are tunneled mode ipv6ip. This is causing much problems for our downstreams, and is forcing us to default route to people in less-than-friendly ways. thanks in advance. Thanks Rob Rockell Sprintlink Internet Service Center Operations Engineering 703-689-6322 1-800-724-3329, PIN 385-8833 From roque@cisco.com Mon Jul 27 21:33:55 1998 From: roque@cisco.com (Pedro Marques) Date: Mon, 27 Jul 1998 13:33:55 -0700 (PDT) Subject: BGP oddity In-Reply-To: References: Message-ID: <199807272033.NAA29003@pedrom-ultra.cisco.com> >>>>> "Robert" == Robert Rockell writes: Robert> having trouble with an IGP bgp4+ peering routes are Robert> showing up as B 3FFE:2C00::0/24 [200/4] via Robert> 3FFE:C00:E:1::1, Null, 00:00:00/never Rob, This is a cisco support question which should go to the cisco ipv6 beta mailing list instead of the 6bone list which is not concerned with support of any particular vendor's equipment. Robert> instead of having the interface listed, they are "nulled" They are recursive routes. Routes for which the next-hop is not directly connected. That route should only be in the routing table if a route to 3FFE:C00:E:1::1 is present. Robert> -running cisco 0501 code, and this is an IGP Robert> peering. Anyone run into this? All peers are tunneled Robert> mode ipv6ip. When you send your problem report to cisco please include the config file. Robert> This is causing much problems for our downstreams, and is Robert> forcing us to default route to people in Robert> less-than-friendly ways. It is not clear to me that you have anything unusual. You should have an IGP route to 3ffe:c00:e:1::1 that resolves the BGP route and allows you to forward traffic. regards, Pedro. From rrockell@sprint.net Mon Jul 27 21:46:26 1998 From: rrockell@sprint.net (Robert Rockell) Date: Mon, 27 Jul 1998 16:46:26 -0400 (EDT) Subject: BGP oddity In-Reply-To: <199807272033.NAA29003@pedrom-ultra.cisco.com> Message-ID: Thanks for the message. Please mail me the cisco mailing list domain, and I will sign up for it, and report there. the null routes may not be the problem, but I am not able to send a routing table between two ibgp peers. I moved the necessary peering stuff onto the same router, and then split it again, and this time is stuck in the table. I have always seen bgp routes, but they are not getting put into the routing table. Since most of everyone uses cisco, I just assumed that someone out there would know. NOt trying to diss the ios, but trying to make my 6-bone pass routes. Anyway, thanks for the note. Please send me the mailing list to subscribe to, and I woudl be happy to do so. Thanks Rob Rockell Sprintlink Internet Service Center Operations Engineering 703-689-6322 1-800-724-3329, PIN 385-8833 On Mon, 27 Jul 1998, Pedro Marques wrote: ->>>>>> "Robert" == Robert Rockell writes: -> -> Robert> having trouble with an IGP bgp4+ peering routes are -> Robert> showing up as B 3FFE:2C00::0/24 [200/4] via -> Robert> 3FFE:C00:E:1::1, Null, 00:00:00/never -> ->Rob, ->This is a cisco support question which should go to the cisco ipv6 beta ->mailing list instead of the 6bone list which is not concerned with ->support of any particular vendor's equipment. -> -> Robert> instead of having the interface listed, they are "nulled" -> ->They are recursive routes. Routes for which the next-hop is not directly ->connected. That route should only be in the routing table if a route to ->3FFE:C00:E:1::1 is present. -> -> Robert> -running cisco 0501 code, and this is an IGP -> Robert> peering. Anyone run into this? All peers are tunneled -> Robert> mode ipv6ip. -> ->When you send your problem report to cisco please include the config file. -> -> Robert> This is causing much problems for our downstreams, and is -> Robert> forcing us to default route to people in -> Robert> less-than-friendly ways. -> ->It is not clear to me that you have anything unusual. You should have an ->IGP route to 3ffe:c00:e:1::1 that resolves the BGP route and allows you ->to forward traffic. -> ->regards, -> Pedro. -> -> From Andrew Watkins Thu Jul 30 12:02:21 1998 From: Andrew Watkins (Andrew Watkins) Date: Thu, 30 Jul 1998 12:02:21 +0100 (BST) Subject: Tunneling from a Solaris hosts. Message-ID: <199807301103.MAA21363@rhea.dcs.bbk.ac.uk> Hello, I sure this is an easy one for you lot, but not for me!! I am setting up a IPv6 host, but so far I have been unable to ping hosts past the 6bone. I can ping the 6bone but no others, also I have used Lancaster Univ. ping web program and have failed to ping my IPv6 interface. Any help would be welcome. Andrew Watkins Here is the script of the installation, plus a summary: pv4 tunnel entry: 144.82.29.51 ipv4 tunnel end: 193.63.94.6 ipv6 source: 3ffe:2100:0001:0010::0/64 ipv6 destination: 3FFE:2100:0001:0010:0:C46:B898:10 ==================================================== %/usr/ipv6/etc/conf_ipv6 This script is used to configure the start up scripts for the IPv6 prototype. The file that this script produces is /etc/rc2.d/S70ipv6. This file can be editted after completing this configuration script. Should this node perform automatic tunneling? (y/n) [Y] Configuring tunnel for address ::144.82.29.51 Create a configured tunnel. This is an IPv6 interface that operates by encapsulating IPv6 packets in IPv4 packets. You must provide the IPv4 entry/endpoint of the tunnel as well as the IPv6 source and destination address of the tunnel. For 6BONE connection please consult: http://www-6bone.lbl.gov/6bone/ Should this node do configured tunneling? (y/n) [Y] The following must be the IPv4 address of an existing interface, Enter the IPv4 tunnel entry-point src address [def:144.82.29.51] Enter the IPv4 tunnel exit-point address: 193.63.94.6 Enter the IPv6 source address: 3ffe:2100:0001:0010::0/64 Enter the IPv6 destination address: 3FFE:2100:1:10:0:C46:B898:10 Here is the info you specified for the configured tunnel ipv4 tunnel entry: 144.82.29.51 ipv4 tunnel end: 193.63.94.6 ipv6 source: 3ffe:2100:0001:0010::0/64 ipv6 destination: 3FFE:2100:0001:0010:0:C46:B898:10 Is this correct? y/n [n] y Do you want to create another configured tunnel interface? (y/n) [n] In this section information about IPv6 network interfaces is entered. The name of an IPv6 interfaces is of the form #v6. That is they are the same as IPv4 interfaces only have a #v6 appended. If you choose to configure IPv6 network interfaces, this script will search for all the IPv4 network interfaces (at least those listed in /etc/hostname.*) and for each one found ask if an IPv6 interface should be configured. Currently *only* ethernet interfaces are supported. Do you wish to configure IPv6 interfaces? (y/n) [Y] Found interfaces: le0. Do you want an IPv6 interface for "le0"? (y/n) [Y] An interface can be set to send router advertisments. With router advertisments onlink prefixes can be advertised and this node can be advertised as a default router. Should this interface do router advertising? (y/n) [N] Every IPv6 interface automatically has one address automatically configured called the link local address. This is usually determined by combining the hardware address of the interface with some standard address prefix. Other addresses can also be configured on the interface. Do you want to configure other addresses? (y/n) [N] The routing protocol RIPv6 is supported through the routing daemon "in.routed6". This daemon can be run on a node that is acting as a router and is participating in routing propogation with other routers. Would you like run in.routed6 (y/n) [N] All the necessary configuration information has been gathered. If you do not want to write the configuration to the startup script /etc/rc2.d/S70ipv6 you can choose not to now. Else, the script will be created and upon reboot it will take effect. Write result to /etc/rc2.d/S70ipv6? (y/n) [Y] Wrote results to /etc/rc2.d/S70ipv6 ........ IPv6 configuration is complete. You may undo the changes you have mad and restore the system to its original state by: pkgrm SUNWipv6 Please reboot for changes to take affect. ============================= From danny@public.bjnet.edu.cn Fri Jul 31 17:08:58 1998 From: danny@public.bjnet.edu.cn (danny@public.bjnet.edu.cn) Date: Fri, 31 Jul 1998 09:08:58 -0700 Subject: Tunneling from a Solaris hosts. Message-ID: <35C1EC1A.8D0@public.bjnet.edu.cn> Hi, Andrew, I am not familiar to the IPv6 stack on Solaris, but I think the experiences on FreeBSD may be help you. In my point of view, tunnel is a mapping from a pair of IPv6 addresses to a pair of IPv4 addresses. So at first, you should be sure that you have assigned the correspoding addresses to the tunnel point. Note that you should give the source IPv6 address with /128 prefix, for the cti0 interface has an access to a 'virtual' link, this link MUST have it's own prefix. e.g.: 3ffe:4321:0:1234::5678/128 Reference: INRIA's IPv6 stack for FreeBSD, documents Don't be worry! Every beginning is hard. Nice to discuss with you. Chen Maoke --------------------------------- TH-CERNET Tsinghua University Beijing, PRC e-mail: danny@public.bjnet.edu.cn cmk@6bone.net.edu.cn --------------------------------- From rlfink@lbl.gov Fri Jul 31 20:20:53 1998 From: rlfink@lbl.gov (Bob Fink) Date: Fri, 31 Jul 1998 12:20:53 -0700 Subject: new pTLA for NTT-SOFTWARE-LAB (3FFE:1800::/24) Message-ID: <1310234842-631581949@cnrmail.lbl.gov> I'm pleased to announce that NTT-SOFTWARE-LAB has been assigned pTLA 3FFE:1800::/24 after open review by the 6bone community. Thanks, Bob From Quool@escape.com Wed Jul 1 00:07:27 1998 From: Quool@escape.com (Quool) Date: Tue, 30 Jun 1998 19:07:27 -0400 Subject: IPv6 Security - Encryption, Authenticity, Trust, anything! Message-ID: <35996FAE.DD06086D@escape.com> --------------DAD600B1FD34A2B8DC34C17C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hey everyone, I am currently working on a research project based mainly on the security of IPv6. Anyone have any tips, ideas, concepts, or just anything relating to the subject! Researching how secure the IPv6 protocol is, compared to IPv4, and what will the effects of its transition be on the Internet, (ie: packet sniffing, tcp attacks, compatabilities, vulnerabilities). Comments are appreciated, Thanx in advance... QuooL -- ICQ: UIN #7432177 E-Mail: QuooL@Escape.Com IRC: EFnet Only: _Guest_ (or) QuooL Snail Mail: (Available Upon Request and Verification) PGP Sig./Fingerprint: {Not yet set} AOL Instant Messenger: Default IP _____________________________________________________ | Knowledge Without Wisdom / Wisdom Without Knowledge | | Dangerous / Frustrating - Unknown | | Free Kevin | |__________"Summa Sedes Capit Non Duos"_-M.O.D. _______| --------------DAD600B1FD34A2B8DC34C17C Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hey everyone,
    I am currently working on a research project based mainly on the security of IPv6.  Anyone have any tips, ideas, concepts, or just anything relating to the subject!
    Researching how secure the IPv6 protocol is, compared to IPv4, and what will the effects of its transition be on the Internet, (ie: packet sniffing, tcp attacks, compatabilities, vulnerabilities).

                Comments are appreciated,
                                                            Thanx in advance...
                                                                                           QuooL
 
 
 

--
ICQ:                                     UIN #7432177
E-Mail:                                  QuooL@Escape.Com
IRC:                                      EFnet Only:   _Guest_   (or)   QuooL
Snail Mail:                             (Available Upon Request and Verification)
PGP Sig./Fingerprint:             {Not yet set}
AOL Instant Messenger:        Default IP
                     _____________________________________________________
                    |        Knowledge Without Wisdom / Wisdom Without Knowledge       |
                     |                                 Dangerous / Frustrating  - Unknown                 |
                      |                                            Free Kevin                                          |
                       |__________"Summa Sedes Capit Non Duos"_-M.O.D. _______|
  --------------DAD600B1FD34A2B8DC34C17C--