Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Ole Trøan" <otroan@employees.org>
To: Steven Barth <cyrus@openwrt.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Current state of ipv6 in openwrt barrier breaker
Date: Wed, 12 Dec 2012 10:28:32 +0100	[thread overview]
Message-ID: <7E37A46B-7F40-40D1-9A59-B176F5219DB4@employees.org> (raw)
In-Reply-To: <50C84C38.7040207@openwrt.org>

Steven,

>> the worst you can expect is a /64 on the link-net and no PD. I suggest you don't support that case.
> The problem is that (some) people are expecting to be able to just plug other routers behind their main uplink router for whatever reasons (e.g. additional WiFi-network etc.) like they have with IPv4 or e.g. make a router just connect to a non-WDS WiFi in client mode and extend their network.

that only works in IPv4 if you have a good tail wind and your fingers crossed.

> As the home router shouldn't do PD to further distribute the ISP-prefix it is hard to support this with IPv6 except with detecting the case and doing NDP-Proxying then as bridging might not always be possible or desired in this case.

you could use hierarchical PD, just that it doesn't work well with:
 - networks with loops
 - multi-homed networks

and it is quite wasteful with regards to subnet space.

> And supporting all of this above would have the side-effect that such ISP without PD would be supported as well so I'm not really sure.

ND proxy fails in any topology with a loop.

we do have an implementation on github that implements
http://datatracker.ietf.org/doc/draft-arkko-homenet-prefix-assignment/
that supports prefix assignment with an arbitrary topology in the network. why not use that?

cheers,
Ole


  reply	other threads:[~2012-12-12  9:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 19:56 Ole Trøan
2012-12-11 20:25 ` Dave Taht
2012-12-11 21:31   ` Ole Trøan
2012-12-12  8:19     ` Dave Taht
2012-12-12  9:08       ` Ole Trøan
2012-12-12  9:19         ` Steven Barth
2012-12-12  9:28           ` Ole Trøan [this message]
2012-12-12  9:47             ` Steven Barth
2012-12-12 10:11               ` Dave Taht
2012-12-12 18:56       ` Michael Richardson
2012-12-12  9:05     ` Török Edwin
2012-12-11 20:46 ` Steven Barth
2012-12-11 21:02   ` Ole Trøan
2012-12-12  8:23     ` Steven Barth
2012-12-12  8:43       ` Ole Trøan
  -- strict thread matches above, loose matches on Subject: below --
2012-12-10  8:41 Dave Taht
2012-12-10  9:15 ` Dave Taht
2012-12-10 11:27   ` Steven Barth
2012-12-10 11:40     ` Dave Taht
2012-12-10 11:53       ` Steven Barth

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=7E37A46B-7F40-40D1-9A59-B176F5219DB4@employees.org \
    --to=otroan@employees.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cyrus@openwrt.org \
    /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