Date: Mon, 24 Jun 2002 19:04:53 -0700 (PDT) From: Chris Pepper <pepper@mail.rockefeller.edu> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/39814: GENERIC kernel should include ipfw Message-ID: <200206250204.g5P24r2A052851@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206250204.g5P24r2A052851>