From owner-freebsd-stable Thu Jan 24 23:12: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hsd.com.au (CPE-144-132-42-44.vic.bigpond.net.au [144.132.42.44]) by hub.freebsd.org (Postfix) with ESMTP id E6C2D37B402 for ; Thu, 24 Jan 2002 23:12:02 -0800 (PST) Received: from ariel by hsd.com.au with SMTP (MDaemon.v3.0.1.R) for ; Fri, 25 Jan 2002 18:10:20 +1100 Reply-To: From: "Andrew Cowan" To: "Crist J. Clark" , "Patrick Greenwell" Cc: Subject: RE: Firewall config non-intuitiveness Date: Fri, 25 Jan 2002 18:10:19 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20020124220302.N87663@blossom.cjclark.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-MDaemon-Deliver-To: stable@FreeBSD.ORG X-Return-Path: andrew.cowan@hsd.com.au X-MDRcpt-To: stable@FreeBSD.ORG 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 > On Thu, Jan 24, 2002 at 08:21:50PM -0800, Patrick Greenwell wrote: > > > > I recently got bit by this: I have firewall options configured into my > > kernel, and made the mistake of thinking that in order to disable > > this functionality to allow all traffic that I merely needed to > remove the > > firewall_enable paramater from my rc.conf since firewall_enable > is set to NO in > > /etc/defaults/rc.conf. > > > > This did not have the intended result of disabling the > firewall, rather a > > default deny was applied. If firewall_enable is set to NO, > wouldn't it make > > more sense to have the init scripts set net.inet.ip.fw.enable > to 0, or am I > > missing something? > > > > Opinions welcome. > > I think this is a valid point. When 'firewall_enable="NO"' the > firewalling should be disabled with the net.inet.ip.fw.enable > sysctl(8). Sounds good - just print a big fat warning message when it does so :) > That said, it _may_ be a little late to make this change in > -STABLE. Although the name may be misleading, I think the rest of the > documentation is accurate. Besides all the stuff people have quoted > about the 'options IPFIREWALL' in the kernel, I think rc.conf(5) is > fairly clear, > > firewall_enable > (bool) Set to ``YES'' to load firewall rules > at startup. > If the kernel was not built with IPFIREWALL, > the ipfw ker- > nel module will be loaded. See also ipfilter_enable. > > In that it only says special things happen when it is "YES" and > doesn't say it is explicitly disabled when set to "NO." Since this is > such a security critical option, I really hesitate when it comes to > changing this in -STABLE. -CURRENT OTOH... > -- > Crist J. Clark | cjclark@alum.mit.edu > | cjclark@jhu.edu > http://people.freebsd.org/~cjc/ | cjc@freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message