From joris.dobbelsteen@mail.com Mon Jan 1 15:01:04 2001 From: joris.dobbelsteen@mail.com (Joris Dobbelsteen) Date: Mon, 1 Jan 2001 16:01:04 +0100 Subject: Happy new year Message-ID: <000701c07403$aa00d8c0$01ff1fac@Joris2K.local> To all WGs I'm subscribed to, nobody does it, so I'll just send it: Happy new year and a good start of the new millennium Hope I can say this for all members of the WGs... - Joris From wd6bone@sina.com Wed Jan 3 14:32:06 2001 From: wd6bone@sina.com (wd6bone) Date: Wed, 3 Jan 2001 22:32:06 +0800 Subject: How can I get IPv6 Router Message-ID: <20010103143206.18404.qmail@sina.com> I want to build a IPv6 experiment network. But how can I get a router which can be used in the IPv6 environment. i.e. an "IPv6" router? Thanks very much! dong ______________________________________ =================================================================== ÐÂÀËÃâ·Ñµç×ÓÓÊÏä http://mail.sina.com.cn ÄãÑ¡ÊÖ»úÎÒÂòµ¥£¡(http://mall.sina.com.cn/yesmobile/) From pim@wise-guys.nl Wed Jan 3 19:00:45 2001 From: pim@wise-guys.nl (Pim van Pelt) Date: Wed, 3 Jan 2001 20:00:45 +0100 (CET) Subject: How can I get IPv6 Router In-Reply-To: <20010103143206.18404.qmail@sina.com> from wd6bone at "Jan 3, 2001 10:32:06 pm" Message-ID: <200101031900.UAA05847@godfather.wise-guys.nl> Dong, You can purchange some Cisco box (eg 2500/3600 series) and install IOS 12.1 on that which is capable of IPv4 and IPv6. They can be quite expensive for an individual though. Other possibility is taking some computer (Intel/Sparc) and installing a Unix on it (OpenBSD/Solaris or Linux) and compiling the OS specific tools in order to create a router. In the latter case, you should check out Zebra (www.zebra.org) which has a fully featured router in C code. Getting connectivity should not be too hard. I myself can be of help in that case. Visit www.ipng.nl for details about Static Tunnels (only 24/7 connection and static IP) regards, good luck, Pim > I want to build a IPv6 experiment network. But how can I get a router which can be > used in the IPv6 environment. i.e. an "IPv6" router? > Thanks very much! > > dong > ______________________________________ > > =================================================================== > ÐÂÀËÃâ·Ñµç×ÓÓÊÏä http://mail.sina.com.cn > > ÄãÑ¡ÊÖ»úÎÒÂòµ¥£¡(http://mall.sina.com.cn/yesmobile/) > -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pvanpelt@wise-guys.nl http://www.wise-guys.nl/ GSM: +31629064049 ----------------------------------------------- From kristoff.bonne@skypro.be Wed Jan 3 19:15:23 2001 From: kristoff.bonne@skypro.be (Kristoff Bonne) Date: Wed, 3 Jan 2001 20:15:23 +0100 (CET) Subject: How can I get IPv6 Router In-Reply-To: <20010103143206.18404.qmail@sina.com> Message-ID: Greetings, On Wed, 3 Jan 2001, wd6bone wrote: > I want to build a IPv6 experiment network. But how can I get a router which can be > used in the IPv6 environment. i.e. an "IPv6" router? > Thanks very much! Two possibilities: - Either you get hold of a 'old' cisco-router (e.g. a 1600 or a 2500), add sufficiant memory and use one of the experimental IPv6 images found on cisco's FTP-site. - Either you use a old 'PC', install one of the free unices (linux or {free,net,open}BSD and configure IPv6 on it. Cheerio! Kr. Bonne. -- KB905-RIPE belgacom internet backbone (c=be,a=rtt,p=rttipc,s=Bonne,g=Kristoff) Internet, IP and IP/VPN kristoff.bonne@skypro.be Fax: +32 2 2435122 From sgunderson@bigfoot.com Thu Jan 4 00:45:59 2001 From: sgunderson@bigfoot.com (Steinar H. Gunderson) Date: Thu, 4 Jan 2001 01:45:59 +0100 Subject: How can I get IPv6 Router In-Reply-To: <200101031900.UAA05847@godfather.wise-guys.nl>; from pim@wise-guys.nl on Wed, Jan 03, 2001 at 08:00:45PM +0100 References: <20010103143206.18404.qmail@sina.com> <200101031900.UAA05847@godfather.wise-guys.nl> Message-ID: <20010104014559.A1618@uio.no> On Wed, Jan 03, 2001 at 08:00:45PM +0100, Pim van Pelt wrote: >In the latter case, you should check out Zebra (www.zebra.org) which has >a fully featured router in C code. Does Zebra contain any actual routing code? I can only find software for setting up the routes (dynamically, of course)... /* Steinar */ -- Homepage: http://members.xoom.com/sneeze/ From sean.lin@alliedtelesyn.co.nz Thu Jan 4 03:28:47 2001 From: sean.lin@alliedtelesyn.co.nz (Sean Lin) Date: Thu, 4 Jan 2001 15:28:47 +1200 (NZT) Subject: 6bone attachment request Message-ID: <3A5496AE.6226.58ACDE6E@localhost> Following the instructions from http://www.6bone.net/6bone_hookup.html, I tried to obtain registry information from http://www.cs-ipv6.lancs.ac.uk/ipv6/6Bone/Whois/bycountry.html but it seems that the site is down and thus have not found/contacted any nearby 6bone attachment points. http://www.viagenie.qc.ca/en/ipv6/registry/index.shtml does not seem to be much of a help if you don't know the site name to query. So I'm turning to this list for help in obtaining a /48 or /64 prefix or some ipv6 addresses for testing purposes. I'm based in Christchurch, New Zealand. Cheers, Sean ------------------------------------------------------------- Sean Lin 27 Nazareth Avenue Software Engineer PO Box 8011 Allied Telesyn Research Christchurch phone +64 3 339 3000 New Zealand fax +64 3 339 3002 email: sean.lin@alliedtelesyn.co.nz web: http://www.alliedtelesyn.co.nz/ ------------------------------------------------------------- From fink@es.net Thu Jan 4 02:52:34 2001 From: fink@es.net (Bob Fink) Date: Wed, 03 Jan 2001 18:52:34 -0800 Subject: 6bone attachment request In-Reply-To: <3A5496AE.6226.58ACDE6E@localhost> Message-ID: <5.0.0.25.0.20010103184946.02604b80@imap2.es.net> Sean, At 03:28 PM 1/4/2001 +1200, Sean Lin wrote: >Following the instructions from http://www.6bone.net/6bone_hookup.html, I >tried to obtain registry information from >http://www.cs-ipv6.lancs.ac.uk/ipv6/6Bone/Whois/bycountry.html but it >seems that the site is down and thus have not found/contacted any nearby >6bone attachment points. I just used this site to look at three NZ sites: try it now. However, if you don't want to try again, try the Canterbury guys in Christchurch: >ipv6-site: CANTERBURY >origin: AS9432 >descr: University of Canterbury >location: Christchurch >country: NZ >prefix: 3FFE:2900:FFE1:1::/64 >contact: KRB1-6BONE >remarks: DNS not operational yet >remarks: ipv6 site operational since Aug 1999 >notify: soa@its.canterbury.ac.nz >changed: k.baker@its.canterbury.ac.nz 19990806 >source: 6BONE > >person: Kerry Baker >address: University of Canterbury, New Zealand >phone: +64 3 364 2336 >e-mail: k.baker@its.canterbury.ac.nz >nic-hdl: KRB1-6BONE >notify: k.baker@its.canterbury.ac.nz >changed: k.baker@its.canterbury.ac.nz 19990806 >source: 6BONE Bob From luoyan@cnnic.net.cn Thu Jan 4 05:41:46 2001 From: luoyan@cnnic.net.cn (pop) Date: Thu, 4 Jan 2001 13:41:46 +0800 Subject: No subject Message-ID: <7744FEE515F1.AAA12156A@oak.cnnic.net.cn> I want to use my computer(win98) and a Cisco3600 router to link to the 6bone in China,can you pls tell me what to do now? thanks alot! 00 From mtl23@student.canterbury.ac.nz Thu Jan 4 06:47:28 2001 From: mtl23@student.canterbury.ac.nz (Sean Lin) Date: Thu, 4 Jan 2001 19:47:28 +1300 Subject: 6bone attachment request References: <5.0.0.25.0.20010103184946.02604b80@imap2.es.net> Message-ID: <001901c0761a$35ff87a0$0100a8c0@mt> hi Bob, The NZ sites are not working anymore, the information there is out of date, CLEAR-NZ and CANTERBURY is no longer operating. All CANTERBURY had was a tunnel to CLEAR-NZ and the person in charge of the ipv6 router at CLEAR has quit his job and nobody at CLEAR Communications knows anything about a ipv6 router. I still can't seem to get a DNS reply for the lancs website. DNS error again. Sean ----- Original Message ----- From: "Bob Fink" To: ; <6bone@ISI.EDU> Sent: Thursday, January 04, 2001 3:52 PM Subject: Re: 6bone attachment request > Sean, > > At 03:28 PM 1/4/2001 +1200, Sean Lin wrote: > >Following the instructions from http://www.6bone.net/6bone_hookup.html, I > >tried to obtain registry information from > >http://www.cs-ipv6.lancs.ac.uk/ipv6/6Bone/Whois/bycountry.html but it > >seems that the site is down and thus have not found/contacted any nearby > >6bone attachment points. > > I just used this site to look at three NZ sites: > > > > try it now. > > However, if you don't want to try again, try the Canterbury guys in > Christchurch: > > >ipv6-site: CANTERBURY > >origin: AS9432 > >descr: University of Canterbury > >location: Christchurch > >country: NZ > >prefix: 3FFE:2900:FFE1:1::/64 > >contact: KRB1-6BONE > >remarks: DNS not operational yet > >remarks: ipv6 site operational since Aug 1999 > >notify: soa@its.canterbury.ac.nz > >changed: k.baker@its.canterbury.ac.nz 19990806 > >source: 6BONE > > > >person: Kerry Baker > >address: University of Canterbury, New Zealand > >phone: +64 3 364 2336 > >e-mail: k.baker@its.canterbury.ac.nz > >nic-hdl: KRB1-6BONE > >notify: k.baker@its.canterbury.ac.nz > >changed: k.baker@its.canterbury.ac.nz 19990806 > >source: 6BONE > > > Bob > > From kre@munnari.OZ.AU Thu Jan 4 07:00:54 2001 From: kre@munnari.OZ.AU (Robert Elz) Date: Thu, 04 Jan 2001 14:00:54 +0700 Subject: How can I get IPv6 Router In-Reply-To: Your message of "Thu, 04 Jan 2001 01:45:59 +0100." <20010104014559.A1618@uio.no> Message-ID: <2449.978591654@brandenburg.cs.mu.OZ.AU> Date: Thu, 4 Jan 2001 01:45:59 +0100 From: "Steinar H. Gunderson" Message-ID: <20010104014559.A1618@uio.no> | Does Zebra contain any actual routing code? I can only find software for | setting up the routes (dynamically, of course)... That is the routing code ... I suspect that what you're asking about is forwarding code, and no, I don't believe that zebra does that (though just about every unix for ages has had that capability in it .. the bigger problem has often been turning it off when it wasn't wanted). kre From rzm@icm.edu.pl Thu Jan 4 14:33:18 2001 From: rzm@icm.edu.pl (Rafal Maszkowski) Date: Thu, 4 Jan 2001 15:33:18 +0100 Subject: IPv6 tcpblast (with tons of options) Message-ID: <20010104153318.B26@burza.icm.edu.pl> I am maintaining a tcpblast variation based on FreeBSD version from 1996. Recently I added IPv6 support, also in included (but not in RPM) standalone discard program. There is also a lot of options added since I started hacking original version, recently packet size setting. See ftp://ftp.6bone.pl/pub/blast/ for source, Linux (S)RPMs and binaries for some other Unix systems. to get announcements: echo subscribe tcpblast | mail majordomo@sunsite.icm.edu.pl Usage: tcpblast [options] destination[:port] tcpblast/udpblast is a simple tool for probing network and estimating its throughput. By default it sends 300 blocks (1024 bytes each) of data to specified destination host. Destination can be name or address, IPv4 or IPv6. When IPv6 address is specified with port it should look like: '[3ffe:8010::1]:9' (with single quotes to prevent shell expansion of []). Options: -4, --ipv4 use only ipv4 address -6, --ipv6 use only ipv6 address -a send random data -b BUF_SIZE socket buf size (default: -1 == don't change), with `-' to be substracted from results -c, --count BLOCKS change default (300) number of blocks, range: 1..10000000 -d DOTFREQ print dot every DOTFREQ blocks, disables cont. speed disp. -h, --help this help -i, --delay DELAY write delay in microseconds (EXPERIMENTAL) -l, --last BLKS show also speed for last BLKS blocks -m results for every block in separate line -n, --nwrite do not write, use e.g. with chargen port -o switch from continuous speed displaying to dots printing -p PORT bind this local PORT -q --quiet show only final statistics -r, --read read data returned to us, switches default port to echo -R, --rate RATESPEC limit the speed according to the RATESPEC -s BLOCK_SIZE block size (default 1024 bytes) -t MAXTIME limit time to MAXTIME (up to 42950 h) --tcp use TCP (default) --udp use UDP (default if named udpblast) -v, --verbosity verbosity, default 0, maximum 3. -v adds time display, -vv also speed in B/s, -v - speed in b/s. -V, --version version -x, --maxseg SIZE setting packet SIZE using TCP_MAXSEG destination host name or address port use port #/name xyz instead of default port 9 RATESPEC RATE[,TIME][:RATE[,TIME]]... RATE generating data at RATE speed in B/s TIME for TIME seconds (can be floating point number), last can be omitted and that time will be infinite Options -b, -c, -R, -s and -t can use case insensitive unit multipliers and specifiers: size (bytes): -b and -s argument without units is in bytes, can use [{k,m,g}]b (lower or upper case) for KB, MB or GB. {k,m,g} are powers of 1024. number: -c argument is just a number, can have k, m or g added (powers of 1024), no unit needed rate (bytes pes second): -R RATE is in B/s or Bps, the postfixes can be [{k,m,g}]{b/s,bps} time (seconds): -t and -R TIME argument is in seconds, can be postfixed with [{k,m,g}]{s,min,h,w,m,y} Example: tcpblast -b 4KB -c 10k -R 10KBps,2:20kbps,3s target tcpblast version: FreeBSD + rzm 20010104 The README file contains examples of use. R. -- W iskier krzesaniu ¿ywem/Materia³ to rzecz g³ówna From nhua@biigroup.com Thu Jan 4 16:19:41 2001 From: nhua@biigroup.com (huaning(bii)) Date: Fri, 5 Jan 2001 00:19:41 +0800 Subject: References: <7744FEE515F1.AAA12156A@oak.cnnic.net.cn> Message-ID: <002101c0766a$25766160$97086aca@hmobile> It's easy, you can download a Cisco's IPv6 IOS, which is a evaluation version now , then upgrade your 3600's IOS. At this time, the 3600 is IPv6 enable. Now , Microsoft has not released IPv6 protocal stack for win98, except for win2000 sp1, but you can find other company's IPv6 stack, e.g http:/www.trumpet.com.au/ipv6.htm Good Luck. _________________________________________________ Hua Ning Chief Engineer BII Group Holdings Ltd(Beijing Internet-networking Institute), 110E 11F China Merchants Tower, No.2 Dong Huan Nan Lu, Chao Yang District, Beijing,China Zip Code: 100022 Mobile: +86-13501067449 Tel:+86-10-65660290-223 Fax:+86-10-65660297 _________________________________________________ ----- Original Message ----- From: "pop" To: "6bone@isi.edu" <6bone@ISI.EDU> Sent: Thursday, January 04, 2001 1:41 PM > I want to use my computer(win98) and a Cisco3600 router to link to the 6bone in China,can you pls tell me what to do now? > thanks alot! > 00 > > From sean.lin@alliedtelesyn.co.nz Sun Jan 7 20:43:35 2001 From: sean.lin@alliedtelesyn.co.nz (Sean Lin) Date: Mon, 8 Jan 2001 08:43:35 +1200 (NZT) Subject: 6bone attachment request In-Reply-To: <20010105165021.73ABBE32@RASKOL.STYX.ORG> References: <3A5496AE.6226.58ACDE6E@localhost> "from Sean Lin at Jan 4, 2001 03:28:47 pm" Message-ID: <3A597DB9.30751.6BD3E979@localhost> Thank you everyone for your help. I've managed to obtained a /64 from Pat Jensen and also from Auckland University. Cheers, Sean Subject: Re: 6bone attachment request To: sean.lin@alliedtelesyn.co.nz Date sent: Fri, 5 Jan 2001 11:50:20 -0500 (EST) From: ww@AREA22.STYX.ORG (William Waites) > Hi there, > > Just wondering if you've found a tunnel yet. If not, I'd be happy > to make you one although I can't speak to the bandwidth you'd > get over it. Our endpoint would be 216.129.192.34 which > is in Toronto, Canada. We have a tunnel to merit.edu > and a /48 out of which we can give you some space. > > Cheers, > -w > > > Following the instructions from http://www.6bone.net/6bone_hookup.html, I > > tried to obtain registry information from > > http://www.cs-ipv6.lancs.ac.uk/ipv6/6Bone/Whois/bycountry.html but it > > seems that the site is down and thus have not found/contacted any nearby > > 6bone attachment points. > > > > http://www.viagenie.qc.ca/en/ipv6/registry/index.shtml does not seem to > > be much of a help if you don't know the site name to query. > > > > So I'm turning to this list for help in obtaining a /48 or /64 prefix or > > some ipv6 addresses for testing purposes. I'm based in Christchurch, New > > Zealand. > > > > Cheers, > > Sean > > > > ------------------------------------------------------------- > > Sean Lin 27 Nazareth Avenue > > Software Engineer PO Box 8011 > > Allied Telesyn Research Christchurch > > phone +64 3 339 3000 New Zealand > > fax +64 3 339 3002 email: sean.lin@alliedtelesyn.co.nz > > web: http://www.alliedtelesyn.co.nz/ > > ------------------------------------------------------------- > > > > > ------------------------------------------------------------- Sean Lin 27 Nazareth Avenue Software Engineer PO Box 8011 Allied Telesyn Research Christchurch phone +64 3 339 3000 New Zealand fax +64 3 339 3002 email: sean.lin@alliedtelesyn.co.nz web: http://www.alliedtelesyn.co.nz/ ------------------------------------------------------------- From goddardm@home.com Mon Jan 8 00:32:26 2001 From: goddardm@home.com (Matthew Goddard) Date: Sun, 7 Jan 2001 19:32:26 -0500 Subject: 6bone attachment request In-Reply-To: <3A597DB9.30751.6BD3E979@localhost> Message-ID: Just wait until /64 and /48 are being sold as commodities on the open market ;) -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Sean Lin Sent: Sunday, January 07, 2001 3:44 PM To: 6bone@ISI.EDU Subject: Re: 6bone attachment request Thank you everyone for your help. I've managed to obtained a /64 from Pat Jensen and also from Auckland University. Cheers, Sean Subject: Re: 6bone attachment request To: sean.lin@alliedtelesyn.co.nz Date sent: Fri, 5 Jan 2001 11:50:20 -0500 (EST) From: ww@AREA22.STYX.ORG (William Waites) > Hi there, > > Just wondering if you've found a tunnel yet. If not, I'd be happy > to make you one although I can't speak to the bandwidth you'd > get over it. Our endpoint would be 216.129.192.34 which > is in Toronto, Canada. We have a tunnel to merit.edu > and a /48 out of which we can give you some space. > > Cheers, > -w > > > Following the instructions from http://www.6bone.net/6bone_hookup.html, I > > tried to obtain registry information from > > http://www.cs-ipv6.lancs.ac.uk/ipv6/6Bone/Whois/bycountry.html but it > > seems that the site is down and thus have not found/contacted any nearby > > 6bone attachment points. > > > > http://www.viagenie.qc.ca/en/ipv6/registry/index.shtml does not seem to > > be much of a help if you don't know the site name to query. > > > > So I'm turning to this list for help in obtaining a /48 or /64 prefix or > > some ipv6 addresses for testing purposes. I'm based in Christchurch, New > > Zealand. > > > > Cheers, > > Sean > > > > ------------------------------------------------------------- > > Sean Lin 27 Nazareth Avenue > > Software Engineer PO Box 8011 > > Allied Telesyn Research Christchurch > > phone +64 3 339 3000 New Zealand > > fax +64 3 339 3002 email: sean.lin@alliedtelesyn.co.nz > > web: http://www.alliedtelesyn.co.nz/ > > ------------------------------------------------------------- > > > > > ------------------------------------------------------------- Sean Lin 27 Nazareth Avenue Software Engineer PO Box 8011 Allied Telesyn Research Christchurch phone +64 3 339 3000 New Zealand fax +64 3 339 3002 email: sean.lin@alliedtelesyn.co.nz web: http://www.alliedtelesyn.co.nz/ ------------------------------------------------------------- From mithrandir@skynet.be Mon Jan 8 13:43:54 2001 From: mithrandir@skynet.be (Mithrandir) Date: Mon, 8 Jan 2001 14:43:54 +0100 Subject: Thanks Message-ID: <003e01c07979$4f75d560$0401a8c0@mithrandir> Thanks to everyone who helped achieve this configuration. Here's an example of 2 cisco 2500 series routers who are connected to each other with their serial interface. IN A CLOSED LAN ENVIRONMENT. (no internet connection) Special Thanks to Pim, he devoted a lot of his precious time for us, and explained the mechanics of Tunneling. Thank you all. Greetings Mithrandir and Johan. hostname Bugs ! enable secret enable password xxxx ! ipv6 unicast-routing ! interface Tunnel1 no ip address ipv6 enable tunnel source Ethernet0 tunnel destination 10.1.1.1 tunnel mode ipv6ip ! interface Ethernet0 ip address 192.168.1.95 255.255.255.0 ipv6 enable ipv6 address 3FFE:8114:3001:2::1/64 ! interface Serial0 ip address 172.16.0.1 255.255.0.0 no ip mroute-cache ! ip classless ip route 10.0.0.0 255.0.0.0 Serial0 ! ipv6 route 3FFE:8114:3001:1::0/64 Tunnel1 ! line con 0 line aux 0 line vty 0 4 password xxxx login ! end ____________________________________________________ hostname Bunny ! enable secret enable password xxxx ! ipv6 unicast-routing ! interface Tunnel2 no ip address ipv6 enable tunnel source Ethernet0 tunnel destination 192.168.1.95 tunnel mode ipv6ip ! interface Ethernet0 ip address 10.1.1.1 255.0.0.0 ipv6 enable ipv6 address 3FFE:8114:3001:1::1/64 ! interface Serial0 ip address 172.16.0.2 255.255.0.0 no ip mroute-cache clockrate 64000 ! ip classless ip route 192.168.1.0 255.255.255.0 Serial0 ! ipv6 route 3FFE:8114:3001:2::0/64 Tunnel2 ! line con 0 line aux 0 line vty 0 4 password xxxx login ! end From tony@lava.net Tue Jan 9 03:12:51 2001 From: tony@lava.net (Antonio Querubin) Date: Mon, 8 Jan 2001 17:12:51 -1000 (HST) Subject: ipv6 version of h2n Message-ID: Does anybody know of the existance of an IPv6 version of the h2n script which converts /etc/hosts records into named zone files? From mithrandir@skynet.be Tue Jan 9 13:49:06 2001 From: mithrandir@skynet.be (Mithrandir) Date: Tue, 9 Jan 2001 14:49:06 +0100 Subject: Sunsol8 Message-ID: <003e01c07a42$f596b9e0$0401a8c0@mithrandir> As the 'kwak' doctor in the Simpsons would say: Hello, Everybody ! I'm working with Sun Solaris8 machines IPv6 compatible. Recently I succeeded in tunneling IPv6 in IPv4 with two Cisco 2500 series routers. This time I want to try to communicate with two IPv6 hosts with two IPv4 cisco routers inbetween. This is the second type of tunnel we want to experiment with. Does anyone have some pointers. Sorry but the documentation is too dificult to understand. Call me a dummy. (I don't care) I like interacting with people. The cisco configuration is still available, just ask Thanks Greetings Mithrandir. From psb@ast.cam.ac.uk Tue Jan 9 16:03:54 2001 From: psb@ast.cam.ac.uk (Peter Bunclark) Date: Tue, 9 Jan 2001 16:03:54 +0000 (GMT) Subject: Sunsol8 In-Reply-To: <003e01c07a42$f596b9e0$0401a8c0@mithrandir> Message-ID: On Tue, 9 Jan 2001, Mithrandir wrote: > As the 'kwak' doctor in the Simpsons would say: > > Hello, Everybody ! > > I'm working with Sun Solaris8 machines IPv6 compatible. > Recently I succeeded in tunneling IPv6 in IPv4 with two > Cisco 2500 series routers. > > This time I want to try to communicate with two IPv6 hosts > with two IPv4 cisco routers inbetween. > > This is the second type of tunnel we want to experiment with. > Does anyone have some pointers. > Sorry but the documentation is too dificult to understand. > Call me a dummy. (I don't care) > I like interacting with people. > > The cisco configuration is still available, just ask > > Thanks > Greetings > Mithrandir. Between two Solaris systems with IPv4 connectivity, it should be dead easy. Create /etc/hosname6/ip.tun0 (or 1 or 2 or 3...) on each machine; the contents are tdst a.b.c.d where a.b.c.d is the IPv4 address of the other one. (you might need tsrc w.x.y.z where w.x.y.z is the address of the host). Reboot 'em both. Pete. From extml@ndsoftware.net Tue Jan 9 18:39:36 2001 From: extml@ndsoftware.net (NDSoftware) Date: Tue, 9 Jan 2001 19:39:36 +0100 Subject: IPs In-Reply-To: <003e01c07a42$f596b9e0$0401a8c0@mithrandir> Message-ID: How i can get ip for IPV6 ? Thanks From pim@bfib.ipng.nl Tue Jan 9 21:13:13 2001 From: pim@bfib.ipng.nl (Pim van Pelt) Date: Tue, 9 Jan 2001 22:13:13 +0100 (CET) Subject: Sunsol8 In-Reply-To: <003e01c07a42$f596b9e0$0401a8c0@mithrandir> from "Mithrandir" at Jan 09, 2001 02:49:06 PM Message-ID: <200101092113.f09LDDD14897@bfib.ipng.nl> > This time I want to try to communicate with two IPv6 hosts > with two IPv4 cisco routers inbetween. > > This is the second type of tunnel we want to experiment with. > Does anyone have some pointers. > Sorry but the documentation is too dificult to understand. > Call me a dummy. (I don't care) > I like interacting with people. > It is exactly the same 'type of tunnel' as the first setup. This time, you have boxA46 | routerA4 | routerB4 | boxB46 Assuming your routers speak only IPv4, and they can route traffic from boxA to boxB, you can set up a tunnel between the two solaris machines. Let us say boxA is IPv4 address 10.0.1.2 and boxB is 10.0.2.2 On boxA, you would create /etc/hostname6.ip.tun0 with contents: -- tsrc 10.0.1.2 tdst 10.0.2.2 up addif 3ffe:8114:3000::0 3ffe:8114:3000::1 up -- and on boxB, /etc/hostname6.ip.tun0 becomes: -- tsrc 10.0.2.2 tdst 10.0.1.2 up addif 3ffe:8114:3000::1 3ffe:8114:3000::0 up -- You can then ping6 the other endpoint (ping6 is not standard software for Solaris, but ping works in both address families) happy pinging :) Pim > The cisco configuration is still available, just ask > > Thanks > Greetings > Mithrandir. > > -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From dolemite@wuli.nu Sun Jan 7 20:23:38 2001 From: dolemite@wuli.nu (dolemite) Date: Sun, 07 Jan 2001 15:23:38 -0500 Subject: IPs References: Message-ID: <3A58D049.CCBBADCB@wuli.nu> *This message was transferred with a trial version of CommuniGate(tm) Pro* NDSoftware wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > How i can get ip for IPV6 ? > Thanks If you mean you would like access to a large public network that uses the ipv6 protocol may i suggest: http://www.6bone.net/6bone_hookup.html and www.freenet6.net I hope I have been helpful Alex Newman From pim@bfib.ipng.nl Tue Jan 9 23:15:44 2001 From: pim@bfib.ipng.nl (Pim van Pelt) Date: Wed, 10 Jan 2001 00:15:44 +0100 (CET) Subject: IPs In-Reply-To: from "NDSoftware" at Jan 09, 2001 07:39:36 PM Message-ID: <200101092315.f09NFjb04562@bfib.ipng.nl> > > How i can get ip for IPV6 ? Look at http://www.freenet6.net/ or various other tunnel brokers on the internet. groet, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From mithrandir@skynet.be Wed Jan 10 12:21:13 2001 From: mithrandir@skynet.be (Mithrandir) Date: Wed, 10 Jan 2001 13:21:13 +0100 Subject: Host to router Message-ID: <009101c07b01$e0ed3680$0401a8c0@mithrandir> Thank you guys and girls For the input on host6 over IPv4 network to host6 communication. Here 's an explanation from www.sun.com. See below: Also, thank you very much for all your help. Next problem: Tunneling from a IPv6/IPv4 host over IPv4 router Through IPv6/IPv4 router and to IPv6 host. I already made a configuration similar to the cisco router tunneling. It does not work. Here 's the input from sun: Automatic Tunnels ----------------- To configure automatic tunnels, you want to configure interface ip.atun0. The easiest way to do this is to create the file /etc/hostname6.ip.atun0, with this contents tsrc up where is an IPv4 address on this system. At boot time, Solaris will create ip.atun0 and configure it with a tunnel source address of , and also configure the IPv6 address as ::/96. For example, on the system where I just did this I have /etc/hostname6.ip.atun0 with this as its contents: tsrc 129.153.128.110 up After booting, I ran "ifconfig ip.atun0 inet6" and saw this: ip.atun0: flags=2200041 mtu 1480 index 3 inet tunnel src 129.153.128.110 inet6 ::129.153.128.110/96 If you do this on both IPv6 nodes, you'll have two IPv4-compatible addresses that you can route through. For example, let's say you have nodes A and B. A's IPv4 address is 10.0.0.1 and B's IPv4 address is 10.0.0.2. If you set up ip.atun0 on each of these, then A will have IPv4-compatible address ::10.0.0.1 and B will have address ::10.0.0.2. A can now route to B via ::10.0.0.2, and B can route to A via ::10.0.0.1. Remember that if you are using A and B as gateways for other networks, you'll have to turn on ip6_forwarding using ndd. Configured Tunnels ------------------ Someone forwarded me a copy of a note that you should have gotten on 6bone@isi.edu. But to be complete, here's the information. For configured tunnels, you need to configure both endpoints with the information you want. You'll want to configure ip.tun0 (or ip.tun1, ip.tun2, etc.) with the tunnel source and destination addresses. Again, create /etc/hostname6.ip.tun0. Here's the contents of mine from one machine whose IP address is 129.153.128.110, tunneling to 129.146.177.26: tsrc 129.153.128.110 tdst 129.146.177.26 up Here's what "ifconfig ip.tun0 inet6" shows after boot: ip.tun0: flags=2200851 mtu 1480 index 3 inet tunnel src 129.153.128.110 tunnel dst 129.146.177.26 inet6 fe80::8199:806e/10 --> fe80::8192:b11a If you want additional IPv6 addresses, an "addif" statement to /etc/hostname6.ip.tun0, specifying the source and destination addresses, like this: addif 2::45 2::46 up Then after boot we have a new interface ip.tun0:1. Here's what the tunnel stuff from "ifconfig -au6" looks like now: ip.tun0: flags=2200851 mtu 1480 index 3 inet tunnel src 129.153.128.110 tunnel dst 129.146.177.26 inet6 fe80::8199:806e/10 --> fe80::8192:b11a ip.tun0:1: flags=2200851 mtu 1480 index 3 inet6 2::45/128 --> 2::46 Enjoy. Greeetings Mithrandir. From pim@bfib.ipng.nl Fri Jan 12 11:36:23 2001 From: pim@bfib.ipng.nl (Pim van Pelt) Date: Fri, 12 Jan 2001 12:36:23 +0100 (CET) Subject: Cisco 'ipv6 route' problem. Message-ID: <200101121136.f0CBaNg27467@bfib.ipng.nl> Hallo, I have a question for the Cisco people that might be of public interrest. Assume we have a Cisco that builds a tunnel to an IPv4 endpoint using a /127 tunnelnetwork. This is interface Tunnel1 and the Cisco endpoint is 3ffe:8114:1000::2/127. The Cisco then routes a /64 over the tunnel to the remote server. As far as I can tell, I can route it via two different commands, which both result in different behavior! 1. ipv6 route 3ffe:8114:2000:b0::/64 Tunnel1 2. ipv6 route 3ffe:8114:2000:b0::/64 3ffe:8114:1000::3 If you agree with me that this is an unambigous way to define a static route over the tunnel, please try and explain to my why the rule under (2) makes for approximately 50% packet loss from hosts on the 6bone to hosts in the tunneled /64, and also the same packet loss from users in the /64 to the 6bone. If I change the rule from (2) to (1), the problem is solved. (IOS is the thanksgiving release (12.0)) Kind regards, Pim van Pelt -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From fink@es.net Mon Jan 15 19:38:13 2001 From: fink@es.net (Bob Fink) Date: Mon, 15 Jan 2001 11:38:13 -0800 Subject: 6bone pTLA 3FFE:8130::/28 allocated to NOKIA Message-ID: <5.0.0.25.0.20010115113532.0f767c10@imap2.es.net> NOKIA has been allocated pTLA 3FFE:8130::/28 having finished its 2-week review period with no negative comments. Note that it will take a short while for their inet6num object to show up as they have to create it. However, their registration is listed on: Thanks, Bob From fink@es.net Tue Jan 16 05:37:25 2001 From: fink@es.net (Bob Fink) Date: Mon, 15 Jan 2001 21:37:25 -0800 Subject: pTLA request for APAN-JO Message-ID: <5.0.0.25.0.20010115213403.0f88e4b8@imap2.es.net> 6bone Folk, APAN-JP has requested a pTLA allocation. The open review period for this will close 29 Jan 2001. Please send any comments to me or the list. Thanks, Bob ====================================== >Date: Tue, 16 Jan 2001 11:33:46 +0900 >From: Yuichiro HEI >To: fink@es.net >CC: kdd@jp.apan.net >Subject: pTLA request for APAN-JP > >Dear Mr.Fink, > >This is Yuichiro Hei from APAN-JP, requesting 6Bone pTLA address. > >I attach the request form of pTLA. >We hope we meet the 6bone's requirement, but if something is missing, >please let us know. > >Best regards, > >Yuichiro Hei >APAN-JP > >----------------- >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: > >A: We have been connected to the 6Bone since 1998. > > 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. > >A: We do not maintain 6Bone registry entries now (I mean it is mainly for > 3ffe:... address), but now we maintain a sNLA address space delegated > from WIDE, and maintain an up-to-date APNIC registry. Please refer the > APNIC registry. For example: > % whois -h whois.apnic.net 2001:200:900::/40 > > 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. > >A: We maintain the BGP4+ peering with WIDE(AS2500) via NSPIXP6, which is > an IX for IPv6 in Japan. Our IPv6 router is tp6r2.jp.apan.net. > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > >A: We maintain DNS forward (AAAA) and reverse (ip6.int) entries on > ns.jp.apan.net. For example: > >% dig ns2.jp.apan.net aaaa >... > >;; ANSWER SECTION: >ns2.jp.apan.net. 22h1m44s IN AAAA 2001:200:901:2::2 >... > >% dig 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.1.0.9.0.0.0.2.0.1.0.0.2.ip6.int > ptr > >;; ANSWER SECTION: >2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.1.0.9.0.0.0.2.0.1.0.0.2.ip6.int. >1D IN PTR ns2.jp.apan.net. > > > 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. > >A: www.jp.apan.net is the web server that describes our research and > development activities. This can be accessed by both IPv4 and IPv6. > Our IPv6 activity described in this server is old, so we will update > it soon. > > 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. > >A: Support staff: > Kazunori Konishi (konish@jp.apan.net) > Akira Kato (kato@wide.ad.jp) > Yoshinori Kitatsuji (kitaji@jp.apan.net) > Yuichiro Hei (hei@jp.apan.net) > > 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. > >A: Common mailbox: > ops@jp.apan.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. > >A: APAN (Asia Pacific Advanced Network) is a non-profit international > consortium for research and development in advanced networking and > services in the Asia-Pacific region. APAN provides a high-performance > network environment for research community mainly in the country of > Asia, for example Japan, Korea, Singapore, Australia, Malaysia, > China, etc., and many research communities work actively on APAN network. > So we have an Asian-wide potential usr community. > We will intent to use pTLA address for these research communities > and collaborate on them. > > > 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. > >A: We agree the 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. From fink@es.net Tue Jan 16 14:22:44 2001 From: fink@es.net (Bob Fink) Date: Tue, 16 Jan 2001 06:22:44 -0800 Subject: SOLNET-CH 6bone pTLA request Message-ID: <5.0.0.25.0.20010116062015.0f89c558@imap2.es.net> 6bone Folk, SOLNET-CH has requested a pTLA allocation. The open review period for this will close 30 Jan 2001. Please send any comments to me or the list. Thanks, Bob ====================================== >Date: Tue, 16 Jan 2001 12:51:33 +0100 (MET) >From: Erich Hohermuth >To: fink@es.net >Subject: SOLNET-CH 6bone pTLA request > >Hello, > >We would like to request a test pTLA on 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 since September 2000 from SWITCH a 3FFE:2028:1000::/36 Network. > > > 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. > >see SOLNET-CH > > 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. > > >tunnel: IPv6 in IPv4 bb6.solnet.ch -> cisco25.space.net SPACENET-DE STATIC >tunnel: IPv6 in IPv4 bb6.solnet.ch -> swiPV6.switch.ch SWITCH BGP4+ >tunnel: IPv6 in IPv4 bb6.solnet.ch -> doc-6r1.pipex.net UUNET-UK >BGP4+ > >router: bb6.solnet.ch (2514 IOS 12.1) > ipv4 212.101.8.19 > ipv6 3FFE:2028:1000::1 > > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > >Domain: ipv6.solnet.ch > >DNS: arcade.ipv6.solnet.ch 3FFE:2028:1000:F000::10B > anarcho.ipv6.solnet.ch 3FFE:2028:1000:F000::10D > > > 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. > >Web: www.ipv6.solnet.ch > (providing the latest information about the > project and the network.) > > telnet, ssh, ftp is also ipv6 accesible for managment from our > LAN. > > > 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. > >Markus Binz (MB44-Ripe) [MB8-6BONE] >Erich Hohermuth (EH974-RIPE) [EH2-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@solnet.ch > > > 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. > > >SolNet is an ISP in Switzerland since 1996 who provides Internet Services >to privat, soho and business customers. The service includes dialup, xDSL, >leased lines, housing, hosting and consulting. Our main goal is to provide >high quality Internet Service to all our cutomers. > > > 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 commit any current and any future 6Bone operational >rules and policies. > >If there are some questions please feel free to contact us. > > Erich Hohermuth > Markus Binz > > ipv6@solnet.ch From baixauli@mat.upc.es Tue Jan 16 19:13:06 2001 From: baixauli@mat.upc.es (Julio Baixauli) Date: Tue, 16 Jan 2001 20:13:06 +0100 Subject: DNS Message-ID: <3A649D42.71146D16@mat.upc.es> Hello! Can a IPv6-only node access to a DNS IPv6-server to resolve addresses? There are any documents that explains me this situation? Thank you very much!! -- ******************************************** Julio Baixauli Garreta baixauli@mat.upc.es ******************************************** From peter@ipsec.nu Wed Jan 17 08:15:29 2001 From: peter@ipsec.nu (Peter Håkanson) Date: Wed, 17 Jan 2001 09:15:29 +0100 Subject: Fwd: DNS Message-ID: <01011709160902.34720@warp.ipsec.nu> ---------- Forwarded Message ---------- Subject: DNS Date: Tue, 16 Jan 2001 20:13:06 +0100 From: Julio Baixauli Hello! Can a IPv6-only node access to a DNS IPv6-server to resolve addresses? There are any documents that explains me this situation? Yes. BIND-9 may use IPv6 adresses. Thank you very much!! -- ******************************************** Julio Baixauli Garreta baixauli@mat.upc.es ******************************************** ------------------------------------------------------- -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden From roha@mimos.my Wed Jan 17 09:04:11 2001 From: roha@mimos.my (Che Rohani Ishak) Date: Wed, 17 Jan 2001 17:04:11 +0800 Subject: Commercial IPv6 Services Message-ID: <00e501c08064$7578a660$a186e4c0@mimos.my> This is a multi-part message in MIME format. ------=_NextPart_000_00E2_01C080A7.8361EAA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Currently, I know that there are only two ISP providing commercial IPv6 = services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get = Clarification.Thanks =20 Regards, Rohani=20 ------=_NextPart_000_00E2_01C080A7.8361EAA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Currently, I know that there are only = two ISP=20 providing commercial IPv6 services that is IIJ and NTT. How about = Surfnet and=20 Trumpet? Hope to get Clarification.Thanks
 
