From owner-freebsd-questions@FreeBSD.ORG Wed Jul 6 14:44:39 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0711106564A for ; Wed, 6 Jul 2011 14:44:39 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 400B48FC13 for ; Wed, 6 Jul 2011 14:44:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id p66EibPi033106; Thu, 7 Jul 2011 00:44:37 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 7 Jul 2011 00:44:37 +1000 (EST) From: Ian Smith To: Unga In-Reply-To: <1309961647.1837.YahooMailClassic@web160105.mail.bf1.yahoo.com> Message-ID: <20110707003258.F84785@sola.nimnet.asn.au> References: <1309961647.1837.YahooMailClassic@web160105.mail.bf1.yahoo.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-477406475-1309963477=:84785" Cc: freebsd-questions@freebsd.org Subject: Re: ipfw: getsockopt(IP_FW_ADD): Invalid argument X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2011 14:44:39 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-477406475-1309963477=:84785 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT On Wed, 6 Jul 2011, Unga wrote: > On Tue, 7/5/11, Ian Smith wrote: > > > Does anybody successfully use the "ipfw fwd"? If so > > > in which FreeBSD version? > > > Not I, but many do.  On the face of it the rule looks > > correct.  Do you > > have a TCP service running on localhost:1234 ?  Does > > wlan0 exist?  You > > may do better posting to the freebsd-ipfw list, with more > > information. > > > cheers, Ian > > Hi Ian > > I have added 'options IPFIREWALL' and rebuilt all, now 'ipfw fwd' > works well. > > So the 'options IPFIREWALL_FORWARD' alone is insufficient, the > 'options IPFIREWALL' is also required. Right; I guess if you're building it into kernel you have to configure all relevant options there too. That could be more explicitly stated. > Thank you and all others who helped me in this regard. Glad it's working. Another win for the collective wisdom .. cheers, Ian --0-477406475-1309963477=:84785--