From owner-freebsd-stable Thu Jan 30 0: 7:18 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E96637B401 for ; Thu, 30 Jan 2003 00:07:17 -0800 (PST) Received: from 12-234-22-23.client.attbi.com (12-234-22-23.client.attbi.com [12.234.22.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E79143F43 for ; Thu, 30 Jan 2003 00:07:17 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from slave.gorean.org (pcdy48r1ggi399kh@slave.gorean.org [10.0.0.1]) by 12-234-22-23.client.attbi.com (8.12.6/8.12.6) with ESMTP id h0U87GfS001030 for ; Thu, 30 Jan 2003 00:07:16 -0800 (PST) (envelope-from DougB@FreeBSD.org) Date: Thu, 30 Jan 2003 00:07:16 -0800 (PST) From: Doug Barton To: freebsd-stable@FreeBSD.org Subject: Re: ipfw/natd problem with tonight's releng_4 In-Reply-To: <20030129010515.C1559@12-234-22-23.pyvrag.nggov.pbz> Message-ID: <20030130000219.T341@12-234-22-23.pyvrag.nggov.pbz> References: <20030129010515.C1559@12-234-22-23.pyvrag.nggov.pbz> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Ok, I found the problem, thanks to someone who wrote me privately. It turns out that even if you put IPDIVERT in the CFLAGS for the ipfw module Makefile, that option still has to be in the kernel config file. This should probably be documented, since the whole process of creating the module with the appropriate options was a little opaque to me, and this bit escaped me completely. Thanks to those who responded, Doug -- If it's moving, encrypt it. If it's not moving, encrypt it till it moves, then encrypt it some more. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message