Regards,
Rohani 
------=_NextPart_000_00E2_01C080A7.8361EAA0-- From peter@ipsec.nu Wed Jan 17 09:49:31 2001 From: peter@ipsec.nu (Peter Håkanson) Date: Wed, 17 Jan 2001 10:49:31 +0100 Subject: DNS In-Reply-To: <3A65689A.509F9895@mat.upc.es> References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> Message-ID: <01011710511905.34720@warp.ipsec.nu> On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden From baixauli@mat.upc.es Wed Jan 17 10:29:23 2001 From: baixauli@mat.upc.es (Julio Baixauli) Date: Wed, 17 Jan 2001 11:29:23 +0100 Subject: DNS References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> <01011710511905.34720@warp.ipsec.nu> Message-ID: <3A657403.4C0F6A2F@mat.upc.es> "Peter Håkanson" wrote: > > On Wed, 17 Jan 2001, you wrote: > > "Peter Håkanson" wrote: > > > > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > Bind-9 is the latest version of bind from isc.org > The software may be obtained from www.isc.org, > the unpacked manpages may be browsed at : > > http://www.ipsec.nu/dns/bind9/Bv9ARM.html OK. Bind9 is the DNS-server. Now... how can I configure a IPv6-only node (client) to access to a DNS server that is a IPv6-only node too. I've modified /etc/resolv.conf with the IPv6 address of DNS-server, but don't work (no DNS-query packet found on the net). More ideas?? I'm working with Linux. Thank you!! -- ******************************************** Julio Baixauli Garreta baixauli@mat.upc.es ******************************************** From itojun@itojun.org Wed Jan 17 12:13:59 2001 From: itojun@itojun.org (Jun-ichiro itojun Hagino) Date: Wed, 17 Jan 2001 21:13:59 +0900 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) Message-ID: <20010117121359.41CD47E66@starfruit.itojun.org> # not sure why it did not get through. at PAIX, we use 3ffe:80a::/32 (acutally 3ffe:80a::/64) for the peering segment between ISPs. 3ffe:800::/24 is assigned to ISI, and as ISI and PAIX are not directly connected, 3ffe:800::/24 has two (or more) disconnected networks. we did not expect to receive/propagate prefixes longer than sTLA/pTLA prefixes (*), our EBGP routers filter out logner prefixes (as suggested in 6bone operation RFC) and internal routers do not have the route for 3ffe:80a::/32. packets to 3ffe:80a::/32 get routed to ISI (instead of PAIX) and get dropped. (*) currently our rule is as follows: - prefixes that match 3ffe:0000::/17 and prefixlen = 24 - prefixes that match 3ffe:8000::/17 and prefixlen = 28 - prefixes that match 2001::/16 and prefixlen = 29 to 35 - prefixes that match 2000::/3 and prefixlen = 16 - prefixes specifically agreed with other peers what should we do? if we need to receive/propagate 3ffe:80a::/32 or /64, we may just need to do that and then the particular problem will be solved. however, i have some worry here... if we add more and more practice like this, we eventually get more external routes. i can think of couple of solutions: - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world based on normal prefix length (like /28 for pTLA). the IX will ensure connectivity between IX segments (so there will be no reachability issue). - define an address range for IX segments (like 3ffe:fff0::/28). assign /48 out of it to IX (who assigns it is another question). ask everyone to accept /48 (not just /28) for the prefix. - do not use global address on the IX segment. I know some routers cannot establish BGP4+ peers using linklocal address. - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. what do people think? itojun From baixauli@mat.upc.es Wed Jan 17 10:29:23 2001 From: baixauli@mat.upc.es (Julio Baixauli) Date: Wed, 17 Jan 2001 11:29:23 +0100 Subject: DNS References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> <01011710511905.34720@warp.ipsec.nu> Message-ID: <3A657403.4C0F6A2F@mat.upc.es> *This message was transferred with a trial version of CommuniGate(tm) Pro* "Peter Håkanson" wrote: > > On Wed, 17 Jan 2001, you wrote: > > "Peter Håkanson" wrote: > > > > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > Bind-9 is the latest version of bind from isc.org > The software may be obtained from www.isc.org, > the unpacked manpages may be browsed at : > > http://www.ipsec.nu/dns/bind9/Bv9ARM.html OK. Bind9 is the DNS-server. Now... how can I configure a IPv6-only node (client) to access to a DNS server that is a IPv6-only node too. I've modified /etc/resolv.conf with the IPv6 address of DNS-server, but don't work (no DNS-query packet found on the net). More ideas?? I'm working with Linux. Thank you!! -- ******************************************** Julio Baixauli Garreta baixauli@mat.upc.es ******************************************** From areitzel@mci.net Wed Jan 17 14:29:51 2001 From: areitzel@mci.net (Andrea Reitzel) Date: Wed, 17 Jan 2001 09:29:51 -0500 Subject: Commercial IPv6 Services In-Reply-To: <00e501c08064$7578a660$a186e4c0@mimos.my> Message-ID: This is a multi-part message in MIME format. --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT In the U.S., the vBNS+ commercial services include IPv6. For more information see http://www.vbns.net or feel free to contact me directly. Regards, Andrea Reitzel vBNS Engineering/Worldcom areitzel@mci.net 703-886-1809 -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak Sent: Wednesday, January 17, 2001 4:04 AM To: 6bone@ISI.EDU Subject: Commercial IPv6 Services Hi, Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks Regards, Rohani --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
In the U.S., the vBNS+ commercial services include IPv6.  For more information see http://www.vbns.net or feel free to contact me directly.
 
