From owner-freebsd-current  Fri Jan  9 14:29:42 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA19761
          for current-outgoing; Fri, 9 Jan 1998 14:29:42 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19745
          for <current@freebsd.org>; Fri, 9 Jan 1998 14:29:32 -0800 (PST)
          (envelope-from daveh@CSUA.Berkeley.EDU)
Received: (from daveh@localhost) 
	by soda.CSUA.Berkeley.EDU (8.8.8/) id OAA04841
        for current@freebsd.org; Fri, 9 Jan 1998 14:29:01 -0800 (PST)
        env-from (daveh)
Date: Fri, 9 Jan 1998 14:29:01 -0800 (PST)
From: daveh@CSUA.Berkeley.EDU (David M. Holloway)
Message-Id: <199801092229.OAA04841@soda.CSUA.Berkeley.EDU>
To: current@freebsd.org
Subject: Re: Firewall in kernel?
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>       Looks like you compiled the firewall into your kernel without enabling
> the loading of the script in /etc/rc.conf. If you are going to compile
> firewall stuff into your kernel, I *highly* recommend using the default
> to accept rule option at least till you get to know things better. 


and to imagine, that Sun Microsystems only just today
annoucned plans to put firewall support in their workstations.