Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Shane Turner <turner@chebucto.ns.ca>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Extensive IPv6 support can be dropped from cerowrt rc8
Date: Tue, 06 Dec 2011 13:10:44 -0400	[thread overview]
Message-ID: <4EDE4C94.6020701@chebucto.ns.ca> (raw)
In-Reply-To: <CAA93jw6b8EY8F0whL5TdmhD66fku_EeRrundue1NHPTMcELCAA@mail.gmail.com>

[Re-posting to list. Accidentally sent directly to Dave previously.]

I was hoping that IPv6 would remain one of the focuses of this, but I'll 
admit I never got anywhere beyond registering for a SiXXS account.

Shane

On 06/12/2011 12:49 PM, Dave Taht wrote:
> This is the third of a string of mails discussing what can be dropped
> from cerowrt rc8.
>
> IPv6 is always a headache. Universally, feedback on the 6to4 scheme we
> have in place has been negative. It works well in places where
> 6to4 works, and not at all where 6to4 doesn't work, and creates
> complications in the firewall rules and doubles the amount of
> testing we should theoretically be doing against all forms of
> networking, notably TCP.
>
> The only portion of the ipv6 support that anyone with funding has
> expressed an interest in has been DHCP-PD, and expending
> resources to make that work well, may well be a good idea.
>
> That said, we've found and helped fix plenty of bugs in ipv6, and
> going DHCP-PD only makes it impossible for anyone not
> in a DHCP-PD environement to accomplish anything with ipv6, and most
> early deployments are only giving out a /64 which
> is useless for doing anything with the current, multiply routed
> architecture of cerowrt. If we kept AHCP we could leverage
> that + DHCP-PD.
>
> I am not able to test ipv6 at all, in paris, at present. It is
> completely blocked everywhere I have been in Paris.
>
> Eliminating IPv6 entirely from our test cycles and build process would
> save a lot of time.
>
> This gets bugs #98, #140, #145, #239, #273, and to some extent #311
> and a few others off our plate in the next quarter.
>

  reply	other threads:[~2011-12-06 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 16:49 Dave Taht
2011-12-06 17:10 ` Shane Turner [this message]
2011-12-06 19:33   ` david

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=4EDE4C94.6020701@chebucto.ns.ca \
    --to=turner@chebucto.ns.ca \
    --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