Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Teco Boot <teco@inf-net.nl>
To: Steven Barth <cyrus@openwrt.org>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] IPv6 address assignment and naming
Date: Sat, 17 Aug 2013 19:04:37 +0200	[thread overview]
Message-ID: <8E1B6F15-6F4C-4CA1-A849-CBBE2AF70711@inf-net.nl> (raw)
In-Reply-To: <0396737f-79ff-40bb-ac0a-9c4d97e2542d@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]

Yes, source address dependent routing in main table. Just use from <prefix>. Typically on default route. 

Add also normal default for source address selection. 

Teco

Op 17 aug. 2013 om 16:53 heeft Steven Barth <cyrus@openwrt.org> het volgende geschreven:

> Well lets see how this could help us. I presume this makes ipv6 source routing usable without policy rules and distinct tables? Sorry didnt have time to look into it in more Detail.
> 
> As 3.10 has become LTS it would probably be a good candidate for a release.
> 
> I hope to start a new Iteration for ipv6 in openwrt in the near future. Lets see if we can get anything out of the meetings in Berlin. If anyone wants to contribute anything to owrt please let me know so we can coordinate all efforts.
> 
> Cheers,
> 
> Steven
> 
> 
> 
> Hannes Frederic Sowa <hannes@stressinduktion.org> schrieb:
>> 
>> Hello all!
>> 
>> On Fri, Aug 16, 2013 at 11:21:03PM +0200, Teco Boot wrote:
>>> The IPv6 subtrees in on its way :-). After 3.11 we can ask for backports.
>> 
>> It is already in davem's stable queue and should be integrated in the next stable
>> kernels. If openwrt picks them up, it should show up there, too.
>> 
>>>> While most of the ipv6 stuff in openwrt is going increasingly well, AND we just got working multi-prefix routing fixed in the linux kernel (not sure if the IPV6_subtrees spatches are committed or backported yet), there are still integration hassles with ipv6 going on. (I exp
>>>>  ect
>>>> integration hassles for years, actually - dealing with the pure dynamic assignments the isps are demanding is nearly impossible)
>> May I ask if those fixes for multi-prefix routing made it upstream? Btw. I
>> am more then willing to have a look at ipv6 kernel problems and maybe
>> fix them. ;)
>> 
>> Thanks a lot,
>> 
>> Hannes

[-- Attachment #2: Type: text/html, Size: 2758 bytes --]

      reply	other threads:[~2013-08-17 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 19:13 Dave Taht
2013-08-16 21:21 ` Teco Boot
2013-08-16 21:35   ` Dave Taht
2013-08-16 21:39     ` Teco Boot
2013-08-16 22:08   ` Hannes Frederic Sowa
2013-08-17 14:53     ` Steven Barth
2013-08-17 17:04       ` Teco Boot [this message]

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=8E1B6F15-6F4C-4CA1-A849-CBBE2AF70711@inf-net.nl \
    --to=teco@inf-net.nl \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cyrus@openwrt.org \
    --cc=hannes@stressinduktion.org \
    --cc=jch@pps.univ-paris-diderot.fr \
    --cc=nbd@nbd.name \
    /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