From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 11:38:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D63216A4CE; Tue, 2 Mar 2004 11:38:38 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB64C43D2D; Tue, 2 Mar 2004 11:38:37 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 00E946520E; Tue, 2 Mar 2004 19:38:37 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28383-02-16; Tue, 2 Mar 2004 19:38:36 +0000 (GMT) Received: from saboteur.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 31850651FA; Tue, 2 Mar 2004 19:38:32 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 2243018; Tue, 2 Mar 2004 19:38:31 +0000 (GMT) Date: Tue, 2 Mar 2004 19:38:31 +0000 From: Bruce M Simpson To: Andre Oppermann Message-ID: <20040302193831.GF7115@saboteur.dek.spc.org> Mail-Followup-To: Andre Oppermann , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org, James References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <404496AE.300E1457@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <404496AE.300E1457@freebsd.org> cc: Wes Peters cc: freebsd-current@freebsd.org cc: James cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 19:38:38 -0000 On Tue, Mar 02, 2004 at 03:14:06PM +0100, Andre Oppermann wrote: > > 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. This sounds like an excellent idea. I agree that the PF_ROUTE interface is long in need of an overhaul (see previous mail to this effect in archives). The bit mask extraction sockaddr fandango we do to get things like netmasks in and out is nothing short of evil. The routing code could also benefit from some style cleanup and the use of the UMA zone allocator. > > > 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? It's another one of those cross OS features which, whilst deceptively simple on the surface, requires some hacking of the routing daemon to grok PF_KEY messages (a well defined interface). We need a well-defined interface which is hopefully cross OS for policy routing. BMS