From owner-freebsd-net Thu Nov 14 7:12: 1 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A001337B401 for ; Thu, 14 Nov 2002 07:12:00 -0800 (PST) Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 540C343E3B for ; Thu, 14 Nov 2002 07:12:00 -0800 (PST) (envelope-from kudzu@tenebras.com) Received: (qmail 5350 invoked from network); 14 Nov 2002 15:11:59 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by 0 with SMTP; 14 Nov 2002 15:11:59 -0000 Message-ID: <3DD3BD3F.7070506@tenebras.com> Date: Thu, 14 Nov 2002 07:11:59 -0800 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en, fr-fr, ru MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: natd woes with 4.7-RELEASE-p2 References: <3DD2B1EF.4020603@tenebras.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As it stands, on a system with almost no network traffic, natd climbs to about 95% CPU, latency through the firewall quadruples, and killing and restarting natd always cures the problem. I'd like to find a better way, but as it stands it needs to be restarted about every 10 hours or so. Any insight would be welcome. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message