From: Ole Troan <otroan@employees.org>
To: Steven Barth <cyrus@openwrt.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt dev 3.8.13-7 released
Date: Wed, 12 Jun 2013 11:38:03 +0200 [thread overview]
Message-ID: <BE4267FB-7284-4278-B0B5-17D94E8F18D9@employees.org> (raw)
In-Reply-To: <51B82AB8.3090204@openwrt.org>
Steven,
> Source-based IPv6 routing was introduced a few weeks ago to properly support multiple IPv6 uplink-interfaces. Therefore OpenWrt only let's you route through the tunnel if it knows you have a suitable source address.
out of curiosity, is this SADR as described in http://tools.ietf.org/html/draft-troan-homenet-sadr-00?
cheers,
Ole
next prev parent reply other threads:[~2013-06-12 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 6:10 Dave Taht
2013-06-12 8:00 ` Steven Barth
2013-06-12 7:37 ` Dave Taht
2013-06-12 9:11 ` Steven Barth
2013-06-12 9:40 ` Dave Taht
2013-06-12 9:38 ` Ole Troan [this message]
2013-06-12 9:58 ` Steven Barth
2013-06-12 10:10 ` Ole Troan
2013-06-12 10:30 ` 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=BE4267FB-7284-4278-B0B5-17D94E8F18D9@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