Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-users <cerowrt-users@lists.bufferbloat.net>,
	 cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-users] IPv6 router advertisements on custom interfaces
Date: Mon, 10 Dec 2012 13:53:54 +0000	[thread overview]
Message-ID: <CAA=Zby7O8yKZUm4epqQe+XHtn4rTqV+Fzoz0t7Ma95MpKLJ3+Q@mail.gmail.com> (raw)
In-Reply-To: <50C59F7A.7000508@openwrt.org>

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

On 10 December 2012 08:38, Steven Barth <cyrus@openwrt.org> wrote:

>
> So far the current IPv6-featureset is:
>
> * Support for native IPv6 with static configuration
> * Support for native IPv6 with DHCPv6-Prefix Delegation
> * Support for native IPv6 without PD via relaying or masquerading
> * Support for 6in4, 6to4 and 6rd
> * Prefixes are automatically split up and distributed over
> downstream-interfaces OR by choice mapped to an ULA-address (NPT66).
>

Out of interest, what benefit is there to using NPT66?  I understand that
people seem to want it, just not what you gain over advertising multiple
prefixes.
-- 
Robert Bradley

[-- Attachment #2: Type: text/html, Size: 955 bytes --]

  reply	other threads:[~2012-12-10 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 23:04 Michael Richardson
2012-12-10  7:56 ` Dave Taht
2012-12-10  8:38   ` Steven Barth
2012-12-10 13:53     ` Robert Bradley [this message]
2012-12-10  8:40   ` Dave Taht
2012-12-10 14:23   ` Michael Richardson
2012-12-10 14:42     ` Steven Barth
2012-12-10 14:51       ` Dave Taht

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='CAA=Zby7O8yKZUm4epqQe+XHtn4rTqV+Fzoz0t7Ma95MpKLJ3+Q@mail.gmail.com' \
    --to=robert.bradley1@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt-users@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