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: IPFire 3 and IPv6
Date: Sat, 23 Jan 2016 13:05:55 +0000	[thread overview]
Message-ID: <1453554355.585.128.camel@ipfire.org> (raw)

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

Hi,

because this topic came up a few times in the last days I would like to
post an update to keep us all on the same page.

So years ago we made the decision to get rid of most of the
unmaintainable code in IPFire 2, rewrite it and by doing that adding
support for IPv6. IPv6 is really difficult because many things do not
work like they do with IPv4. So just adding that wasn't very well
possible either in our opinion.

So far we have pretty much completed a lot of the work of the network
stack. That is what I call everything that is in the "network" package.

  http://git.ipfire.org/?p=network.git;a=summary
  https://pakfire.ipfire.org/package/network

Please have a look around.

I also held a talk about this at the last summit. It is really not the
best, but should give you a brief introduction about how things work,
are supposed to work, and what some of the thoughts behind that are.

  https://www.youtube.com/watch?v=xzLmUvNrAik

As mentioned in there, this is pretty much at an alpha state and needs
more work to get stable. This is why I am writing this email. If you
are interested in working on IPFire 3, maybe install the latest image
and set up networking on it. That might run either very well, or you
might run into some bugs. In the latter case, please open bug reports.

The network component is the core of the IPFire functionality. It
should be rock solid hence we need to test it well and make it as
robust as we possibly can. It is working for me and some others have
been playing around with it, but every new user will run into new bugs
:)

When we have this working properly, we can move on to the next big
things that are still to do in IPFire 3.

The latest image can be downloaded here:

 http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20151101/x86_64/

Documentation is available here:

  http://source.ipfire.org/releases/network/man-pages/

Pay special attention to the quick start guide:

  http://source.ipfire.org/releases/network/man-pages/network-quick-start.html

There is also more on this in the talk.

Best,
-Michael

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

                 reply	other threads:[~2016-01-23 13:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1453554355.585.128.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