From owner-freebsd-stable Mon Jan 28 16:10:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 3431E37B400 for ; Mon, 28 Jan 2002 16:10:20 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id RAA13779; Mon, 28 Jan 2002 17:10:11 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g0T0ABJ77586; Mon, 28 Jan 2002 17:10:11 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15445.59490.902141.369997@caddis.yogotech.com> Date: Mon, 28 Jan 2002 17:10:10 -0700 To: "M. Warner Losh" Cc: nate@yogotech.com, cjm2@earthling.net, stable@FreeBSD.ORG, n@nectar.cc Subject: Re: Proposed Solution To Recent "firewall_enable" Thread. [Please Read] In-Reply-To: <20020128.170659.97077059.imp@village.org> References: <15445.54136.731213.811969@caddis.yogotech.com> <20020128.154656.123855750.imp@village.org> <15445.54755.551301.284078@caddis.yogotech.com> <20020128.170659.97077059.imp@village.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > Nate Williams writes: > : > : Yes, and I think having this is a good thing. However, what are the > : > : default values for the variables? > : > > : > In previous mail I suggested: > : > > : > ipfw_enable=no > : > ipfw_firewall_enable=yes > : > : Gotcha, I confused ipfw_enable with ipfw_firewall_enable. > : Unfortunately, it's not obvious which one the users should use to enable > : the functionality. > : > : Now we have two variables that *appear* to be redundant.... > > That's as far as I'm willing to go. The rest would be a documentation > issue. It can be clearly stated how to disable things in the > documentation. Sorry, but I think this would be *worse* (ie; more confusing) than the already confusing setup we have now. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message