General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Maxim Kharlamov <mcs@podsolnuh.biz>
Cc: bloat@lists.bufferbloat.net
Subject: [Bloat] DHCP-PD and cerowrt
Date: Thu, 10 Nov 2011 13:17:40 +0100	[thread overview]
Message-ID: <CAA93jw5NMdnQ=EeaaySey9qvsEWfVHsuwk-7PPoNCFTD1ZU9aw@mail.gmail.com> (raw)

Dear Maxim:

> Updated to smoketest10.
> Those features are slightly tested now. After installing the necessary
> packages, 3g and pppoe work, dhcp6c also seems to be OK, but requires some
> messing with the /etc/config/dhcp6c.conf file.

What sorts of 'messing about' were required? (please send conf file)

How big a PD (/64? /60? /56? what?) do they delegate?

With comcast starting to go live with their dual stack trial, they
only will be delegating a /64 at first,

http://blog.comcast.com/2011/11/ipv6-deployment-technology.html

which blows up the routing-only concept in cerowrt when used with
classic autonegotiated /64 ipv6 addressing. However I'd planned for
that, in having AHCP available and babel be the default routing
protocols. AHCP distributes /128s across all interfaces, and in
combination with babel, lets you move transparently from wired to
wireless domains and back again, which is very liberating and an
advancement on the state of the art in home networking.

so having hooks to AHCP and babel in there as alternative means to
distribute /128s across all the routed interfaces would be exciting.
If I knew what they were.

Regardless of this particular hook, I'd like to make dhcpv6-pd
enablement part of the next release, by default, rather than as an
optional package.

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 12:17 Dave Taht [this message]
2011-11-10 20:08 ` Maxim Kharlamov
2011-11-11  2:27 ` Jim Gettys
2011-11-11  4:52   ` Jeremy Visser

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5NMdnQ=EeaaySey9qvsEWfVHsuwk-7PPoNCFTD1ZU9aw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=mcs@podsolnuh.biz \
    /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