From owner-freebsd-bugs Mon Jun 24 19:10:45 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B9C6E37B404 for ; Mon, 24 Jun 2002 19:10:01 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g5P2A1P67974; Mon, 24 Jun 2002 19:10:01 -0700 (PDT) (envelope-from gnats) Received: from nwww.freebsd.org (www.FreeBSD.org [216.136.204.117]) by hub.freebsd.org (Postfix) with ESMTP id BFED437B40B for ; Mon, 24 Jun 2002 19:04:53 -0700 (PDT) Received: from www.freebsd.org (localhost [127.0.0.1]) by nwww.freebsd.org (8.12.2/8.12.2) with ESMTP id g5P24rhG052852 for ; Mon, 24 Jun 2002 19:04:53 -0700 (PDT) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.2/8.12.2/Submit) id g5P24r2A052851; Mon, 24 Jun 2002 19:04:53 -0700 (PDT) Message-Id: <200206250204.g5P24r2A052851@www.freebsd.org> Date: Mon, 24 Jun 2002 19:04:53 -0700 (PDT) From: Chris Pepper To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/39814: GENERIC kernel should include ipfw Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 39814 >Category: kern >Synopsis: GENERIC kernel should include ipfw >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jun 24 19:10:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Chris Pepper >Release: 4.6-STABLE >Organization: >Environment: FreeBSD guest.reppep.com 4.6-STABLE FreeBSD 4.6-STABLE #0: Tue Jun 18 21:27:59 EDT 2002 pepper@guest.reppep.com:/usr/obj/usr/src/sys/GENERIC i386 >Description: ipfw should be in the GENERIC (default) kernel configuration. Firewalling shouldn't require a kernel rebuild. Further, this increases the likelihood of shooting oneself in the foot when activating firewalling, if it's not yet configured properly (over providing a non-restrictive default ruleset, and then tightening it to cause a change). >How-To-Repeat: Install 4.5-RELEASE >Fix: Add IPFIREWALL (v4) options to GENERIC, and if IPv6 is activated, add IPFIREWALL (v6) options as well. options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 options IPV6FIREWALL_DEFAULT_TO_ACCEPT >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message