From owner-freebsd-stable Thu Dec 9 15: 4: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D8F32156B0; Thu, 9 Dec 1999 15:03:57 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA02150; Thu, 9 Dec 1999 15:00:31 -0800 (PST) Date: Thu, 9 Dec 1999 15:00:30 -0800 (PST) From: Julian Elischer To: Joe Greco Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <199912092144.PAA91916@aurora.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so can it be committed? On Thu, 9 Dec 1999, Joe Greco wrote: > The patch previously mentioned has completely fixed my problem, as far as I > can tell. > > routetbl 131 17K 25K 40960K 93624 0 0 16,32,64,128,256 > > after a day of uptime. > > > here's mine.. > > this is from a single homed machine, with a default route. it's also a IRC > > server (irc.stanford.edu), with a LOT of filtering of inbound traffic. > > > > FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 > > > > 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 > > > > routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 > > > > note that the table maxed out at some point (during a DoS attack.) > > > > root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc > > 70 409 4741 > > > > looks like it leaked 135 in 2.8 days.. > > > > > > -- Welcome My Son, Welcome To The Machine -- > > Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org > > | P.O. Box 9792, Stanford, Ca 94309-9792 > > -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message