From ville@stealth.net Thu Nov 1 08:50:21 2001 From: ville@stealth.net (Ville) Date: Thu, 1 Nov 2001 03:50:21 -0500 (EST) Subject: Looking for BGP peers In-Reply-To: Message-ID: On Wed, 31 Oct 2001, Pekka Savola wrote: > On Wed, 31 Oct 2001, Michel Py wrote: > Sure, but you don't _need_ to ask on 6bone list -- you could just send an > email or knock your neighbour's door. Pekka, perhaps it's simply time for you to face it - 6bone@ is a high-traffic list. There is no need for you to begin individually judging which of the requests you see sane and which not. They may make perfect sense to others. After all, 6BONE clearly _is_ a testbed for the deployment of IPv6 and that's making no restrictions towards the aim of gaining operational experience before really going final. I could only be delighted to see people have so different goals as to what they are looking for and how they are wishing to achieve it. > Pekka Savola "Tell me of difficulties surmounted, Chill, -- Ville Network Security/IPv6 Solutions Stealth Communications, Inc. From jfleming@anet.com Thu Nov 1 13:14:27 2001 From: jfleming@anet.com (Jim Fleming) Date: Thu, 1 Nov 2001 07:14:27 -0600 Subject: Looking for BGP peers References: Message-ID: <005201c162d7$236e33c0$3e00a8c0@pamela> ----- Original Message ----- From: "Ville" > perhaps it's simply time for you to face it - 6bone@ is a high-traffic > list. There is no need for you to begin individually judging which of > the requests you see sane and which not. They may make perfect sense > to others. > "high-traffic" ? Do you use a 2002::0000 prefix ? http://www.dot-arizona.com/IPv8/IPv4/ http://www.ietf.org/mail-archive/ietf/Current/msg12213.html JimFleming@Unir.com http://www.unir.com http://www.unir.com/images/architech.gif http://www.unir.com/images/headers.gif http://www.unir.com/images/address.gif http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp http://www.ietf.org/mail-archive/ietf/Current/msg12213.html http://www.ietf.org/mail-archive/ietf/Current/msg12223.html From jeroen@unfix.org Thu Nov 1 17:52:46 2001 From: jeroen@unfix.org (Jeroen Massar) Date: Thu, 1 Nov 2001 18:52:46 +0100 Subject: Looking for BGP peers In-Reply-To: <005201c162d7$236e33c0$3e00a8c0@pamela> Message-ID: <002c01c162fe$041a1d00$420d640a@HELL> Jim Fleming wrote: > ----- Original Message ----- > From: "Ville" > > perhaps it's simply time for you to face it - 6bone@ is a high-traffic > > list. There is no need for you to begin individually judging which of > > the requests you see sane and which not. They may make perfect sense > > to others. > > > > "high-traffic" ? Wellps... is that all the 'constructive' and '6bone-related' content of that message? Your 'signature' brings more 6bone-unrelated traffic than the body.... > Do you use a 2002::0000 prefix ? Oh boy... not here too.... let's point Mr. Jim Fla^Heming into the right directions so maybe he can read up and learn from those so he actually knows what he's talking about... http://www.daemonnews.org/200101/6to4.html - 6to4 IPv6 Explained, or: Flogging a Dead Horse http://www.6bone.net/6bone_6to4.html - 6Bone 6to4 Information http://www.ieng.com/warp/public/759/ipj_3-1/ipj_3-1_routing.html - Connecting IPv6 Routing Domains Over the IPv4 Internet http://www.join.uni-muenster.de/JOIN/ipv6/rfc/rfc2373.txt - RFC 2373: IP Version 6 Addressing Architecture http://www.join.uni-muenster.de/JOIN/ipv6/rfc/rfc2374.txt - RFC 2374: An IPv6 Aggregatable Global Unicast Address Format Jups Mr. Fla^Heming those are RFC's... as in REQUEST FOR COMMENTS... *official* stuff... and stuff that WORKS and is implemented... Not some vague idea tearing apart something people actually use on a day by day basis... Now read up.... and stop bashing your stupid IPv8/16/* whatever ideas here too... I think you don't want to banned here too now do you? Check http://www1.ietf.org/mail-archive/ietf/Current/msg14158.html: 8<---------------------------------------------------------------------- --------------------------------- After having read the 4 messages that Jim Fleming sent to the list after having received my warning note, I have revoked Jim Fleming's posting privilleges to the IETF list. This revocation will remain in effect for the next month. Harald T. Alvestrand IETF Chair ------------------------------------------------------------------------ ------------------------------>8 And they are quite nice you know... the only revoked it for a month... hope you grow up in the mean time. Maybe it's a nice chance to read some stuff so you can act like a grown up and discuss things like any other normal being... with actually knowing what you are talking about... Greets, Jeroen PS: For the rest of your IPv8/IPv16 "ideas" why not start a nice mailinglist (ipv8@unir.com ?) and announce that once somewhere... that certainly won't make you step on everybodies toes... and interrested people will actually join it.... but it won't bother other people either... From jfleming@anet.com Thu Nov 1 18:45:45 2001 From: jfleming@anet.com (Jeroen Massar) Date: Thu, 1 Nov 2001 19:45:45 +0100 Subject: Looking for BGP peers In-Reply-To: <019a01c16300$4f2ec6e0$3e00a8c0@pamela> Message-ID: <002d01c16305$6b1c5610$420d640a@HELL> Jim Fleming [mailto:jfleming@anet.com] wrote: > From: "Jeroen Massar" > > > > > Do you use a 2002::0000 prefix ? > > > > > It all boils down to fairness. > > Which list do you think is more fair ? > > The "toy" IPv4 Internet Early Experimentation Allocations ? > http://www.iana.org/assignments/ipv4-address-space > or > The Proof-of-Concept IPv8 Allocations ? > http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt You asked which "list" ... those things you mentioned are URL's.... and 'fair' all depends on point of view.... Is it 'fair' for all the subscribers of all those lists you spam to try and push your 'IPv8' idea down everybodies throat? And IPv4 isn't a toy.... it's USED by MILLIONS of people on a day by day basis.... and IPv6 is also catching on in user count... Has your 'IPv8' got _any_ users whatsoever ??? Is there an implementation? > Why would people pay for Address Space, when it is FREE ? I never have payed for "Addresss Space" in all those years I have been using the internet... being it IPv4 and/or IPv6... I do pay for stuff like a phonenumber on my cell phone... Big companies do have to pay for the management of the IP space but hey... somebody has to do that... and have you got any idea how expensive a good working backup solution and maintainance staff is for something as crucial as the internet for some businesses... That 'free' entitity which is going to 'manage' (I sincerely hope some entity is going to manage your IPv8 space) is surely going to ask money for your IPv8 space management... You prolly don't want to hear your bank say that they can't recall having your money on account 2242424241 or something now do you? And yes indeed you have to pay for that management (banks simply invest your money and get revenue out of that) Oh by the way... I don't use the 6to4 range (2002::/16) simply because I got my own *free* IPv6 /60 :) Maybe you should try www.freenet6.net which give you a /48 FOR FREE (unless you start counting your ISP and electrical bills and stuff) Nothing is *FREE* in this world.... now go grow a brain... Greets, Jeroen PS: Jim, I set the reply-to to your own email so you can converse the rest of your stupendous mailings with yourself... the 6bone@isi.edu (bcc'd so it will go away too on reply) is a mailinglist for 6bone content _not_ for fle^Hame wars about 'IPv8' or other delusions... From jfleming@anet.com Thu Nov 1 19:25:18 2001 From: jfleming@anet.com (Jeroen Massar) Date: Thu, 1 Nov 2001 20:25:18 +0100 Subject: Looking for BGP peers In-Reply-To: <01f101c16309$11286500$3e00a8c0@pamela> Message-ID: <003401c1630a$f0cb1b70$420d640a@HELL> > -----Original Message----- > From: Jim Fleming [mailto:jfleming@anet.com] Hi Jim.... Please tell me what has all this to do with the 6bone? If it has nothing Also are you afraid to answer any questions which are put in front of you or do you really don't know any answers? Maybe you should, like most beginners be directed to for instance www.google.com where you can find many of the answers you are trying to seek. And otherwise go setup your own list and go talk to yourself or something... have fun at it... don't bother the 6bone community with your nonsense... > ----- Original Message ----- > From: "Jeroen Massar" > > > > That 'free' entitity which is going to 'manage' (I sincerely hope some > > entity is going to manage your IPv8 space) is surely going to ask money > > for your IPv8 space management... > > > IPv8 Address Space Managers (ASMs) can do as they please. > They obtain their FREE allocations via their ownership of IN-ADDR.[TLD] names. You mean like the .tv tld which simply ask $100.000++ for a single stupid ascii name.... ah great... now I truly understand what you mean :) And you are going to govern which of those TLD's to become filty rich ? Stupid me... I thought you really wanted *free* stuff... > Are you familiar with the way IN-ADDR.ARPA works ? Yes I am familiar with the way in-addr.arpa works... are you? Just too enlighten you a bit: IN-ADDR.ARPA is a DNS (Domain Name System) zone.... it's used by millions of people... even though they don't know it. in the IPv6 world we use ip6.int (for PTR) and maybe soon after the debates are over we might even shift to ip6.arpa See http://www.crt.se/dnssec/bind9/Bv9ARM.ch04.html#AEN1036 and ofcourse RFC 1034 amongst others... IN-ADDR.ARPA has subzones which get delegated from the LIR's and RIR's to the delegates so they can manage those spaces... In the IPv6 world the same happens... Does that answer your question? If not I recommend you some of the great O'Reilly books which can amongst others be bought (yup they are not free) at amazon.com. Check out: http://www.oreilly.com/catalog/tcp2/ (TCP/IP Network Administration, 2nd Edition) and http://www.oreilly.com/catalog/coreprot/ (Internet Core Protocols: The Definitive Guide) And many of their other fine books... Greets, Jeroen PS: Jim, I set the reply-to to your own email so you can converse the rest of your stupendous mailings with yourself... the 6bone@isi.edu (bcc'd so it will go away too on reply) is a mailinglist for 6bone content _not_ for fle^Hame wars about 'IPv8' or other delusions... From fink@es.net Fri Nov 2 01:10:43 2001 From: fink@es.net (Bob Fink) Date: Thu, 01 Nov 2001 17:10:43 -0800 Subject: pTLA request for INTERNET-MULTIFEED (www.v6.mfeed.ad.jp) - review closes 15 November 2001 Message-ID: <5.1.0.14.0.20011101170752.02d97398@imap2.es.net> 6bone Folk, INTERNET-MULTIFEED (www.v6.mfeed.ad.jp) has requested a pTLA allocation. The open review period for this will close 15 November 2001. Please send your comments to me or the list. Thanks, Bob === >Date: Fri, 02 Nov 2001 09:38:14 +0900 >From: "Ishii, Toshinori" >To: Bob Fink >Subject: pTLA request for INTERNET-MULTIFEED >Cc: ipv6-exp@mfeed.ad.jp > >Dear Bob, > >This is Toshinori Ishii working for Internet Multifeed Co. >We'd like to request pTLA of 6Bone. Please allocate 6Bone pTLA address space. > >Thank you. > >------------------------------------ >7. Guidelines for 6Bone pTLA sites > > The following rules apply to qualify for a 6Bone pTLA allocation. It > should be recognized that holders of 6Bone pTLA allocations are > expected to provide production quality backbone network services for > the 6Bone. > > 1. The pTLA Applicant must have a minimum of three (3) months > qualifying experience as a 6Bone end-site or pNLA transit. During > the entire qualifying period the Applicant must be operationally > providing the following: > >We have about two years experience as a 6Bone end-site. > > a. Fully maintained, up to date, 6Bone Registry entries for their > ipv6-site inet6num, mntner, and person objects, including each > tunnel that the Applicant has. > >ipv6-site: INTERNET-MULTIFEED >inet6num: 3FFE:1801:2010::/48 >mntner: MFEED-MNT >person: Nobuhisa Miyake >person: Kunihiro Sizuku >person: Toshinori Ishii > > 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. > >NATIVE IPv6 BGP4+ link to NTT-ECL. >ping ote-gate6.v6.mfeed.ad.jp > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > >host: ns.v6.mfeed.ad.jp >router: ote-gate6.v6.mfeed.ad.jp > >$ host -t aaaa ns.v6.mfeed.ad.jp >ns.v6.mfeed.ad.jp. has AAAA address 3ffe:1801:2010:201::53 > >$ host -n 3ffe:1801:2010:201::53 >3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.2.0.0.1.0.2.1.0.8.1.e.f.f.3.ip6.int. >domain name pointer ns.v6.mfeed.ad.jp. > >$ host -t aaaa ote-gate6.v6.mfeed.ad.jp >ote-gate6.v6.mfeed.ad.jp. has AAAA address 3ffe:1801:2010:2::d2ad:a044 > >$ host -n 3ffe:1801:2010:2::d2ad:a044 >4.4.0.a.d.a.2.d.0.0.0.0.0.0.0.0.2.0.0.0.0.1.0.2.1.0.8.1.e.f.f.3.ip6.int. >domain name pointer ote-gate6.v6.mfeed.ad.jp. > > 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. > >http://www.v6.mfeed.ad.jp/ > > 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. > >There are three person object in our network. > >admin-c: NM2-6BONE >tech-c: KS4-6BONE >tech-c: TI2-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. > >notify: tech-c@mfeed.ad.jp > > 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. > >Internet Multifeed Co. links the content servers of Internet Content >Providers directly to the high-speed backbones of many major Internet >Service Providers serving millions of end users. It also provides the >means for fast delivery of rich content on the IPv6 Internet. > > 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. > >Yes, we commit and agree the rules. > > >-- >ishii @ mfeed.ad.jp From fink@es.net Fri Nov 2 14:14:29 2001 From: fink@es.net (Bob Fink) Date: Fri, 02 Nov 2001 06:14:29 -0800 Subject: pTLA request for WEBONLINE-NET (www.webonline.no) - review closes 15 November 2001 Message-ID: <5.1.0.14.0.20011102061123.039e52e8@imap2.es.net> 6bone Folk, WEBONLINE-NET (www.webonline.no) has requested a pTLA allocation. The open review period for this will close 16 November 2001. Please send your comments to me or the list. Thanks, Bob === >From: Jørgen Hovland >To: "Bob Fink" >Subject: pTLA request (WO) >Date: Fri, 2 Nov 2001 13:27:53 +0100 > >Hi > > > >I think everything is right this time. > > > >Sincerly, > >Joergen Hovland > >WebOnline AS > >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: > >WebOnline is an isp/asp in Norway. > >We have a 6bonelink through td.org.uit.no/ Roger Jørgensen since he got it >in November last year from Toledo. IP-prefix is 3ffe:1ce3:12:a::/64 > > >Also a 2 prefixes from Hot-web in Germany ( 2001:740:102:a::/64 and >2001:740:102:b::/80) > > >Just for the record: >traceroute to www.6bone.net (3ffe:b00:c18:1::10) >1 ipv6-gw.webonline.no (2001:740:102:a::0) 0.419 ms 0.309 ms 0.318 ms >2 3ffe:1ce3:12::2:1 (3ffe:1ce3:12::2:1) 23.133 ms 22.927 ms 23.329 ms >3 server.pasta.cs.uit.no (3ffe:2a00:100:3001::2) 249.963 ms 256.741 ms >251.527 ms > > > 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 dont have any inet6num cause they are owned by the somebody else. > >ipv6-site: WEBONLINE-NET >origin: AS16186 >descr: WebOnline AS >location: Drammen >country: NO >prefix: 3FFE:1CE3:12:A::/64 >prefix: 2001:740:102:A::/64 >prefix: 2001:740:102:B::/80 >tunnel: IPv6 in IPv4 webonline.no -> chello.no CHELLO-MNT BGP4+ >tunnel: IPv6 in IPv4 webonline.no -> uit.no JAMESB BGP4+ >tunnel: IPv6 in IPv4 webonline.no -> hot-web.net JF7286-RIPE BGP4+ >contact: JH >remarks: Mail jorgen@ssc.net for any questions or peering requests >remarks: We do not announce any prefixes yet >url: http://www.webonline.no >notify: noc@webonline.no > mnt-by: WEBONLINE > changed: jorgen@ssc.net 20011102 >source: 6BONE > >person: Joergen Hovland >address: Nedre storgate 10 >phone: +47 98456333 >e-mail: ipv6@hovland.cx >nic-hdl: JH >mnt-by: WEBONLINE >changed: jorgen@ssc.net 20010921 >source: 6BONE > >mntner: WEBONLINE >descr: WebOnline AS >admin-c: JH >upd-to: hostmaster@webonline.no >auth: CRYPT-PW * >mnt-by: WEBONLINE >changed: jorgen@ssc.net 20011030 >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. > > > >Linux bgp+ has been running almost since last year I think. >Bgp4+ on the cisco's was newly implemented because the non-beta ios is kinda >new. > >We have 1 ipv6 peer: Chello broadband (also ipv4) > >Native peering in Norway will come when the ix is ready. > >The 2 other's are default routes ( 2000::/3) > >We do not announce anything because we dont have anything to announce yet. > >#sh bgp ipv6 >BGP table version is 18, local router ID is 10.0.3.2 >Status codes: s suppressed, d damped, h history, * valid, > best, i - >internal >Origin codes: i - IGP, e - EGP, ? - incomplete > > Network Next Hop Metric LocPrf Weight Path >*>i2000::/3 2001:740:102:A::F > 100 0 65001 i >*> 2001:730::/35 2001:730:3::1:C 0 6830 i >*> 2001:740:102:A::/64 > :: 32768 i >*>i2001:740:102:C::/64 > 2001:740:102:A::F > 100 0 65001 i >*> 3FFE:1CE3:12:A::/64 > :: 32768 i > >BGP router identifier 10.0.3.2, local AS number 16186 >BGP table version is 18, main routing table version 18 >5 network entries and 5 paths using 985 bytes of memory >17591 BGP path attribute entries using 1056420 bytes of memory >15446 BGP AS-PATH entries using 397332 bytes of memory >23 BGP community entries using 776 bytes of memory >0 BGP route-map cache entries using 0 bytes of memory >2 BGP filter-list cache entries using 24 bytes of memory >BGP activity 109424/507859 prefixes, 112573/7642 paths, scan interval 15 >secs > > > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > > > >This should be already working see section 1. > > > d. A fully maintained, and reliable, IPv6-accessible system > providing, at a mimimum, one or more web pages, describing the > Applicant's IPv6 services. This server must be IPv6 pingable. > >our smtp.webonline.no runs ipv6. Also sshd, telnet, imap, pop3, ircd on a >couple of servers. > >www.webonline.no does not run ipv6 (yet). its a nt-server... > >www.ipv6.webonline.no is up. > > > > 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. > >Iver Olsen (iver.olsen@webonline.no) >Oyvind Ellefsen (oyvind@webonline.no) >and me > > > 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. > >noc@webonline.no > > 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. > >We will serve all customers who support and wishes to use ipv6. > >All leased lines customers will be allocated ipv6 and ipv4. >All servers will be allocated ipv6 (if supported) and ipv4. > >All dsl-customers will be allocated ipv6 if supported. (router >advertisement) >Dialup has its own ipv6 number. >We have a lot of hosted websites (win2k and unix servers). They will support >ipv6 when there are non-beta software availible. > >Free tunnels will be given out for non-commercial purposes for >non-customers. > > > > 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. > > > >Iver, Oyvind and I will abide the 6bone rules and policies as they exist >today and future rules and policies as they evolve. > > >http://www.ietf.org/rfc/rfc2772.txt > > > > 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>. > >I have joined the mailinglist. From itojun@iijlab.net Wed Nov 7 09:08:15 2001 From: itojun@iijlab.net (itojun@iijlab.net) Date: Wed, 07 Nov 2001 18:08:15 +0900 Subject: 2001:400::/29 In-Reply-To: itojun's message of Fri, 19 Oct 2001 17:14:02 +0900. <12075.1003479242@itojun.org> Message-ID: <11786.1005124095@itojun.org> > we (AS2500) are seeing 2001:400::/29 advertised from the following AS > path: > 4554 3748 4755 > is it for real? did RIR assigned /29 to AS4755? > I don't think it correct, since: > - http://www.dfn.de/service/ipv6/ipv6aggis.html does not list it > - 2001:400::/35 is advertised from different origin AS (AS293) FYI, 2001:400::/29 is still advertised, while 2001:400::/35 is too. itojun From dios-vol@telecom.noc.udg.mx Wed Nov 7 20:14:46 2001 From: dios-vol@telecom.noc.udg.mx (Harold de Dios Tovar Volunt) Date: Wed, 7 Nov 2001 14:14:46 -0600 (CST) Subject: pTLA request for UDG Message-ID: Hi Bob, We would like to apply for a pTLA allocation from 6bone, we are UDG, Universidad de Guadalajara (http://www.udg.mx) we are one of the members of Internet 2 here in Mexico, the name of the organisation is CUDI. The Mission of CUDI is to promote and to coordinate the development of networks of telecommunications and computing, focused to the scientific and educative development in Mexico. We would like to request one pTLA block, conformance to RFC 2772 pTLA prefix requests. 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: UDG is in 6bone since Mon, 3 Sep 2001 as pNLA of ITESM 3ffe:8240:8012::/48 at this moment we have pNLA 3FFE:8070:1012::1/64 from UNAM too. 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 UDG has the following objects: inet6num: 3FFE:8070:1012::/48 ipv6-site: UDG mntner: MNT-UDG mnt-by: UDG-6BONE person: Harold de Dios Tovar. theses are our BGP4+ peer conections: tunnels: IPv6 in IPv4 border.ipv6.udg.mx -> gwipv6.ipv6.itesm.mx ITESM BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> unam-ipv6-1.ipv6.unam.mx UNAM STATIC IPv6 in IPv4 border.ipv6.udg.mx -> ipv6-lab-gw.cisco.com CISCO BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> pioneer.ipv6.berkom.de BERKOM BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> rtr.ipv6.he.net HURRICANE BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> v6-gw.cygate.fi SMS BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> cern-atm7.cern.ch CERN BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> ipv6-gw.grnet.gr GRNET BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> border-gw2.caladan.net CALADAN BGP4+ IPv6 in IPv4 border.ipv6.udg.mx -> ziggy.ci.ulsa.mx ULSA STATIC application: ping imperio.ipv6.udg.mx ping noc6.ipv6.udg.mx url: www.ipv6.udg.mx 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 BGP4+ conections are working on cisco 3600, this router is border.ipv6.udg.mx and can be Ipv6 pingable. c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) entries for the Applicant's router(s) and at least one host system. UDG has the following about DNS, actually we have 3 IPv6 zone, it is maintain and is using DNS forward (AAAA) and reverse (ip6.int). Those are the records: ;; QUESTION SECTION: ;imperio.ipv6.udg.mx. IN ANY ;; ANSWER SECTION: imperio.ipv6.udg.mx. 86400 IN AAAA 3ffe:8240:8012:1:201:3ff:fee6:ad36 imperio.ipv6.udg.mx. 86400 IN A 148.202.15.149 ------------------- ;; QUESTION SECTION: ;noc6.ipv6.udg.mx. IN ANY ;; ANSWER SECTION: noc6.ipv6.udg.mx. 86400 IN AAAA 3ffe:8240:8012:1:210:5aff:fe99:f59b noc6.ipv6.udg.mx. 86400 IN A 148.202.15.220 ------------------ ;; QUESTION SECTION: ;border.ipv6.udg.mx. IN ANY ;; ANSWER SECTION: border.ipv6.udg.mx. 86400 IN A 148.202.15.8 border.ipv6.udg.mx. 86400 IN AAAA 3ffe:8240:8012:1:204:c1ff:fe89:5c71 d. A fully maintained, and reliable, IPv6-accessible system providing, at a mimimum, one or more web pages, describing the Applicant's IPv6 services. This server must be IPv6 pingable. Our Dual-Stack (IPv4/Iv6) web page is http://www.ipv6.udg.mx/ Here you could find some basicall information about IPv6, in fact our tunnels status can be seen here. We are implementing TunnelBroker and other aplications to be used by people interested in IPv6. 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. HDDT2-6BONE The support staff of UdG has 7 person, the name person in charge is Harold de Dios Tovar. OBEJCT:ipv6-site changed: dios-vol@telecom.noc.udg.mx OBJECT:person changed: harold@noc.udg.mx 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. staff@ipv6.udg.mx 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. UDG is a mexican university, UDG network ha sa user comunity made up of more than 100,000 students, teachers, researchs and personal working at UDG. You can find this information at UDG web page -> http://www.udg.mx UDG is one of the principal members of CUDI (Cooperacion Universitaria para el desarollo de internet), this is the internet 2 consortium in Mexico. --> http://www.cudi.edu.mx 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. UDG undertand the 6bone operational rules and we are strongly agree whit them all and we will to abide to the current and the future 6bone operational rules and policies. Regards from Mexico!! -------------------------------------- Harold de Dios Tovar home: (01) 36 726016 work: (01) 31 342232 ext. 2321 e-m@il: harold@noc.udg.mx harold@mexp5.mexplaza.com.mx NOC: Network Operation Center IPv6 Staff Working Group -------------------------------------- From fink@es.net Thu Nov 8 17:08:33 2001 From: fink@es.net (Bob Fink) Date: Thu, 08 Nov 2001 09:08:33 -0800 Subject: pTLA request for NC-REN - review closes 23 November 2001 Message-ID: <5.1.0.14.0.20011108085550.02d829b0@imap2.es.net> 6bone Folk, NC-REN has requested a pTLA allocation. The open review period for this will close 23 November 2001. Please send your comments to me or the list. Thanks, Bob === >Date: Wed, 7 Nov 2001 23:51:41 -0500 (EST) >From: Alan Halachmi >To: >cc: >Subject: pTLA Request for NC-REN > >Bob, > > I'm forwarding you our pTLA request. We've had a v6 webserver up >for a while now, but never loaded content. I'm having the folks at Duke >take up that piece, and I imagine that'll be done by weeks end. Otherwise, >I believe everything's in order. > >Best!! >Alan >------------------------------------------------------------------------ > >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. > > ipv6-site: NC-REN > > 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. > > 3ffe:1cdd::1 > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > > We have no control over ip6.int, as MERIT is not longer funding > IPv6; we do, however, have router setup w/ AAAA records. > ipv6-gw-3600.ncni.net is the core router. > ipv6.duke.edu is the host. > > d. A fully maintained, and reliable, IPv6-accessible system > providing, at a mimimum, one or more web pages, describing the > Applicant's IPv6 services. This server must be IPv6 pingable. > > ipv6.duke.edu > > 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. > > ipv6-site: NC-REN > contact: AH2-6BONE > contact: RDC-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. > > helpdesk@ncren.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. > > NCREN Internet Services serves as the Internet access provider for 16 > campus universities, 40 private and community colleges, and a number > of other educational and research institutions throughout North > Carolina. http://www.ncren.net/Internet/ for more information. > > 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. > > This commitment is hereby made. ... From ipv6@isis.unlp.edu.ar Thu Nov 8 23:28:46 2001 From: ipv6@isis.unlp.edu.ar (Miguel Luengo) Date: Thu, 8 Nov 2001 20:28:46 -0300 Subject: test Message-ID: <000d01c168ad$1d07dcd0$5b000aa3@cespint.unlp.edu.ar> This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C16893.F7A82E40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Only test ------=_NextPart_000_000A_01C16893.F7A82E40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Only test
------=_NextPart_000_000A_01C16893.F7A82E40-- From ipv6@isis.unlp.edu.ar Thu Nov 8 23:44:00 2001 From: ipv6@isis.unlp.edu.ar (ipv6@isis.unlp.edu.ar) Date: Thu, 8 Nov 2001 20:44:00 -0300 (ART) Subject: Test list Message-ID: Test From ipv6@isis.unlp.edu.ar Thu Nov 8 23:56:14 2001 From: ipv6@isis.unlp.edu.ar (ipv6@isis.unlp.edu.ar) Date: Thu, 8 Nov 2001 20:56:14 -0300 (ART) Subject: No ping Message-ID: Hello, I have 3 linux (2 Red Hat 7,1 and Suse 7.1 on Sparc), 1 FreeBSD and 1 Solaris 8 IPv6 enable. My network IPv6 is connected to UNAM (Mexico) with Cisco router. I want to do ping to the unicast address in my LAN do not obtain answer. if ping is to the link local or an address in other network, I obtain answer. Can You help me??? Miguel From marcelo@sosa.com.ar Fri Nov 9 01:27:14 2001 From: marcelo@sosa.com.ar (Marcelo M. Sosa Lugones) Date: Thu, 8 Nov 2001 22:27:14 -0300 Subject: No ping References: Message-ID: <010301c168bd$a9d4fca0$6541a8c0@centauri.com.ar> Hi Miguel, > My network IPv6 is connected to UNAM (Mexico) with Cisco router. > I want to do ping to the unicast address in my LAN do not obtain answer. > if ping is to the link local or an address in other network, I obtain > answer. If you ping the unicast address of any computer in your lan, do you see the packets coming in in the destination machine? does it reply? It happens only with the linux boxes or with any computer? can you ping the local gateway? try changing the ttl (ping6 -t ttl host) Regards, Marcelo. From killyeon@yahoo.com Fri Nov 9 06:16:03 2001 From: killyeon@yahoo.com (killyeon kim) Date: Thu, 8 Nov 2001 22:16:03 -0800 (PST) Subject: How to configure mozilla and apache for IPv6 in Linux7.1? Message-ID: <20011109061603.84501.qmail@web13701.mail.yahoo.com> Hello, every one. I have installed apache-1.3.19-5.src.rpm(with apache-1.3.19+IPv6.spec) and mozilla-i686-pc-linux-gnu-0.9.5.tar.gz refer to Peter Bieringer's linux IPv6 beginner's guide in WowLinux 7.1. But I cant't access the apache server with mozilla by IPv6 address, although I can access it with IPv4 address. I don't know the problem is because of mozilla client or apache web server? Shoud I configure the httpd.conf with some IPv6 supporting option? Or, should mozilla be patched with IPv6? If so, where can I get the patch file? And where can I get some detail guide for configuration IPv6 application servers, like apache, Bind, ftpd, etc. Please give me any help... Thanks in advance __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com From psb@ast.cam.ac.uk Fri Nov 9 07:57:03 2001 From: psb@ast.cam.ac.uk (Peter Bunclark) Date: Fri, 9 Nov 2001 07:57:03 +0000 (GMT) Subject: How to configure mozilla and apache for IPv6 in Linux7.1? In-Reply-To: <20011109061603.84501.qmail@web13701.mail.yahoo.com> Message-ID: Did you add this bit to httpd.conf? # Listen can take two arguments. # (this is an extension for supporting IPv6 addresses) Listen :: 80 Listen 0.0.0.0 80 Pete. On Thu, 8 Nov 2001, killyeon kim wrote: > > Hello, every one. > > I have installed apache-1.3.19-5.src.rpm(with > apache-1.3.19+IPv6.spec) and > mozilla-i686-pc-linux-gnu-0.9.5.tar.gz refer to Peter > Bieringer's linux IPv6 beginner's guide in WowLinux > 7.1. > But I cant't access the apache server with mozilla by > IPv6 address, although I can access it with IPv4 > address. > I don't know the problem is because of mozilla client > or apache web server? > Shoud I configure the httpd.conf with some IPv6 > supporting option? Or, should mozilla be patched with > IPv6? If so, where can I get the patch file? > And where can I get some detail guide for > configuration IPv6 application servers, like apache, > Bind, ftpd, etc. > Please give me any help... > Thanks in advance > > > > __________________________________________________ > Do You Yahoo!? > Find a job, post your resume. > http://careers.yahoo.com > From scott@fenton.baltimore.md.us Fri Nov 9 11:32:48 2001 From: scott@fenton.baltimore.md.us (Scott Fenton) Date: Fri, 9 Nov 2001 06:32:48 -0500 Subject: How to configure mozilla and apache for IPv6 in Linux7.1? In-Reply-To: <20011109061603.84501.qmail@web13701.mail.yahoo.com> References: <20011109061603.84501.qmail@web13701.mail.yahoo.com> Message-ID: <20011109063248.A16551@home.com> --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 08, 2001 at 10:16:03PM -0800, the keyboard of killyeon kim was = alleged to have written: > [snip] > I don't know the problem is because of mozilla client > or apache web server? > [snip] Try going to some other IPv6 server that you know is working. I can tell you that Debian's moz build comes with working IPv6=20 support, but I'm not sure about RH. -Scott --=20 GPG public key fingerprint: B6B9 9F98 848B 540D 419D 5487 6B6B 5DB9 B5A5 = 25FA -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d>- s: a14 C++>++++ UL++++>$ P++(++++) L+++>++++=20 E>++ W++(--) N !o K w--- !O M+(--) !V PS++(+++) PE=20 Y+>++ PGP+@ t- 5- !X R- tv+>! b>+++ DI++++ !D G=20 e->++++ h! r y- ------END GEEK CODE BLOCK------ --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7677ga2tdubWlJfoRAt6DAKCHxfMPZF+cMn5P8Hur4SxgoRXrdACaAh2K lEsVspsMsgk1ySgbRCnfRQw= =qX1a -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- From pekkas@netcore.fi Fri Nov 9 15:11:03 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Fri, 9 Nov 2001 17:11:03 +0200 (EET) Subject: How to configure mozilla and apache for IPv6 in Linux7.1? In-Reply-To: <20011109063248.A16551@home.com> Message-ID: On Fri, 9 Nov 2001, Scott Fenton wrote: > On Thu, Nov 08, 2001 at 10:16:03PM -0800, the keyboard of killyeon kim was alleged to have written: > > [snip] > > I don't know the problem is because of mozilla client > > or apache web server? > > [snip] > > Try going to some other IPv6 server that you know is working. I > can tell you that Debian's moz build comes with working IPv6 > support, but I'm not sure about RH. Red Hat's mozilla works with IPv6 since about RHL70. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From fink@es.net Fri Nov 9 16:06:08 2001 From: fink@es.net (Bob Fink) Date: Fri, 09 Nov 2001 08:06:08 -0800 Subject: 6bone pTLA 3FFE:8290::/28 allocated to AOL Message-ID: <5.1.0.14.0.20011109080405.028d7e18@imap2.es.net> AOL has been allocated pTLA 3FFE:8290::/28 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to either bmanning@isi.edu or hostmaster@ep.net. Thanks, Bob From ariel@alfa.com.ni Mon Nov 12 00:14:23 2001 From: ariel@alfa.com.ni (Ariel A. Ramos R.) Date: Sun, 11 Nov 2001 19:14:23 -0500 Subject: Some questions Message-ID: <5.1.0.14.0.20011111191113.00b391a8@alfa.com.ni> Hey guys, i have some questions 1) I connect to internet via dialup, the computer uses win98 and uses winroute to act as a gateway of my LAN... My pc has windows 2000 with sp2 and ipv6 support that i have downloaded from microsoft's page. Can i send ipv6 traffic? I tried to ping www.6bone.net with ping6 but i got these results: D:\>ping6 www.6bone.net Pinging 6bone.net [3ffe:b00:c18:1::10] with 32 bytes of data: No route to destination. No route to destination. No route to destination. No route to destination. I think that my gateway can't route ipv6 packets how i can correct this? i need to have a *NIX router? From lazy@bsdbox.org Mon Nov 12 03:51:24 2001 From: lazy@bsdbox.org (lazy) Date: Sun, 11 Nov 2001 22:51:24 -0500 Subject: Some questions References: <5.1.0.14.0.20011111191113.00b391a8@alfa.com.ni> Message-ID: <3BEF473C.DF2E606E@bsdbox.org> Have you properly configured your IPv6 stuff? Is the TCPIP6 stuff running? > Commands: net stop tcpip6 net start tcpip6 > For a IPv6 tunnel (non-NAT): 1.2.3.4 -- Endpoint of tunnel 3ffe:a:b:a::1285 -- Your IPv6 address Commands: ipv6 rtu ::/0 2/::1.2.3.4 pub ipv6 adu 2/3ffe:a:b:a::1285 > For a NAT windows box: 2002:aabb:ccdd:1::3 - IP of NAT box 2002:aabb:ccdd:1::2 - IP of next hop (router internal interface) Commands: net stop tcpip6 net start tcpip6 ipv6 adu 4/2002:aabb:ccdd:1::3 ipv6 rtu ::/0 4/2002:aabb:ccdd:1::2 "Ariel A. Ramos R." wrote: > > Hey guys, i have some questions > > 1) I connect to internet via dialup, the computer uses win98 and uses > winroute to act as a gateway of my LAN... My pc has windows 2000 with sp2 > and ipv6 support that i have downloaded from microsoft's page. Can i send > ipv6 traffic? > I tried to ping www.6bone.net with ping6 but i got these results: > D:\>ping6 www.6bone.net > > Pinging 6bone.net [3ffe:b00:c18:1::10] with 32 bytes of data: > > No route to destination. > No route to destination. > No route to destination. > No route to destination. > > I think that my gateway can't route ipv6 packets > how i can correct this? i need to have a *NIX router? -- :: No officer, I said I use BSD, not LSD... lazy http://packetjunkie.net/ From lists@geminis.myip.org Mon Nov 12 11:02:49 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Mon, 12 Nov 2001 08:02:49 -0300 (ART) Subject: Some questions In-Reply-To: <5.1.0.14.0.20011111191113.00b391a8@alfa.com.ni> Message-ID: Ariel, are you sure you already set up an IPv6 over IPv4 tunnel with an IPv6 tunnel broker in your gateway? AFAIK, nor win98 neither winroute have the capability of establishing IPv6 tunnels. You'd probably need to change your win98 gateway box for a win2000 (or *NIX) box before you can route IPv6 packets. To get a tunnel broker look at www.freenet6.net where you can obtain an upstream provider and a /48 for free in a few minutes. Regards, Flavio. On Sun, 11 Nov 2001, Ariel A. Ramos R. wrote: > Hey guys, i have some questions > > 1) I connect to internet via dialup, the computer uses win98 and uses > winroute to act as a gateway of my LAN... My pc has windows 2000 with sp2 > and ipv6 support that i have downloaded from microsoft's page. Can i send > ipv6 traffic? > I tried to ping www.6bone.net with ping6 but i got these results: > D:\>ping6 www.6bone.net > > Pinging 6bone.net [3ffe:b00:c18:1::10] with 32 bytes of data: > > No route to destination. > No route to destination. > No route to destination. > No route to destination. > > I think that my gateway can't route ipv6 packets > how i can correct this? i need to have a *NIX router? > From Mehdi.ElAbed@Compaq.com Tue Nov 13 15:06:44 2001 From: Mehdi.ElAbed@Compaq.com (El Abed, Mehdi) Date: Tue, 13 Nov 2001 15:06:44 -0000 Subject: ipv6 snmp agent Message-ID: Hello, I've tried to use the ucd-snmp 4.2.2 in order to run an ipv6 snmp agent over tru64 but with no success (the full configuration doesen't compile) and the minimal agent configuration doesn't work with ipv6; Could anyone please give me a right version (or a patch) to use so that i can implement an snmp ipv6 agent over unix tru64? Thanks Mehdi El Abed From todd@fries.net Wed Nov 14 13:02:08 2001 From: todd@fries.net (Todd T. Fries) Date: Wed, 14 Nov 2001 07:02:08 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] Message-ID: <20011114070208.E30841@eclipse.fries.net> Anyone know of another registrar that supports this? ----- Forwarded message from Network Solutions ----- From: Network Solutions To: "'todd@fries.net'" Subject: Service Request Number: 1-UX4DN Date: Tue, 13 Nov 2001 19:48:27 -0600 Dear Todd Fries Thank you for your inquiry received on 11/1/01 1:39:31 AM. We do not currently support these new ipv6 dns servers. At this time there is no estimated date on when we will support them. If you need to contact us in the future about this inquiry, please provide number 1-UX4DN to our customer service representative. Thank you for choosing Network Solutions. Sincerely, NADELE001 Customer Service Representative Network Solutions, Inc. www.networksolutions.com Please do not reply directly to this email address. Replies sent to this email address will not be responded to. To reach Network Solutions, please visit our web site at www.networksolutions.com or send an email to help@networksolutions.com. Thank you. ----- End forwarded message ----- -- Todd Fries .. todd@fries.net From bmanning@ISI.EDU Wed Nov 14 13:34:31 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Wed, 14 Nov 2001 05:34:31 -0800 (PST) Subject: BOUNCE 6bone@zephyr.iipv6 DNS servers Message-ID: <200111141334.fAEDYV203945@zed.isi.edu> % On Wed, Nov 14, 2001 at 07:02:08AM -0600, Todd T. Fries wrote: % > We do not currently support these new ipv6 dns servers. At this time there % > is no estimated date on when we will support them. % % WTH are ipv6 DNS Servers? % % -mc IPv6 DNS servers are DNS servers that speak DNS on an IPv6 stack. Most DNS servers todate are IPv4 speakers only. There are some servers that speak both v4 and v6 and some experimental systems that speak IPv6 only. If there is interest in native v6 speaking DNS service for the whole DNS heirarchy, please let me know. -- bill From todd@fries.net Wed Nov 14 14:19:46 2001 From: todd@fries.net (Todd T. Fries) Date: Wed, 14 Nov 2001 08:19:46 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <20011114152017.E15927@potato.amsterdam.weirdnet.nl>; from paul@mail.me.maar.nu on Wed, Nov 14, 2001 at 03:20:17PM +0100 References: <20011114070208.E30841@eclipse.fries.net> <20011114141712.A20143@magrathea.ukeer.de> <20011114145242.D15927@potato.amsterdam.weirdnet.nl> <20011114144136.A18869@magrathea.ukeer.de> <20011114152017.E15927@potato.amsterdam.weirdnet.nl> Message-ID: <20011114081946.F30841@eclipse.fries.net> It makes perfect sense to do this. Please explain if I'm missing something, but the current strategy for resolving a domain is to try the first dns server, and if that doesn't work, the next, etc. Not that I want the 'first' dns server to be an ipv6 only dns server (aka ns6.fries.net is 3ffe:b00:4004:1::1:6 and nothing else A or AAAA wise) .. What I am trying to determine here is .. that if we're truly wanting to tell the world 'here is ipv6, it is fully functional' how can we say this and yet not be able to register a single ipv6 ip for a dns server? Sure, I buy into the argument that it is not forward and not compatible thinking if the only dns server for any domain is ipv6 only. The time will come for that, it is not yet here. But the time has come and past to be able to register an ipv6 dns server. Case in point that this works, ip6.int: todd:1$ host -t ns ip6.int ip6.int. name server z.ip6.int. ip6.int. name server ns3.nic.fr. ip6.int. name server flag.ep.net. ip6.int. name server imag.imag.fr. ip6.int. name server munnari.oz.au. ip6.int. name server y.ip6.int. todd:2$ host -t any z.ip6.int z.ip6.int. has v6 address 0 3ffe:0:1::c620:242 z.ip6.int. has address 198.32.2.66 z.ip6.int. has AAAA address 3ffe:0:1::c620:242 todd:3$ host -t any ns3.nic.fr ns3.nic.fr. has address 192.134.0.49 todd:4$ host -t any flag.ep.net flag.ep.net. has address 198.32.4.13 todd:5$ host -t any imag.imag.fr imag.imag.fr. mail is handled by 50 ebene.inrialpes.fr. imag.imag.fr. mail is handled by 10 imag.imag.fr. imag.imag.fr. mail is handled by 20 harmonie.imag.fr. imag.imag.fr. has address 129.88.30.1 todd:6$ host -t any munnari.oz.au munnari.oz.au. has address 128.250.22.2 munnari.oz.au. has address 128.250.1.21 todd:7$ host -t any y.ip6.int y.ip6.int. has AAAA address 3ffe:50e::1 todd:8$ If you will note, there are several ipv6 dns servers and one (y.ip6.int) is ipv6 only. This does not stop ipv4 only clients from determining the hostname of an ipv6 address. But it does show that you can mix ipv4 and ipv6 dns servers and things will work properly. Now if someone could just give me an example of a *-servers.net server (where * is a.root and a.gtld) that dispenses AAAA addresses for any domain, I'd be grateful. This would be a 'step' to show that the toplevel dns servers are capable of dispensing information, and only the infrastructure to update them is what is not in place. In short, we're not 'there' yet. Where 'there' is 'having deployed ipv6 globally everywhere'. How do we get 'there' ? I feel that taking steps such as the one I'm trying to is one of many ways. The more ways we try, the better off we are. As Vincent Cerf says (speaking of the 6bone and ipv6 usage in general) at http://www.ipv6forum.com/navbar/technology/papers.htm, "Think of it this way: my old friend Bob Metcalf calling something we call METCALF's Law. It says that the value of a network is equal to the square of the number of people who use it. So when you join a network, you not only get to enjoy its facilities, but your presence also increases the value of the network for others. Together, we can take the Internet where no other network has gone before." Penned by Paul de Weerd on Wed, Nov 14, 2001 at 03:20:17PM +0100, we have: | On Wed, Nov 14, 2001 at 02:41:36PM +0100, Rico -mc- Gloeckner wrote: | | On Wed, Nov 14, 2001 at 02:52:42PM +0100, Paul de Weerd wrote: | | > Servers that either | | > a) resolve IPv6 adresses (back and forth) | | | | any DNS Server is able to do this. | | IPV6 RRs forward are just AAAA (instead of A) RRs. | | Reverse its just the hexa ip, dot-seperated nibbles read reversely under | | the ip6.int domain | | (i.e. e.f.f.3.ip6.int for IN RR of 3ffe::) | | | | > b) are accessible through IPv6 | | | | It doesnt (yet) make sense to do this. Any ipv4 client trying to resolve | | your domin will fail in doing that because it wont be able to reach your | | DNS Server via ipv6. | | Why not ? I have a fully operational DNS server that is accessible | through IPv4 *AND* IPv6. | Suppose NS contains'ns.domain.tld' and that this resolves to both an | IPv4 and an IPv6 address. Where does the ipv4 client fail in resolving | my domain ? | | Anyway, I was just answering your question on what IPv6 DNS servers | were and I still think that it's either a or b or both. | | | | | -mc | | | | PS: Yes, i know what iam speaking of - i have a fully functional ipv6 | | Setup, including forward- and Reverse-RRs for IPv6 and ipv6-accessible | | DNS. | | Any Host having a working IPV6 SMTP Server will even try to deliver Mails | | to me via Ipv6 first. | | So do I, and, So do I. | | Paul 'WEiRD' de Weerd | | -- | >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ | +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] -- Todd Fries .. todd@fries.net From jorgen@hovland.cx Wed Nov 14 17:22:19 2001 From: jorgen@hovland.cx (=?iso-8859-1?Q?J=F8rgen_Hovland?=) Date: Wed, 14 Nov 2001 18:22:19 +0100 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] References: <20011114070208.E30841@eclipse.fries.net> Message-ID: <00ef01c16d30$eaa4a100$b94a2780@6140> What is the problem? Buy a domain which has ipv6 nameservers? Just put IN NS to a host you control that has ipv6. Want netsol to host it? Want the NS' of the tld to have ipv6 nameservers? -j ----- Original Message ----- From: "Todd T. Fries" To: ; <6bone@ISI.EDU> Sent: Wednesday, November 14, 2001 2:02 PM Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] > Anyone know of another registrar that supports this? > > ----- Forwarded message from Network Solutions ----- > > From: Network Solutions > To: "'todd@fries.net'" > Subject: Service Request Number: 1-UX4DN > Date: Tue, 13 Nov 2001 19:48:27 -0600 > > Dear Todd Fries > > Thank you for your inquiry received on 11/1/01 1:39:31 AM. > > We do not currently support these new ipv6 dns servers. At this time there > is no estimated date on when we will support them. > > If you need to contact us in the future about this inquiry, please provide > number 1-UX4DN to our customer service representative. > > Thank you for choosing Network Solutions. > > Sincerely, > > NADELE001 > Customer Service Representative > Network Solutions, Inc. > www.networksolutions.com > > Please do not reply directly to this email address. Replies sent to this > email address will not be responded to. To reach Network Solutions, please > visit our web site at www.networksolutions.com or send an email to > help@networksolutions.com. Thank you. > > ----- End forwarded message ----- > > -- > Todd Fries .. todd@fries.net > From jeroen@unfix.org Wed Nov 14 22:09:13 2001 From: jeroen@unfix.org (Jeroen Massar) Date: Wed, 14 Nov 2001 23:09:13 +0100 Subject: BOUNCE 6bone@zephyr.iipv6 DNS servers In-Reply-To: <200111141334.fAEDYV203945@zed.isi.edu> Message-ID: <000701c16d58$fe880040$420d640a@HELL> Bill Manning wrote: > % On Wed, Nov 14, 2001 at 07:02:08AM -0600, Todd T. Fries wrote: > % > We do not currently support these new ipv6 dns servers. > At this time there > % > is no estimated date on when we will support them. > % > % WTH are ipv6 DNS Servers? > % > % -mc > > IPv6 DNS servers are DNS servers that speak DNS on an IPv6 stack. > Most DNS servers todate are IPv4 speakers only. There are some > servers that speak both v4 and v6 and some experimental systems > that speak IPv6 only. If there is interest in native v6 speaking > DNS service for the whole DNS heirarchy, please let me know. Ofcourse this would be a great thing to have the root servers available over IPv6 without having to depend on IPv4. For the coming 20 years or something it will be inevitable to have them speaking IPv4 too ofcourse... But having at least a couple of them doing 'native' IPv6 would be a great thing IMHO. So a dualstacked root server would be great and a small step for IPv6 but a big step into the future... ;) Greets, Jeroen From ariel@alfa.com.ni Thu Nov 15 02:08:51 2001 From: ariel@alfa.com.ni (Ariel A. Ramos R.) Date: Wed, 14 Nov 2001 21:08:51 -0500 Subject: 6bone Message-ID: <5.1.0.14.0.20011114210522.00b49250@alfa.com.ni> who has tested a ping6 to 6bone, using microsoft ipv6 support for win2k? i can ping only to MS hosts, as shown below: D:\>ping6 ipv6.research.microsoft.com Pinging ipv6.research.microsoft.com [2002:836b:4179::836b:4179] with 32 bytes of data: Reply from 2002:836b:4179::836b:4179: bytes=32 time=357ms Reply from 2002:836b:4179::836b:4179: bytes=32 time=310ms Reply from 2002:836b:4179::836b:4179: bytes=32 time=390ms Reply from 2002:836b:4179::836b:4179: bytes=32 time=330ms but, when i ping to 6bone host: D:\>ping6 www.6bone.net Pinging 6bone.net [3ffe:b00:c18:1::10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. to configure the 6to4 in win2k, i used D:\>6to4cfg -b Probing 6to4 relay router 192.88.99.1... Probing 6to4 relay router 131.107.152.32... Found 6to4 relay router host1504.rte.microsoft.com (131.107.152.32)... Using local address 206.128.113.51 for the 6to4 prefix. Anybody can help me? From killyeon@yahoo.com Thu Nov 15 03:49:12 2001 From: killyeon@yahoo.com (killyeon kim) Date: Wed, 14 Nov 2001 19:49:12 -0800 (PST) Subject: how to configure for IPv4 and IPv6 in BIND9.1.3? Message-ID: <20011115034912.46806.qmail@web13705.mail.yahoo.com> Hello. I want to set bind9.1.3 to support IPv4 and IPv6. Should I give the different domains for IPv4 hosts and IPv6 hosts? How shoud I configure the "named.conf" to support IPv4 and IPv6 at the same time? I don't know what's wrong in my named.conf. The following is part of my configuration. ======= zone "galaxy.pusan.ac.kr" { type master; file "galaxy.zone"; }; zone "v6.galaxy.pusan.ac.kr" { type master; file "v6.galaxy.zone"; }; ========= And I put A records for IPv4 hosts in galaxy.zone, and AAAA records for IPv6 hosts in v6.galaxy.zone. Then, IPv4 hosts and IPv6 hosts have the same domain or not? The name server works well for IPv4 host and IPv6 reverse zone, but it can't work for IPv6 forward zone. And if I want to set a bind9 dns server authoritative for more than one domain, how should I do? Please attach me named.conf and zone files if you have ones. Thanks a lot. __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com From mike@wackypackets.com Thu Nov 15 06:29:06 2001 From: mike@wackypackets.com (Michael K. Smith) Date: Wed, 14 Nov 2001 22:29:06 -0800 (PST) Subject: 6bone In-Reply-To: <5.1.0.14.0.20011114210522.00b49250@alfa.com.ni> Message-ID: Hello: I am able to successfully ping both hosts using the Win2K ipv6 stack for SP2. Have you configured Win2K beyond the defaults? I had to put in a static address and default gateway because the auto-configuration parameters were not anything like what I needed. I used the following commands... ipv6 if (to figure out which interface number was in use) ipv6 adu (to configure the ipv6 address to the interface from the command above) ipv6 rt (to find the default route in place) ipv6 rtu (to remove the standard default gateway and add my own default gateway) The readme.html file included with the IPv6 kit is pretty good, but if you still have problems, hit me offline and I'll see if I can help. Mike On Wed, 14 Nov 2001, Ariel A. Ramos R. wrote: > who has tested a ping6 to 6bone, using microsoft ipv6 support for win2k? > i can ping only to MS hosts, as shown below: > > D:\>ping6 ipv6.research.microsoft.com > > Pinging ipv6.research.microsoft.com [2002:836b:4179::836b:4179] with 32 > bytes of > data: > > Reply from 2002:836b:4179::836b:4179: bytes=32 time=357ms > Reply from 2002:836b:4179::836b:4179: bytes=32 time=310ms > Reply from 2002:836b:4179::836b:4179: bytes=32 time=390ms > Reply from 2002:836b:4179::836b:4179: bytes=32 time=330ms > > but, when i ping to 6bone host: > > D:\>ping6 www.6bone.net > > Pinging 6bone.net [3ffe:b00:c18:1::10] with 32 bytes of data: > > Request timed out. > Request timed out. > Request timed out. > Request timed out. > > to configure the 6to4 in win2k, i used > > D:\>6to4cfg -b > Probing 6to4 relay router 192.88.99.1... > Probing 6to4 relay router 131.107.152.32... > Found 6to4 relay router host1504.rte.microsoft.com (131.107.152.32)... > Using local address 206.128.113.51 for the 6to4 prefix. > > > Anybody can help me? > > From jeroen@unfix.org Thu Nov 15 09:50:35 2001 From: jeroen@unfix.org (Jeroen Massar) Date: Thu, 15 Nov 2001 10:50:35 +0100 Subject: 6bone In-Reply-To: <5.1.0.14.0.20011114210522.00b49250@alfa.com.ni> Message-ID: <000f01c16dba$fa0cebe0$2a1410ac@kei.azr.nl> Ariel A. Ramos R. wrote: > who has tested a ping6 to 6bone, using microsoft ipv6 support for win2k? > i can ping only to MS hosts, as shown below: > D:\>6to4cfg -b > Probing 6to4 relay router 192.88.99.1... > Probing 6to4 relay router 131.107.152.32... > Found 6to4 relay router host1504.rte.microsoft.com (131.107.152.32)... > Using local address 206.128.113.51 for the 6to4 prefix. Check your routing tables and try 'tracert6 ' to determine if there wasn't anything down at the moment. You should very probably also add a default route over the 6to4 device. Try something like: cmd> ipv6 rtu ::/0 2/::131.107.152.32 pub life 1800 Also see: http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp and ofcourse http://www.microsoft.com/ipv6/ :) Greets, Jeroen From jeroen@unfix.org Thu Nov 15 09:58:09 2001 From: jeroen@unfix.org (Jeroen Massar) Date: Thu, 15 Nov 2001 10:58:09 +0100 Subject: how to configure for IPv4 and IPv6 in BIND9.1.3? In-Reply-To: <20011115034912.46806.qmail@web13705.mail.yahoo.com> Message-ID: <001701c16dbc$085a9d40$2a1410ac@kei.azr.nl> killyeon kim wrote: > I want to set bind9.1.3 to support IPv4 and IPv6. > Should I give the different domains for IPv4 hosts and IPv6 hosts? Nopes unless you really want that. It's all administrative alike and the admin of a zone may put (almost :) anything in their zones and structure them in any way the want to. Personally I used to have a separate ipv6.. too but I currently only use that for software not being able to specifically request the use of IPv6, or ipv4.. for IPv4 ofcourse :). > How shoud I configure the "named.conf" to support IPv4 and IPv6 at the same time? > I don't know what's wrong in my named.conf. > The following is part of my configuration. > ======= > zone "galaxy.pusan.ac.kr" { > type master; > file "galaxy.zone"; > }; > > zone "v6.galaxy.pusan.ac.kr" { > type master; > file "v6.galaxy.zone"; > }; > ========= > > And I put A records for IPv4 hosts in galaxy.zone, and > AAAA records for IPv6 hosts in v6.galaxy.zone. Then, > IPv4 hosts and IPv6 hosts have the same domain or not? You can easily have in the v6.galaxy: 8<---------------------------------------- host-one A 192.168.0.42 AAAA 3ffe:1234:5678::xxx:xxx A6 mychain ::xxx:xxx ---------------------------------------->8 Which will give the host IPv4 (A) and IPv6 (AAAA and/or A6) addresses. And wether you want to make a separate ipv6.. zone is entirely up to you. > The name server works well for IPv4 host and IPv6 > reverse zone, but it can't work for IPv6 forward zone. reverse is just PTR :) > And if I want to set a bind9 dns server authoritative > for more than one domain, how should I do? Make multiple zones and add those to the > Please attach me named.conf and zone files if you have ones. > Thanks a lot. It's probably best if you read http://www.crt.se/dnssec/bind9/Bv9ARM.ch04.html#AEN980 - IPv6 support in Bind9, which also covers IPv6 on bind8 for most parts, though afaik bind8 doesn't support all RR's. The rest of that document (http://www.crt.se/dnssec/bind9/) will nicely show you how the rest is done. Greets, Jeroen From bruce_campbell@ripe.net Thu Nov 15 11:19:16 2001 From: bruce_campbell@ripe.net (Bruce Campbell) Date: Thu, 15 Nov 2001 12:19:16 +0100 (CET) Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <20011114081946.F30841@eclipse.fries.net> Message-ID: On Wed, 14 Nov 2001, Todd T. Fries wrote: > It makes perfect sense to do this. Please explain if I'm missing something, > but the current strategy for resolving a domain is to try the first dns > server, and if that doesn't work, the next, etc. Network Solution's problem may very well be in their database being unable to store anything other than an IPv4 address in the Host record at the present time. > will come for that, it is not yet here. But the time has come and > past to be able to register an ipv6 dns server. Case in point that > this works, ip6.int: The nameservers for ip6.int's parent domain, 'int', are not under the control of NSI, hence these nameservers can delegate 'ip6.int' to (at least one) IPv6-only nameserver(s). -- Bruce Campbell RIPE NCC I do not speak for my Employer Operations From mithrandir@skynet.be Thu Nov 15 13:09:42 2001 From: mithrandir@skynet.be (Mithrandir) Date: Thu, 15 Nov 2001 14:09:42 +0100 Subject: IOS for 2500 Message-ID: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Hello friends of the 6bone I was browsing the Cisco site, hoping to find a IPv6 IOS release for the 2500 series router. But that site is BIG!! I get lost in that place. I can't get the IOS myself but a company I work with can. So, does anyone of you know which latest IOS release I'm looking for? It must support IPv6 ofcourse, and run on a Cisco 2514, 2505 and 2503. If anyone knows the exact name/version of that IOS please let me know. Thank you very much Kind regards Mithrandir Cielen Fddi Institute Belgium From fink@es.net Thu Nov 15 13:59:31 2001 From: fink@es.net (Bob Fink) Date: Thu, 15 Nov 2001 05:59:31 -0800 Subject: 6bone pTLA 3FFE:82A0::/28 allocated to INTERNET-MULTIFEED Message-ID: <5.1.0.14.0.20011115055657.03205dd8@imap2.es.net> INTERNET-MULTIFEED has been allocated pTLA 3FFE:82A0::/28 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: [To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to either bmanning@isi.edu or hostmaster@ep.net.] Thanks, Bob From paitken@cisco.com Thu Nov 15 14:04:31 2001 From: paitken@cisco.com (Paul Aitken) Date: Thu, 15 Nov 2001 14:04:31 +0000 Subject: IOS for 2500 References: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Message-ID: <3BF3CB6F.91F6A80B@cisco.com> Mithrandir wrote: > > Hello friends of the 6bone > > I was browsing the Cisco site, hoping to find a IPv6 IOS release for the > 2500 series router. > But that site is BIG!! I get lost in that place. > > I can't get the IOS myself but a company I work with can. > So, does anyone of you know which latest IOS release I'm looking for? > It must support IPv6 ofcourse, and run on a Cisco 2514, 2505 and 2503. > > If anyone knows the exact name/version of that IOS please let me know. Questions about cisco IPv6 are best sent to ipv6-support@cisco.com ;) One of the best tools for finding Cisco IOS images is Cisco Feature Navigator at http://www.cisco.com/go/fn. Select "Feature" and search for "IPv6". Next, narrow down the possibilities by choosing your desired release, platform and feature set. When a list of images is displayed, you can choose a particular one and click "All Features" to see the full feature list. Once the list is narrowed down to a single image, you can click "Get this image" to download the image. Alternatively, if you like to do things the hard way but see all the details, try our IOS Upgrade Planner at http://www.cisco.com/go/iosplanner Note that there are only two IPv6-enabled images available for the 2500 series (the 12.2(4)T IP-Plus and the 12.2(4)T1 IP-Plus). So while the 2500 can still be used as an experimental IPv6 box, if you're serious about IPv6 I really recommend you upgrade to a new platform. Ultimately we're not going to be able to fit a fully featured IPv6-enabled IOS into the 2500. Cheers. -- Paul Aitken IPv6 Development, Cisco Systems Ltd, Edinburgh, Scotland. EH6 6LX From mharrell@bittwiddlers.com Thu Nov 15 14:15:22 2001 From: mharrell@bittwiddlers.com (Matthew Harrell) Date: Thu, 15 Nov 2001 09:15:22 -0500 Subject: Linux route question Message-ID: <20011115141522.GA26874@bittwiddlers.com> --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm currently setting up one of the /48 networks from freenet6 and I'm having some routing issues with my machines behind my tunnel endpoint. The network looks like 192.168.10. network <-> my ipv6 gateway <-> freenet6 ipv6 gateway I can do everything from my gateway and from the outside I can access all the machines on my network with ipv6 addresses. The problem is that when I try something like a ping from one of the internal machines I get {26}: ping6 -n www.kame.net PING www.kame.net(2001:200:0:4819:280:adff:fe71:81fc) from 3ffe:b80:411:1:250:4ff:fed6:1907 : 56 data bytes From 3ffe:b80:411:1::1 icmp_seq=1 Destination unreachable: Address unreachable From 3ffe:b80:411:1::1 icmp_seq=2 Destination unreachable: Address unreachable --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% loss, time 1003ms It actually worked at one point for a minute or two but I haven't been able to get the behavior back again. I can ping all local ipv6 addresses on my gateway from one of the 192.168.10 machines but get the error above trying to ping anything beyond my machine. Seems like a route issue to me but I'm not familiar enough with ipv6 to realize what route I'm missing. I've attached the ifconfig and route info from my gateway below. I would have though the ::/0 route in there would have taken care of things. thanks for any help -- Matthew Harrell Programmer - a red-eyed mumbling Bit Twiddlers, Inc. mammal capable of conversing with mharrell@bittwiddlers.com inanimate objects. --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ifconfig.txt" eth0 Link encap:Ethernet HWaddr 00:60:97:B7:9F:37 inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: 3ffe:b80:411:1::1/64 Scope:Global inet6 addr: fe80::260:97ff:feb7:9f37/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:97479 errors:0 dropped:0 overruns:0 frame:0 TX packets:120586 errors:0 dropped:0 overruns:0 carrier:0 collisions:11309 txqueuelen:100 RX bytes:8736899 (8.3 Mb) TX bytes:103090225 (98.3 Mb) Interrupt:17 Base address:0xff00 eth1 Link encap:Ethernet HWaddr 00:A0:C9:55:16:AE inet addr:24.7.169.75 Bcast:24.7.169.127 Mask:255.255.255.128 inet6 addr: fe80::2a0:c9ff:fe55:16ae/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:189379 errors:0 dropped:0 overruns:0 frame:0 TX packets:68475 errors:0 dropped:0 overruns:0 carrier:0 collisions:1837 txqueuelen:100 RX bytes:39443229 (37.6 Mb) TX bytes:10507529 (10.0 Mb) Interrupt:18 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:45098 errors:0 dropped:0 overruns:0 frame:0 TX packets:45098 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:60608024 (57.8 Mb) TX bytes:60608024 (57.8 Mb) sit1 Link encap:IPv6-in-IPv4 inet6 addr: fe80::1807:a94b/10 Scope:Link inet6 addr: fe80::c0a8:a01/10 Scope:Link inet6 addr: 3ffe:b80:2:240e::2/128 Scope:Global UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1 RX packets:551 errors:0 dropped:0 overruns:0 frame:0 TX packets:651 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:62598 (61.1 Kb) TX bytes:85423 (83.4 Kb) --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="routes.txt" Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 39 0 lo 3ffe:b80:2:240e::2/128 :: U 0 12 0 lo 3ffe:b80:411:1::1/128 :: U 0 5 0 lo 3ffe:b80:411:1:250:4ff:fed6:1907/128 3ffe:b80:411:1:250:4ff:fed6:1907 UAC 0 113 1 eth0 3ffe:b80:411:1::/64 :: UA 256 0 0 eth0 3ffe:b80:411::/48 :: U 1 0 0 eth0 fe80::1807:a94b/128 :: U 0 0 0 lo fe80::c0a8:a01/128 :: U 0 0 0 lo fe80::260:97ff:feb7:9f37/128 :: U 0 68 0 lo fe80::2a0:c9ff:fe55:16ae/128 :: U 0 8 0 lo fe80::/10 :: UA 256 0 0 eth0 fe80::/10 :: UA 256 0 0 eth1 fe80::/10 :: UA 256 0 0 sit1 ff02::1/128 ff02::1 UAC 0 4 1 eth0 ff00::/8 :: UA 256 0 0 eth0 ff00::/8 :: UA 256 0 0 eth1 ff00::/8 :: UA 256 0 0 sit1 ::/0 :: U 1 0 0 sit1 --5vNYLRcllDrimb99-- From jch@oleane.net Thu Nov 15 15:18:50 2001 From: jch@oleane.net (Jean-Claude Christophe) Date: Thu, 15 Nov 2001 16:18:50 +0100 Subject: IOS for 2500 In-Reply-To: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> References: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Message-ID: <20011115161850.C24448@oleane.net> > I was browsing the Cisco site, hoping to find a IPv6 IOS release for the > 2500 series router. > But that site is BIG!! I get lost in that place. You may be registered on the CCO to download cisco IOS. Any registered user should know where he can download on the web site. Regards, -- Jean-Claude Christophe / jch@oleane.net From mharrell@bittwiddlers.com Thu Nov 15 15:45:38 2001 From: mharrell@bittwiddlers.com (Matthew Harrell) Date: Thu, 15 Nov 2001 10:45:38 -0500 Subject: Linux route question In-Reply-To: References: <20011115141522.GA26874@bittwiddlers.com> Message-ID: <20011115154538.GA28554@bittwiddlers.com> > I don't think the Linux IPv6 code will forward packets to the default route. > If you want your machine to act as a gateway, you need to set up (more) > specific routes for the destinations you want to deal with. Try adding a > route for 3ffe::/16 and see if that helps at all. Very odd. It worked alright so far. Is this a known thing with Linux or am I doing something wrong? -- Matthew Harrell To err is human, Bit Twiddlers, Inc. to purr feline. mharrell@bittwiddlers.com From cougar@kpnqwest.ee Thu Nov 15 16:49:55 2001 From: cougar@kpnqwest.ee (Marko Veelma) Date: Thu, 15 Nov 2001 18:49:55 +0200 (EET) Subject: IOS for 2500 In-Reply-To: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Message-ID: I asked that in September and that was the answer from Cisco: :: We are still working on a plan to support 12.2T on 2509/2511 platforms.  :: There are some memory constraints that we have to resolve.  We hope to :: have a resolution soon.  --- Cougar Marko Veelma Marko.Veelma@KPNQwest.ee KPNQwest Estonia @ the speed Tel. +372 626 6299 Suur-Karja 13 of light Fax. +372 626 6262 10140 Tallinn http://www.kpnqwest.ee/ From cschuerger@pssconsulting.com Thu Nov 15 16:59:20 2001 From: cschuerger@pssconsulting.com (chris schuerger) Date: Thu, 15 Nov 2001 11:59:20 -0500 Subject: IOS for 2500 Message-ID: I just checked the Cisco site. Looks like the IOS version you want to get your hands on is 12.2T, the page also says IPv6 is only available on IP Plus, Enterprise, or Service Provider IOS images. I'm not really sure what that means. have a look: http://www.cisco.com/warp/public/732/Tech/ipv6/index.shtml thanks, Chris Schuerger -----Original Message----- From: Mithrandir [mailto:mithrandir@skynet.be] Sent: Thursday, November 15, 2001 8:10 AM To: 6bone@ISI.EDU Subject: IOS for 2500 Hello friends of the 6bone I was browsing the Cisco site, hoping to find a IPv6 IOS release for the 2500 series router. But that site is BIG!! I get lost in that place. I can't get the IOS myself but a company I work with can. So, does anyone of you know which latest IOS release I'm looking for? It must support IPv6 ofcourse, and run on a Cisco 2514, 2505 and 2503. If anyone knows the exact name/version of that IOS please let me know. Thank you very much Kind regards Mithrandir Cielen Fddi Institute Belgium From mele@cartel-info.fr Thu Nov 15 17:04:28 2001 From: mele@cartel-info.fr (Laurent Mele) Date: Thu, 15 Nov 2001 18:04:28 +0100 Subject: IOS for 2500 In-Reply-To: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> References: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Message-ID: <20011115180428.W19681@cartel-info.fr> Hi, Cisco had officialy announced ipv6 with IOS 12.2.2T The IOS you are looking for (2501-2525) platforms is : 12.2.4T1 with differents features available : - IP - IP PLUS - REMOTE ACCESS SERVER But cisco does not release his IOS for free :) When you have an access with download rights to the cisco site, you find this IOS with no problems ! According to Mithrandir: > Hello friends of the 6bone > > I was browsing the Cisco site, hoping to find a IPv6 IOS release for the > 2500 series router. > But that site is BIG!! I get lost in that place. > > I can't get the IOS myself but a company I work with can. > So, does anyone of you know which latest IOS release I'm looking for? > It must support IPv6 ofcourse, and run on a Cisco 2514, 2505 and 2503. > > If anyone knows the exact name/version of that IOS please let me know. > > Thank you very much > Kind regards > Mithrandir Cielen > Fddi Institute > Belgium > -- Laurent Mele -- Ingenieur Systeme et reseau Cartel Informatique Mom, somebody's at the door. Coming hon! Hey! I can't see the TV! From andreas@corp.home.net Thu Nov 15 17:08:25 2001 From: andreas@corp.home.net (Andreas Ott) Date: Thu, 15 Nov 2001 09:08:25 -0800 Subject: IOS for 2500 In-Reply-To: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir>; from mithrandir@skynet.be on Thu, Nov 15, 2001 at 02:09:42PM +0100 References: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Message-ID: <20011115090825.B7609@bear.eos.home.net> Hi, On Thu, Nov 15, 2001 at 02:09:42PM +0100, Mithrandir wrote: > I was browsing the Cisco site, hoping to find a IPv6 IOS release for the > 2500 series router. ... > I can't get the IOS myself but a company I work with can. > So, does anyone of you know which latest IOS release I'm looking for? > It must support IPv6 ofcourse, and run on a Cisco 2514, 2505 and 2503. You (theoretically) need a support login to get updates of IOS. Once you are logged in the web pages change their appearance, then go to http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml And you need to know how much RAM you have in your 2500, this is the gating factor for what release/features you are able to run. I pretty much settled for a very early reelase as my 2514 has only 4MB (I really only need to do static routes), I can't run any of the 12.1/12.2 train images, they are hungry for much more memory even with the limited IP feature set. -andreas -- Andreas Ott andreas@excitehome.net Network Architect @Home Network http://www.excitehome.net/ Excite@Home 450 Broadway Street Redwood City, CA 94063-3132 USA phone +1 (650) 556-5460 fax +1 (650) 569-5856 pager +1 (650) 524-8073 From bmanning@ISI.EDU Thu Nov 15 17:11:34 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 15 Nov 2001 09:11:34 -0800 (PST) Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: from "Bruce Campbell" at Nov 15, 2001 12:19:16 PM Message-ID: <200111151711.fAFHBYd06308@zed.isi.edu> % > will come for that, it is not yet here. But the time has come and % > past to be able to register an ipv6 dns server. Case in point that % > this works, ip6.int: % % The nameservers for ip6.int's parent domain, 'int', are not under the % control of NSI, hence these nameservers can delegate 'ip6.int' to (at % least one) IPv6-only nameserver(s). % % -- It is true that INT did allow IPv6 nameservers to be entered. IP6.INT will allow IPv6 nameservers. I understand that some TLD nics will allow IPv6 servers to be entered, JP comes to mind. -- --bill From todd@fries.net Thu Nov 15 17:30:54 2001 From: todd@fries.net (Todd T. Fries) Date: Thu, 15 Nov 2001 11:30:54 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <200111151711.fAFHBYd06308@zed.isi.edu>; from bmanning@ISI.EDU on Thu, Nov 15, 2001 at 09:11:34AM -0800 References: <200111151711.fAFHBYd06308@zed.isi.edu> Message-ID: <20011115113054.W30841@eclipse.fries.net> What would be the most productive course to ask/suggest/pursuade all tld's to allow ipv6 domain name servers? I presume this is a goal of ipv6 deployment initiatives somewhere, if only by inference. I personally am not a fan of political processes and agendas. But I get the distinct impression that to get ipv6 in tld's globally, it will take some polticking. Any action/inaction items anyone knows about? Penned by Bill Manning on Thu, Nov 15, 2001 at 09:11:34AM -0800, we have: | % > will come for that, it is not yet here. But the time has come and | % > past to be able to register an ipv6 dns server. Case in point that | % > this works, ip6.int: | % | % The nameservers for ip6.int's parent domain, 'int', are not under the | % control of NSI, hence these nameservers can delegate 'ip6.int' to (at | % least one) IPv6-only nameserver(s). | % | % -- | | It is true that INT did allow IPv6 nameservers to be entered. | IP6.INT will allow IPv6 nameservers. I understand that some | TLD nics will allow IPv6 servers to be entered, JP comes to | mind. | | -- | --bill -- Todd Fries .. todd@fries.net From bmanning@ISI.EDU Thu Nov 15 17:57:52 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 15 Nov 2001 09:57:52 -0800 (PST) Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <20011115113054.W30841@eclipse.fries.net> from "Todd T. Fries" at Nov 15, 2001 11:30:54 AM Message-ID: <200111151757.fAFHvqj06399@zed.isi.edu> based on a brief mtg @ IETF last year, a few of the registries, including NSI indicated that they had support for registration of IPv6 "hosts" as nameservers in the planning process. For some, this winodw is short, for others, there are longer term implications for adding this change. % % What would be the most productive course to ask/suggest/pursuade all tld's % to allow ipv6 domain name servers? I presume this is a goal of ipv6 % deployment initiatives somewhere, if only by inference. I personally % am not a fan of political processes and agendas. But I get the distinct % impression that to get ipv6 in tld's globally, it will take some polticking. % % Any action/inaction items anyone knows about? % % Penned by Bill Manning on Thu, Nov 15, 2001 at 09:11:34AM -0800, we have: % | % > will come for that, it is not yet here. But the time has come and % | % > past to be able to register an ipv6 dns server. Case in point that % | % > this works, ip6.int: % | % % | % The nameservers for ip6.int's parent domain, 'int', are not under the % | % control of NSI, hence these nameservers can delegate 'ip6.int' to (at % | % least one) IPv6-only nameserver(s). % | % % | % -- % | % | It is true that INT did allow IPv6 nameservers to be entered. % | IP6.INT will allow IPv6 nameservers. I understand that some % | TLD nics will allow IPv6 servers to be entered, JP comes to % | mind. % | % | -- % | --bill % % -- % Todd Fries .. todd@fries.net % -- --bill From pgrosset@cisco.com Thu Nov 15 18:19:20 2001 From: pgrosset@cisco.com (Patrick Grossetete) Date: Thu, 15 Nov 2001 19:19:20 +0100 Subject: IOS for 2500 In-Reply-To: References: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> Message-ID: <4.3.2.7.2.20011115191842.017e0100@europe.cisco.com> It is now officially supported on Cisco IOS 12.2(4)T IP Plus image, available on CCO. Regards Patrick At 06:49 PM 15-11-01 +0200, Marko Veelma wrote: >I asked that in September and that was the answer from Cisco: > >:: We are still working on a plan to support 12.2T on 2509/2511 platforms. >:: There are some memory constraints that we have to resolve. We hope to >:: have a resolution soon. > >--- >Cougar > > Marko Veelma Marko.Veelma@KPNQwest.ee > KPNQwest Estonia @ the speed Tel. +372 626 6299 > Suur-Karja 13 of light Fax. +372 626 6262 > 10140 Tallinn http://www.kpnqwest.ee/ ____________________________________________ Patrick Grossetete Cisco Systems Internet Technology Division (ITD) - Product Manager Phone/Vmail: 33.1.58.04.61.52 Fax: 33.1.58.04.61.00 mobile: 33.6.89.10.81.28 Email:pgrosset@cisco.com 11 Rue Camille Desmoulins 92782 Issy les Moulineaux Cedex 9 France ____________________________________________ From lists@geminis.myip.org Thu Nov 15 18:31:24 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Thu, 15 Nov 2001 15:31:24 -0300 (ART) Subject: Linux route question In-Reply-To: <20011115141522.GA26874@bittwiddlers.com> Message-ID: Matthew, just add a route to 2000::/3 pointing thru your sit device in your gateway. That will fix it. Linux doesn't like default routes in IPv6, that's all. /sbin/ip route add 2000::/3 dev sitX (where X is the number for your tunnel) Regards, Flavio. On Thu, 15 Nov 2001, Matthew Harrell wrote: > > I'm currently setting up one of the /48 networks from freenet6 and I'm having > some routing issues with my machines behind my tunnel endpoint. > > The network looks like > > 192.168.10. network <-> my ipv6 gateway <-> freenet6 ipv6 gateway > > I can do everything from my gateway and from the outside I can access all > the machines on my network with ipv6 addresses. The problem is that when > I try something like a ping from one of the internal machines I get > > {26}: ping6 -n www.kame.net > PING www.kame.net(2001:200:0:4819:280:adff:fe71:81fc) from 3ffe:b80:411:1:250:4ff:fed6:1907 : 56 data bytes > From 3ffe:b80:411:1::1 icmp_seq=1 Destination unreachable: Address unreachable > From 3ffe:b80:411:1::1 icmp_seq=2 Destination unreachable: Address unreachable > --- www.kame.net ping statistics --- > 2 packets transmitted, 0 received, +2 errors, 100% loss, time 1003ms > > It actually worked at one point for a minute or two but I haven't been able > to get the behavior back again. I can ping all local ipv6 addresses on my > gateway from one of the 192.168.10 machines but get the error above trying > to ping anything beyond my machine. Seems like a route issue to me but I'm > not familiar enough with ipv6 to realize what route I'm missing. I've attached > the ifconfig and route info from my gateway below. I would have though the > ::/0 route in there would have taken care of things. > > thanks for any help > > From pekkas@netcore.fi Thu Nov 15 19:18:49 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Thu, 15 Nov 2001 21:18:49 +0200 (EET) Subject: Linux route question In-Reply-To: <20011115154538.GA28554@bittwiddlers.com> Message-ID: On Thu, 15 Nov 2001, Matthew Harrell wrote: > > I don't think the Linux IPv6 code will forward packets to the default route. > > If you want your machine to act as a gateway, you need to set up (more) > > specific routes for the destinations you want to deal with. Try adding a > > route for 3ffe::/16 and see if that helps at all. > > Very odd. It worked alright so far. Is this a known thing with Linux or am > I doing something wrong? Known issue. Default route was designed not to work for forwarded packets. I suggest using 2000::/3 for now, that includes 3ffe::/16. This may be changed in the future. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From kirk@thebollingers.net Thu Nov 15 19:29:02 2001 From: kirk@thebollingers.net (kirk@thebollingers.net) Date: Thu, 15 Nov 2001 11:29:02 -0800 (PST) Subject: IOS for 2500 In-Reply-To: <20011115090825.B7609@bear.eos.home.net> Message-ID: How about just for tesing - ie a couple rip routes - and using v6telnet from router to router??? Will the image boot and be functional - just not ready for anything but a lab?? -kirk On Thu, 15 Nov 2001, Andreas Ott wrote: > Hi, > On Thu, Nov 15, 2001 at 02:09:42PM +0100, Mithrandir wrote: > > I was browsing the Cisco site, hoping to find a IPv6 IOS release for the > > 2500 series router. > ... > > I can't get the IOS myself but a company I work with can. > > So, does anyone of you know which latest IOS release I'm looking for? > > It must support IPv6 ofcourse, and run on a Cisco 2514, 2505 and 2503. > > You (theoretically) need a support login to get updates of IOS. Once you > are logged in the web pages change their appearance, then go to > http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml > > And you need to know how much RAM you have in your 2500, this is the gating > factor for what release/features you are able to run. I pretty much settled > for a very early reelase as my 2514 has only 4MB (I really only need to do > static routes), I can't run any of the 12.1/12.2 train images, they are > hungry for much more memory even with the limited IP feature set. > > -andreas > From lists@geminis.myip.org Thu Nov 15 19:41:37 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Thu, 15 Nov 2001 16:41:37 -0300 (ART) Subject: Linux route question In-Reply-To: <20011115184034.GA2721@bittwiddlers.com> Message-ID: On Thu, 15 Nov 2001, Matthew Harrell wrote: > Can I ask a quick routing question of you? Does the 2000::/3 work because > you're matching traffic that starts with 001 (in binary)? Are there any yes, it matchs whatever that starts with binary 001. > destinations outside of 001 that I would currently have to worry about? I'm > only just getting into this so I'm not very familiar with the network > designations. None, AFAIK. from pTLA formats document: The original TLA and NLA ID-s as specified in [AGGR] are as follows: | 3 | 13 | 32 | 16 | 64 bits | +---+-----+---------------------+--------+-----------------+ |001| TLA | NLA ID | SLA ID | Interface ID | +---+-----+---------------------+--------+-----------------+ ... Additionally: Therefore, the first 12-bits of the NLA ID space are assigned as the pTLA that defines the top level of aggegation (backbone) for the 6bone. This would eventually provide for 4096 6bone backbone networks, or pTLA-s, and leaves a 20-bit pNLA ID for each pTLA to assign as needed. | 16 | 12 | 20 | 16 | 64 bits | +-+---------+-------+-----------+--------+-----------------+ | 0x3FFE | pTLA | pNLA | SLA ID | Interface ID | +-+---------+-------+-----------+--------+-----------------+ Sample IPv6 address: 3FFE:8000:0001/48 6bone _|||| |||| ||||___site |||| | b/b site____|||| | | | transit________|_| Regards, Flavio. From bmanning@ISI.EDU Thu Nov 15 20:03:23 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 15 Nov 2001 12:03:23 -0800 (PST) Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <20011115113054.W30841@eclipse.fries.net> from "Todd T. Fries" at Nov 15, 2001 11:30:54 AM Message-ID: <200111152003.fAFK3NU06689@zed.isi.edu> Well, I've been gently hounding folk for a little while and have been doing impromptu surveys. If folks think it would be productive, I'll be a bit more proactive and start publishing results. Interest? --------------------------------------------------------- % % What would be the most productive course to ask/suggest/pursuade all tld's % to allow ipv6 domain name servers? I presume this is a goal of ipv6 % deployment initiatives somewhere, if only by inference. I personally % am not a fan of political processes and agendas. But I get the distinct % impression that to get ipv6 in tld's globally, it will take some polticking. % % Any action/inaction items anyone knows about? % % Penned by Bill Manning on Thu, Nov 15, 2001 at 09:11:34AM -0800, we have: % | % > will come for that, it is not yet here. But the time has come and % | % > past to be able to register an ipv6 dns server. Case in point that % | % > this works, ip6.int: % | % % | % The nameservers for ip6.int's parent domain, 'int', are not under the % | % control of NSI, hence these nameservers can delegate 'ip6.int' to (at % | % least one) IPv6-only nameserver(s). % | % % | % -- % | % | It is true that INT did allow IPv6 nameservers to be entered. % | IP6.INT will allow IPv6 nameservers. I understand that some % | TLD nics will allow IPv6 servers to be entered, JP comes to % | mind. % | % | -- % | --bill % % -- % Todd Fries .. todd@fries.net % -- --bill From paitken@cisco.com Thu Nov 15 20:30:24 2001 From: paitken@cisco.com (Paul Aitken) Date: Thu, 15 Nov 2001 20:30:24 +0000 Subject: IOS for 2500 - roundup References: Message-ID: <3BF425E0.995500D@cisco.com> Thanks to everyone for their input on the 2500 issue. There are several points I'd like to follow up. Marko Veelma wrote: > > I asked that in September and that was the answer from Cisco: > > :: We are still working on a plan to support 12.2T on 2509/2511 platforms. > :: There are some memory constraints that we have to resolve. We hope to > :: have a resolution soon. Some of the 12.2(2)T images were too big for the 2500 platform, so none were released while we considered what to do. Most of the 12.2(4)T images are also too big, but realising how popular this platform is for experimenting with IPv6, we managed to release the IP PLUS image. This is great if you're just learning about IPv6, but if you're serious about IPv6 you should upgrade your hardware ;) chris schuerger wrote: > > I just checked the Cisco site. Looks like the IOS version you want to > get your hands on is 12.2T, IPv6 was introduced in 12.2(2)T, so you need a version not older than that - which for now means 12.2(2)T, 12.2(2)T1, 12.2(4)T or 12.2(4)T1. > the page also says IPv6 is only available on > IP Plus, Enterprise, or Service Provider IOS images. I'm not really > sure what that means. It means that not all images include IPv6 functionality. If you use the Cisco IOS Upgrade Planner at http://www.cisco.com/go/iosplanner, you'll see all possible images including those with IPv6 support and those without. On the other hand, if you use Cisco Feature Navigator at http://www.cisco.com/go/fn and search for "IPv6", you'll only be shown images that include IPv6 support. > have a look: http://www.cisco.com/warp/public/732/Tech/ipv6/index.shtml Or more memorably, http://www.cisco.com/ipv6 -- Paul Aitken IPv6 Development, Cisco Systems Ltd, Edinburgh, Scotland. EH6 6LX From todd@fries.net Thu Nov 15 21:08:24 2001 From: todd@fries.net (Todd T. Fries) Date: Thu, 15 Nov 2001 15:08:24 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <200111152003.fAFK3NU06689@zed.isi.edu>; from bmanning@ISI.EDU on Thu, Nov 15, 2001 at 12:03:23PM -0800 References: <20011115113054.W30841@eclipse.fries.net> <200111152003.fAFK3NU06689@zed.isi.edu> Message-ID: <20011115150824.X30841@eclipse.fries.net> By all means. In my understanding, anything that would help get ipv6 deployed would help get ipv6 deployed. Penned by Bill Manning on Thu, Nov 15, 2001 at 12:03:23PM -0800, we have: | Well, I've been gently hounding folk for a little while and have been | doing impromptu surveys. If folks think it would be productive, I'll | be a bit more proactive and start publishing results. Interest? -- Todd Fries .. todd@fries.net From killyeon@yahoo.com Fri Nov 16 03:39:58 2001 From: killyeon@yahoo.com (killyeon kim) Date: Thu, 15 Nov 2001 19:39:58 -0800 (PST) Subject: "Bad Request" while access httpd with IPv6 server address Message-ID: <20011116033958.90561.qmail@web13705.mail.yahoo.com> Hello. I have installed apache 1.3.19 with ipv6 enable. And the server's IPv6 address is 3ffe:2e01:2:1::2 in our local testbed. But when I access with http://[3ffe:2e01:2:1::2], "400 Bad Request. Your browser sent a request that this server could not understand. Client sent malfored Host header <<3ffe:2e01:2:1::2>>. And in the server's log file, there is error message like [Fri. Nov 16 12:28:41 2001] [error] [client 3ffe:2e01:2:1::1] Client sent malfored Host header <<3ffe:2e01:2:1::2>> But if I add the follwing line to /etc/hosts and access the server with http://ipv6-server, it works well. 3ffe:2e01:2:1::2 ipv6-server And web browser I used is mozilla 0.9.5. Please give me any help. I try to solve this problem for a few days, but I can't get the answer. __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com From aridaman kaushik" hi all, I have a doubt about site concept in ipv6. We are implementing isis rouing protocol for ipv6. 1. Can we map area in isis to site. 2. is it possible to have two or three areas belongs to the same site. thanks in advance ari From mithrandir@skynet.be Fri Nov 16 07:52:16 2001 From: mithrandir@skynet.be (Mithrandir) Date: Fri, 16 Nov 2001 08:52:16 +0100 Subject: Thank you all Message-ID: <008201c16e73$abb2ca00$5f01a8c0@Mithrandir> Thank you all for your input and help. Thanks to you i found the correct images for the 2500 series router. Thanks again Greetings Mithrandir From killyeon@yahoo.com Fri Nov 16 08:47:33 2001 From: killyeon@yahoo.com (killyeon kim) Date: Fri, 16 Nov 2001 00:47:33 -0800 (PST) Subject: "Bad Request" while access web server with IPv6 address In-Reply-To: Message-ID: <20011116084733.20474.qmail@web13704.mail.yahoo.com> I have an IPv6 dns server. I registered the IPv6 www server in the forward zone. And the web server works well when I use the web server's v6 domain name. But I really hope to know why I've got an error message when I access the server with IPv6 address like http://[3ffe:2e01:2:1::2] If someone solve this problem, please give me the answer. Thanks in advance. --- "Carla P. Quiblat" wrote: > > Hi there. > This happened to me before too but it just did not > work > so I worked on having a working DNS (bind 9.1.2) > that > speaks IPv6 first so I don't have to explicitly > write > the IPv6 addresses on the browser. Do you have IPv6 > dns working already? > > carla > > On Thu, 15 Nov 2001, killyeon kim wrote: > > > Hello. > > > > I have installed apache 1.3.19 with ipv6 enable. > And > > the server's IPv6 address is 3ffe:2e01:2:1::2 in > our > > local testbed. > > But when I access with http://[3ffe:2e01:2:1::2], > "400 > > Bad Request. Your browser sent a request that > this > > server could not understand. Client sent malfored > Host > > header <<3ffe:2e01:2:1::2>>. And in the server's > log > > file, there is error message like > > [Fri. Nov 16 12:28:41 2001] [error] [client > > 3ffe:2e01:2:1::1] Client sent malfored Host header > > <<3ffe:2e01:2:1::2>> > > > > But if I add the follwing line to /etc/hosts and > > access the server with http://ipv6-server, it > works > > well. > > 3ffe:2e01:2:1::2 ipv6-server > > And web browser I used is mozilla 0.9.5. > > > > Please give me any help. I try to solve this > problem > > for a few days, but I can't get the answer. > > > > > > __________________________________________________ > > Do You Yahoo!? > > Find the one for you at Yahoo! Personals > > http://personals.yahoo.com > > > __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com From paitken@cisco.com Fri Nov 16 11:17:20 2001 From: paitken@cisco.com (Paul Aitken) Date: Fri, 16 Nov 2001 11:17:20 +0000 Subject: "Bad Request" while access web server with IPv6 address References: <20011116084733.20474.qmail@web13704.mail.yahoo.com> Message-ID: <3BF4F5C0.FF5A85EE@cisco.com> killyeon kim wrote: > > I have an IPv6 dns server. I registered the IPv6 www > server in the forward zone. And the web server works > well when I use the web server's v6 domain name. > > But I really hope to know why I've got an error > message when I access the server with IPv6 address > like http://[3ffe:2e01:2:1::2] > If someone solve this problem, please give me the > answer. > Thanks in advance. It'd help if you told us which web browser you are using? ;) For example, if you're using Internet Explorer on Windows XP, go here: http://www.microsoft.com/WINDOWSXP/pro/techinfo/administration/ipv6/default.asp. Near the end there's this question: "Q. How can I force IPv6 connections using my Web browser?" Part of the answer is: "URLs that use the format for literal IPv6 addresses described in RFC 2732, "Format for Literal IPv6 Addresses in URLs" are not supported by the version of Internet Explorer provided with Windows XP." If your browser doesn't support RFC 2732, you'll have to map all your server names in DNS. Is that so hard? -- Paul Aitken IPv6 Development, Cisco Systems Ltd, Edinburgh, Scotland. EH6 6LX From fink@es.net Fri Nov 16 14:35:44 2001 From: fink@es.net (Bob Fink) Date: Fri, 16 Nov 2001 06:35:44 -0800 Subject: 6bone pTLA 3FFE:82B0::/28 allocated to WEBONLINE-NET Message-ID: <5.1.0.14.0.20011116063254.00abc660@imap2.es.net> WEBONLINE-NET has been allocated pTLA 3FFE:82B0::/28 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: [To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to either bmanning@isi.edu or hostmaster@ep.net.] Thanks, Bob From todd@fries.net Fri Nov 16 16:50:46 2001 From: todd@fries.net (Todd T. Fries) Date: Fri, 16 Nov 2001 10:50:46 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <00ef01c16d30$eaa4a100$b94a2780@6140>; from jorgen@hovland.cx on Wed, Nov 14, 2001 at 06:22:19PM +0100 References: <20011114070208.E30841@eclipse.fries.net> <00ef01c16d30$eaa4a100$b94a2780@6140> Message-ID: <20011116105046.B8761@eclipse.fries.net> I want one dns server in my domain (fries.net) to be registered using an AAAA record, not an A record. Yes, this is one small detail in the global scope of deploying ipv6. So why wait when this is just sitting around not being attended to? Penned by Jørgen Hovland on Wed, Nov 14, 2001 at 06:22:19PM +0100, we have: | What is the problem? | | Buy a domain which has ipv6 nameservers? Just put IN NS to a host you control that has ipv6. | Want netsol to host it? | Want the NS' of the tld to have ipv6 nameservers? | | | -j | | ----- Original Message ----- | From: "Todd T. Fries" | To: ; <6bone@ISI.EDU> | Sent: Wednesday, November 14, 2001 2:02 PM | Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] | | | > Anyone know of another registrar that supports this? | > | > ----- Forwarded message from Network Solutions ----- | > | > From: Network Solutions | > To: "'todd@fries.net'" | > Subject: Service Request Number: 1-UX4DN | > Date: Tue, 13 Nov 2001 19:48:27 -0600 | > | > Dear Todd Fries | > | > Thank you for your inquiry received on 11/1/01 1:39:31 AM. | > | > We do not currently support these new ipv6 dns servers. At this time there | > is no estimated date on when we will support them. | > | > If you need to contact us in the future about this inquiry, please provide | > number 1-UX4DN to our customer service representative. | > | > Thank you for choosing Network Solutions. | > | > Sincerely, | > | > NADELE001 | > Customer Service Representative | > Network Solutions, Inc. | > www.networksolutions.com | > | > Please do not reply directly to this email address. Replies sent to this | > email address will not be responded to. To reach Network Solutions, please | > visit our web site at www.networksolutions.com or send an email to | > help@networksolutions.com. Thank you. | > | > ----- End forwarded message ----- | > | > -- | > Todd Fries .. todd@fries.net -- Todd Fries .. todd@fries.net From todd@fries.net Fri Nov 16 16:59:51 2001 From: todd@fries.net (Todd T. Fries) Date: Fri, 16 Nov 2001 10:59:51 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <20011116105046.B8761@eclipse.fries.net>; from todd@fries.net on Fri, Nov 16, 2001 at 10:50:46AM -0600 References: <20011114070208.E30841@eclipse.fries.net> <00ef01c16d30$eaa4a100$b94a2780@6140> <20011116105046.B8761@eclipse.fries.net> Message-ID: <20011116105951.C8761@eclipse.fries.net> Penned by Todd T. Fries on Fri, Nov 16, 2001 at 10:50:46AM -0600, we have: | I want one dns server in my domain (fries.net) to be registered using an AAAA | record, not an A record. | | Yes, this is one small detail in the global scope of deploying ipv6. So | why wait when this is just sitting around not being attended to? Hmm, perhaps that was abit strongly worded. How about I replace 'this is just ..' with 'this is not possible yet?' .. since I understand Bill has done some preliminary work on this. -- Todd Fries .. todd@fries.net From todd@fries.net Fri Nov 16 21:29:19 2001 From: todd@fries.net (Todd T. Fries) Date: Fri, 16 Nov 2001 15:29:19 -0600 Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] In-Reply-To: <3BF58141.D4E41BD2@uswest.com>; from bdrhoad@uswest.com on Fri, Nov 16, 2001 at 03:12:33PM -0600 References: <20011114070208.E30841@eclipse.fries.net> <00ef01c16d30$eaa4a100$b94a2780@6140> <20011116105046.B8761@eclipse.fries.net> <3BF58141.D4E41BD2@uswest.com> Message-ID: <20011116152919.F30841@eclipse.fries.net> Um, I think you are missing the point here. By 'register a v6 dns server' I mean not the technical capability to set one up. I already have this: todd:26$ host -t any ns6.fries.net 3ffe:b00:4004:1::1:6| egrep -v "mail|Trunc > Using domain server: Name: 3ffe:b00:4004:1::1:6 Address: 3ffe:b00:4004:1::1:6#53 Aliases: ns6.fries.net. has AAAA address 3ffe:b00:4004:1::1:6 ns6.fries.net. host information "IPv6 only" "bind9" ns6.fries.net. text "ns6.fries.net NS?????-HST (host handle)" ns6.fries.net. text "how do I get internic to register an ipv6 dns server?" todd:27$ ... and I have had this setup for quite some time. What I am suggesting is that internic will not allow me to register a v6 dns server for the domain fries.net in their database which then allows me to see this server in the following output: todd:27$ dig @a.gtld-servers.net fries.net ; <<>> DiG 9.1.3 <<>> @a.gtld-servers.net fries.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47493 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 6 ;; QUESTION SECTION: ;fries.net. IN A ;; AUTHORITY SECTION: fries.net. 172800 IN NS NS.SIGMASOFT.COM. fries.net. 172800 IN NS NS1.fries.net. fries.net. 172800 IN NS NS0.fries.net. fries.net. 172800 IN NS NS1.THOUGHTPROCESS.net. fries.net. 172800 IN NS NS1.MISN.COM. fries.net. 172800 IN NS GOOBER.MRLENG.COM. ;; ADDITIONAL SECTION: NS.SIGMASOFT.COM. 172800 IN A 198.144.202.98 NS1.fries.net. 172800 IN A 206.30.141.11 NS0.fries.net. 172800 IN A 206.30.141.10 NS1.THOUGHTPROCESS.net. 172800 IN A 64.240.158.3 NS1.MISN.COM. 172800 IN A 64.240.20.10 GOOBER.MRLENG.COM. 172800 IN A 64.217.3.234 ;; Query time: 57 msec ;; SERVER: 192.5.6.30#53(a.gtld-servers.net) ;; WHEN: Fri Nov 16 15:43:48 2001 ;; MSG SIZE rcvd: 273 todd:28$ As of this moment, to my understanding, they only allow 'A' records not 'AAAA' records in the toplevel domain name servers. Penned by Bradley D. Rhoades on Fri, Nov 16, 2001 at 03:12:33PM -0600, we have: | | | "Todd T. Fries" wrote: | > | > I want one dns server in my domain (fries.net) to be registered using an AAAA | > record, not an A record. | > | > Yes, this is one small detail in the global scope of deploying ipv6. So | > why wait when this is just sitting around not being attended to? | | It seems to be working fine with Bind under FreeBSD. I am running Bind | 8, but I believe you need Bind 9 to perform native IPv6 DNS querys. I | believe that is what you are actually looking for. I assume OpenBSD | should work the same. | | % nslookup | Default Server: horton.iaces.com | Address: 204.147.87.98 | | > server ns1.uswest.net. | Default Server: ns1.uswest.net | Address: 204.147.80.5 | | > set type=any | > ipv6.iaces.com. | Server: ns1.uswest.net | Address: 204.147.80.5 | | Non-authoritative answer: | ipv6.iaces.com nameserver = badroads.iaces.com | ipv6.iaces.com nameserver = horton.iaces.com | ipv6.iaces.com nameserver = badroads.ipv6.iaces.com | | Authoritative answers can be found from: | ipv6.iaces.com nameserver = badroads.iaces.com | ipv6.iaces.com nameserver = horton.iaces.com | ipv6.iaces.com nameserver = badroads.ipv6.iaces.com | badroads.iaces.com internet address = 207.108.70.2 | horton.iaces.com internet address = 204.147.87.98 | badroads.ipv6.iaces.com IPv6 address = | 3ffe:c00:8031:1:220:e0ff:fe62:e472 | > horton.503: named -v | named 8.2.4-REL Thu Sep 27 10:22:14 CDT 2001 | root@horton.iaces.com:/src/obj/src/src/usr.sbin/named | | | And here is what my /etc/named.boot file looks like: | | $ORIGIN iaces.com. | ipv6 86400 IN SOA badroads.iaces.com. | postmaster.iaces.com. ( | 2001111302 | 3600 | 1800 | 604800 | 86400 ) | 86400 IN NS badroads.iaces.com. | 86400 IN NS horton.iaces.com. | 86400 IN NS badroads.ipv6.iaces.com. | 86400 IN A 207.108.70.2 | 86400 IN A 204.147.87.98 | 86400 IN AAAA 3ffe:c00:8031:1:220:e0ff:fe62:e472 | | | Brad | | > | > Penned by Jørgen Hovland on Wed, Nov 14, 2001 at 06:22:19PM +0100, we have: | > | What is the problem? | > | | > | Buy a domain which has ipv6 nameservers? Just put IN NS to a host you control that has ipv6. | > | Want netsol to host it? | > | Want the NS' of the tld to have ipv6 nameservers? | > | | > | | > | -j | > | | > | ----- Original Message ----- | > | From: "Todd T. Fries" | > | To: ; <6bone@ISI.EDU> | > | Sent: Wednesday, November 14, 2001 2:02 PM | > | Subject: [custserv@netsol.com: Service Request Number: 1-UX4DN] | > | | > | | > | > Anyone know of another registrar that supports this? | > | > | > | > ----- Forwarded message from Network Solutions ----- | > | > | > | > From: Network Solutions | > | > To: "'todd@fries.net'" | > | > Subject: Service Request Number: 1-UX4DN | > | > Date: Tue, 13 Nov 2001 19:48:27 -0600 | > | > | > | > Dear Todd Fries | > | > | > | > Thank you for your inquiry received on 11/1/01 1:39:31 AM. | > | > | > | > We do not currently support these new ipv6 dns servers. At this time there | > | > is no estimated date on when we will support them. | > | > | > | > If you need to contact us in the future about this inquiry, please provide | > | > number 1-UX4DN to our customer service representative. | > | > | > | > Thank you for choosing Network Solutions. | > | > | > | > Sincerely, | > | > | > | > NADELE001 | > | > Customer Service Representative | > | > Network Solutions, Inc. | > | > www.networksolutions.com | > | > | > | > Please do not reply directly to this email address. Replies sent to this | > | > email address will not be responded to. To reach Network Solutions, please | > | > visit our web site at www.networksolutions.com or send an email to | > | > help@networksolutions.com. Thank you. | > | > | > | > ----- End forwarded message ----- | > | > | > | > -- | > | > Todd Fries .. todd@fries.net | > | > -- | > Todd Fries .. todd@fries.net Content-Description: Card for Bradley D. Rhoades -- Todd Fries .. todd@fries.net From extml@ndsoftware.net Sat Nov 17 22:05:59 2001 From: extml@ndsoftware.net (NDSoftware) Date: Sat, 17 Nov 2001 23:05:59 +0100 Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? Message-ID: <000301c16fb4$0b0778c0$0104010a@localnet.ndsoftware.net> Hello, I have a problem on a machine (with Linux Debian Woody). I can't ping (or trace) the next router or 6bone from it. Trace 6bone from Woody: traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:8271:2101:1::1, 30 hops max, 16 byte packets 1 ip6-localhost (::1) 2990.86 ms !H 2999.53 ms !H 2999.92 ms ! Routes on Woody: Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 0 0 lo 3ffe:8271:2101:1::1/128 :: U 0 8 1 lo 3ffe:8271:2101:1::/64 :: UA 256 594 0 eth0 2000::/3 :: U 1 0 0 eth0 fe80::2d0:70ff:fe01:811b/128 :: U 0 5 0 lo fe80::/10 :: UA 256 0 0 eth0 ff00::/8 :: UA 256 0 0 eth0 ::/0 fe80::a0:2434:1d91 UGDA 1024 34 0 eth0 Beetween 6bone and Woody i have a router who have my IPv6 over IPv4 tunnel, this router work without problem and Potato (eth1) connected on it too. Only Woody (eth2) don't work. Routes on Router: Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 4 0 lo ::10.0.0.1/128 :: U 0 0 0 lo ::10.0.2.1/128 :: U 0 0 0 lo ::10.0.10.1/128 :: U 0 0 0 lo ::62.4.18.114/128 :: U 0 0 0 lo ::62.4.22.213/128 :: U 0 0 0 lo ::127.0.0.1/128 :: U 0 0 0 lo ::/96 :: U 256 0 0 sit0 2000::/16 fe80::d5ba:2246 UG 1 0 0 sit1 2001::/16 fe80::d5ba:2246 UG 1 0 0 sit1 2002::/16 fe80::d5ba:2246 UG 1 0 0 sit1 3ffe:8271:1000:20::1/128 :: U 0 0 0 lo 3ffe:8271:1000:20::/64 :: UA 256 0 0 eth0 3ffe:8271:1000:21::1/128 :: U 0 89080 0 lo 3ffe:8271:1000:21::/64 :: UA 256 0 0 eth1 3ffe:8271:1000:22::1/128 :: U 0 21 0 lo 3ffe:8271:1000:22::/64 :: UA 256 0 0 eth2 3ffe:8271:1000:2f::1/128 :: U 0 0 0 lo 3ffe:8271:1000:30::1/128 3ffe:8271:1000:30::1 UC 0 2665 0 eth1 3ffe:8271:1000:30::/64 :: U 1 0 0 eth1 3ffe:8271:1000:3f::/64 :: U 1 0 0 eth1 3ffe:8271:10ff:11::2/128 :: U 0 2162 0 lo 3ffe:8271:10ff:11::/64 :: UA 256 18 1 sit1 3ffe:8271:2101:1::/64 :: U 1 0 0 eth2 3ffe::/16 fe80::d5ba:2246 UG 1 312 0 sit1 fe80::a00:1/128 :: U 0 0 0 lo fe80::a00:201/128 :: U 0 0 0 lo fe80::a00:a01/128 :: U 0 0 0 lo fe80::3e04:1272/128 :: U 0 0 0 lo fe80::3e04:16d5/128 :: U 0 0 0 lo fe80::10:4b44:56cc/128 :: U 0 0 0 lo fe80::60:9795:cc55/128 :: U 0 7082 0 lo fe80::a0:2434:1d91/128 :: U 0 5 0 lo fe80::/10 :: UA 256 0 0 eth0 fe80::/10 :: UA 256 0 0 eth1 fe80::/10 :: UA 256 0 0 eth2 fe80::/10 :: UA 256 0 0 sit1 ff02::1/128 ff02::1 UAC 0 1 1 eth2 ff00::/8 :: UA 256 0 0 eth0 ff00::/8 :: UA 256 0 0 eth1 ff00::/8 :: UA 256 0 0 eth2 ff00::/8 :: UA 256 0 0 sit1 Trace Woody from router: traceroute6 to 3ffe:8271:2101:1::1 (3ffe:8271:2101:1::1) from 3ffe:8271:1000:22::1, 30 hops max, 16 byte packets 1 ip6-localhost (::1) 3004.78 ms !H 3000.65 ms !H 2999.21 ms !H Trace Potato from router: traceroute6 to 3ffe:8271:1000:30::1 (3ffe:8271:1000:30::1) from 3ffe:8271:1000:21::1, 30 hops max, 16 byte packets 1 3ffe:8271:1000:30::1 (3ffe:8271:1000:30::1) 2.279 ms 2.13 ms 1.968 ms With tcpdump i have get this: 21:38:02.882404 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol: who has 3ffe:8271:2101:1::1 21:38:03.882226 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol: who has 3ffe:8271:2101:1::1 Router: Linux 2.2.19 Debian Potato Potato: Linux 2.2.19 Debian Potato Woody: Linux 2.4.13 Debian Woody All machines have last updates. Who can help me ? Any help are Welcome !!!! How i can fix this problem ? Thanks very very much, Best Regards, Nicolas From extml@ndsoftware.net Sat Nov 17 22:41:32 2001 From: extml@ndsoftware.net (NDSoftware) Date: Sat, 17 Nov 2001 23:41:32 +0100 Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? In-Reply-To: <20011117233328.B75519@cicely8.cicely.de> Message-ID: <000401c16fb9$01780400$0104010a@localnet.ndsoftware.net> > -----Original Message----- > From: Bernd Walter [mailto:ipv6@cicely.de] > Sent: Saturday, November 17, 2001 11:33 PM > To: NDSoftware > Cc: 6bone@ISI.EDU; debian-ipv6@lists.debian.org; users@ipv6.org > Subject: Re: ip6-localhost (::1) 2990.86 ms !H -> Why ? > > > On Sat, Nov 17, 2001 at 11:05:59PM +0100, NDSoftware wrote: > > Hello, > > > > I have a problem on a machine (with Linux Debian Woody). > > I can't ping (or trace) the next router or 6bone from it. > > > > > > Trace 6bone from Woody: > > > > traceroute to 6bone.net (3ffe:b00:c18:1::10) from > 3ffe:8271:2101:1::1, > > 30 hops max, 16 byte packets > > 1 ip6-localhost (::1) 2990.86 ms !H 2999.53 ms !H 2999.92 ms ! > > > > Routes on Woody: > > > > Kernel IPv6 routing table > > Destination Next Hop > > Flags Metric Ref Use Iface > > ::1/128 :: > > U 0 0 0 lo > > 3ffe:8271:2101:1::1/128 :: > > U 0 8 1 lo > > 3ffe:8271:2101:1::/64 :: > > UA 256 594 0 eth0 > > This one matches all valid global IPv6 addresses, so your > default route > looses. > > > 2000::/3 :: > > U 1 0 0 eth0 > > fe80::2d0:70ff:fe01:811b/128 :: > > U 0 5 0 lo > > fe80::/10 :: > > UA 256 0 0 eth0 > > ff00::/8 :: > > UA 256 0 0 eth0 > > ::/0 fe80::a0:2434:1d91 > > UGDA 1024 34 0 eth0 > > You need to remove the 2000:/3 route - asuming your ::/0 is right. route -A inet6 add ::/0 dev eth0 And after: traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:8271:2101:1::1, 30 hops max, 16 byte packets 1 ip6-localhost (::1) 2999.48 ms !H I have try too 3ffe::/16, 2001::/16 for default route. Thanks > > -- > B.Walter COSMO-Project > http://www.cosmo-project.de > ticso@cicely.de Usergroup > info@cosmo-project.de > > From lists@geminis.myip.org Sun Nov 18 04:58:19 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Sun, 18 Nov 2001 01:58:19 -0300 (ART) Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? In-Reply-To: <000301c16fb4$0b0778c0$0104010a@localnet.ndsoftware.net> Message-ID: Hi, it looks like you have a route to 3ffe:8271:2101:1::1/128 pointed to your loopback interface: > 3ffe:8271:2101:1::1/128 :: U 0 0 0 lo That's odd and the cause of trouble. Just remove it and the less specific route to 3ffe:8271:2101:1::/64 thru eth0 will be used in your traceroute. Regards, Flavio. On Sat, 17 Nov 2001, NDSoftware wrote: > Hello, > > I have a problem on a machine (with Linux Debian Woody). > I can't ping (or trace) the next router or 6bone from it. > > > Trace 6bone from Woody: > > traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:8271:2101:1::1, > 30 hops max, 16 byte packets > 1 ip6-localhost (::1) 2990.86 ms !H 2999.53 ms !H 2999.92 ms ! > > Routes on Woody: > > Kernel IPv6 routing table > Destination Next Hop > Flags Metric Ref Use Iface > ::1/128 :: > U 0 0 0 lo > 3ffe:8271:2101:1::1/128 :: > U 0 8 1 lo > 3ffe:8271:2101:1::/64 :: > UA 256 594 0 eth0 > 2000::/3 :: > U 1 0 0 eth0 > fe80::2d0:70ff:fe01:811b/128 :: > U 0 5 0 lo > fe80::/10 :: > UA 256 0 0 eth0 > ff00::/8 :: > UA 256 0 0 eth0 > ::/0 fe80::a0:2434:1d91 > UGDA 1024 34 0 eth0 > > Beetween 6bone and Woody i have a router who have my IPv6 over IPv4 > tunnel, this router work without problem and Potato (eth1) connected on > it too. Only Woody (eth2) don't work. > > Routes on Router: > > Kernel IPv6 routing table > Destination Next Hop > Flags Metric Ref Use Iface > ::1/128 :: > U 0 4 0 lo > ::10.0.0.1/128 :: > U 0 0 0 lo > ::10.0.2.1/128 :: > U 0 0 0 lo > ::10.0.10.1/128 :: > U 0 0 0 lo > ::62.4.18.114/128 :: > U 0 0 0 lo > ::62.4.22.213/128 :: > U 0 0 0 lo > ::127.0.0.1/128 :: > U 0 0 0 lo > ::/96 :: > U 256 0 0 sit0 > 2000::/16 fe80::d5ba:2246 > UG 1 0 0 sit1 > 2001::/16 fe80::d5ba:2246 > UG 1 0 0 sit1 > 2002::/16 fe80::d5ba:2246 > UG 1 0 0 sit1 > 3ffe:8271:1000:20::1/128 :: > U 0 0 0 lo > 3ffe:8271:1000:20::/64 :: > UA 256 0 0 eth0 > 3ffe:8271:1000:21::1/128 :: > U 0 89080 0 lo > 3ffe:8271:1000:21::/64 :: > UA 256 0 0 eth1 > 3ffe:8271:1000:22::1/128 :: > U 0 21 0 lo > 3ffe:8271:1000:22::/64 :: > UA 256 0 0 eth2 > 3ffe:8271:1000:2f::1/128 :: > U 0 0 0 lo > 3ffe:8271:1000:30::1/128 3ffe:8271:1000:30::1 > UC 0 2665 0 eth1 > 3ffe:8271:1000:30::/64 :: > U 1 0 0 eth1 > 3ffe:8271:1000:3f::/64 :: > U 1 0 0 eth1 > 3ffe:8271:10ff:11::2/128 :: > U 0 2162 0 lo > 3ffe:8271:10ff:11::/64 :: > UA 256 18 1 sit1 > 3ffe:8271:2101:1::/64 :: > U 1 0 0 eth2 > 3ffe::/16 fe80::d5ba:2246 > UG 1 312 0 sit1 > fe80::a00:1/128 :: > U 0 0 0 lo > fe80::a00:201/128 :: > U 0 0 0 lo > fe80::a00:a01/128 :: > U 0 0 0 lo > fe80::3e04:1272/128 :: > U 0 0 0 lo > fe80::3e04:16d5/128 :: > U 0 0 0 lo > fe80::10:4b44:56cc/128 :: > U 0 0 0 lo > fe80::60:9795:cc55/128 :: > U 0 7082 0 lo > fe80::a0:2434:1d91/128 :: > U 0 5 0 lo > fe80::/10 :: > UA 256 0 0 eth0 > fe80::/10 :: > UA 256 0 0 eth1 > fe80::/10 :: > UA 256 0 0 eth2 > fe80::/10 :: > UA 256 0 0 sit1 > ff02::1/128 ff02::1 > UAC 0 1 1 eth2 > ff00::/8 :: > UA 256 0 0 eth0 > ff00::/8 :: > UA 256 0 0 eth1 > ff00::/8 :: > UA 256 0 0 eth2 > ff00::/8 :: > UA 256 0 0 sit1 > > > Trace Woody from router: > > traceroute6 to 3ffe:8271:2101:1::1 (3ffe:8271:2101:1::1) from > 3ffe:8271:1000:22::1, 30 hops max, 16 byte packets > 1 ip6-localhost (::1) 3004.78 ms !H 3000.65 ms !H 2999.21 ms !H > > Trace Potato from router: > > traceroute6 to 3ffe:8271:1000:30::1 (3ffe:8271:1000:30::1) from > 3ffe:8271:1000:21::1, 30 hops max, 16 byte packets > 1 3ffe:8271:1000:30::1 (3ffe:8271:1000:30::1) 2.279 ms 2.13 ms > 1.968 ms > > With tcpdump i have get this: > 21:38:02.882404 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol: > who has 3ffe:8271:2101:1::1 > 21:38:03.882226 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol: > who has 3ffe:8271:2101:1::1 > > Router: Linux 2.2.19 Debian Potato > Potato: Linux 2.2.19 Debian Potato > Woody: Linux 2.4.13 Debian Woody > All machines have last updates. > > Who can help me ? > Any help are Welcome !!!! > > How i can fix this problem ? > > Thanks very very much, > > Best Regards, > > Nicolas > From pekkas@netcore.fi Sun Nov 18 06:34:54 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Sun, 18 Nov 2001 08:34:54 +0200 (EET) Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? In-Reply-To: <000301c16fb4$0b0778c0$0104010a@localnet.ndsoftware.net> Message-ID: Note: I think linux-net@vger.kernel.org would be the most appropriate place for questions like this.. On Sat, 17 Nov 2001, NDSoftware wrote: > Hello, > > I have a problem on a machine (with Linux Debian Woody). > I can't ping (or trace) the next router or 6bone from it. > > > Trace 6bone from Woody: > > traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:8271:2101:1::1, > 30 hops max, 16 byte packets > 1 ip6-localhost (::1) 2990.86 ms !H 2999.53 ms !H 2999.92 ms ! > > Routes on Woody: > > Kernel IPv6 routing table > Destination Next Hop > Flags Metric Ref Use Iface > ::1/128 :: > U 0 0 0 lo > 3ffe:8271:2101:1::1/128 :: > U 0 8 1 lo > 3ffe:8271:2101:1::/64 :: > UA 256 594 0 eth0 > 2000::/3 :: > U 1 0 0 eth0 The last one is the problem; effectively you're saying all addresses are on-link, and this is better than the default route to your router box. Remove it and the 6bone should work just fine. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From extml@ndsoftware.net Sun Nov 18 09:44:04 2001 From: extml@ndsoftware.net (NDSoftware) Date: Sun, 18 Nov 2001 10:44:04 +0100 Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? In-Reply-To: Message-ID: <000701c17015$90876120$0104010a@localnet.ndsoftware.net> > -----Original Message----- > From: Flavio Villanustre [mailto:lists@geminis.myip.org] > Sent: Sunday, November 18, 2001 5:58 AM > To: NDSoftware > Cc: 6bone@ISI.EDU; debian-ipv6@lists.debian.org; users@ipv6.org > Subject: Re: ip6-localhost (::1) 2990.86 ms !H -> Why ? > > > Hi, > > it looks like you have a route to 3ffe:8271:2101:1::1/128 > pointed to your > loopback interface: > > > > 3ffe:8271:2101:1::1/128 :: U 0 > 0 0 lo > > That's odd and the cause of trouble. Just remove it and the > less specific > route to 3ffe:8271:2101:1::/64 thru eth0 will be used in your > traceroute. route -A inet6 del 3ffe:8271:2101:1::1/128 dev lo SIOCDELRT: No such process I can't remove it. If i add a another ip to eth0 et /128 route for lo will be created :( Thanks > > Regards, > > Flavio. > > > > On Sat, 17 Nov 2001, NDSoftware wrote: > > > Hello, > > > > I have a problem on a machine (with Linux Debian Woody). > > I can't ping (or trace) the next router or 6bone from it. > > > > > > Trace 6bone from Woody: > > > > traceroute to 6bone.net (3ffe:b00:c18:1::10) from > 3ffe:8271:2101:1::1, > > 30 hops max, 16 byte packets > > 1 ip6-localhost (::1) 2990.86 ms !H 2999.53 ms !H 2999.92 ms ! > > > > Routes on Woody: > > > > Kernel IPv6 routing table > > Destination Next Hop > > Flags Metric Ref Use Iface > > ::1/128 :: > > U 0 0 0 lo > > 3ffe:8271:2101:1::1/128 :: > > U 0 8 1 lo > > 3ffe:8271:2101:1::/64 :: > > UA 256 594 0 eth0 > > 2000::/3 :: > > U 1 0 0 eth0 > > fe80::2d0:70ff:fe01:811b/128 :: > > U 0 5 0 lo > > fe80::/10 :: > > UA 256 0 0 eth0 > > ff00::/8 :: > > UA 256 0 0 eth0 > > ::/0 fe80::a0:2434:1d91 > > UGDA 1024 34 0 eth0 > > > > Beetween 6bone and Woody i have a router who have my IPv6 over IPv4 > > tunnel, this router work without problem and Potato (eth1) > connected on > > it too. Only Woody (eth2) don't work. > > > > Routes on Router: > > > > Kernel IPv6 routing table > > Destination Next Hop > > Flags Metric Ref Use Iface > > ::1/128 :: > > U 0 4 0 lo > > ::10.0.0.1/128 :: > > U 0 0 0 lo > > ::10.0.2.1/128 :: > > U 0 0 0 lo > > ::10.0.10.1/128 :: > > U 0 0 0 lo > > ::62.4.18.114/128 :: > > U 0 0 0 lo > > ::62.4.22.213/128 :: > > U 0 0 0 lo > > ::127.0.0.1/128 :: > > U 0 0 0 lo > > ::/96 :: > > U 256 0 0 sit0 > > 2000::/16 fe80::d5ba:2246 > > UG 1 0 0 sit1 > > 2001::/16 fe80::d5ba:2246 > > UG 1 0 0 sit1 > > 2002::/16 fe80::d5ba:2246 > > UG 1 0 0 sit1 > > 3ffe:8271:1000:20::1/128 :: > > U 0 0 0 lo > > 3ffe:8271:1000:20::/64 :: > > UA 256 0 0 eth0 > > 3ffe:8271:1000:21::1/128 :: > > U 0 89080 0 lo > > 3ffe:8271:1000:21::/64 :: > > UA 256 0 0 eth1 > > 3ffe:8271:1000:22::1/128 :: > > U 0 21 0 lo > > 3ffe:8271:1000:22::/64 :: > > UA 256 0 0 eth2 > > 3ffe:8271:1000:2f::1/128 :: > > U 0 0 0 lo > > 3ffe:8271:1000:30::1/128 3ffe:8271:1000:30::1 > > UC 0 2665 0 eth1 > > 3ffe:8271:1000:30::/64 :: > > U 1 0 0 eth1 > > 3ffe:8271:1000:3f::/64 :: > > U 1 0 0 eth1 > > 3ffe:8271:10ff:11::2/128 :: > > U 0 2162 0 lo > > 3ffe:8271:10ff:11::/64 :: > > UA 256 18 1 sit1 > > 3ffe:8271:2101:1::/64 :: > > U 1 0 0 eth2 > > 3ffe::/16 fe80::d5ba:2246 > > UG 1 312 0 sit1 > > fe80::a00:1/128 :: > > U 0 0 0 lo > > fe80::a00:201/128 :: > > U 0 0 0 lo > > fe80::a00:a01/128 :: > > U 0 0 0 lo > > fe80::3e04:1272/128 :: > > U 0 0 0 lo > > fe80::3e04:16d5/128 :: > > U 0 0 0 lo > > fe80::10:4b44:56cc/128 :: > > U 0 0 0 lo > > fe80::60:9795:cc55/128 :: > > U 0 7082 0 lo > > fe80::a0:2434:1d91/128 :: > > U 0 5 0 lo > > fe80::/10 :: > > UA 256 0 0 eth0 > > fe80::/10 :: > > UA 256 0 0 eth1 > > fe80::/10 :: > > UA 256 0 0 eth2 > > fe80::/10 :: > > UA 256 0 0 sit1 > > ff02::1/128 ff02::1 > > UAC 0 1 1 eth2 > > ff00::/8 :: > > UA 256 0 0 eth0 > > ff00::/8 :: > > UA 256 0 0 eth1 > > ff00::/8 :: > > UA 256 0 0 eth2 > > ff00::/8 :: > > UA 256 0 0 sit1 > > > > > > Trace Woody from router: > > > > traceroute6 to 3ffe:8271:2101:1::1 (3ffe:8271:2101:1::1) from > > 3ffe:8271:1000:22::1, 30 hops max, 16 byte packets > > 1 ip6-localhost (::1) 3004.78 ms !H 3000.65 ms !H 2999.21 ms !H > > > > Trace Potato from router: > > > > traceroute6 to 3ffe:8271:1000:30::1 (3ffe:8271:1000:30::1) from > > 3ffe:8271:1000:21::1, 30 hops max, 16 byte packets > > 1 3ffe:8271:1000:30::1 (3ffe:8271:1000:30::1) 2.279 ms 2.13 ms > > 1.968 ms > > > > With tcpdump i have get this: > > 21:38:02.882404 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: > neighbor sol: > > who has 3ffe:8271:2101:1::1 > > 21:38:03.882226 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: > neighbor sol: > > who has 3ffe:8271:2101:1::1 > > > > Router: Linux 2.2.19 Debian Potato > > Potato: Linux 2.2.19 Debian Potato > > Woody: Linux 2.4.13 Debian Woody > > All machines have last updates. > > > > Who can help me ? > > Any help are Welcome !!!! > > > > How i can fix this problem ? > > > > Thanks very very much, > > > > Best Regards, > > > > Nicolas > > > > From lists@geminis.myip.org Sun Nov 18 12:39:16 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Sun, 18 Nov 2001 09:39:16 -0300 (ART) Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? In-Reply-To: <000701c17015$90876120$0104010a@localnet.ndsoftware.net> Message-ID: On Sun, 18 Nov 2001, NDSoftware wrote: Don't use the "route" command. It's deprecated and has been replaced by "ip" command: /sbin/ip -f inet6 route del xxxxxxxxx/yy dev zzz Regards, Flavio. > > route -A inet6 del 3ffe:8271:2101:1::1/128 dev lo > SIOCDELRT: No such process > > I can't remove it. > > If i add a another ip to eth0 et /128 route for lo will be created :( > > Thanks From pekkas@netcore.fi Sun Nov 18 19:56:17 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Sun, 18 Nov 2001 21:56:17 +0200 (EET) Subject: ip6-localhost (::1) 2990.86 ms !H -> Why ? In-Reply-To: Message-ID: On Sun, 18 Nov 2001, Pekka Savola wrote: > On Sun, 18 Nov 2001, NDSoftware wrote: > > Ok, these pings look sane. The problem here was very probably that: 1) router (2.2.x kernel) had been configured with: CONFIG_IPV6 2) woody (2.4.x) kernel had been configured with: [didn't work] CONFIG_IPV6 which for 2.4.x, x > 4 or so, effectively means: CONFIG_IPV6_EUI64 CONFIG_IPV6_NO_PB 3) potato (2.2.18) kernel had been configured with: CONFIG_IPV6 CONFIG_IPV6_EUI64 (possibly) So, in effect the router was only using provider-based addresses, and PB addressing had been removed from Woody as obsolete. Potato was still working because the support appears to have not been removed yet. The problem could be noted by checking which solicited-node multicast addresses had been joined (netstat -g). Rebooting 'router' to a kernel with EUI64 support fixed the problem. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords From fink@es.net Mon Nov 19 15:54:10 2001 From: fink@es.net (Bob Fink) Date: Mon, 19 Nov 2001 07:54:10 -0800 Subject: pTLA request for OXYGEN - review closes 3 December 2001 Message-ID: <5.1.0.14.0.20011119075044.0329df88@imap2.es.net> 6bone Folk, OXYGEN has requested a pTLA allocation. The open review period for this will close 3 December 2001. Please send your comments to me or the list. Thanks, Bob === >Subject: pTLA for OXYGEN >To: fink@es.net >Cc: ipv6@o2.net.tr >From: "BUGRA GUMUS" >Date: Mon, 19 Nov 2001 13:33:37 +0200 > >Hi Bob, > >We would like to apply for a pTLA allocation: > >1. We have been operational since April 2001 > >a) ipv6-site: OXYGEN > >b) tunnel: IPv6 in IPv4 ipv6-gw.ipv6.o2.net.tr -> >sl-bb1-6bone.sprintlink.net SPRINT STATIC > tunnel: IPv6 in IPv4 ipv6-gw.ipv6.o2.net.tr -> rap.viagenie.qc.ca >VIAGENIE BGP4+ > > >c) nameserver is ns1.o2.net.tr > >d) www.ipv6.o2.net.tr (3ffe:2900:a00d:1::2) > >2. We are TR based ISP, We have ethernet connection to our IPv6 servers and >we are at same location with our IPv6 servers. We have software development >team ; and we want to develop IPv6 applications as well. You can see our >products at www.o2.com.tr web page. > >a) We have three people registered in the database as contacts for ipv6 >related queries. > >b) ipv6@o2.net.tr common mailbox of us. > >3. Our brother company TELSIM GSM A.S is one of the biggest GSM company of >TURKEY ; for GPRS test purposes they will request IPv6 addresses over us. >And >We want to deploy 3G services all over TURKEY. > >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. -end From bdrhoad@badroads.iaces.com Mon Nov 19 22:31:04 2001 From: bdrhoad@badroads.iaces.com (Bradley D. Rhoades) Date: Mon, 19 Nov 2001 16:31:04 -0600 (CST) Subject: Native IPv6 SMTP testing. Message-ID: <200111192231.fAJMV4s01021@badroads.iaces.com> I tried searching for this info in the 6bone archives, but the search tool is broken (http://www.wcug.wwu.edu/lists/6bone). I have configured my system to support inet and inet6 smtp connections. I am hoping to do some very simple email exchanges with a few sites to verify basic functionality. If your interested, drop me a note. Thanks, Brad From lists@geminis.myip.org Tue Nov 20 11:34:25 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Tue, 20 Nov 2001 08:34:25 -0300 (ART) Subject: Native IPv6 SMTP testing. In-Reply-To: <200111192231.fAJMV4s01021@badroads.iaces.com> Message-ID: Interested! What about distribution of 6bone mailing list thru ipv6 smpt? Regards, Flavio. On Mon, 19 Nov 2001, Bradley D. Rhoades wrote: > > I tried searching for this info in the 6bone archives, but the > search tool is broken (http://www.wcug.wwu.edu/lists/6bone). > > I have configured my system to support inet and inet6 smtp connections. > I am hoping to do some very simple email exchanges with a few sites to > verify basic functionality. > > If your interested, drop me a note. > > Thanks, > > Brad > From paitken@cisco.com Tue Nov 20 14:48:26 2001 From: paitken@cisco.com (Paul Aitken) Date: Tue, 20 Nov 2001 14:48:26 +0000 Subject: IOS for 2500 References: <003001c16dd6$d222a7c0$5f01a8c0@Mithrandir> <3BF3CB6F.91F6A80B@cisco.com> <20011119201119.A8478@snew.com> Message-ID: <3BFA6D3A.F3B81FD8@cisco.com> Chuck Yerkes wrote: > > How about an image for the 2500 that doesn't have that crufty > old IPv4 stuff? > > Just a nice clean IPv6 image. Chuck, Given the choice of adding new IPv6 features or removing old IPv4 ones, which would you chose? Right now our top priority is to impliment all the IPv6 features that our customers want. After all, we can hardly make a selling point of "less IPv4 features!", can we? ;) I'm sure that IPv6 only (or more likely, IPv6-mostly) routers will emerge in the fullness of time. However, I would be very surprised if the 2500 platform were the target for such a project. Cheers. -- Paul Aitken IPv6 Development, Cisco Systems Ltd, Edinburgh, Scotland. EH6 6LX From lists@geminis.myip.org Tue Nov 20 23:07:18 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Tue, 20 Nov 2001 20:07:18 -0300 (ART) Subject: New 6bone web ring Message-ID: People, I've just created an ipv6 web ring dedicated mainly to IPv6 only sites though dual IPv4/IPv6 could also fit. This web ring can be a good workaround until internet search engines begin supporting IPv6 only sites. It can be a simple/free way of getting sites linked to each other to simplify location of IPv6 only sites. For those interested to add their site to it please see: http://s.webring.com/hub?ring=6bone&id=1&hub or http://flavio.acme.com Regards, Flavio. From lists@geminis.myip.org Wed Nov 21 00:26:30 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Tue, 20 Nov 2001 21:26:30 -0300 (ART) Subject: Native IPv6 SMTP testing. In-Reply-To: <200111192231.fAJMV4s01021@badroads.iaces.com> Message-ID: Could you test sending an e-mail to flavio@flavio.acme.com? It's an IPv6 only SMTP server... Regards, Flavio. On Mon, 19 Nov 2001, Bradley D. Rhoades wrote: > > I tried searching for this info in the 6bone archives, but the > search tool is broken (http://www.wcug.wwu.edu/lists/6bone). > > I have configured my system to support inet and inet6 smtp connections. > I am hoping to do some very simple email exchanges with a few sites to > verify basic functionality. > > If your interested, drop me a note. > > Thanks, > > Brad > From lists@geminis.myip.org Wed Nov 21 10:52:14 2001 From: lists@geminis.myip.org (Flavio Villanustre) Date: Wed, 21 Nov 2001 07:52:14 -0300 (ART) Subject: Native IPv6 SMTP testing. In-Reply-To: <3BFB226F.80BC6B33@dialtone.com> Message-ID: Yes, my mistake. Changed the list of local domains to add flavio.acme.com and went out, without restarting sendmail :-( One of those thinks that make me feel stupid... Please, could you try again? It's fixed now, promised! Thanks and regards, Flavio. On Tue, 20 Nov 2001, John Comeau wrote: > No joy, check sendmail.cw or equivalent on your system... > > The garbage below is due to lag times, I didn't wait for the echo before starting to type the next line... - jc > > [root@ipv6 /root]# telnet6 flavio.acme.com 25 > Trying 3ffe:b80:36b:1:2a0:c9ff:fece:2fd6... > Connected to flavio.acme.com. > Escape character is '^]'. > helop220 localhost.localdomain ESMTP Sendmail 8.11.6/8.11.6; Wed, 21 Nov 2001 00:37:42 -0300 > ipv6 > 250 localhost.localdomain Hello ns.ipv6.dialtone.com [2002:d857:dff0::1], pleased to meet you > mail from: root@ipv6.dialtone.com > rcpt to: 250 2.1.0 root@ipv6.dialtone.com... Sender ok > flavio@flavio.acme.com > 550 5.7.1 flavio@flavio.acme.com... Relaying denied > quit > 221 2.0.0 localhost.localdomain closing connection > Connection closed by foreign host. > > Flavio Villanustre wrote: > > > > Could you test sending an e-mail to flavio@flavio.acme.com? It's an IPv6 > > only SMTP server... > > > > Regards, > > > > Flavio. > > > > On Mon, 19 Nov 2001, Bradley D. Rhoades wrote: > > > > > > > > I tried searching for this info in the 6bone archives, but the > > > search tool is broken (http://www.wcug.wwu.edu/lists/6bone). > > > > > > I have configured my system to support inet and inet6 smtp connections. > > > I am hoping to do some very simple email exchanges with a few sites to > > > verify basic functionality. > > > > > > If your interested, drop me a note. > > > > > > Thanks, > > > > > > Brad > > > > > From yjchui@cht.com.tw Thu Nov 22 01:28:45 2001 From: yjchui@cht.com.tw (Yann-Ju Chu) Date: Thu, 22 Nov 2001 09:28:45 +0800 Subject: ADSL with IPv6 Message-ID: <003601c172f5$072b0b60$26a9900a@chttl.com.tw> This is a multi-part message in MIME format. ------=_NextPart_000_0033_01C17338.150B27E0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Hi:=20 I am trying IPv6 over ADSL. I use fixed line (not dial-up), so PPPoE = or PPPoA is not neccessary. Besides, ATU-R is set to bridged mode. The = interface between host and ATU-R is ethernet. host <---> ATU-R <---> DLAM <----> ATM switch <---> router Instinctively, I think it will work for both IPv4 and IPv6. = (Becasue it only deal with Ethernet layer) However, it does not. I debug = the condition and find that the problem MAY BE caused by router. Does = anyone ever try similar test? Because I use Cisco router (7206), does = any one know if Cisco support ATM bridge mode with IPv6? Thanks Yann-Ju Chu ------=_NextPart_000_0033_01C17338.150B27E0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
Hi:
    I am = trying IPv6 over ADSL. I use=20 fixed line (not dial-up), so PPPoE or PPPoA is not neccessary. Besides, = ATU-R is=20 set to bridged mode. The interface between host and ATU-R is=20 ethernet.
 
 
