public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Enable tools for IPv6
Date: Wed, 05 Aug 2015 16:31:36 +0100	[thread overview]
Message-ID: <1438788696.2448.53.camel@ipfire.org> (raw)
In-Reply-To: <op.x2wij5sbcahio0@atl-uetersen.atlantisgmbh.local>

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

On Wed, 2015-08-05 at 17:27 +0200, Larsen wrote:
> On Wed, 05 Aug 2015 12:28:01 +0200, Michael Tremer  
> <michael.tremer(a)ipfire.org> 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.

If someone is using them and they do not cause any issues then we can
enable IPv6. Having out-of-tree packages is really pain.

I am also okay with compiling in IPv6 support for the other things I
mentioned. There are only bugs to fix first before we can do that.
Disabling IPv6 is more of a workaround than a solution for the issues.

-Michael

> 
> 
> Lars

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

  reply	other threads:[~2015-08-05 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 12:46 Larsen
2015-08-05 10:28 ` Michael Tremer
2015-08-05 15:27   ` Larsen
2015-08-05 15:31     ` Michael Tremer [this message]
2015-08-05 15:59       ` Larsen
2015-08-05 16:19         ` Michael Tremer
2015-08-05 21:51           ` Larsen
2015-08-07 12:59             ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1438788696.2448.53.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox