IETF Logo Mail Archive

Re: [dhcwg] Enabling ipv6 forwarding with dhcpv6

Cristian Cadar <Cristian.Cadar@netlab.nec.de> Thu, 27 May 2004 11:50 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17498; Thu, 27 May 2004 07:50:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTJ4V-0004KY-Ua; Thu, 27 May 2004 07:29:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTIvL-0007WK-CP for dhcwg@megatron.ietf.org; Thu, 27 May 2004 07:19:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15568 for <dhcwg@ietf.org>; Thu, 27 May 2004 07:19:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BTIv4-0007kW-Ud for dhcwg@ietf.org; Thu, 27 May 2004 07:19:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BTIu9-0007Zk-00 for dhcwg@ietf.org; Thu, 27 May 2004 07:18:33 -0400
Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1BTItM-0007D6-00 for dhcwg@ietf.org; Thu, 27 May 2004 07:17:44 -0400
Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i4RBHCDW075640 for <dhcwg@ietf.org>; Thu, 27 May 2004 13:17:12 +0200 (CEST)
Received: from cadar.office (cadar.office [10.1.1.118]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 2EAE2138BE9 for <dhcwg@ietf.org>; Thu, 27 May 2004 13:17:12 +0200 (CEST)
From: Cristian Cadar <Cristian.Cadar@netlab.nec.de>
Organization: NEC Europe Ltd.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Enabling ipv6 forwarding with dhcpv6
Date: Thu, 27 May 2004 13:18:31 +0200
User-Agent: KMail/1.5.4
References: <9C422444DE99BC46B3AD3C6EAFC9711B0644C239@tayexc13.americas.cpqcorp.net>
In-Reply-To: <9C422444DE99BC46B3AD3C6EAFC9711B0644C239@tayexc13.americas.cpqcorp.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200405271318.31936.Cristian.Cadar@netlab.nec.de>
X-Scanned-By: MIMEDefang 2.35
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Jim,

I think since the use of the RA daemon on ipv6 routers is "almost" a must and it comes together
with enabling the ipv6 forwarding the problem is somehow solved.  
I might be wrong....

Cristian



On Tuesday 25 May 2004 18:11, Bound, Jim wrote:
> Hi Christian,
> 
> IPv6 is very clear about Host vs Router.  An interface cannot be both.
> So a router interface would not be using a DHCPv6 client is my guess. I
> think giving hints to the Host interface of a client that has a router
> interface state too is not a good idea.  A UNIX router interface will
> get all it needs from being a router.  We had to do this to support
> MIPv6 HA on UNIX where I work and the trick is to get all the OSPF,
> IS-IS, RIPng, BGP et al updates via routing daemon for that interface.
> 
> Does this answer help?
> 
> Good question.
> 
> /jim 
> 
> > -----Original Message-----
> > From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On 
> > Behalf Of Cristian Cadar
> > Sent: Monday, May 24, 2004 5:30 AM
> > To: dhcwg@ietf.org
> > Subject: [dhcwg] Enabling ipv6 forwarding with dhcpv6
> > 
> > Hi ,
> > 
> > Since there might be clients configured by dhcpv6 with 
> > routing capabilities in the network I'm missing the feature 
> > of enabling the ipv6 forwarding in dhcpv6. As far as I know 
> > the RA does not provide this feature. On a dual-stack UNIX 
> > machine there are two different flags to be set for enabling 
> > ip forwarding, one for ipv4 and the other for ipv6.
> > Is there any way for doing it with dhcp or RA ? I could not find any.
> > 
> > TNX
> > Cristian
> > 
> > 
> > _______________________________________________
> > dhcwg mailing list
> > dhcwg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/dhcwg
> > 
> > 
> 

-- 
________________________________________________________
| Cristian Cadar                   cadar@netlab.nec.de
| Network Laboratories Heidelberg  NEC Europe Ltd.
| Kurfuerstenanlage 36             D 69115 Heidelberg
| Tel. (+49) 6221 90511-21         Fax: (+49) 6221 90511-55
| URL:  http://www.netlab.nec.de/heidelberg/index.html
| ________________________________________________________



_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email