From owner-freebsd-stable Sun Oct 14 2:44:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 3F04B37B406; Sun, 14 Oct 2001 02:44:52 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id B780913B; Sun, 14 Oct 2001 10:44:32 +0100 (BST) Date: Sun, 14 Oct 2001 10:44:32 +0100 From: Josef Karthauser To: David Kelly Cc: "Thomas T. Veldhouse" , Alfatrion , "Maine LOA List Admin (Brent Bailey)" , "Hartmann, O." , freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: IPFW or IPFILTER? Message-ID: <20011014104432.L31066@tao.org.uk> Mail-Followup-To: Josef Karthauser , David Kelly , "Thomas T. Veldhouse" , Alfatrion , "Maine LOA List Admin (Brent Bailey)" , "Hartmann, O." , freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG References: <20011012154307.O52936-100000@klima.physik.uni-mainz.de> <003601c15328$db264480$24b4a8c0@pretorian> <3BC700CE.8000201@cybertron.tmfweb.nl> <010001c15331$23f1da00$3028680a@tgt.com> <20011012130628.A11301@grumpy.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="1hKfHPzOXWu1rh0v" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011012130628.A11301@grumpy.dyndns.org>; from dkelly@hiwaay.net on Fri, Oct 12, 2001 at 01:06:28PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --1hKfHPzOXWu1rh0v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 12, 2001 at 01:06:28PM -0500, David Kelly wrote: >=20 > The only problem I have with the "failed to write back packet" message > is that it doesn't say enough about why the packet was dropped. Or > details about the packet which was dropped. The best "cure" i've found > is to set natd's logging facility to "security" so both natd and ipfw > log to /var/log/security (default /etc/syslog.conf) placing both what > natd say and ipfw say close enough in one file to connect both views of > the same incident. Easily fixed. Just run 'natd -v' and you'll get more verbose output. Joe --1hKfHPzOXWu1rh0v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvJXoAACgkQXVIcjOaxUBbHfQCg7hqFw/VC6OGiDsAkpMsBBfbI AmoAoOYsAhdkaQyOzhiCrm9dXM0JsyNt =b/QE -----END PGP SIGNATURE----- --1hKfHPzOXWu1rh0v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message