host <---> ATU-R = <---> DLAM <---->=20 ATM switch <---> router
 
 
     = Instinctively, I think it=20 will work for both IPv4 and IPv6. (Becasue it only deal with Ethernet=20 layer) However, it does not. I debug the condition and find that = the=20 problem MAY BE caused by router. Does anyone ever try similar test? = Because I=20 use Cisco router (7206), does any one know if Cisco support ATM bridge = mode with=20 IPv6?
 
Thanks
Yann-Ju = Chu
------=_NextPart_000_0033_01C17338.150B27E0-- From michel@arneill-py.sacramento.ca.us Thu Nov 22 04:57:10 2001 From: michel@arneill-py.sacramento.ca.us (Michel Py) Date: Wed, 21 Nov 2001 20:57:10 -0800 Subject: ADSL with IPv6 Message-ID: <2B81403386729140A3A899A8B39B046403AF29@server2000.arneill-py.sacramento.ca.us> There are some obscure Cisco issues with bridging mode atm. Instead of Ethernet, you should enable IRB and use a BVI interface. However, it appears that the command you might need (bridge x route ipv6) is not implemented yet; I run 12.2(2)T. When everything else has failed, open a TAC case¡K.. Config might look like this: Ipv6 unicast-routing Bridge irb Inte f0/0 No ip add Bridge-group 1 Inte atm5/0 Pvc xx/x Bridge-group 1 Inte bvi 1 Ip add x.x.x.x x.x.x.x Ipv6 add xx:xx::/xx Bridge 1 protocol ieee Bridge 1 route ipv6 <== this does not exist yet. Michel. -----Original Message----- From: Yann-Ju Chu [mailto:yjchui@cht.com.tw] Sent: Wednesday, November 21, 2001 5:29 PM To: 6Bone Subject: ADSL with IPv6 Hi: I am trying IPv6 over ADSL. I use fixed line (not dial-up), so PPPoE or PPPoA is not neccessary. Besides, ATU-R is set to bridged mode. The interface between host and ATU-R is ethernet. host <---> ATU-R <---> DLAM <----> ATM switch <---> router Instinctively, I think it will work for both IPv4 and IPv6. (Becasue it only deal with Ethernet layer) However, it does not. I debug the condition and find that the problem MAY BE caused by router. Does anyone ever try similar test? Because I use Cisco router (7206), does any one know if Cisco support ATM bridge mode with IPv6? Thanks Yann-Ju Chu From pgrosset@cisco.com Thu Nov 22 11:03:39 2001 From: pgrosset@cisco.com (Patrick Grossetete) Date: Thu, 22 Nov 2001 12:03:39 +0100 Subject: ADSL with IPv6 In-Reply-To: <003601c172f5$072b0b60$26a9900a@chttl.com.tw> Message-ID: <4.3.2.7.2.20011122120011.0224cec8@europe.cisco.com> --=====================_88487257==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi, ATM RFC 1483 Bridged mode on a Cisco router is either configured using a BVI interface, either RBE mode (see http://www.cisco.com/warp/public/794/routed_bridged_encap.html). None of them support IPv6 on the current FCS IOS release. We don't intend to support IPv6 over BVI interfaces. You may want to contact us directly for future feature. Regards Patrick At 09:28 AM 22-11-01 +0800, Yann-Ju Chu wrote: >Hi: > I am trying IPv6 over ADSL. I use fixed line (not dial-up), so PPPoE > or PPPoA is not neccessary. Besides, ATU-R is set to bridged mode. The > interface between host and ATU-R is ethernet. > > >host <---> ATU-R <---> DLAM <----> ATM switch <---> router > > > Instinctively, I think it will work for both IPv4 and IPv6. (Becasue > it only deal with Ethernet layer) However, it does not. I debug the > condition and find that the problem MAY BE caused by router. Does anyone > ever try similar test? Because I use Cisco router (7206), does any one > know if Cisco support ATM bridge mode with IPv6? > >Thanks >Yann-Ju Chu ____________________________________________ Patrick Grossetete Cisco Systems Internet Technology Division (ITD) - Product Manager Phone/Vmail: 33.1.58.04.61.52 Fax: 33.1.58.04.61.00 mobile: 33.6.89.10.81.28 Email:pgrosset@cisco.com 11 Rue Camille Desmoulins 92782 Issy les Moulineaux Cedex 9 France ____________________________________________ --=====================_88487257==_.ALT Content-Type: text/html; charset="us-ascii"         Hi,

        ATM RFC 1483 Bridged mode on a Cisco router is either configured using a BVI interface, either RBE mode
(see http://www.cisco.com/warp/public/794/routed_bridged_encap.html).
None of them support IPv6 on the current FCS IOS release. We don't intend to support IPv6 over BVI interfaces.
You may want to contact us directly for future feature.

Regards
Patrick


At 09:28 AM 22-11-01 +0800, Yann-Ju Chu wrote:
Hi:
    I am trying IPv6 over ADSL. I use fixed line (not dial-up), so PPPoE or PPPoA is not neccessary. Besides, ATU-R is set to bridged mode. The interface between host and ATU-R is ethernet.
 
 
host <---> ATU-R <---> DLAM <----> ATM switch <---> router
 
 
     Instinctively, I think it will work for both IPv4 and IPv6. (Becasue it only deal with Ethernet layer) However, it does not. I debug the condition and find that the problem MAY BE caused by router. Does anyone ever try similar test? Because I use Cisco router (7206), does any one know if Cisco support ATM bridge mode with IPv6?
 
Thanks
Yann-Ju Chu

____________________________________________
Patrick Grossetete
Cisco Systems
Internet Technology Division (ITD) - Product Manager
                        
Phone/Vmail: 33.1.58.04.61.52   
Fax: 33.1.58.04.61.00   
mobile: 33.6.89.10.81.28        
Email:pgrosset@cisco.com        
11 Rue Camille Desmoulins
92782 Issy les Moulineaux Cedex 9
France
____________________________________________ --=====================_88487257==_.ALT-- From tony@lava.net Thu Nov 22 19:20:03 2001 From: tony@lava.net (Antonio Querubin) Date: Thu, 22 Nov 2001 09:20:03 -1000 (HST) Subject: ADSL with IPv6 In-Reply-To: <4.3.2.7.2.20011122120011.0224cec8@europe.cisco.com> Message-ID: On Thu, 22 Nov 2001, Patrick Grossetete wrote: > ATM RFC 1483 Bridged mode on a Cisco router is either configured > using a BVI interface, either RBE mode > (see http://www.cisco.com/warp/public/794/routed_bridged_encap.html). > None of them support IPv6 on the current FCS IOS release. We don't intend > to support IPv6 over BVI interfaces. If not over BVI interfaces then how about IPv6 over RBE? From fink@es.net Mon Nov 26 00:31:24 2001 From: fink@es.net (Bob Fink) Date: Sun, 25 Nov 2001 16:31:24 -0800 Subject: 6bone pTLA 3FFE:82C0::/28 allocated to NC-REN Message-ID: <5.1.0.14.0.20011125162734.033923e8@imap2.es.net> NC-REN has been allocated pTLA 3FFE:82C0::/28 having finished its 2-week review period. Note that it will take a short while for their pTLA inet6num entry to appear in the 6bone registry as they have to create it themselves. However, their registration is listed on: [To create a reverse DNS registration for pTLAs, please send the prefix allocated above, and a list of at least two authoritative nameservers, to either bmanning@isi.edu or hostmaster@ep.net.] Thanks, Bob From fink@es.net Thu Nov 29 16:13:01 2001 From: fink@es.net (Bob Fink) Date: Thu, 29 Nov 2001 08:13:01 -0800 Subject: pTLA request for LDCOM - review closes 13 December 2001 Message-ID: <5.1.0.14.0.20011129080434.0bf89b88@imap2.es.net> 6bone Folk, LDCOM has requested a pTLA allocation. The open review period for this will close 13 December 2001. Please send your comments to me or the list. Thanks, Bob === >From: "Bergfeld, Vladimir" >To: "'fink@es.net'" >Subject: pTLA request from LDCOM Networks (FR) >Date: Thu, 29 Nov 2001 16:49:52 +0100 > >Hi, > >I'm Vladimir Bergfeld, from LDCOM Networks, an european facilities-based >provider of broadband infrastructure and services >(http://www.ldcomnetworks.com/index_en.htm). We would like to request a pTLA >on the 6Bone to continue our experimentation and provide experimental IPv6 >services in France. > >Here is how we comply with the RFC 2772. > > >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 started our experimentation at the end of July this year, running in >our lab some routers, 2 DNS and some services (web server, mail server, ftp, >proxy, FW. ..) on Linux and FreeBSD, using the pNLA 3FFE :304 :11F ::/48 >delegated by G6. > > >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. > >http://whois.6bone.net/cgi-bin/whois?LDCOM > > > >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 maintain BGP4+ session with our peers using the AS15557 origin, and we do >not readvertise the routes we learn. > >tunnel: gw.ipv6.gaoland.net -> nio-ipv6.cssi.renater.fr PIR-IDF BGP4+ >tunnel: IPv6 in IPv4 gw.ipv6.gaoland.net -> rap.viagenie.qc.ca VIAGENIE >BGP4+ >tunnel: IPv6 in IPv4 gw.ipv6.gaoland.net -> 6r1.routers.fr.fastnetxp.net >FASTNETXP-FR BGP4+ > >router : >212.94.162.106 >3FFE:304:11F::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.gaoland.net >DNS primary : dns1.ipv6.gaoland.net > secondary : dns2.ipv6.gaoland.net and cyclope.ipv6.nic.fr (AFNIC) > >our gateway is gw.ipv6.gaoland.net (3FFE:304:11F::1) >our web server is www6.ipv6.gaoland.net (3FFE:304:11F:100::1) > > >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.gaoland.net (IPv4) >www6.ipv6.gaoland.net (IPv6) > > > >2. The pTLA Applicant MUST have the ability and intent to provide >"production-quality" 6Bone backbone service. > >We are building a native IPv6 Network in France and we will be soon >connected at the French IPv6 IX SFINX6. >We believe IPv6 will arrive soon and we want to prepare ourselves and offer >our partners and clients to experiment it. > > >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. > >Our staff is composed of 3 persons : > >David Gavarret DG2-6BONE >Jean-Jacques Martres JJM1-6BONE >Vladimir Bergfeld VB2-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. > >All the staff can be reach at support@ipv6.gaoland.net ( >notify@ipv6.gaoland.net can also be used) > > >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. > >LDCOM Networks is an European facilities-based provider of broadband >infrastructure and services. As a wholesale telecom and internet services >provider with 30 hosting sites, it provides Ethernet and IP hosting and >connectivity services (through Wireless local loop, local access through >xDSL and unbundled telephone lines). >Our intent is to prepare IPv6 services and migration for theses access >technologies with our clients or partners. And we would be happy to peer >with anyone who is interested. > > >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. > > >Thanks for your attention. >If you need more information, you can ask me directly. > > >Regards, > >Vladimir Bergfeld > > > > > --------------------------------------------------------------- > > Vladimir Bergfeld > > LDCOM Networks - IP Services > > 1 square Chaptal -92309 Levallois Cedex > > Tel : (+33) 1 58 63 19 80 > > E-mail : vladimir.bergfeld@ldcom.fr > > > > From tsoome@ut.ee Fri Nov 30 17:16:28 2001 From: tsoome@ut.ee (Toomas Soome) Date: Fri, 30 Nov 2001 19:16:28 +0200 Subject: IPv6 support for uw-imap Message-ID: <3C07BEEC.D005A44C@ut.ee> hi! I have developed ipv6 support for uw-imap imap-2001a version. udiff is downloadable at http://muhv.pri.ee/~tsoome/soft/IPv6/ if anyone is interested.... it's implemented on solaris system, others may need little work (or extra libs to link it). this diff can be used to make pine 4.43 to support IPv6 as well. toomas -- The all-softening overpowering knell, The tocsin of the soul, -- the dinner bell. -- Lord Byron