Regards,
Andrea Reitzel
 
vBNS Engineering/Worldcom
703-886-1809
-----Original Message-----
From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak
Sent: Wednesday, January 17, 2001 4:04 AM
To: 6bone@ISI.EDU
Subject: Commercial IPv6 Services

Hi,
 
Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks
 
Regards,
Rohani  
 
--Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ)-- From peter@ipsec.nu Wed Jan 17 09:49:31 2001 From: peter@ipsec.nu (Peter Håkanson) Date: Wed, 17 Jan 2001 10:49:31 +0100 Subject: DNS In-Reply-To: <3A65689A.509F9895@mat.upc.es> References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> Message-ID: <01011710511905.34720@warp.ipsec.nu> *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden From itojun@itojun.org Wed Jan 17 12:13:59 2001 From: itojun@itojun.org (Jun-ichiro itojun Hagino) Date: Wed, 17 Jan 2001 21:13:59 +0900 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) Message-ID: <20010117121359.41CD47E66@starfruit.itojun.org> *This message was transferred with a trial version of CommuniGate(tm) Pro* # not sure why it did not get through. at PAIX, we use 3ffe:80a::/32 (acutally 3ffe:80a::/64) for the peering segment between ISPs. 3ffe:800::/24 is assigned to ISI, and as ISI and PAIX are not directly connected, 3ffe:800::/24 has two (or more) disconnected networks. we did not expect to receive/propagate prefixes longer than sTLA/pTLA prefixes (*), our EBGP routers filter out logner prefixes (as suggested in 6bone operation RFC) and internal routers do not have the route for 3ffe:80a::/32. packets to 3ffe:80a::/32 get routed to ISI (instead of PAIX) and get dropped. (*) currently our rule is as follows: - prefixes that match 3ffe:0000::/17 and prefixlen = 24 - prefixes that match 3ffe:8000::/17 and prefixlen = 28 - prefixes that match 2001::/16 and prefixlen = 29 to 35 - prefixes that match 2000::/3 and prefixlen = 16 - prefixes specifically agreed with other peers what should we do? if we need to receive/propagate 3ffe:80a::/32 or /64, we may just need to do that and then the particular problem will be solved. however, i have some worry here... if we add more and more practice like this, we eventually get more external routes. i can think of couple of solutions: - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world based on normal prefix length (like /28 for pTLA). the IX will ensure connectivity between IX segments (so there will be no reachability issue). - define an address range for IX segments (like 3ffe:fff0::/28). assign /48 out of it to IX (who assigns it is another question). ask everyone to accept /48 (not just /28) for the prefix. - do not use global address on the IX segment. I know some routers cannot establish BGP4+ peers using linklocal address. - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. what do people think? itojun From stuart@mfnx.net Wed Jan 17 17:15:19 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Wed, 17 Jan 2001 09:15:19 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Wed, 17 Jan 2001 21:13:59 +0900." <20010117121359.41CD47E66@starfruit.itojun.org> Message-ID: <200101171715.f0HHFJl55971@hi.tech.org> PAIX followed the same model it uses for v4 address space to get v6 address space - ISI provides micro-allocation services out of a block from which they provide IXs with address space. > i can think of couple of solutions: > - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world > based on normal prefix length (like /28 for pTLA). the IX will > ensure connectivity between IX segments (so there will be no > reachability issue). PAIX does not have any "interior" connectivity - that would amount to having the IX compete with its customers for the carriage of traffic in the wide area. Also, PAIX owns no routers with which to make an aggregated announcement (not that it couldn't be done, but it's not part of the current model). > - do not use global address on the IX segment. I know some routers > cannot establish BGP4+ peers using linklocal address. Possible. > - define an address range for IX segments (like 3ffe:fff0::/28). > assign /48 out of it to IX (who assigns it is another question). > ask everyone to accept /48 (not just /28) for the prefix. > > - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. Given that the IX can't carry bits in the wide area, these wind up being mostly the same option, and (I agree) infeasible. Stephen From baixauli@mat.upc.es Wed Jan 17 10:29:23 2001 From: baixauli@mat.upc.es (Julio Baixauli) Date: Wed, 17 Jan 2001 11:29:23 +0100 Subject: DNS References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> <01011710511905.34720@warp.ipsec.nu> Message-ID: <3A657403.4C0F6A2F@mat.upc.es> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* "Peter Håkanson" wrote: > > On Wed, 17 Jan 2001, you wrote: > > "Peter Håkanson" wrote: > > > > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > Bind-9 is the latest version of bind from isc.org > The software may be obtained from www.isc.org, > the unpacked manpages may be browsed at : > > http://www.ipsec.nu/dns/bind9/Bv9ARM.html OK. Bind9 is the DNS-server. Now... how can I configure a IPv6-only node (client) to access to a DNS server that is a IPv6-only node too. I've modified /etc/resolv.conf with the IPv6 address of DNS-server, but don't work (no DNS-query packet found on the net). More ideas?? I'm working with Linux. Thank you!! -- ******************************************** Julio Baixauli Garreta baixauli@mat.upc.es ******************************************** From areitzel@mci.net Wed Jan 17 14:29:51 2001 From: areitzel@mci.net (Andrea Reitzel) Date: Wed, 17 Jan 2001 09:29:51 -0500 Subject: Commercial IPv6 Services In-Reply-To: <00e501c08064$7578a660$a186e4c0@mimos.my> Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* This is a multi-part message in MIME format. --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT In the U.S., the vBNS+ commercial services include IPv6. For more information see http://www.vbns.net or feel free to contact me directly. Regards, Andrea Reitzel vBNS Engineering/Worldcom areitzel@mci.net 703-886-1809 -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak Sent: Wednesday, January 17, 2001 4:04 AM To: 6bone@ISI.EDU Subject: Commercial IPv6 Services Hi, Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks Regards, Rohani --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
In the U.S., the vBNS+ commercial services include IPv6.  For more information see http://www.vbns.net or feel free to contact me directly.
 
