Date: Sat, 02 May 1998 01:05:07 -0500 From: Chris Csanady <ccsanady@friley585.res.iastate.edu> To: dg@root.com Cc: Pierre Beyssac <pb@fasterix.freenix.org>, freebsd-net@FreeBSD.ORG Subject: Re: Fwd: NetBSD network code improvements Message-ID: <199805020605.BAA04820@friley585.res.iastate.edu> In-Reply-To: Your message of "Fri, 01 May 1998 16:30:17 PDT." <199805012330.QAA11741@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>[ 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. This is sortof unrelated, but how does our syn flood code compare to the NetBSD syn cache mechanism? The syn cache code seems like a generally good idea.. >>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. Looking through NetBSD's ip_input(), they also seem to have generic hooks for packet filter type things. Perhaps these are worth looking at as well. The code is ifdef'd by PFIL_HOOKS. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805020605.BAA04820>