From: Steven Barth <cyrus@openwrt.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Latest IPv6 Updates
Date: Fri, 28 Dec 2012 18:56:40 +0100 [thread overview]
Message-ID: <50DDDD58.9090901@openwrt.org> (raw)
Hi guys,
the following updates / changes for IPv6 have been commited to OpenWrt
in the last days. Most of these affect RFC 6204 CE-compliance, some are
convenience changes.
Feel free to merge and test CeroWrt.
* Detect and delegate IPv6-specific MTU from upstream interfaces (e.g.
tunnels, pppoe, etc.) and propagate them to downstream interfaces
(supporting cases where IPv4-MTU and IPv6-MTU differ, e.g. 6in4, 6rd,
6to4, ...)
* Add a default null-route for delegated prefixes (CE-requirement WPD-6)
This fixes routing loops in case packets with a destination within an
unused / unassigned part of a delegated prefix are received.
* Added support for site-borders (interfaces which ULA-traffic might not
cross) as specified in CE-requirement ULA-4
* Added support to override CE-requirement ULA-5 for NPT-setups (iirc
not relevant if dnsmasq is used, as it does not follow ULA-5).
Documentation on http://wiki.openwrt.org/doc/uci/network6 has been updated.
Btw. Simon Kelley released 2.66-test4 which fixes some bugs related to
stateful DHCPv6 and should make it usable finally. Also the new
MTU-propagation mentioned above is now supported by dnsmasq as well.
I haven't tested it myself yet but you can try if you are brave.
I will try to make a table about the RFC requirements for Customer Edge
(CE)-Routers soon which sums up which requirements are fulfilled and
which are still not implemented both for CeroWrt / OpenWrt with 6relayd
and with dnsmasq as RA/DHCPv6-server.
Cheers,
Steven
next reply other threads:[~2012-12-28 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 17:56 Steven Barth [this message]
2012-12-28 20:19 ` Dave Taht
2012-12-28 23:34 ` Maciej Soltysiak
2012-12-29 3:05 ` Dave Taht
2012-12-28 23:37 ` Maciej Soltysiak
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=50DDDD58.9090901@openwrt.org \
--to=cyrus@openwrt.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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