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 <[email protected]> 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 <[email protected]> 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
_______________________________________________ Cerowrt-devel mailing list [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
