Date: Wed, 20 Jun 2001 13:16:56 +0200 From: "Patrick O'Reilly" <patrick@mip.co.za> To: "Joe Clarke" <marcus@marcuscom.com> Cc: "FreeBSD Question List" <freebsd-questions@freebsd.org> Subject: RE: ipfw Message-ID: <NDBBIMKICMDGDMNOOCAIEEMECMAA.patrick@mip.co.za> In-Reply-To: <20010620014537.E9098-100000@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
And, while you are about it - you might want to include: options IPFIREWALL_FORWARD # Enable support for transparent proxying options DUMMYNET # Enable the Dummynet Traffic Shaping pipes options IPDIVERT # enable ipfw to divert to NAT, etc. Patrick. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Joe Clarke Sent: 20 June 2001 07:48 To: Brad McNeney Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ipfw Do you have options IPFIREWALL in the kernel, or the ipfw.ko module loaded? You need IPFIREWALL before you can have IPFIREWALL_VERBOSE. Joe Clarke On Tue, 19 Jun 2001, Brad McNeney wrote: > I'm having no luck using ipfw -- getting thingslike: > # ipfw -f flush > ipfw: setsockopt(IP_FW_FLUSH): Protocol not available > > or > # ipfw list > ipfw: getsockopt(IP_FW_GET): Protocol not available > > I built a 4.3-STABLE kernel with options IPFIREWALL_VERBOSE > and have set firewall_type="OPEN" in /etc/rc.conf. > > I'm sure I'm missing something obvious here... Any thoughts? > > Brad > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBIMKICMDGDMNOOCAIEEMECMAA.patrick>