Date: Tue, 02 Mar 2004 15:14:06 +0100 From: Andre Oppermann <andre@freebsd.org> To: Bruce M Simpson <bms@spc.org> Cc: James <haesu@towardex.com> Subject: Re: My planned work on networking stack Message-ID: <404496AE.300E1457@freebsd.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce M Simpson wrote: > > On Mon, Mar 01, 2004 at 10:16:25PM -0500, James wrote: > > > > [] move IPv4 routing to its own optimized routing table structure and > > > > finally it's about time :) > > I've been fielding suggestions from individuals who feel using a multi-bit > trie might be more suitable for achieving higher PPS rates. Yes. Which one should not matter. I want to make an API for the IPv4 routing code. Different routing implementations then can be loaded or changed at runtime or boot time. > > > > add multi-path and policy-routing options. (planned) > > > > would the policy-routing optioned table sort of similar to VRF's or > > different routing instances that could potentially be tied to userlands > > like Quagga? > > That's the plan, I believe, anyway... It would be nice if Quagga could be > taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. What is the relationship tcp-md5 --> policy-routing? -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?404496AE.300E1457>