Regards,
Andrea Reitzel
 
vBNS Engineering/Worldcom
703-886-1809
-----Original Message-----
From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak
Sent: Wednesday, January 17, 2001 4:04 AM
To: 6bone@ISI.EDU
Subject: Commercial IPv6 Services

Hi,
 
Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks
 
Regards,
Rohani  
 
--Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ)-- From peter@ipsec.nu Wed Jan 17 09:49:31 2001 From: peter@ipsec.nu (Peter Håkanson) Date: Wed, 17 Jan 2001 10:49:31 +0100 Subject: DNS In-Reply-To: <3A65689A.509F9895@mat.upc.es> References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> Message-ID: <01011710511905.34720@warp.ipsec.nu> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden From itojun@itojun.org Wed Jan 17 12:13:59 2001 From: itojun@itojun.org (Jun-ichiro itojun Hagino) Date: Wed, 17 Jan 2001 21:13:59 +0900 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) Message-ID: <20010117121359.41CD47E66@starfruit.itojun.org> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* # not sure why it did not get through. at PAIX, we use 3ffe:80a::/32 (acutally 3ffe:80a::/64) for the peering segment between ISPs. 3ffe:800::/24 is assigned to ISI, and as ISI and PAIX are not directly connected, 3ffe:800::/24 has two (or more) disconnected networks. we did not expect to receive/propagate prefixes longer than sTLA/pTLA prefixes (*), our EBGP routers filter out logner prefixes (as suggested in 6bone operation RFC) and internal routers do not have the route for 3ffe:80a::/32. packets to 3ffe:80a::/32 get routed to ISI (instead of PAIX) and get dropped. (*) currently our rule is as follows: - prefixes that match 3ffe:0000::/17 and prefixlen = 24 - prefixes that match 3ffe:8000::/17 and prefixlen = 28 - prefixes that match 2001::/16 and prefixlen = 29 to 35 - prefixes that match 2000::/3 and prefixlen = 16 - prefixes specifically agreed with other peers what should we do? if we need to receive/propagate 3ffe:80a::/32 or /64, we may just need to do that and then the particular problem will be solved. however, i have some worry here... if we add more and more practice like this, we eventually get more external routes. i can think of couple of solutions: - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world based on normal prefix length (like /28 for pTLA). the IX will ensure connectivity between IX segments (so there will be no reachability issue). - define an address range for IX segments (like 3ffe:fff0::/28). assign /48 out of it to IX (who assigns it is another question). ask everyone to accept /48 (not just /28) for the prefix. - do not use global address on the IX segment. I know some routers cannot establish BGP4+ peers using linklocal address. - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. what do people think? itojun From stuart@mfnx.net Wed Jan 17 17:15:19 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Wed, 17 Jan 2001 09:15:19 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Wed, 17 Jan 2001 21:13:59 +0900." <20010117121359.41CD47E66@starfruit.itojun.org> Message-ID: <200101171715.f0HHFJl55971@hi.tech.org> *This message was transferred with a trial version of CommuniGate(tm) Pro* PAIX followed the same model it uses for v4 address space to get v6 address space - ISI provides micro-allocation services out of a block from which they provide IXs with address space. > i can think of couple of solutions: > - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world > based on normal prefix length (like /28 for pTLA). the IX will > ensure connectivity between IX segments (so there will be no > reachability issue). PAIX does not have any "interior" connectivity - that would amount to having the IX compete with its customers for the carriage of traffic in the wide area. Also, PAIX owns no routers with which to make an aggregated announcement (not that it couldn't be done, but it's not part of the current model). > - do not use global address on the IX segment. I know some routers > cannot establish BGP4+ peers using linklocal address. Possible. > - define an address range for IX segments (like 3ffe:fff0::/28). > assign /48 out of it to IX (who assigns it is another question). > ask everyone to accept /48 (not just /28) for the prefix. > > - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. Given that the IX can't carry bits in the wide area, these wind up being mostly the same option, and (I agree) infeasible. Stephen From areitzel@mci.net Wed Jan 17 14:29:51 2001 From: areitzel@mci.net (Andrea Reitzel) Date: Wed, 17 Jan 2001 09:29:51 -0500 Subject: Commercial IPv6 Services In-Reply-To: <00e501c08064$7578a660$a186e4c0@mimos.my> Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* This is a multi-part message in MIME format. --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT In the U.S., the vBNS+ commercial services include IPv6. For more information see http://www.vbns.net or feel free to contact me directly. Regards, Andrea Reitzel vBNS Engineering/Worldcom areitzel@mci.net 703-886-1809 -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak Sent: Wednesday, January 17, 2001 4:04 AM To: 6bone@ISI.EDU Subject: Commercial IPv6 Services Hi, Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks Regards, Rohani --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
In the U.S., the vBNS+ commercial services include IPv6.  For more information see http://www.vbns.net or feel free to contact me directly.
 
Regards,
Andrea Reitzel
 
vBNS Engineering/Worldcom
703-886-1809
-----Original Message-----
From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak
Sent: Wednesday, January 17, 2001 4:04 AM
To: 6bone@ISI.EDU
Subject: Commercial IPv6 Services

Hi,
 
Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks
 
Regards,
Rohani  
 
--Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ)-- From peter@ipsec.nu Wed Jan 17 09:49:31 2001 From: peter@ipsec.nu (Peter Håkanson) Date: Wed, 17 Jan 2001 10:49:31 +0100 Subject: DNS In-Reply-To: <3A65689A.509F9895@mat.upc.es> References: <3A649D42.71146D16@mat.upc.es> <01011709131801.34720@warp.ipsec.nu> <3A65689A.509F9895@mat.upc.es> Message-ID: <01011710511905.34720@warp.ipsec.nu> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden From itojun@itojun.org Wed Jan 17 12:13:59 2001 From: itojun@itojun.org (Jun-ichiro itojun Hagino) Date: Wed, 17 Jan 2001 21:13:59 +0900 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) Message-ID: <20010117121359.41CD47E66@starfruit.itojun.org> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* # not sure why it did not get through. at PAIX, we use 3ffe:80a::/32 (acutally 3ffe:80a::/64) for the peering segment between ISPs. 3ffe:800::/24 is assigned to ISI, and as ISI and PAIX are not directly connected, 3ffe:800::/24 has two (or more) disconnected networks. we did not expect to receive/propagate prefixes longer than sTLA/pTLA prefixes (*), our EBGP routers filter out logner prefixes (as suggested in 6bone operation RFC) and internal routers do not have the route for 3ffe:80a::/32. packets to 3ffe:80a::/32 get routed to ISI (instead of PAIX) and get dropped. (*) currently our rule is as follows: - prefixes that match 3ffe:0000::/17 and prefixlen = 24 - prefixes that match 3ffe:8000::/17 and prefixlen = 28 - prefixes that match 2001::/16 and prefixlen = 29 to 35 - prefixes that match 2000::/3 and prefixlen = 16 - prefixes specifically agreed with other peers what should we do? if we need to receive/propagate 3ffe:80a::/32 or /64, we may just need to do that and then the particular problem will be solved. however, i have some worry here... if we add more and more practice like this, we eventually get more external routes. i can think of couple of solutions: - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world based on normal prefix length (like /28 for pTLA). the IX will ensure connectivity between IX segments (so there will be no reachability issue). - define an address range for IX segments (like 3ffe:fff0::/28). assign /48 out of it to IX (who assigns it is another question). ask everyone to accept /48 (not just /28) for the prefix. - do not use global address on the IX segment. I know some routers cannot establish BGP4+ peers using linklocal address. - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. what do people think? itojun From stuart@mfnx.net Wed Jan 17 17:15:19 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Wed, 17 Jan 2001 09:15:19 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Wed, 17 Jan 2001 21:13:59 +0900." <20010117121359.41CD47E66@starfruit.itojun.org> Message-ID: <200101171715.f0HHFJl55971@hi.tech.org> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* PAIX followed the same model it uses for v4 address space to get v6 address space - ISI provides micro-allocation services out of a block from which they provide IXs with address space. > i can think of couple of solutions: > - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world > based on normal prefix length (like /28 for pTLA). the IX will > ensure connectivity between IX segments (so there will be no > reachability issue). PAIX does not have any "interior" connectivity - that would amount to having the IX compete with its customers for the carriage of traffic in the wide area. Also, PAIX owns no routers with which to make an aggregated announcement (not that it couldn't be done, but it's not part of the current model). > - do not use global address on the IX segment. I know some routers > cannot establish BGP4+ peers using linklocal address. Possible. > - define an address range for IX segments (like 3ffe:fff0::/28). > assign /48 out of it to IX (who assigns it is another question). > ask everyone to accept /48 (not just /28) for the prefix. > > - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. Given that the IX can't carry bits in the wide area, these wind up being mostly the same option, and (I agree) infeasible. Stephen From ina@mimos.my Thu Jan 18 03:30:41 2001 From: ina@mimos.my (Raja Azlina Raja Mahmood) Date: Thu, 18 Jan 2001 11:30:41 +0800 (MYT) Subject: IPSec and Flow Label implementation progress? Message-ID: Hi, I understand these features are already shipped-in the IPv6 header in today IPv6 stack implementation. However, is it true that we haven't use these features yet, since there is some standardization need to be done? Are there more reasons to it? How can we participate in this implementation? Any pointers? Appreciate any help. -ina From areitzel@mci.net Wed Jan 17 14:29:51 2001 From: areitzel@mci.net (Andrea Reitzel) Date: Wed, 17 Jan 2001 09:29:51 -0500 Subject: Commercial IPv6 Services In-Reply-To: <00e501c08064$7578a660$a186e4c0@mimos.my> Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* This is a multi-part message in MIME format. --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT In the U.S., the vBNS+ commercial services include IPv6. For more information see http://www.vbns.net or feel free to contact me directly. Regards, Andrea Reitzel vBNS Engineering/Worldcom areitzel@mci.net 703-886-1809 -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak Sent: Wednesday, January 17, 2001 4:04 AM To: 6bone@ISI.EDU Subject: Commercial IPv6 Services Hi, Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks Regards, Rohani --Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
In the U.S., the vBNS+ commercial services include IPv6.  For more information see http://www.vbns.net or feel free to contact me directly.
 
Regards,
Andrea Reitzel
 
vBNS Engineering/Worldcom
703-886-1809
-----Original Message-----
From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Che Rohani Ishak
Sent: Wednesday, January 17, 2001 4:04 AM
To: 6bone@ISI.EDU
Subject: Commercial IPv6 Services

Hi,
 
Currently, I know that there are only two ISP providing commercial IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? Hope to get Clarification.Thanks
 
Regards,
Rohani  
 
