Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Cc: cerowrt-users <cerowrt-users@lists.bufferbloat.net>,
	Simon Kelley <simon@thekelleys.org.uk>,
	Michael Richardson <mcr@sandelman.ca>
Subject: Re: [Cerowrt-users] IPv6 router advertisements on custom interfaces
Date: Mon, 10 Dec 2012 15:51:44 +0100	[thread overview]
Message-ID: <CAA93jw69_0W4QJXwZKJ19oXB_OwUKYKLQ34hyfELv1w1Hk99pA@mail.gmail.com> (raw)
In-Reply-To: <50C5F4D7.10509@openwrt.org>

On Mon, Dec 10, 2012 at 3:42 PM, Steven Barth <cyrus@openwrt.org> wrote:
> For OpenWrt, npt66 won't be the default method - instead the default should
> be to split up the WAN prefix to distribute to downstream interfaces and
> fallback to relaying if there are no prefixes.
>
> I personally think npt66 would not make much sense outside of multi-uplink
> situations at least for plain OpenWrt, I cannot speak for CeroWrt.

My concern is explained by example.

I'm a fire department in the path of hurricane sandy. Power goes out.
I have a 7 day public ipv6 lease from a provider like comcast. A team
of volunteers get on bicycles connected to generators to keep the
servers and radios up and connected to the outside world.

Power stays out for 3 weeks. The public lease expires in 1 week.

Power flickers on, briefly. 40,000 users all apply for a new ipv6
lease at the same time. The lease changes. Power goes out.... the
network tries to renumber but has only partial connectivity... power
comes back on... lease changes again... the box in the corner that
controls the satellite uplink doesn't get a message and loses
connectivity entirely... people die.

I am making no long term design decisions vs a vs npt66 at this
point... but I have a strong bias towards only using ipv6 addresses on
an internal net that are as constant as the universe, and as constant
as ipv4 nat. Period.

Lest you think this is not a viable scenario, (although I would hope
hurricane sandy is high in many minds)....

power in nicaragua flickers 6 times a day....

>
>
>
> On 10.12.2012 15:23, Michael Richardson wrote:
>>>>>>>
>>>>>>> "Dave" == Dave Taht <dave.taht@gmail.com> writes:
>>
>>      Dave> Also planned is to (once the 3.7 kernel lands) make npt66 the
>> default
>>      Dave> (for most users). So in a couple weeks, all the underlying ipv6
>>      Dave> infrastructure in openwrt and cerowrt is going to change.
>>
>> Pardon?
>>
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      reply	other threads:[~2012-12-10 14:51 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
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 [this message]

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=CAA93jw69_0W4QJXwZKJ19oXB_OwUKYKLQ34hyfELv1w1Hk99pA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-users@lists.bufferbloat.net \
    --cc=cyrus@openwrt.org \
    --cc=mcr@sandelman.ca \
    --cc=simon@thekelleys.org.uk \
    /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