Re: Enable tools for IPv6

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

Well...

On Tue, 2015-08-04 at 14:46 +0200, Larsen wrote:
> Hi,
> 
> some users are currently translating the wiki instructions on how to 
> set  
> up an external IPv6 connection with IPFire.

I very much appreciate you playing with IPv6 and IPFire. That is good
to learn the system better and also to get familiar with IPv6. I
honestly do not think that this will ever be possible to become some
supported feature in IPFire 2. There is too much to do and this is just
covering the tip of the iceberg.

> Unfortunately, two things (the latter one not necessarily) need to be
>   
> recompiled with IPv6 support:
> 
> http://wiki.ipfire.org/en/add-ipv6/extend/prepare
> http://wiki.ipfire.org/en/add-ipv6/extend/dns
> 
> Would it be possible to enable IPv6 for those by default or might 
> there be  
> negative side effects?

It might. We disabled IPv6 in some packages like squid, curl and so on
because these were sometimes causing errors.

http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=f8c079150ec8df07
a0f90bf25ef3a68f1201756f

I do not know about the others. I think I remember that we disabled
some of them because it won't built. Not too sure about that.

> I think it´s time to get IPFire IPv6 ready, so why not start with 
> this.

IPFire 3 is ready for IPv6. I would appreciate much more to focus on
that then and then finally get rid of IPFire 2.

Just for reference:

http://git.ipfire.org/?p=network.git;a=summary
http://source.ipfire.org/releases/network/man-pages/

> 
> (Maybe the information from the wiki even is outdated and IPv6 
> already  
> enabled for those tools?)

Idk.

> 
> 
> Lars

Best,
-Michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]