From owner-freebsd-bugs Wed Apr 12 19:20: 9 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2381337BCAA for ; Wed, 12 Apr 2000 19:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id TAA12580; Wed, 12 Apr 2000 19:20:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AC0DE37BB97 for ; Wed, 12 Apr 2000 19:18:39 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id TAA12378; Wed, 12 Apr 2000 19:18:39 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Message-Id: <200004130218.TAA12378@freefall.freebsd.org> Date: Wed, 12 Apr 2000 19:18:39 -0700 (PDT) From: brian@pocketscience.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: bin/17963: NATD appears to memory leak when a connection fails from the internal network to the external network. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 17963 >Category: bin >Synopsis: NATD appears to memory leak when a connection fails from the internal network to the external network. >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 12 19:20:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Brian Nelson >Release: 3.4-STABLE >Organization: PocketScience, Inc >Environment: FreeBSD vpn1.pocketmail.com 3.4-STABLE FreeBSD 3.4-STABLE #0: Wed Apr 12 11:14:46 PDT 2000 notgod@vpn1.pocketmail.com:/usr/src/sys/compile/VPN i386 >Description: In production, we are making several connection attempts to do AOL polling. Some are getting a failure to connect (actually, a significant number are). Since we have noticed this behavior (a bug on our end), we have also noticed that natd memory leaks, actually pretty significantly. We're pulling ~50k connections/hour. It takes ~16 hours for the daemon to leak enough that the network dies on the machine, until you restart natd. >How-To-Repeat: Set up natd. from an internal machine, make several network connections that get dropped on the remote end (not denied, but connection timeouts) >Fix: None at this time. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message