From owner-freebsd-net Fri May 1 23:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17120 for freebsd-net-outgoing; Fri, 1 May 1998 23:42:54 -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 XAA17115 for ; Fri, 1 May 1998 23:42:47 -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 XAA17167; Fri, 1 May 1998 23:41:16 -0700 (PDT) Message-Id: <199805020641.XAA17167@implode.root.com> To: Chris Csanady cc: Pierre Beyssac , freebsd-net@FreeBSD.ORG Subject: Re: Fwd: NetBSD network code improvements In-reply-to: Your message of "Sat, 02 May 1998 01:05:07 CDT." <199805020605.BAA04820@friley585.res.iastate.edu> From: David Greenman Reply-To: dg@root.com Date: Fri, 01 May 1998 23:41:16 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>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.. I think it might be more correct to say "the BSD/OS syn cache mechanism", since that's where the idea originated, although I don't know if the NetBSD code is their own or if it came from BSDI. Yes, I think the SYN cache is probably something we should have. I'm not overly thrilled, however since I think it unnecessarily obscures the code and of course slows it down a bit. -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