From owner-freebsd-net Thu Jul 6 19:24:24 2000 Delivered-To: freebsd-net@freebsd.org Received: from mrout1.yahoo.com (mrout1.yahoo.com [208.48.125.95]) by hub.freebsd.org (Postfix) with ESMTP id 6F10037BD7D for ; Thu, 6 Jul 2000 19:24:16 -0700 (PDT) (envelope-from jayanth@yahoo-inc.com) Received: from milk.yahoo.com (milk.yahoo.com [206.251.16.37]) by mrout1.yahoo.com (8.10.0/8.10.0/y.out) with ESMTP id e672O2488469 for ; Thu, 6 Jul 2000 19:24:03 -0700 (PDT) Received: (from jayanth@localhost) by milk.yahoo.com (8.8.8/8.6.12) id TAA26629 for net@FreeBSD.ORG; Thu, 6 Jul 2000 19:24:02 -0700 (PDT) Date: Thu, 6 Jul 2000 19:24:02 -0700 From: jayanth To: net@FreeBSD.ORG Subject: deleting cloned routes Message-ID: <20000706192402.A25086@yahoo-inc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One of the issues during a syn flood is that the routing table fills up easily because of the cloned routes being generated. In Freebsd current, an incomplete connection is randomly dropped when the listen queue overflows. This logic could be easily extended by deleting the cloned route that is associated with the connection being dropped , if there is no information cached for that route. Is this a reasonable fix ? jayanth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message