From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Teco Boot <teco@inf-net.nl>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
Steven Barth <cyrus@openwrt.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] IPv6 address assignment and naming
Date: Sat, 17 Aug 2013 00:08:38 +0200 [thread overview]
Message-ID: <20130816220838.GA16508@order.stressinduktion.org> (raw)
In-Reply-To: <E3A60B17-3140-4791-8746-B54406E28EC8@inf-net.nl>
Hello all!
On Fri, Aug 16, 2013 at 11:21:03PM +0200, Teco Boot wrote:
> The IPv6 subtrees in on its way :-). After 3.11 we can ask for backports.
It is already in davem's stable queue and should be integrated in the next stable
kernels. If openwrt picks them up, it should show up there, too.
> > While most of the ipv6 stuff in openwrt is going increasingly well, AND we just got working multi-prefix routing fixed in the linux kernel (not sure if the IPV6_subtrees spatches are committed or backported yet), there are still integration hassles with ipv6 going on. (I expect integration hassles for years, actually - dealing with the pure dynamic assignments the isps are demanding is nearly impossible)
May I ask if those fixes for multi-prefix routing made it upstream? Btw. I
am more then willing to have a look at ipv6 kernel problems and maybe
fix them. ;)
Thanks a lot,
Hannes
next prev parent reply other threads:[~2013-08-16 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 19:13 Dave Taht
2013-08-16 21:21 ` Teco Boot
2013-08-16 21:35 ` Dave Taht
2013-08-16 21:39 ` Teco Boot
2013-08-16 22:08 ` Hannes Frederic Sowa [this message]
2013-08-17 14:53 ` Steven Barth
2013-08-17 17:04 ` Teco Boot
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130816220838.GA16508@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.org \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=nbd@nbd.name \
--cc=teco@inf-net.nl \
/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