From: Lorenzo Colitti <lorenzo@google.com>
To: Steven Barth <cyrus@openwrt.org>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
Markus Stenberg <markus.stenberg@iki.fi>,
Ole Troan <otroan@employees.org>,
boutier@pps.univ-paris-diderot.fr,
"homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Source-specific routes in Linux [was: atomic updates...]
Date: Wed, 8 May 2013 20:06:19 +0900 [thread overview]
Message-ID: <CAKD1Yr1EVXbMRDAtiSwejL21AeJdivVHL9vipzp1Xz6HUEANMg@mail.gmail.com> (raw)
In-Reply-To: <3c2ea3e2-a587-4cf6-820b-929e6d75a9ad@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Wed, May 8, 2013 at 7:51 PM, Steven Barth <cyrus@openwrt.org> wrote:
> if there would be multiple routers which I guess is unlikely in that
> situation. One could maybe attribute the prefix to the source address of
> the DHCPv6 server but that sounds problematic to me aswell.
>
So you're talking about the case where you have ISP1 and ISP2 "plugged into
a switch together with your router"?
In that case I can't see any better way than attempting to match the
link-local IPv6 address that you got the RA from to the link-local address
of the DHCPv6 server you got the PD from.
I can't think of a situation why these would be different, but perhaps
there is. Can the DHCPv6 server be a global address?
[-- Attachment #2: Type: text/html, Size: 1185 bytes --]
next prev parent reply other threads:[~2013-05-08 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 21:38 Dave Taht
2013-05-05 22:23 ` Dave Taht
[not found] ` <loom.20130507T130051-512@post.gmane.org>
[not found] ` <87vc6vgghx.wl%jch@pps.univ-paris-diderot.fr>
[not found] ` <8F7177E4-6212-4A74-8A7C-A2D1703A59BF@iki.fi>
[not found] ` <87sj1zgfot.wl%jch@pps.univ-paris-diderot.fr>
2013-05-08 8:51 ` [homenet] " Dave Taht
2013-05-08 9:48 ` Steven Barth
2013-05-08 10:28 ` Ole Troan
2013-05-08 10:51 ` Steven Barth
2013-05-08 10:58 ` Ole Troan
2013-05-08 12:54 ` Steven Barth
2013-05-08 11:06 ` Lorenzo Colitti [this message]
2013-05-08 22:46 ` Juliusz Chroboczek
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=CAKD1Yr1EVXbMRDAtiSwejL21AeJdivVHL9vipzp1Xz6HUEANMg@mail.gmail.com \
--to=lorenzo@google.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=boutier@pps.univ-paris-diderot.fr \
--cc=cyrus@openwrt.org \
--cc=homenet@ietf.org \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=markus.stenberg@iki.fi \
--cc=otroan@employees.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