From owner-freebsd-security Wed Jan 31 10:22:29 2001 Delivered-To: freebsd-security@freebsd.org Received: from mail.gmx.net (sproxy.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id DC19037B503 for ; Wed, 31 Jan 2001 10:22:08 -0800 (PST) Received: (qmail 30860 invoked by uid 0); 31 Jan 2001 18:22:06 -0000 Received: from pc19e969b.dip.t-dialin.net (HELO forge.local) (193.158.150.155) by mail.gmx.net (mail09) with SMTP; 31 Jan 2001 18:22:06 -0000 Received: from thomas by forge.local with local (Exim 3.16 #1 (Debian)) id 14O1tL-0000Vm-00 for ; Wed, 31 Jan 2001 19:22:03 +0100 Date: Wed, 31 Jan 2001 19:22:03 +0100 To: freebsd-security@freebsd.org Subject: Re: NATD insecure / DoS? Message-ID: <20010131192203.A1959@crow.dom2ip.de> Mail-Followup-To: tmoestl@gmx.net, freebsd-security@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from natedac@kscable.com on Wed, Jan 31, 2001 at 12:05:41PM -0600 From: Thomas Moestl Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jan 31, 2001 at 12:05:41PM -0600, Nate Dannenberg wrote: > The IP address of this machine (which runs 4.2-Release), which is normally > more or less static, changed yesterday. When that happened, I ended up > without any Internet connectivity, and I think it was NATD's fault: Are you running natd with the -dynamic option? If not, check natd(8). - thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message