[dhcwg] Enabling ipv6 forwarding with dhcpv6
Cristian Cadar <Cristian.Cadar@netlab.nec.de> Mon, 24 May 2004 09:56 UTC
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23442; Mon, 24 May 2004 05:56:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BSC1D-00020M-7X; Mon, 24 May 2004 05:45:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BSBog-0008Nl-DE for dhcwg@optimus.ietf.org; Mon, 24 May 2004 05:32:18 -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 FAA22498 for <dhcwg@ietf.org>; Mon, 24 May 2004 05:32:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BSBoc-0001c5-J7 for dhcwg@ietf.org; Mon, 24 May 2004 05:32:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BSBna-0001JN-00 for dhcwg@ietf.org; Mon, 24 May 2004 05:31:10 -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 1BSBma-0000js-00 for dhcwg@ietf.org; Mon, 24 May 2004 05:30:08 -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 i4O9TcDW063896 for <dhcwg@ietf.org>; Mon, 24 May 2004 11:29:38 +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 21C5D1324F3 for <dhcwg@ietf.org>; Mon, 24 May 2004 11:29:38 +0200 (CEST)
From: Cristian Cadar <Cristian.Cadar@netlab.nec.de>
Organization: NEC Europe Ltd.
To: dhcwg@ietf.org
Date: Mon, 24 May 2004 11:30:29 +0200
User-Agent: KMail/1.5.4
References: <DADF50F5EC506B41A0F375ABEB3206360143BF00@esebe023.ntc.nokia.com> <20040523224328.GB9749@login.ecs.soton.ac.uk>
In-Reply-To: <20040523224328.GB9749@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200405241130.29058.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
Subject: [dhcwg] Enabling ipv6 forwarding with dhcpv6
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
Content-Transfer-Encoding: 7bit
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
- Re: [dhcwg] Default Router information for DHCPv6 Tim Chown
- [dhcwg] Enabling ipv6 forwarding with dhcpv6 Cristian Cadar