From owner-freebsd-security Wed Apr 17 13: 8:46 2002 Delivered-To: freebsd-security@freebsd.org Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by hub.freebsd.org (Postfix) with ESMTP id A451437B404 for ; Wed, 17 Apr 2002 13:08:40 -0700 (PDT) Received: from dc.cis.okstate.edu (localhost [127.0.0.1]) by dc.cis.okstate.edu (8.11.6/8.11.3) with ESMTP id g3HK8Sx19717 for ; Wed, 17 Apr 2002 15:08:28 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200204172008.g3HK8Sx19717@dc.cis.okstate.edu> To: freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:21.tcpip Date: Wed, 17 Apr 2002 15:08:28 -0500 From: Martin McCormick Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does this advisory apply to systems that do not function as routers but send and receive all their out-of-network traffic through a router? If this is the lamest question that gets asked here, I am sorry, but I want to make sure I am not missing some non-obvious function that this memory leak involves. Thank you very much. Martin McCormick FreeBSD Security Advisories writes: >Topic: routing table memory leak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message