From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:19:22 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8433B16A4CE for ; Tue, 2 Mar 2004 13:19:22 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3C0E43D3F for ; Tue, 2 Mar 2004 13:19:21 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 95596 invoked from network); 2 Mar 2004 21:19:20 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 21:19:20 -0000 Message-ID: <4044FA58.87832F22@freebsd.org> Date: Tue, 02 Mar 2004 22:19:20 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce M Simpson References: <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> <20040302160902.GB26977@cell.sick.ru> <20040302193258.GD7115@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org cc: Kris Kennaway Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 21:19:22 -0000 Bruce M Simpson wrote: > > On Tue, Mar 02, 2004 at 07:09:02PM +0300, Gleb Smirnoff wrote: > > I do not insist that AS pathes in kernel are good idea. If you show me an > > other way to get AS information when constructing netflow exports in kernel, > > I'd be thankful. I'd be also thankful if you describe how policy routing can be > > implemented while no AS info in kernel. > > What do other FreeBSD networking withards think? > > I don't see any reason why we couldn't accept, for example, a 32-bit cookie > for abuse by a userland daemon, with pid, as it pleases (via an rtmsg > extension and PF_ROUTE). That is generic enough to provide the tie-in > needed with the userland RIB and the kernel FIB. Ugh, I'm happily running my accounting in userland via BPF/PCAP and it adds only 2-3% CPU load. The BGP information I get from MRT routing table dumps. Pretty slick stuff. We (Claudio and me) are preparing it for public release later this week. >From my experience here and a performance point of view there is no need to do netflow and related accounting stuff in the kernel at all. Userland is much more flexible. > ABI breakage may occur, but I would consider that the PF_ROUTE code is in need > of an overhaul anyway (see my mail to ru@ from some months ago on -current or > -net with code able to panic a kernel through malformed rtmsg contents). Please don't break the current RTM5 API. We will design a nice and much more flexible RTM6 message format later this year. It needs a good deal of deep thought and not be rushed just for the sake of it. -- Andre