--Boundary_(ID_jwrPbX5NmffawuuRrrG3AQ)-- From horape@tinuviel.compendium.net.ar Thu Jan 18 05:01:21 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Thu, 18 Jan 2001 02:01:21 -0300 Subject: Duplicates messages. Message-ID: <20010118020121.B10842@tinuviel.compendium.net.ar> ¡Hola! I'm the only receiving dupes? Interesting things about the dupes are: X-Delivered-To: X-Envelope-To: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* ----- Forwarded message from Peter Håkanson ----- X-Delivered-To: X-Envelope-To: From: Peter Håkanson To: Julio Baixauli Subject: Re: DNS Date: Wed, 17 Jan 2001 10:49:31 +0100 X-Mailer: KMail [version 1.0.28] Cc: 6bone <6bone@ISI.EDU> X-MIME-Autoconverted: from quoted-printable to 8bit by zephyr.isi.edu id BAA01467 X-SpamBouncer: 1.3 beta (6/24/00) X-SBNote: FROM_DAEMON/Listserv X-SBClass: Bulk *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden ----- End forwarded message ----- -- HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From ina@mimos.my Thu Jan 18 03:30:41 2001 From: ina@mimos.my (Raja Azlina Raja Mahmood) Date: Thu, 18 Jan 2001 11:30:41 +0800 (MYT) Subject: IPSec and Flow Label implementation progress? Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I understand these features are already shipped-in the IPv6 header in today IPv6 stack implementation. However, is it true that we haven't use these features yet, since there is some standardization need to be done? Are there more reasons to it? How can we participate in this implementation? Any pointers? Appreciate any help. -ina From stuart@mfnx.net Wed Jan 17 17:15:19 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Wed, 17 Jan 2001 09:15:19 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Wed, 17 Jan 2001 21:13:59 +0900." <20010117121359.41CD47E66@starfruit.itojun.org> Message-ID: <200101171715.f0HHFJl55971@hi.tech.org> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* PAIX followed the same model it uses for v4 address space to get v6 address space - ISI provides micro-allocation services out of a block from which they provide IXs with address space. > i can think of couple of solutions: > - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world > based on normal prefix length (like /28 for pTLA). the IX will > ensure connectivity between IX segments (so there will be no > reachability issue). PAIX does not have any "interior" connectivity - that would amount to having the IX compete with its customers for the carriage of traffic in the wide area. Also, PAIX owns no routers with which to make an aggregated announcement (not that it couldn't be done, but it's not part of the current model). > - do not use global address on the IX segment. I know some routers > cannot establish BGP4+ peers using linklocal address. Possible. > - define an address range for IX segments (like 3ffe:fff0::/28). > assign /48 out of it to IX (who assigns it is another question). > ask everyone to accept /48 (not just /28) for the prefix. > > - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. Given that the IX can't carry bits in the wide area, these wind up being mostly the same option, and (I agree) infeasible. Stephen From horape@tinuviel.compendium.net.ar Thu Jan 18 05:01:21 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Thu, 18 Jan 2001 02:01:21 -0300 Subject: Duplicates messages. Message-ID: <20010118020121.B10842@tinuviel.compendium.net.ar> *This message was transferred with a trial version of CommuniGate(tm) Pro* ¡Hola! I'm the only receiving dupes? Interesting things about the dupes are: X-Delivered-To: X-Envelope-To: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* ----- Forwarded message from Peter Håkanson ----- X-Delivered-To: X-Envelope-To: From: Peter Håkanson To: Julio Baixauli Subject: Re: DNS Date: Wed, 17 Jan 2001 10:49:31 +0100 X-Mailer: KMail [version 1.0.28] Cc: 6bone <6bone@ISI.EDU> X-MIME-Autoconverted: from quoted-printable to 8bit by zephyr.isi.edu id BAA01467 X-SpamBouncer: 1.3 beta (6/24/00) X-SBNote: FROM_DAEMON/Listserv X-SBClass: Bulk *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden ----- End forwarded message ----- -- HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From Ronald.vanderPol@surfnet.nl Thu Jan 18 10:46:11 2001 From: Ronald.vanderPol@surfnet.nl (Ronald.vanderPol@surfnet.nl) Date: Thu, 18 Jan 2001 11:46:11 +0100 (CET) Subject: Commercial IPv6 Services In-Reply-To: <00e501c08064$7578a660$a186e4c0@mimos.my> Message-ID: On Wed, 17 Jan 2001, Che Rohani Ishak wrote: > Hi, > > Currently, I know that there are only two ISP providing commercial > IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? > Hope to get Clarification.Thanks SURFnet is not a commercial ISP but the National Research Network of the Netherlands. We are a closed network for higher education and research institutes in the Netherlands only. We offer IPv6 pilot production service to our customers. We have an IPv6 in IPv4 tunneled network with peerings at the AMS-IX, 6TAP and TEN-155. rvdp From bstojakovic@netway.at Thu Jan 18 10:46:55 2001 From: bstojakovic@netway.at (Stojakovic, Branislav) Date: Thu, 18 Jan 2001 11:46:55 +0100 Subject: Config. example for DNS (Bind FreeBSD) Message-ID: Hi there I am searching Bind (DNS) example configuration of IPv6 on FreeBSD. Cheers Brani From ina@mimos.my Thu Jan 18 03:30:41 2001 From: ina@mimos.my (Raja Azlina Raja Mahmood) Date: Thu, 18 Jan 2001 11:30:41 +0800 (MYT) Subject: IPSec and Flow Label implementation progress? Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I understand these features are already shipped-in the IPv6 header in today IPv6 stack implementation. However, is it true that we haven't use these features yet, since there is some standardization need to be done? Are there more reasons to it? How can we participate in this implementation? Any pointers? Appreciate any help. -ina From stuart@mfnx.net Wed Jan 17 17:15:19 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Wed, 17 Jan 2001 09:15:19 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Wed, 17 Jan 2001 21:13:59 +0900." <20010117121359.41CD47E66@starfruit.itojun.org> Message-ID: <200101171715.f0HHFJl55971@hi.tech.org> PAIX followed the same model it uses for v4 address space to get v6 address space - ISI provides micro-allocation services out of a block from which they provide IXs with address space. > i can think of couple of solutions: > - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world > based on normal prefix length (like /28 for pTLA). the IX will > ensure connectivity between IX segments (so there will be no > reachability issue). PAIX does not have any "interior" connectivity - that would amount to having the IX compete with its customers for the carriage of traffic in the wide area. Also, PAIX owns no routers with which to make an aggregated announcement (not that it couldn't be done, but it's not part of the current model). > - do not use global address on the IX segment. I know some routers > cannot establish BGP4+ peers using linklocal address. Possible. > - define an address range for IX segments (like 3ffe:fff0::/28). > assign /48 out of it to IX (who assigns it is another question). > ask everyone to accept /48 (not just /28) for the prefix. > > - get 1 sTLA/pTLA prefix for each of the IX segment. it is infeasible. Given that the IX can't carry bits in the wide area, these wind up being mostly the same option, and (I agree) infeasible. Stephen From horape@tinuviel.compendium.net.ar Thu Jan 18 05:01:21 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Thu, 18 Jan 2001 02:01:21 -0300 Subject: Duplicates messages. Message-ID: <20010118020121.B10842@tinuviel.compendium.net.ar> *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* ¡Hola! I'm the only receiving dupes? Interesting things about the dupes are: X-Delivered-To: X-Envelope-To: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* ----- Forwarded message from Peter Håkanson ----- X-Delivered-To: X-Envelope-To: From: Peter Håkanson To: Julio Baixauli Subject: Re: DNS Date: Wed, 17 Jan 2001 10:49:31 +0100 X-Mailer: KMail [version 1.0.28] Cc: 6bone <6bone@ISI.EDU> X-MIME-Autoconverted: from quoted-printable to 8bit by zephyr.isi.edu id BAA01467 X-SpamBouncer: 1.3 beta (6/24/00) X-SBNote: FROM_DAEMON/Listserv X-SBClass: Bulk *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, you wrote: > "Peter Håkanson" wrote: > > > > > > Yes. Bind-9 should be able to communicate with ipv6 > > > > I've not found any bind man page in section 9. there is bind(2) man > page, but it not seems to be that you refers. > Where can I find bind-9? Bind-9 is the latest version of bind from isc.org The software may be obtained from www.isc.org, the unpacked manpages may be browsed at : http://www.ipsec.nu/dns/bind9/Bv9ARM.html > > Thank you very much!! > > -- > ******************************************** > > Julio Baixauli Garreta > baixauli@mat.upc.es > > ******************************************** -- Peter Håkanson Phone +46707328101 Fax +4631223190 IPSec sverige Email peter@ipsec.nu "Safe by design" Address Bror Nilssons gata 16 Lundbystrand S-417 55 Gothenburg Sweden ----- End forwarded message ----- -- HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From bstojakovic@netway.at Thu Jan 18 10:46:55 2001 From: bstojakovic@netway.at (Stojakovic, Branislav) Date: Thu, 18 Jan 2001 11:46:55 +0100 Subject: Config. example for DNS (Bind FreeBSD) Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi there I am searching Bind (DNS) example configuration of IPv6 on FreeBSD. Cheers Brani From Ronald.vanderPol@surfnet.nl Thu Jan 18 10:46:11 2001 From: Ronald.vanderPol@surfnet.nl (Ronald.vanderPol@surfnet.nl) Date: Thu, 18 Jan 2001 11:46:11 +0100 (CET) Subject: Commercial IPv6 Services In-Reply-To: <00e501c08064$7578a660$a186e4c0@mimos.my> Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* On Wed, 17 Jan 2001, Che Rohani Ishak wrote: > Hi, > > Currently, I know that there are only two ISP providing commercial > IPv6 services that is IIJ and NTT. How about Surfnet and Trumpet? > Hope to get Clarification.Thanks SURFnet is not a commercial ISP but the National Research Network of the Netherlands. We are a closed network for higher education and research institutes in the Netherlands only. We offer IPv6 pilot production service to our customers. We have an IPv6 in IPv4 tunneled network with peerings at the AMS-IX, 6TAP and TEN-155. rvdp From ina@mimos.my Thu Jan 18 03:30:41 2001 From: ina@mimos.my (Raja Azlina Raja Mahmood) Date: Thu, 18 Jan 2001 11:30:41 +0800 (MYT) Subject: IPSec and Flow Label implementation progress? Message-ID: *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I understand these features are already shipped-in the IPv6 header in today IPv6 stack implementation. However, is it true that we haven't use these features yet, since there is some standardization need to be done? Are there more reasons to it? How can we participate in this implementation? Any pointers? Appreciate any help. -ina From goddardm@home.com Thu Jan 18 20:09:34 2001 From: goddardm@home.com (Matthew Goddard) Date: Thu, 18 Jan 2001 15:09:34 -0500 Subject: Repeating Message-ID: Is it someone's trial CommuniGate Pro which is relaying e-mails back to the list? That message seems to be popping up a lot..... Matthew Goddard (goddardm@home.com) From martijn@zeelandnet.nl Thu Jan 18 21:58:01 2001 From: martijn@zeelandnet.nl (Martijn van Dorst) Date: Thu, 18 Jan 2001 22:58:01 +0100 Subject: Config. example for DNS (Bind FreeBSD) References: Message-ID: <3A6766E9.6D1CFDB4@zeelandnet.nl> "Stojakovic, Branislav" wrote: > > *This message was transferred with a trial version of CommuniGate(tm) Pro* > Hi there > > I am searching Bind (DNS) example configuration of IPv6 on FreeBSD. Take a look at http://www.ipv6.zeelandnet.nl/bind.html Very simple and working bind sample. Regards Martijn From Francis.Dupont@enst-bretagne.fr Fri Jan 19 08:50:52 2001 From: Francis.Dupont@enst-bretagne.fr (Francis Dupont) Date: Fri, 19 Jan 2001 09:50:52 +0100 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of Wed, 17 Jan 2001 21:13:59 +0900. <20010117121359.41CD47E66@starfruit.itojun.org> Message-ID: <200101190850.f0J8oqO10168@givry.rennes.enst-bretagne.fr> In your previous mail you wrote: (*) currently our rule is as follows: - prefixes that match 3ffe:0000::/17 and prefixlen = 24 - prefixes that match 3ffe:8000::/17 and prefixlen = 28 - prefixes that match 2001::/16 and prefixlen = 29 to 35 => you should accept prefixes with shorter prefixlen (because someone can aggregate some prefixes in these three blocks. I don't believe this happens but this shall happen). i can think of couple of solutions: - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world based on normal prefix length (like /28 for pTLA). the IX will ensure connectivity between IX segments (so there will be no reachability issue). => this seems the good solution (IXes are good TLA candidates!) - do not use global address on the IX segment. I know some routers cannot establish BGP4+ peers using linklocal address. => if the peer address is used in order to detect loops (ie config errors) then it is very reasonnable to mandate global addresses. Same for iBGP or multi-hop eBGP... Thanks Francis.Dupont@enst-bretagne.fr From stuart@mfnx.net Fri Jan 19 20:28:07 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Fri, 19 Jan 2001 12:28:07 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Fri, 19 Jan 2001 09:50:52 +0100." <200101190850.f0J8oqO10168@givry.rennes.enst-bretagne.fr> Message-ID: <200101192028.f0JKS7f15112@hi.tech.org> > i can think of couple of solutions: > - an IX (say PAIX) gets an sTLA/pTLA. the IX announces it to the world > based on normal prefix length (like /28 for pTLA). the IX will > ensure connectivity between IX segments (so there will be no > reachability issue). > > => this seems the good solution (IXes are good TLA candidates!) How does an entity that does not operate a router announce any kind of prefix to the world? Networks that attach to an IX need to carry the /64 of the IX network in their IGP or iBGP in order to recursively look up next-hop addresses of peers at that IX. The only thing that having the IX announce an aggregated prefix would accomplish is to allow traceroute for networks *not* connected to the IX to work without seeing "* * *" in place of the hop through the IX. While it's nice when traceroute works, traffic will flow correctly on a path without it. As I said in my previous mail, PAIX does *not* operate a router, and does *not* compete with its customers for the wide-area carriage of traffic. One of the problems we encounter at IXes is participants who rewrite next-hop or install static routes to cause other networks to carry traffic that they did not offer to carry. This same technique could be used to cause an IX that offered interior connectivity between exchange points to function as a transit carrier. An IX that does not want to function as a transit carrier now has to implement defenses against it; an IX that does now competes with its customers. Neither option sounds good to me. Stephen -- Stephen Stuart stuart@mfnx.net VP, Research and Advanced Development Metromedia Fiber Network PAIX.Net is a subsidiary of Metromedia Fiber Network From stuart@mfnx.net Sat Jan 20 16:11:37 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Sat, 20 Jan 2001 08:11:37 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Fri, 19 Jan 2001 12:28:07 PST." <200101192028.f0JKS7f15112@hi.tech.org> Message-ID: <200101201611.f0KGBbf36010@hi.tech.org> So, I said: > The only thing that having the IX announce an aggregated prefix would > accomplish is to allow traceroute for networks *not* connected to the > IX to work without seeing "* * *" in place of the hop through the > IX. While it's nice when traceroute works, traffic will flow correctly > on a path without it. and. of course, I got it flipped around; traceroute from networks not connected to the IX will report properly when tracing paths through the IX, but networks not connected can't traceroute directly to an IX address if its prefix is not propagated by the connected providers. Stephen From stuart@mfnx.net Sat Jan 20 16:15:44 2001 From: stuart@mfnx.net (Stephen Stuart) Date: Sat, 20 Jan 2001 08:15:44 -0800 Subject: reachability issue with 3ffe:80a::/32 (PAIX IX segment) In-Reply-To: Your message of "Sat, 20 Jan 2001 10:14:58 +0900." <16380.979953298@coconut.itojun.org> Message-ID: <200101201615.f0KGFif36052@hi.tech.org> > sorry for the confusion. the thing i wanted was a (sort of) > standardized way of assigning an IPV6 prefix for use within IX > segment. IPv6 address assignment plans (well, for 2000::/3) has been > very helpful for validating properly aggregated routes, however, > it does not work for IX address assignment I've seen (as presented > in particular example, topologically disjoint address clouds > under 3ffe:800::/24). PAIX prefixes will be /64s within 3ffe:080A:0000::/48. Stephen From erietberg@chello.nl Sun Jan 21 14:32:38 2001 From: erietberg@chello.nl (Erik Rietberg) Date: Sun, 21 Jan 2001 15:32:38 +0100 Subject: 6to4 on a Cisco Message-ID: <005701c083b7$02342700$0fc0a8c0@rietberg.hvd> Has somebody ever configured 6to4-tunneling on a Cisco ??? I tried, but I can't get it work. I have been using the IPv6 kit from Microsoft for Windows2000, which perfectly connects to the microsoft 6to4-relay router, but when I try to use my own Cisco I get the following error: <> c:\>6to4cfg -R 213.x.x.x Probing 6to4 relay router 213.x.x.x... Could not reach a 6to4 relay router. <> This means that to problem is with the Cisco router. I got the config from the IPv6-IOS command list: I use the following IOS version: <> IOS (tm) 3600 Software (C3620-IS-M), Experimental Version 12.1(20001029:175720) [otroan-samhain 114] <> interface Tunnel0 description Used for 6to4 translations no ip address no ip redirects no ip route-cache cef ipv6 unnumbered Ethernet0/0 tunnel source Ethernet0/0 tunnel mode ipv6ip 6to4 ! interface Ethernet0/0 ip address 213.x.x.x 255.255.255.224 no ip redirects no ip proxy-arp ip route-cache flow half-duplex ipv6 address 2002:XXX:XXX::/48 eui-64 ! ipv6 route 2002::/16 Tunnel0 <> b.t.w. Static tunnels to my linux-box work fine ! greetings, ________________________________________________________ Erik Rietberg erietberg@chello.nl / erik@rietberg.nl / PGP: 0x09CE3401 ________________________________________________________ 'Do files get embarrassed when they get unzipped?' From goddardm@home.com Sun Jan 21 19:02:48 2001 From: goddardm@home.com (Matthew Goddard) Date: Sun, 21 Jan 2001 14:02:48 -0500 Subject: 6to4 on a Cisco In-Reply-To: <005701c083b7$02342700$0fc0a8c0@rietberg.hvd> Message-ID: On the Ethernet 0/0 add this command: ip mtu 1480 And assuming you have converted the IPv4 address correctly to it's hex equivalent it looks like it should work then. Make sure you check the routing tables as well. Hope this helps. -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Erik Rietberg Sent: Sunday, January 21, 2001 9:33 AM To: 6bone@ISI.EDU Subject: 6to4 on a Cisco Has somebody ever configured 6to4-tunneling on a Cisco ??? I tried, but I can't get it work. I have been using the IPv6 kit from Microsoft for Windows2000, which perfectly connects to the microsoft 6to4-relay router, but when I try to use my own Cisco I get the following error: <> c:\>6to4cfg -R 213.x.x.x Probing 6to4 relay router 213.x.x.x... Could not reach a 6to4 relay router. <> This means that to problem is with the Cisco router. I got the config from the IPv6-IOS command list: I use the following IOS version: <> IOS (tm) 3600 Software (C3620-IS-M), Experimental Version 12.1(20001029:175720) [otroan-samhain 114] <> interface Tunnel0 description Used for 6to4 translations no ip address no ip redirects no ip route-cache cef ipv6 unnumbered Ethernet0/0 tunnel source Ethernet0/0 tunnel mode ipv6ip 6to4 ! interface Ethernet0/0 ip address 213.x.x.x 255.255.255.224 no ip redirects no ip proxy-arp ip route-cache flow half-duplex ipv6 address 2002:XXX:XXX::/48 eui-64 ! ipv6 route 2002::/16 Tunnel0 <> b.t.w. Static tunnels to my linux-box work fine ! greetings, ________________________________________________________ Erik Rietberg erietberg@chello.nl / erik@rietberg.nl / PGP: 0x09CE3401 ________________________________________________________ 'Do files get embarrassed when they get unzipped?' From indra@marmoset.net Sun Jan 21 21:38:59 2001 From: indra@marmoset.net (indra@marmoset.net) Date: Sun, 21 Jan 2001 16:38:59 -0500 (EST) Subject: pTLA condition.. Message-ID: hello a small doubt, are all the 6bone pTLA sites having IPv6 enabled web-servers? is that a condition for achieving pTLA status (having an IPv6 enabled website, i mean. the clause in the condition document is not very clear). the list of IPv6 enabled web sites is not very big too, as i could find out. could someone clarify this small doubt? thanks in advance, Indra. From mithrandir@skynet.be Mon Jan 22 07:49:28 2001 From: mithrandir@skynet.be (Mithrandir) Date: Mon, 22 Jan 2001 08:49:28 +0100 Subject: 6to4 on a Cisco References: Message-ID: <002301c08448$54faacc0$0401a8c0@mithrandir> I don't see a tunnel destination. Don't you think a tunnel destination is needed here? If you've already done so, never mind. greetings, Mithrandir ----- Original Message ----- From: "Matthew Goddard" To: "Erik Rietberg" Cc: <6bone@ISI.EDU> Sent: Sunday, January 21, 2001 8:02 PM Subject: RE: 6to4 on a Cisco > > On the Ethernet 0/0 add this command: > > ip mtu 1480 > > And assuming you have converted the IPv4 address correctly to it's hex > equivalent it looks like it should work then. Make sure you check the > routing tables as well. > > Hope this helps. > > -----Original Message----- > From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Erik > Rietberg > Sent: Sunday, January 21, 2001 9:33 AM > To: 6bone@ISI.EDU > Subject: 6to4 on a Cisco > > > Has somebody ever configured 6to4-tunneling on a Cisco ??? > > I tried, but I can't get it work. I have been using the IPv6 kit from > Microsoft for Windows2000, which perfectly connects to the microsoft > 6to4-relay router, but when I try to use my own Cisco I get the following > error: > <> > c:\>6to4cfg -R 213.x.x.x > Probing 6to4 relay router 213.x.x.x... > Could not reach a 6to4 relay router. > <> > > This means that to problem is with the Cisco router. I got the config from > the IPv6-IOS command list: > I use the following IOS version: > <> > IOS (tm) 3600 Software (C3620-IS-M), Experimental Version > 12.1(20001029:175720) [otroan-samhain 114] > <> > > > interface Tunnel0 > description Used for 6to4 translations > no ip address > no ip redirects > no ip route-cache cef > ipv6 unnumbered Ethernet0/0 > tunnel source Ethernet0/0 > tunnel mode ipv6ip 6to4 > ! > interface Ethernet0/0 > ip address 213.x.x.x 255.255.255.224 > no ip redirects > no ip proxy-arp > ip route-cache flow > half-duplex > ipv6 address 2002:XXX:XXX::/48 eui-64 > ! > ipv6 route 2002::/16 Tunnel0 > <> > > b.t.w. Static tunnels to my linux-box work fine ! > > greetings, > ________________________________________________________ > Erik Rietberg > erietberg@chello.nl / erik@rietberg.nl / PGP: 0x09CE3401 > ________________________________________________________ > 'Do files get embarrassed when they get unzipped?' > > > > From Marc.Blanchet@viagenie.qc.ca Mon Jan 22 14:52:54 2001 From: Marc.Blanchet@viagenie.qc.ca (Marc Blanchet) Date: Mon, 22 Jan 2001 09:52:54 -0500 Subject: 6to4 on a Cisco In-Reply-To: <002301c08448$54faacc0$0401a8c0@mithrandir> References: Message-ID: <5.0.2.1.1.20010122095158.03b15408@mail.viagenie.qc.ca> At/À 08:49 2001-01-22 +0100, Mithrandir you wrote/vous écriviez: >I don't see a tunnel destination. >Don't you think a tunnel destination is needed here? nope. ipv4 destination address is extracted from the ipv6 destination address. this is the purpose of 6to4. Regards, Marc. >If you've already done so, never mind. >greetings, >Mithrandir > > > >----- Original Message ----- >From: "Matthew Goddard" >To: "Erik Rietberg" >Cc: <6bone@ISI.EDU> >Sent: Sunday, January 21, 2001 8:02 PM >Subject: RE: 6to4 on a Cisco > > > > > > On the Ethernet 0/0 add this command: > > > > ip mtu 1480 > > > > And assuming you have converted the IPv4 address correctly to it's hex > > equivalent it looks like it should work then. Make sure you check the > > routing tables as well. > > > > Hope this helps. > > > > -----Original Message----- > > From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Erik > > Rietberg > > Sent: Sunday, January 21, 2001 9:33 AM > > To: 6bone@ISI.EDU > > Subject: 6to4 on a Cisco > > > > > > Has somebody ever configured 6to4-tunneling on a Cisco ??? > > > > I tried, but I can't get it work. I have been using the IPv6 kit from > > Microsoft for Windows2000, which perfectly connects to the microsoft > > 6to4-relay router, but when I try to use my own Cisco I get the following > > error: > > <> > > c:\>6to4cfg -R 213.x.x.x > > Probing 6to4 relay router 213.x.x.x... > > Could not reach a 6to4 relay router. > > <> > > > > This means that to problem is with the Cisco router. I got the config from > > the IPv6-IOS command list: > > I use the following IOS version: > > <> > > IOS (tm) 3600 Software (C3620-IS-M), Experimental Version > > 12.1(20001029:175720) [otroan-samhain 114] > > <> > > > > > > interface Tunnel0 > > description Used for 6to4 translations > > no ip address > > no ip redirects > > no ip route-cache cef > > ipv6 unnumbered Ethernet0/0 > > tunnel source Ethernet0/0 > > tunnel mode ipv6ip 6to4 > > ! > > interface Ethernet0/0 > > ip address 213.x.x.x 255.255.255.224 > > no ip redirects > > no ip proxy-arp > > ip route-cache flow > > half-duplex > > ipv6 address 2002:XXX:XXX::/48 eui-64 > > ! > > ipv6 route 2002::/16 Tunnel0 > > <> > > > > b.t.w. Static tunnels to my linux-box work fine ! > > > > greetings, > > ________________________________________________________ > > Erik Rietberg > > erietberg@chello.nl / erik@rietberg.nl / PGP: 0x09CE3401 > > ________________________________________________________ > > 'Do files get embarrassed when they get unzipped?' > > > > > > > > Marc Blanchet Viagénie inc. tel: 418-656-9254 http://www.viagenie.qc.ca ---------------------------------------------------------- Normos (http://www.normos.org): Internet standards portal: IETF RFC, drafts, IANA, W3C, ATMForum, ISO, ... all in one place. From erietberg@chello.nl Mon Jan 22 20:03:37 2001 From: erietberg@chello.nl (Erik Rietberg) Date: Mon, 22 Jan 2001 21:03:37 +0100 Subject: 6to4 on a Cisco References: <502ED1B5ECC92D4FB7A2966CB8A4DE44501BDA@SALTIS10.SIMULTAN.CH> Message-ID: <002301c084ae$68a20b40$0fc0a8c0@rietberg.hvd> Hi Thomas, > the trouble with M$'s 6to4cfg.exe is that they check the prospective 6to4 > gateway for mainly two things: > > 1. Reachability via IPv4 ICMP messages (i.e. ping) > 2. Reachability via automatic IPv6-in-IPv4 tunneling (like ping6 > ::213.x.x.x) > > although the second is not needed by the 6to4 en/decapsulation. That's why > you must do the last step of their config by hand: > > ipv6 rtu ::/0 2/::213.x.x.x pub life 1800 > > Afterwards 6to4 should be working. Yep, it works !! Thanks for the help. I think the problem is with issue 2, because I can normally ping the router. Is the automatic IPv6-in-IPv4 tunneling a feature I can activate on a Cisco ?? Erik From kristoff.bonne@skypro.be Mon Jan 22 21:01:13 2001 From: kristoff.bonne@skypro.be (Kristoff Bonne) Date: Mon, 22 Jan 2001 22:01:13 +0100 (CET) Subject: 6bone to 6to4 Message-ID: Greetings, Besides 6bone (BGP) connectivity, I am also playing with the 6to4 encapsulation. I my router has IP-address 195.13.17.26, I use the block of IP-addresses 2002:C30D:111A/48. (which should be correct). I also set up a static route at my router, that routes traffic to 2002::/16 to the 6-to-4 tunnel. (The rest used the routing-info that is received via BGP4+). (Also note, that I also have a block of IP-addresses from the 6bone: 3FFE:80B0:1001::/48, received from belnet. This seams to work for hosts that have a IPv6-address in my 6bone-range (for all traffic), but a hosts that only has a 6to4-type address can only reach other hosts that have a 6to4 address. Is there something that needs to be done so that nodes on the 6bone can also contact me? Can I announce my 6to4-subnet in BGP to the 6bone BGP-clouth or is there somewhere a 'universal' 6bone -> 6to4 gateway. Cheerio! Kr. Bonne. -- KB905-RIPE Belgacom IP networking (c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff) Internet, IP and IP/VPN kristoff.bonne@skypro.be Faxbox : +32 2 2435122 From horape@tinuviel.compendium.net.ar Mon Jan 22 22:08:23 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Mon, 22 Jan 2001 19:08:23 -0300 Subject: what ASN to use? Message-ID: <20010122190823.A2957@tinuviel.compendium.net.ar> ¡Hola! I want to start using BGP4+ but I have not an ASN. I plan to eventually become a pTLA, so i cannot just ask my upstream and use any IANA-RSVD2 ASN. What should i do? The options I see are: a. Use a IANA-RSVD[2] ASN and go ahead hoping nobody is going to start filtering them out (there are 15 sites in the 6bone registry using rsvd ASNs and only a few using BGP4+) b. Use my IPv4 upstream provider ASN and hope they won't enter the 6bone. (there is at least one pTLA doing that) Some other option? Thanks, HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From david@pananix.com Mon Jan 22 23:21:07 2001 From: david@pananix.com (David A. Bandel) Date: Mon, 22 Jan 2001 18:21:07 -0500 Subject: Request for tunnel Message-ID: <3A6CC063.C2CDBFC2@pananix.com> Ladies and Gentlemen: I run a small ISP in the Republic of Panama. I've contacted some folks down here, but no one here is running IPv6. I have a small problem, though. I know most of you want RT times of < 200ms. Unfortunately, due to the way I'm connected, I will not be able to connect to anyone outside Panama at anything less than 500ms. The problem is, I'm connected through Charter Communications via satellite. The downlink is in Texas. But the absolute best times I've seen through the satellite shot is 560ms. Anyone in Texas (or nearby) willing to work with me? If so, you can contact me directly. TIA, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto From Kurt@OpenLDAP.org Tue Jan 23 02:52:12 2001 From: Kurt@OpenLDAP.org (Kurt D. Zeilenga) Date: Mon, 22 Jan 2001 18:52:12 -0800 Subject: 6bone to 6to4 In-Reply-To: Message-ID: <5.0.2.1.0.20010122185055.00a76b60@router.boolean.net> At 10:01 PM 1/22/01 +0100, Kristoff Bonne wrote: >Greetings, > >Besides 6bone (BGP) connectivity, I am also playing with the 6to4 >encapsulation. >I my router has IP-address 195.13.17.26, I use the block of IP-addresses >2002:C30D:111A/48. (which should be correct). > >I also set up a static route at my router, that routes traffic to >2002::/16 to the 6-to-4 tunnel. (The rest used the routing-info that is >received via BGP4+). > >(Also note, that I also have a block of IP-addresses from the >6bone: 3FFE:80B0:1001::/48, received from belnet. > >This seams to work for hosts that have a IPv6-address in my >6bone-range (for all traffic), but a hosts that only has a 6to4-type >address can only reach other hosts that have a 6to4 address. Do they have a route to the 6BONE? >Is there something that needs to be done so that nodes on the 6bone can >also contact me? >Can I announce my 6to4-subnet in BGP to the 6bone BGP-clouth or is there >somewhere a 'universal' 6bone -> 6to4 gateway. > >Cheerio! Kr. Bonne. >-- >KB905-RIPE Belgacom IP networking >(c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff) Internet, IP and IP/VPN >kristoff.bonne@skypro.be Faxbox : +32 2 2435122 From kristoff.bonne@skypro.be Tue Jan 23 11:44:27 2001 From: kristoff.bonne@skypro.be (Kristoff Bonne) Date: Tue, 23 Jan 2001 12:44:27 +0100 (CET) Subject: 6bone to 6to4 In-Reply-To: <5.0.2.1.0.20010122185055.00a76b60@router.boolean.net> Message-ID: Greetings, On Mon, 22 Jan 2001, Kurt D. Zeilenga wrote: >> Besides 6bone (BGP) connectivity, I am also playing with the 6to4 >> encapsulation. >> I my router has IP-address 195.13.17.26, I use the block of IP-addresses >> 2002:C30D:111A/48. (which should be correct). >> I also set up a static route at my router, that routes traffic to >> 2002::/16 to the 6-to-4 tunnel. (The rest used the routing-info that is >> received via BGP4+). >> This seams to work for hosts that have a IPv6-address in my >> 6bone-range (for all traffic), but a hosts that only has a 6to4-type >> address can only reach other hosts that have a 6to4 address. > Do they have a route to the 6BONE? Yep. This is my config: - A cisco router (25xx) which both BGP 4+ to belnet (and from-there-on the 6bone) and a 6to4-interface. (I used to config posted by Erik Rietberg in this list earlier this week). - Routing static route for 2002::/16 to tunnel1 (6to4). For the rest, it 'falls back' to the BGP 4+ routing. - On the LAN-interface, both the 6bone address-range and 2002-range. Only the 6bone-range (and site-local) is announced via RP. - On the lan: one linux-box (which has a 6bone-address learned via RP from the router) and one OpenBSD-box with a 2002-address (configured statically) and default gateway set statiscally to router (link-local address). Result: - linux-box (hence, 6bone-address) can reach everything. A ping6 to a remote 2002-address (e.g. ipv6-router.cisco.com or 6to4.ipv6.microsoft.com) is now faster then before. (which proves that the shortcut for the 2002-address static-route is used). - OpenBSD-box (hence, 2002-address) can reach the other 2002-addresses, but not the 6bone-addresses. To me, it looks like the 6bone-hosts don't know the return-path to my 2002-address. As a test, I've also added my 2002-addresses in my BGP-4+ announcements, and now I can reach SOME 6bone-addresses (like www.6bone.net and www.ipv6.surfnet.nl), but others do not reply (like www.belnet.be or www.kame.net). Is it possible there any some filters somewhere on the BGP-4+ announcements? Can anybody check their B GP 4+ routing-table for AS6774? What I found strange that (in my BGP4+ routing-table) I did found the follwing entry: *> 2002::/16 3FFE:608:2:2::10 0 2611 3257 4697 1251 109 i So, there DOES is a 'universal' 6bone to 6to4 gateway??? Cheerio! Kr. Bonne. -- KB905-RIPE Belgacom IP networking (c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff) Internet, IP and IP/VPN kristoff.bonne@skypro.be Faxbox : +32 2 2435122 From kristoff.bonne@skypro.be Tue Jan 23 12:09:51 2001 From: kristoff.bonne@skypro.be (Kristoff Bonne) Date: Tue, 23 Jan 2001 13:09:51 +0100 (CET) Subject: 6bone to 6to4 In-Reply-To: <20010123000114.D22F7E88@RASKOL.STYX.ORG> Message-ID: Greetings, On Mon, 22 Jan 2001, William Waites wrote: > > Is there something that needs to be done so that nodes on the 6bone can > > also contact me? > > Can I announce my 6to4-subnet in BGP to the 6bone BGP-clouth or is there > > somewhere a 'universal' 6bone -> 6to4 gateway. > AFAIK announcing the 2002::/16 address space into BGP is not done. At > least I do not see that route in the tables I get from external peers. > Given this, a 'universal' gateway is not possible. I do see this in my BGP4+ routing-table: *> 2002::/16 3FFE:608:2:2::10 0 2611 3257 4697 1251 109 i > > The alternative is to have a 6to4 gateway in each ASN on the 6bone. While > this might be a good practice, it is not required of providers so there > is no guarantee of 2002::/16 reachability globally. Well, it should be an ideal situation, wouldn't it? For people who only have 6bone, they will be directed (using the BGP-4+ information) to the 'closest' gateway, so they do not have to cross half the planet to a 'universal' 6bone-6to4 gateway. For people who only have both BGP4+ and 2002, the system automatically chooses the best way. Cheerio! Kr. Bonne. -- KB905-RIPE Belgacom IP networking (c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff) Internet, IP and IP/VPN kristoff.bonne@skypro.be Faxbox : +32 2 2435122 From erietberg@chello.nl Wed Jan 24 17:46:09 2001 From: erietberg@chello.nl (Erik Rietberg) Date: Wed, 24 Jan 2001 18:46:09 +0100 Subject: 6to4 on a Cisco References: <502ED1B5ECC92D4FB7A2966CB8A4DE44501BDB@SALTIS10.SIMULTAN.CH> Message-ID: <00a801c0862d$8967b7a0$0fc0a8c0@rietberg.hvd> > > I think the problem is with issue 2, because I can normally ping the > router. > > Is the automatic IPv6-in-IPv4 tunneling a feature I can activate on a > Cisco ?? With automatic IPv6-in-IPv4 tunneling activated on the Cisco, the Microsoft 6to4cfg works fine ! <> C:\>6to4cfg -R sixco.ipv6.test.nl Probing 6to4 relay router 213.x.x.x... Found 6to4 relay router sixco.ipv6.test.nl (213.x.x.x)... Using local address 213.x.x.x for the 6to4 prefix. <> For all who are interested below my current Cisco-config, with automatic IPv6-in-IPv4 tunneling and 6to4 enabled: <> version 12.1 no service single-slot-reload-enable service nagle no service pad service tcp-keepalives-in service timestamps debug datetime service timestamps log datetime service password-encryption ! hostname Sixco ! boot system tftp://212.x.x.x/c3620-is-mz.20001101 logging buffered 4096 debugging no logging rate-limit enable secret 5 $1$ihP$wCvwdUvT6COQlmYA68ckZg/ ! ip subnet-zero ip cef ! ! no ip finger ip domain-name ipv6.test.nl ip name-server 212.x.x.x ! no ip bootp server ipv6 unicast-routing call rsvp-sync ! interface Loopback0 no ip address ipv6 address 2002:XXXX:XXXX:0:10:7B15:9881:C/64 ipv6 mtu 1480 ! interface Loopback100 no ip address ipv6 address 3FFE:XXXX::1/128 ipv6 mtu 1480 ! interface Tunnel0 description Used for 6to4 translations no ip address no ip redirects no ip route-cache cef ipv6 enable ipv6 unnumbered Loopback0 tunnel source Loopback0 tunnel mode ipv6ip 6to4 tunnel path-mtu-discovery ! interface Tunnel1 description "to IPng" no ip address no ip route-cache cef ipv6 enable ipv6 address 3FFE:XXXX::X/127 ipv6 rip T0 enable tunnel source Ethernet0/0 tunnel destination 212.19.192.219 tunnel mode ipv6ip ! interface Tunnel2 description "to Laptop" no ip address ipv6 enable ipv6 address 3FFE:XXXX::2/127 ipv6 rip T0 enable tunnel source Ethernet0/0 tunnel destination 213.x.x.x tunnel mode ipv6ip ! interface Tunnel3 description "automatic tunneling" no ip address no ip redirects no ip route-cache cef tunnel source Ethernet0/0 tunnel mode ipv6ip auto-tunnel ! interface Ethernet0/0 ip address 213.x.x.x 255.255.255.224 no ip redirects no ip proxy-arp ip mtu 1480 ip route-cache flow half-duplex ipv6 enable ! interface Serial0/0 no ip address shutdown ! interface Serial0/1 no ip address shutdown ! interface Ethernet1/0 no ip address shutdown half-duplex ! router bgp 100 no synchronization no bgp default ipv4-unicast bgp log-neighbor-changes ! address-family ipv6 network DEAD::/64 exit-address-family ! ip classless ip route 0.0.0.0 0.0.0.0 213.x.x.1 no ip http server ! access-list 1 permit 213.x.x.x ipv6 route 3FFE:XXXX::/60 Null0 200 ipv6 route 3FFE:XXXX::/64 Tunnel2 ipv6 route ::/0 Tunnel1 ! ipv6 access-list vty_in permit 3FFE:XXXX::1/128 ! ipv6 router rip T0 ipv6 router rip T1 ! ! dial-peer cor custom ! ! ! ! line con 0 login transport input none line aux 0 login line vty 0 4 access-class 1 in timeout login response 0 ipv6 access-class vty_in in login escape-character 27 ! ntp clock-period 17179992 ntp server 212.x.x.x end <> greetings, Erik From Kurt@OpenLDAP.org Wed Jan 24 02:15:35 2001 From: Kurt@OpenLDAP.org (Kurt D. Zeilenga) Date: Tue, 23 Jan 2001 18:15:35 -0800 Subject: 6bone to 6to4 In-Reply-To: References: <5.0.2.1.0.20010122185055.00a76b60@router.boolean.net> Message-ID: <5.0.2.1.0.20010123175312.00ab1580@router.boolean.net> Kristoff, I am not sure what the policy is for propagating 2002::/16 routes on the 6bone. I would suspect that 2002::/16 routes should only be exchanged between ASs under mutual agreement as to avoid perverse routing situations. There are clearly areas on the 6bone which have no route to 2002::/16. Your upstream 6bone provider may not have a route to 2002::/16 and hence not able to route packets back to you (unless you advertise a 2002::/16 route to them (with permission)). Note that propagation of 2002: with prefixes longer than 16 on the 6bone is prohibited as this would saturate the IPv6 routing tables. You're welcomed to experiment with ping/traceroute to our IPv6 router: 2002:c690:ce31::1 3ffe:1900:3::2 [but don't use as a default router, we don't have the bandwidth]. At 12:44 PM 1/23/01 +0100, Kristoff Bonne wrote: >Greetings, > >On Mon, 22 Jan 2001, Kurt D. Zeilenga wrote: >>> Besides 6bone (BGP) connectivity, I am also playing with the 6to4 >>> encapsulation. >>> I my router has IP-address 195.13.17.26, I use the block of >IP-addresses >>> 2002:C30D:111A/48. (which should be correct). >>> I also set up a static route at my router, that routes traffic to >>> 2002::/16 to the 6-to-4 tunnel. (The rest used the routing-info that is >>> received via BGP4+). > >>> This seams to work for hosts that have a IPv6-address in my >>> 6bone-range (for all traffic), but a hosts that only has a 6to4-type >>> address can only reach other hosts that have a 6to4 address. >> Do they have a route to the 6BONE? >Yep. >This is my config: >- A cisco router (25xx) which both BGP 4+ to belnet (and from-there-on the >6bone) and a 6to4-interface. (I used to config posted by Erik Rietberg in >this list earlier this week). >- Routing static route for 2002::/16 to tunnel1 (6to4). For the rest, it >'falls back' to the BGP 4+ routing. >- On the LAN-interface, both the 6bone address-range and 2002-range. Only >the 6bone-range (and site-local) is announced via RP. >- On the lan: one linux-box (which has a 6bone-address learned via RP from >the router) and one OpenBSD-box with a 2002-address (configured >statically) and default gateway set statiscally to router (link-local >address). > >Result: >- linux-box (hence, 6bone-address) can reach everything. >A ping6 to a remote 2002-address (e.g. ipv6-router.cisco.com or >6to4.ipv6.microsoft.com) is now faster then before. (which proves that the >shortcut for the 2002-address static-route is used). >- OpenBSD-box (hence, 2002-address) can reach the other 2002-addresses, >but not the 6bone-addresses. > >To me, it looks like the 6bone-hosts don't know the return-path to my >2002-address. > >As a test, I've also added my 2002-addresses in my BGP-4+ announcements, >and now I can reach SOME 6bone-addresses (like www.6bone.net and >www.ipv6.surfnet.nl), but others do not reply (like www.belnet.be or >www.kame.net). > >Is it possible there any some filters somewhere on the BGP-4+ >announcements? Can anybody check their B GP 4+ routing-table for AS6774? > > >What I found strange that (in my BGP4+ routing-table) I did found the >follwing entry: >*> 2002::/16 3FFE:608:2:2::10 0 2611 3257 4697 1251 109 i > >So, there DOES is a 'universal' 6bone to 6to4 gateway??? > > >Cheerio! Kr. Bonne. >-- >KB905-RIPE Belgacom IP networking >(c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff) Internet, IP and IP/VPN >kristoff.bonne@skypro.be Faxbox : +32 2 2435122 From srizkalla@uecomm.com.au Mon Jan 29 03:57:01 2001 From: srizkalla@uecomm.com.au (Rizkalla, Simon) Date: Mon, 29 Jan 2001 14:57:01 +1100 Subject: IPv6 Router solicitation in Address Autoconfiguration Message-ID: <33FDD994A379D411B13A0004AC4C81A102C28EAD@email3> To whom it may concern, I am working for Uecomm in Australia and we are currently in the process of deploying IPv6 in our netowrk. I have a query about router solicitation, within stateless autoconfiguration. After the host sends a query, called neighbor discovery, to the same address (itself) to verify the uniqueness of the link local address and there is no response, hence it is unique, the host then sends a multicast address for configuration by the router (router solicitation). My question is why does the host send a multicast address rather than an anycast address, requesting for router solicitation? Regards Simon Rizkalla From fink@es.net Mon Jan 29 17:34:34 2001 From: fink@es.net (Bob Fink) Date: Mon, 29 Jan 2001 09:34:34 -0800 Subject: pTLA request for IRCD - review closes 12 Feb 01 Message-ID: <5.0.0.25.0.20010129093141.03d6fd70@imap2.es.net> 6bone Folk, IRCD has requested a pTLA allocation on behalf of Edisontel in Italy. The open review period for this will close 12 Feb 2001. Please send any comments to me or the list. Thanks, Bob ====================================== >Date: Sun, 28 Jan 2001 16:36:15 +0100 (CET) >From: Max Gargani >To: Bob Fink >Subject: Re: pTLA request > >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: > > 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 a fully maintained entry on 6Bone database: >ipv6-site: IRCD >origin: AS5609 >descr: IRCd Italia >country: IT >prefix: 3FFE:1001:200::/44 >application: ping ping.ipv6.ircd.it >application: irc irc6.ircd.it >application: www www.ipv6.ircd.it >tunnel: IPv6 in IPv4 c7505-v6.ircd.it -> 6bone-gw3.ipv6.cselt.it >CSELT STA >TIC >tunnel: IPv6 in IPv4 c7505-v6.ircd.it -> route.ipv6.tobit.com TOBIT >STATIC >tunnel: IPv6 in IPv4 c7505-v6.ircd.it -> >exchange4-e0.ltn.panservice.it PA >NSERVICE STATIC >tunnel: IPv6 in IPv4 c7505-v6.ircd.it -> rap.viagenie.qc.ca VIAGENIE >STATI >C >contact: MAX1-6BONE >remarks: ipv6-site is operational since March 2000 > Tunnel Broker Available >remarks: This object is automatically converted from the RIPE181 >registry >url: >mnt-by: IRCD-MNT >changed: max@ipng.it 20000321 >changed: max@ipng.it 20000618 >changed: max@ipng.it 20000918 >changed: auto-dbm@whois.6bone.net 20010117 >source: 6BONE > >person: Massimiliano Gargani >address: Edisontel S.p.A. > Foro Buonaparte, 31 > I-20121 MILANO > Italy >phone: +39 02 6222.1 >fax-no: +39 02 6222.8006 >e-mail: max@ipng.it >nic-hdl: MAX1-6BONE >remarks: This object is automatically converted from the RIPE181 >registry >notify: max@ipng.it >changed: max@ipng.it 20000718 >changed: auto-dbm@whois.6bone.net 20010117 >source: 6BONE > >person: Sergio Chiesa >address: Edisontel S.p.A. > Foro Buonaparte, 31 > I-20121 MILANO > Italy >phone: +39 02 6222.1 >fax-no: +39 02 6222.8006 >e-mail: s.chiesa@ipng.it >nic-hdl: SC2-6BONE >remarks: This object is automatically converted from the RIPE181 >registry >changed: s.chiesa@ipng.it 20000717 >changed: auto-dbm@whois.6bone.net 20010117 >source: 6BONE > >person: Andrea Colangelo >address: Edisontel S.p.A. > Foro Buonaparte, 31 > I-20121 MILANO > Italy >phone: +39 02 6222.1 >fax-no: +39 02 6222.8006 >e-mail: a.colangelo@ipng.it >nic-hdl: AC1-6BONE >remarks: This object is automatically converted from the RIPE181 >registry >changed: a.colangelo@ipng.it 20000717 >changed: auto-dbm@whois.6bone.net 20010117 >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. > >I haven't any IPv6 BGP peers because my address is part of CSELT address >space and I can't annouce it to anyone. >Anyway I have severals IPv4 BGP peers. You can check on RIPE database for >AS15589 > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > >Our DNS is ready for AAAA and ip6.int. Is autoritative for >3ffe:1001:200::/44 > >You can check on ns.irc6.org > > 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. > >You can check www.ipv6.ircd.it (IPv6 only). On that site is described all >what I did with IPv6 > >I can't grant the reachbility of the sity because in the last week I've >noticed >a great unstability of CSELT IPv6 network > > 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. > >The our ipv6 staff is composed by: > >Max Gargani (me) MAX1-6bone >Sergio Chiesa SC2-6bone >Andrea Colangelo AC1-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 common e-mail address is ipv6@ipng.it > > 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. > >Edisontel (the company I rappresent in this request) is a Telco and ISP >here in >Italy. >The pTLA will serve all other our peers in Milan Internet Exchange N.A.P. > >At the MIX we have created an IPv6 working group, and because I'm the only >to have at least 3 month on 6Bone, I'm asking for pTLA >All other peers are the major ISP here in Italy: > >At the working group will partecipate Edisontel, Telecom Italia, >Infostrada, >Cable & Wireless Italy, Blixer, I.Net and many others > > 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. > > 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. > >We agree to the present and future 6Bone policies and the pTLA will be >used >only for experimental purpose > > >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>. > >We are already subscribed on the 6bone IPv6 mailing-list > >Regards, > >.. Massimiliano Gargani >.. Access/Network Engineer >.. EdisonTel S.p.A. - Italy > >On Mon, 22 Jan 2001, Bob Fink wrote: > > > Max, > > > > You need to respond to the pTLA request form available from the 6bone home > > page: > > > > > > > > > > I would specifically call your attention to the BGP4+ and the community of > > users requirements. However, please review all questions and answer them as > > asked. > > > > > > Thanks, > > > > Bob > > > > =============================================== > > At 05:24 PM 1/19/2001 +0100, Max Gargani wrote: > > >Hi, > > > > > >I have a v6 lab in Italy connected through CSELT. I have the address space > > >3ffe:1001:200::/44 and I'm experimenting in IPv6 since march 2000. > > > > > >I have several static tunnel around the world, an IPv6 IRC server linked > > >to IRCnet (the largest IRC net in europe), a tunnel broker service for > > >dynamic IP users. Web and FTP (ipv6/ipv4). > > > > > >You can obtain my details quering the 6bone database. > > > > > >My nic-handle is MAX1-6BONE > > >the ipv6-site is IRCD > > > > > >I'm asking to become pTLA. I have severals peering IPv4 in twn italian > > >N.A.P. in Milan and Rome. > > > > > >My DNS is ready for AAAA and ip6.int and is autoritative for prefix > > >3ffe:1001:200::/44 > > > > > >The other 2 person who are working with me at IPv6 development are: > > > > > >Sergio Chiesa (SC2-6BONE) > > >Andrea Colangelo (AC1-6BONE) > > > > > >the common e-mail address is ipv6@ipng.it > > > > > >The pTLA will part of an IPv6 working group to which take parte most of > > >the Milan Internet Exchange peers. > > > > > >I used IRCD as ipv6-site because I start IPv6 experimentation with IRC > > >servers and so I preferred register it for Italian IRC community, but now > > >I request the pTLA as Edisontel S.p.A. (ASn 15589 network: 62.94.0.0/16) > > > > > >I hope this is enough to become pTLA. > > > > > >Let me know. > > > > > >TIA, > > > > > >.. Massimiliano Gargani > > >.. Access/Network Engineer > > >.. EdisonTel S.p.A. - Italy > > > > From fink@es.net Mon Jan 29 17:42:44 2001 From: fink@es.net (Bob Fink) Date: Mon, 29 Jan 2001 09:42:44 -0800 Subject: 6bone pTLA 3FFE:8140::/28 allocated to APAN-JP Message-ID: <5.0.0.25.0.20010129093956.0389a308@imap2.es.net> APAN-JP has been allocated pTLA 3FFE:8140::/28 having finished its 2-week review period with no negative comments. Note that it will take a short while for their inet6num and ipv6-site objects to show up as they have to create them. However, their registration is listed on: Thanks, Bob From pim@bfib.ipng.nl Tue Jan 30 20:08:31 2001 From: pim@bfib.ipng.nl (Pim van Pelt) Date: Tue, 30 Jan 2001 21:08:31 +0100 (CET) Subject: IPv6 related Search Engine Message-ID: <200101302008.f0UK8Ve13615@bfib.ipng.nl> Dear IPv6 folk, The company I work for, WiseGuys Internet BV in the Netherlands, deploys Datamining Software (webagents/spiders/search engine). I have asked their permission to run an IPv6 related search engine at http://www.ipng.nl/ and they have kindly agreed to license me their software. To this end, I have started an index run on 208 websites that I know of and feel are important to the IPv6 community. My goals are to publish a search engine on my website in March 2001. To this end, I'd very much like your cooperation, in two respects. 1. If you know of sites that are interresting (language irrelevant), please let me know about it. Include entrypoint and scope of the website. 2. If you have a website, please ensure you have a robots.txt file in your docroot, to spare your server from my relentless spiders. They will never come anywhere that you Disallow: them to. Guiding robots through your site is a good idea. Check out http://www.wise-guys.nl/webagent_en.html for strict guidelines on robots.txt and meta noindex/nofollow techniques. Needless to say, if you are interrested in running a search engine and are able to define a scope of websites you wish to see indexed, you can contact WiseGuys for details. Regards, Pim -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pvanpelt@wise-guys.nl http://www.wise-guys.nl/ GSM: +31629064049 ----------------------------------------------- From fink@es.net Tue Jan 30 20:47:58 2001 From: fink@es.net (Bob Fink) Date: Tue, 30 Jan 2001 12:47:58 -0800 Subject: 6bone pTLA 3FFE:8150::/28 allocated to SOLNET-CH Message-ID: <5.0.0.25.0.20010130124453.04560ce8@imap2.es.net> SOLNET-CH has been allocated pTLA 3FFE:8150::/28 having finished its 2-week review period with no negative comments. Note that it will take a short while for their inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: Thanks, Bob From Jae.Lee@intelsat.int Tue Jan 30 20:40:16 2001 From: Jae.Lee@intelsat.int (Jae.Lee@intelsat.int) Date: Tue, 30 Jan 2001 15:40:16 -0500 Subject: /etc/hosts8 ? Message-ID: <490B4C213EC8D211851F00105A29CA5A07A1F99C@admex1.adm.intelsat.int> Greetings everyone. I am wondering if there is a /etc/hosts (/etc/inet/hosts) equivalent file in Solaris8 for IPv6 hosts. I am getting tired of typing in IPv6 addresses, not to mention my memory fails every time. :( Thanks. - Jae p.s. I am not really eager to start my own DNS server, but if a kind soul can provide me a sequence of steps to follow to start up the DNS on Sol8, I am more than willing to give it a try. From Bertil Lindblad Tue Jan 30 21:49:46 2001 From: Bertil Lindblad (Bertil Lindblad) Date: Tue, 30 Jan 2001 22:49:46 +0100 (CET) Subject: /etc/hosts8 ? In-Reply-To: "Your message with ID" <490B4C213EC8D211851F00105A29CA5A07A1F99C@admex1.adm.intelsat.int> Message-ID: The answer is in "man ipnodes" Further, see http://docs.sun.com, Solaris 8 sysadmin collection, System admin guide vol 3 (which is all networking, and quite thick ;-) HTH Regards, Bertil Lindblad > Greetings everyone. > I am wondering if there is a /etc/hosts (/etc/inet/hosts) equivalent file > in Solaris8 for IPv6 hosts. > I am getting tired of typing in IPv6 addresses, not to mention my memory > fails every time. :( > Thanks. > > - Jae > > p.s. I am not really eager to start my own DNS server, but if a kind soul > can provide me a sequence of steps to follow to start up the DNS on Sol8, I > am more than willing to give it a try. ------ Bertil Lindblad Senior SE datacomms Sun Microsystems AB or Box 51, S-164 94 KISTA, Sweden Phone +46-8-631 1256 Fax +46-8-631 10 05 From Alan@halachmi.net Tue Jan 30 22:33:02 2001 From: Alan@halachmi.net (Alan Halachmi) Date: Tue, 30 Jan 2001 17:33:02 -0500 (EST) Subject: /etc/hosts8 ? In-Reply-To: <490B4C213EC8D211851F00105A29CA5A07A1F99C@admex1.adm.intelsat.int> Message-ID: Jae.Le>I am wondering if there is a /etc/hosts (/etc/inet/hosts) Jae.Le>equivalent file in Solaris8 for IPv6 hosts. I am getting Jae.Le>tired of typing in IPv6 addresses, not to mention my memory Jae.Le>fails every time. :( Thanks. I think it is called `ipnodes` in either /etc/ or /etc/inet/ Best, Alan -- Alan Halachmi Wide Area Network Specialist Ingram Entertainment Network Services mailto:alan@halachmi.net http://www.ingramentertainment.com From BMcNamara@zama.net Wed Jan 31 00:41:03 2001 From: BMcNamara@zama.net (Bradley W. McNamara) Date: Tue, 30 Jan 2001 16:41:03 -0800 Subject: /etc/hosts8 ? References: <490B4C213EC8D211851F00105A29CA5A07A1F99C@admex1.adm.intelsat.int> Message-ID: <3A775F1F.7FBA5127@zama.net> Try '/etc/inet/ipnodes'. Brad McNamara ZAMA Networks, Inc. http://www.zama.net http://www.zama6.net Jae.Lee@intelsat.int wrote: > Greetings everyone. > I am wondering if there is a /etc/hosts (/etc/inet/hosts) equivalent file > in Solaris8 for IPv6 hosts. > I am getting tired of typing in IPv6 addresses, not to mention my memory > fails every time. :( > Thanks. > > - Jae > > p.s. I am not really eager to start my own DNS server, but if a kind soul > can provide me a sequence of steps to follow to start up the DNS on Sol8, I > am more than willing to give it a try. From Francis.Dupont@enst-bretagne.fr Wed Jan 31 10:51:25 2001 From: Francis.Dupont@enst-bretagne.fr (Francis Dupont) Date: Wed, 31 Jan 2001 11:51:25 +0100 Subject: IPv6 Router solicitation in Address Autoconfiguration In-Reply-To: Your message of Mon, 29 Jan 2001 14:57:01 +1100. <33FDD994A379D411B13A0004AC4C81A102C28EAD@email3> Message-ID: <200101311051.f0VApPO60585@givry.rennes.enst-bretagne.fr> In your previous mail you wrote: My question is why does the host send a multicast address rather than an anycast address, requesting for router solicitation? => because the host wants an answer from every routers, not from any router. The idea is to be able to get all parameters and to choice the "best" default router. Regards Francis.Dupont@enst-bretagne.fr From fink@es.net Wed Jan 31 16:00:15 2001 From: fink@es.net (Bob Fink) Date: Wed, 31 Jan 2001 08:00:15 -0800 Subject: pTLA request for LavaNet - review closes 14 Feb 01 Message-ID: <5.0.0.25.0.20010131075739.00a852c0@imap2.es.net> 6bone Folk, LavaNet has requested a pTLA allocation. The open review period for this will close 14 Feb 2001. Please send any comments to me or the list. Thanks, Bob ============================================ >Date: Tue, 30 Jan 2001 13:14:40 -1000 (HST) >From: Antonio Querubin >To: >Subject: pTLA request for LavaNet > >Bob, > >LavaNet is applying for a pTLA. Here are our responses to the RFC-2772 >section 7 requirements. Could you review it and let us know what else >needs to be addressed or whether we need to expand on any points before >final submission? Thanks. > >Antonio Querubin >LavaNet System Staff > >-- > From 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: > >LavaNet established it's first 6Bone tunnel in April 2000. It was >reestablished in October 2000 and it has been in continuous operation >since. > > 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. > >The following objects are currently registered in the 6Bone Registry: > LAVANET > LAVANET-SYSTEM-STAFF > AQ7 > JC273 > 3FFE:2900:D00A::/48 > > 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. > >Our router is currently a Linux system running zebra. It's address is >6bone.lava.net and it peers with Sprint over a tunnel. Our goal is to >peer directly with our upstreams on our border cisco routers when IOS 12.2 >reaches maturity. > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > >Our IPv6-enabled nameservers are: > ns1.ipv6.lava.net > ns2.ipv6.lava.net > >A query for PTR records in 0.0.0.0.a.0.0.d.0.0.9.2.e.f.f.3.ip6.int at the >above nameservers will reveal a number of IPv6 hosts. > > 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. > >This will eventually be www.ipv6.lava.net. We hope to have some pertinent >IPv6 pages on it by next week. > > 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. > >These would be: > Antonio Querubin (AQ7) > Julian Cowley (JC273) > Robert Brewer (?) > > 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. > >Our system support staff mailbox is system@lava.net (LAVANET-SYSTEM-STAFF). > > 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. > >LavaNet is the largest locally-owned ISP in the state of Hawaii serving >approximately 11000 customers throughout the major Hawaiian islands and >Johnston Island. We have network connections with Genuity and UUNet (next >month we'll add Sprint) and are doing full BGP peering with them. We also >do regional peering with other Hawaii-based networks at the Hawaii >Internet Exchange (HIX). > > 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 do. -end From ipver6@hotmail.com Wed Jan 31 16:16:22 2001 From: ipver6@hotmail.com (Clifford Magnan) Date: Wed, 31 Jan 2001 11:16:22 -0500 Subject: connecting to 6Bone Message-ID: Hello all IPV6 goers, Can any body give me a lead towards the steps of connecting to the 6Bone? Thanking everybody in advance. Regards, Cliff _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com From fink@es.net Wed Jan 31 19:00:44 2001 From: fink@es.net (Bob Fink) Date: Wed, 31 Jan 2001 11:00:44 -0800 Subject: connecting to 6Bone In-Reply-To: Message-ID: <5.0.0.25.0.20010131105935.02539de0@imap2.es.net> Clifford, At 11:16 AM 1/31/2001 -0500, Clifford Magnan wrote: >Hello all IPV6 goers, > >Can any body give me a lead towards the steps of connecting to the 6Bone? >Thanking everybody in advance. Use the how to join pages: If something makes no sense, please ask me. Thanks, Bob From LarryH@milarnet.com Wed Jan 31 21:12:04 2001 From: LarryH@milarnet.com (Larry D. Hutchison) Date: Wed, 31 Jan 2001 14:12:04 -0700 Subject: connecting to 6Bone Message-ID: http://www.freenet6.net/en/createTunnel.html Regards: Larry Hutchison mailto:LarryH@milarnet.com -----Original Message----- From: Clifford Magnan [mailto:ipver6@hotmail.com] Sent: Wednesday, January 31, 2001 9:16 AM To: 6bone@ISI.EDU Subject: connecting to 6Bone Hello all IPV6 goers, Can any body give me a lead towards the steps of connecting to the 6Bone? Thanking everybody in advance. Regards, Cliff _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com From Joe.Eggleston" Hi all, I am trying to set up our site to meet all the requirements for requesting a pTLA. I think I have everything configured, but I was wondering if someone could try hitting our site to see if everything looks good externally as well. My IPv6 domain is ipv6.motlabs.com. The router that is handling the tunnel is i2router.ipv6.motlabs.com. There's a web server at www.ipv6.motlabs.com and DNS is at dns1.ipv6.motlabs.com. Our 6bone database entries are under MOTOROLA-LABS. thanks! Joe 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: 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. see MOTOROLA-LABS 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're using BGP4+ and our router is at i2router.ipv6.motlabs.com c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) entries for the Applicant's router(s) and at least one host system. I think DNS forward and reverse is working. 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. www.ipv6.motlabs.com 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 an OC-3c link to the Chicago NAP. support staff: JEE1-6BONE, JTE1-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. 6bone@labs.mot.com 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. User community is mainly Motorola. 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. 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>. From LarryH@milarnet.com Wed Jan 31 22:46:13 2001 From: LarryH@milarnet.com (Larry D. Hutchison) Date: Wed, 31 Jan 2001 15:46:13 -0700 Subject: Getting IPv6 pointers to my Domain Message-ID: This is a multi-part message in MIME format. ------_=_NextPart_001_01C08BD7.9D166436 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all: Just wondering how to go about getting pointers or AAAA Records for my domain. Thanks in advance... Regards: Larry Hutchison mailto:LarryH@milarnet.com ------_=_NextPart_001_01C08BD7.9D166436 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 eJ8+Ig8WAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAIwAAAEdldHRpbmcgSVB2NiBwb2lu dGVycyB0byBteSBEb21haW4ATAwBBYADAA4AAADRBwEAHwAPAC4ADQADAEUBASCAAwAOAAAA0QcB AB8ADwAuAA0AAwBFAQEJgAEAIQAAAERBQkJEN0U1RkE1MTY4NDZCN0E4ODkxMkVGNEJBQTE0AHEH AQOQBgCQBgAAMAAAAAsAAgABAAAAAwAmAAAAAAADADYAAAAAAEAAOQA2ZBad14vAAR4APQABAAAA AQAAAAAAAAACAUcAAQAAADUAAABjPXVzO2E9IDtwPU1JTEFSTmV0d29ya3M7bD1CRUxHQVJJT04t MDEwMTMxMjI0NjEzWi0yAAAAAB4AcAABAAAAIwAAAEdldHRpbmcgSVB2NiBwb2ludGVycyB0byBt eSBEb21haW4AAAIBcQABAAAAFgAAAAHAi9edD/I61vlULkdMnOhrtsY6OdwAAB4AGgwBAAAAEwAA AExhcnJ5IEQuIEh1dGNoaXNvbgAAHgAdDgEAAAAjAAAAR2V0dGluZyBJUHY2IHBvaW50ZXJzIHRv IG15IERvbWFpbgAAAgEJEAEAAAAwAQAALAEAAKcBAABMWkZ1uL5hdgMACgByY3BnMTI1FjIA+Atg bg4QMDMzTwH3AqQD4wIAY2gKwHOgZXQwIFYEkGQAcH5hAoMAUANUEMkHbQKAfSUKgXYIkHdrC4Bk NB0MYGMAUAsDC7QyIEiUZWwJACAHQGw6CqKjCoQKgEp1cwVAdwIgQwSBC4BnIGhvB+B0rRagZxah BuB1BUBnETDSdBhycG8LgHQEkAQg3QWxQRrxB/AFkmQEIAIQYQXAbXkgZANxC4Au5iATUBDwbmsE IAuAFrDEZHYAcGNlLh3QFwr3CvQMMBIicw4gFwUWExtAWmcLEXMW9h9+TArAcv0cEEgZgBDgBAAC IBcEHFGKbBjwOiJjSEBtAxDVCsBuETAuBaBtHg8KIC8C0QFAFxMUcQAnYB4ANRABAAAAQAAAADxC N0I5NTk1Mjg0ODQ2MzRGQTVDMERGQkU2RkFCOEUzNDAxOUUzQUBiZWxnYXJpb24ubWlsYXJuZXQu Y29tPgADAIAQ/////x8A8xABAAAATgAAAEcAZQB0AHQAaQBuAGcAIABJAFAAdgA2ACAAcABvAGkA bgB0AGUAcgBzACAAdABvACAAbQB5ACAARABvAG0AYQBpAG4ALgBFAE0ATAAAAAAACwD2EAAAAABA AAcwvIYlfNeLwAFAAAgwujsundeLwAEDAN4/r28AAAMA8T8JBAAAHgD4PwEAAAATAAAATGFycnkg RC4gSHV0Y2hpc29uAAACAfk/AQAAAF8AAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAAL089 TUlMQVJORVRXT1JLUy9PVT1GSVJTVCBBRE1JTklTVFJBVElWRSBHUk9VUC9DTj1SRUNJUElFTlRT L0NOPUxIAAAeAPo/AQAAABUAAABTeXN0ZW0gQWRtaW5pc3RyYXRvcgAAAAACAfs/AQAAAB4AAAAA AAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAALgAAAAMA/T/kBAAAAwAZQAAAAAADABpAAAAAAB4A MEABAAAAAwAAAExIAAAeADFAAQAAAAMAAABMSAAAHgA4QAEAAAADAAAATEgAAB4AOUABAAAAAgAA AC4AAAADAAlZAwAAAAsAZoEIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAAAwB+gQggBgAAAAAA wAAAAAAAAEYAAAAAUoUAAD9xAQAeAH+BCCAGAAAAAADAAAAAAAAARgAAAABUhQAAAQAAAAQAAAA5 LjAAAwDCgQggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAMeBCCAGAAAAAADAAAAAAAAARgAA AAADhQAAAAAAAAMAzIEIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwDRgQggBgAAAAAAwAAA AAAAAEYAAAAAEIUAAAAAAAADANiBCCAGAAAAAADAAAAAAAAARgAAAAAYhQAAAAAAAAsA6IEIIAYA AAAAAMAAAAAAAABGAAAAAAaFAAAAAAAACwApAAAAAAALACMAAAAAAAMABhDFVPyGAwAHEIcAAAAD ABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAASEVMTE9BTEw6SlVTVFdPTkRFUklOR0hPV1RPR09B Qk9VVEdFVFRJTkdQT0lOVEVSU09SQUFBQVJFQ09SRFNGT1JNWURPTUFJTlRIQU5LU0lOQURWQU5D RVJFR0FSRFM6TEFSUgAAAAACAX8AAQAAAEAAAAA8QjdCOTU5NTI4NDg0NjM0RkE1QzBERkJFNkZB QjhFMzQwMTlFM0FAYmVsZ2FyaW9uLm1pbGFybmV0LmNvbT4AeVs= ------_=_NextPart_001_01C08BD7.9D166436-- From tony@lava.net Wed Jan 31 23:44:33 2001 From: tony@lava.net (Antonio Querubin) Date: Wed, 31 Jan 2001 13:44:33 -1000 (HST) Subject: pTLA qualifications In-Reply-To: <3A788CC5.35DD1A3E@labs.mot.com> Message-ID: On Wed, 31 Jan 2001, Joseph E Eggleston wrote: > I am trying to set up our site to meet all the requirements for > requesting a pTLA. I think I have everything configured, but I was > wondering if someone could try hitting our site to see if everything > looks good externally as well. > > My IPv6 domain is ipv6.motlabs.com. The router that is handling the > tunnel is i2router.ipv6.motlabs.com. There's a web server at > www.ipv6.motlabs.com and DNS is at dns1.ipv6.motlabs.com. Our 6bone > database entries are under MOTOROLA-LABS. They're all reachable from here: $ traceroute6 -n i2router.ipv6.motlabs.com traceroute to i2router.ipv6.motlabs.com (3ffe:b00:4025::), 30 hops max, 12 byte packets 1 3ffe:2900:d:a::2 2.547 ms 6.828 ms 7.325 ms 2 3ffe:2900:d:a::1 140.319 ms * 138.48 ms 3 3ffe:b00:c18::e 602.571 ms 607.059 ms 602.783 ms 4 3ffe:b00:4025:: 689.271 ms 692.067 ms 693.559 ms $ traceroute6 -n ipv6.motlabs.com traceroute to ipv6.motlabs.com (3ffe:b00:4025::c), 30 hops max, 12 byte packets 1 3ffe:2900:d:a::2 2.459 ms 2.689 ms 7.003 ms 2 3ffe:2900:d:a::1 137.436 ms * 137.322 ms 3 3ffe:b00:c18::e 627.117 ms 603.002 ms 600.613 ms 4 3ffe:b00:c18::57 685.056 ms 700.387 ms 696.909 ms 5 3ffe:b00:4025::c 760.957 ms 710.317 ms * $ traceroute6 -n www.ipv6.motlabs.com traceroute to www.ipv6.motlabs.com (3ffe:b00:4025::c), 30 hops max, 12 byte packets 1 3ffe:2900:d:a::2 5.929 ms 4.305 ms 3.208 ms 2 3ffe:2900:d:a::1 147.605 ms * 138.826 ms 3 3ffe:b00:c18::e 617.854 ms 617.287 ms 601.08 ms 4 3ffe:b00:c18::57 684.076 ms 687.202 ms 691.625 ms 5 3ffe:b00:4025::c 689.454 ms 696.799 ms 687.057 ms $ traceroute6 -n dns1.ipv6.motlabs.com traceroute to dns1.ipv6.motlabs.com (3ffe:b00:4025::a), 30 hops max, 12 byte packets 1 3ffe:2900:d:a::2 6.041 ms 2.206 ms 5.433 ms 2 3ffe:2900:d:a::1 146.159 ms * 138.142 ms 3 3ffe:b00:c18::e 602.898 ms 608.258 ms 613.11 ms 4 3ffe:b00:c18::57 734.132 ms 694.415 ms 690.847 ms 5 3ffe:b00:4025::a 694.506 ms 686.927 ms 686.01 ms $ telnet 3FFE:B00:4025:0:0:0:0:C 80 Trying 3ffe:b00:4025::c... Connected to 3FFE:B00:4025:0:0:0:0:C. Escape character is '^]'. quit 501 Method Not Implemented

