Date: Thu, 7 Jul 2011 00:44:37 +1000 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Unga <unga888@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: ipfw: getsockopt(IP_FW_ADD): Invalid argument Message-ID: <20110707003258.F84785@sola.nimnet.asn.au> In-Reply-To: <1309961647.1837.YahooMailClassic@web160105.mail.bf1.yahoo.com> References: <1309961647.1837.YahooMailClassic@web160105.mail.bf1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <smithi@nimnet.asn.au> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110707003258.F84785>