From owner-freebsd-ipfw@FreeBSD.ORG Tue Jul 5 19:26:07 2011 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3A03106564A for ; Tue, 5 Jul 2011 19:26:06 +0000 (UTC) (envelope-from fabian@wenks.ch) Received: from batman.home4u.ch (batman.home4u.ch [IPv6:2001:8a8:1005:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 90A538FC0A for ; Tue, 5 Jul 2011 19:26:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at home4u.ch Received: from flashback.wenks.ch (fabian@flashback.wenks.ch [62.12.173.4]) (authenticated bits=0) by batman.home4u.ch (8.14.4/8.14.4) with ESMTP id p65JQ4fb050711 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 5 Jul 2011 21:26:04 +0200 (CEST) (envelope-from fabian@wenks.ch) Message-ID: <4E13654B.4060006@wenks.ch> Date: Tue, 05 Jul 2011 21:26:03 +0200 From: Fabian Wenk User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-ipfw@freebsd.org References: <1309890156.56237.YahooMailClassic@web160113.mail.bf1.yahoo.com> <4E135BEC.80708@wenks.ch> <4E136020.5000206@yandex.ru> In-Reply-To: <4E136020.5000206@yandex.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ipfw fwd on FreeBSD 8.1, does it work? X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2011 19:26:07 -0000 Hello Andrey On 05.07.2011 21:04, Andrey V. Elsukov wrote: > fwd does not work when ipfw loaded as module. Ups, did not know this exactly, thanks for clarify. But it really makes sense that both options are in the kernel. After sending out my mail, it somehow crossed my mind that this eventually would not work. As I usually have almost all things needed in my custom built kernel anyway (including IPFIREWALL_FORWARD), I never had that problem. Sorry Unga, you need to build a new kernel with both options. bye Fabian