Method Not Implemented

quit to /index.html not supported.

Invalid method in request quit

Apache/1.3.14 Server at www.ipv6.motlabs.com Port 80
Connection closed by foreign host. From LarryH@milarnet.com Wed Jan 31 23:50:18 2001 From: LarryH@milarnet.com (Larry D. Hutchison) Date: Wed, 31 Jan 2001 16:50:18 -0700 Subject: Getting IPv6 pointers to my Domain Message-ID: Yes, but who at vigianie do I talk to about being an authority. Like Network Solutions for my IPv4 host? Is there an authority to use for obtaining these? Regards: Larry Hutchison mailto:LarryH@milarnet.com -----Original Message----- From: Todd T. Fries [mailto:todd@fries.net] Sent: Wednesday, January 31, 2001 4:17 PM To: Larry D. Hutchison Cc: 6BONE List (E-mail) Subject: Re: Getting IPv6 pointers to my Domain aaaa records are like any other delegation zone. Whoever is authority for the zone above you can delegate to you. Aka I have: 3ffe:b00:4004::/48 The upstream authority is vigianie, who delegates to me, and thus they have in their zone file: $ORIGIN 0.0.4.0.0.b.0.e.f.f.3.ip6.int. 4 IN NS ns0.fries.net. IN NS ns1.fries.net. And then I have a zone file '4.0.0.4.0.0.b.0.e.f.f.3.ip6.int' .. inside of which I then record the aaaa reverse delegation for all of my hosts. Hope this helps... Penned by Larry D. Hutchison on Wed, Jan 31, 2001 at 03:46:13PM -0700, we have: | Hello all: | | Just wondering how to go about getting pointers or AAAA Records for my | domain. Thanks in advance... | | | Regards: | | Larry Hutchison | mailto:LarryH@milarnet.com | | -- Todd Fries .. todd@fries.net