From owner-freebsd-net Fri May 1 16:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14977 for freebsd-net-outgoing; Fri, 1 May 1998 16:31:55 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14964 for ; Fri, 1 May 1998 16:31:49 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA11741; Fri, 1 May 1998 16:30:17 -0700 (PDT) Message-Id: <199805012330.QAA11741@implode.root.com> To: Pierre Beyssac cc: freebsd-net@FreeBSD.ORG Subject: Re: Fwd: NetBSD network code improvements In-reply-to: Your message of "Fri, 01 May 1998 20:58:33 +0200." <19980501205833.A655@fasterix.frmug.fr.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 01 May 1998 16:30:17 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >[ discussion copied to freebsd-net, please remove -current when replying ] > >On Fri, May 01, 1998 at 02:13:51PM -0400, Garrett Wollman wrote: >> We should think carefully about what WE actually WANT to do (which is >> not necessarily the same as what NASA is paying Jason to do). > >I think A lot of their stuff is generally useful, the MTU discovery >stuff for example (although I don't exactly know what is in -current >and maybe we don't need to integrate NetBSD stuff). We've had Path MTU Discovery in FreeBSD for a couple of years now. It includes support for timing out clone routes. >The fast forwarding stuff is useful for people using FreeBSD as a >fast router. It is modular enough that I ported it in 2 hours, and >I'm currently running it. Everything is in one file (ip_flow.c) >and you just need to add hooks calling it when receiving packets >from the interfaces. Works ok for me so far between PPP and my >ethernet (which doesn't say much about the performance improvement >:-)). I'll send the patches to the list soon. The only problem that >I see is that it clutters up the kernel even if you don't use it >(in NetBSD, it is compiled in only if you have the GATEWAY option, >but you can't do that in FreeBSD since it's a kernel configuration >variable). We should probably make it an explicit option but other >than that I don't see any reason for not taking it. Yeah, that's pretty neat stuff and I'd like to see it as part of FreeBSD. I'm a bit concerned about its interaction (or lack of) with ipfw, however. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message