From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larsen To: development@lists.ipfire.org Subject: Re: Enable tools for IPv6 Date: Wed, 05 Aug 2015 17:59:00 +0200 Message-ID: In-Reply-To: <1438788696.2448.53.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6698558240693505445==" List-Id: --===============6698558240693505445== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Wed, 05 Aug 2015 17:31:36 +0200, Michael Tremer wrote: > On Wed, 2015-08-05 at 17:27 +0200, Larsen wrote: >> On Wed, 05 Aug 2015 12:28:01 +0200, Michael Tremer >> wrote: >> >> > IPFire 3 is ready for IPv6. I would appreciate much more to focus >> > on >> > that then and then finally get rid of IPFire 2. >> >> Ok, fair enough. >> There are precompiled binaries for the needed tools, so this >> shouldn´t >> pose a problem. > > I think that is even worse. When ever we patch those binaries they will > be overwritten on these systems. I guess this problem exists for different aspects of manually getting IPv6 to work on IPFire 2.x. For example, have a look at the following files that will be edited and might possibly be overwritten. http://wiki.ipfire.org/en/add-ipv6/extend/prepare /etc/sysconfig/modules /etc/sysctl.conf /etc/resolv.conf /etc/modprobe.d/ipv6.conf (deleted) http://wiki.ipfire.org/en/add-ipv6/extend/nativ /etc/init.d/network Therefore, we don't really need the tools to be IPv6-enabled. It would just have made things one step easier. So, I have added a warning here: http://wiki.ipfire.org/en/add-ipv6/ipv6/extended Lars --===============6698558240693505445==--