From owner-freebsd-rc@FreeBSD.ORG Thu Mar 29 19:55:09 2007 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17AC716A400; Thu, 29 Mar 2007 19:55:09 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id E10D613C4B7; Thu, 29 Mar 2007 19:55:08 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 17FAD210F7C; Thu, 29 Mar 2007 15:32:37 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 29 Mar 2007 15:32:34 -0400 X-Sasl-enc: UJR41fubeW4EPjXzv65k9NawbDvS0UG5GYuijP4VdraI 1175196753 Received: from [192.168.124.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 2B3E221EE9; Thu, 29 Mar 2007 15:32:33 -0400 (EDT) Message-ID: <460C144E.5000002@incunabulum.net> Date: Thu, 29 Mar 2007 20:32:30 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Mike Makonnen References: <20070329182906.GB38703@rogue.navcom.lan> In-Reply-To: <20070329182906.GB38703@rogue.navcom.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-rc@freebsd.org Subject: Re: Merging rc.d/network_ipv6 into rc.d/netif X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2007 19:55:09 -0000 Mike Makonnen wrote: > I would > especially like feedback from folks more familiar with IPv6. One > gotcha I've noticed is that if you boot with ipv6_enable turned > off, then try to start IPv6 on an interface later on, it doesn't > work because none of the interfaces (except lo0) has a link-local > address (see rc.d/auto_linklocal). How can we fix this? Also, I > would appreciate feedback on how stopping IPv6 on an interface > should be handled. In rc.d/network_ipv6 it was handled at all. > Currently, it goes through and deletes all > IPv6 addresses on the interface. > I agree. We should be able to add/remove IPv6 link-local addresses somehow at runtime, after boot, without necessarily bringing up IPv6 on an interface during boot. I am thinking at some point it may be for the best if some of the code to do with address families is restructured so that the administrator is able to explicitly attach or detach protocol domains e.g. AF_INET, AF_INET6 to network interfaces on the command line, based on my experience of making the changes necessary for refcounting of various network stack structures. I'd like to get this fixed going forward, though, as ever, other work takes priority... Regards, BMS