From owner-freebsd-questions Thu May 24 21:52:43 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id A8A0237B422 for ; Thu, 24 May 2001 21:52:39 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f4P4qSk80775; Thu, 24 May 2001 21:52:28 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Barton" , "Steve Price" Cc: Subject: RE: reloading firewall rules remotely Date: Thu, 24 May 2001 21:52:27 -0700 Message-ID: <000101c0e4d6$7f73be80$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <3B0DB74F.7289B884@DougBarton.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Let me warn you that there's a right way and a wrong way to do this. Typically, firewalls with an explicit accept at the end are intended to be used for "masking off" specific undesirable protocols. For example if you had a network that you didn't want to take responsibility for firewalling (perhaps your an ISP) but you wanted to block a specific protocol or IP number. Or, if you put rules like this on an internal corporate WAN which you didn't want employees using to play network games. In this case the rule list is a number of "deny" rules. Firewalls with an explicit "deny" are used for Internet firewalls because the idea here is you want to create "holes" for only very specifically defined protocols. In this case the rule list is a number of "accept" rules. If your testing a firewall then you might want to set it up with an explicit accept, then _manually_ put in the deny everything rule at the end of the list. That way when your working on it, you remove that rule, do your work, then put it back in for testing. But, most security authorities feel that the explicit deny is much safer for an Internet firewall. Keep this in mind when creating your rule set. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Barton >Sent: Thursday, May 24, 2001 6:37 PM >To: Steve Price >Cc: questions@FreeBSD.ORG >Subject: Re: reloading firewall rules remotely > > >Steve Price wrote: >> >> Ok now I feel more stupid that I usually do. What is the proper >> method to reloading ipfw rules from a remote box? I thought >> running it in the background worked but evidently not. :( > > While the advice you got on this old thread was mostly >good, the most >obvious solution was not stated. Namely, make your default rule "accept" by >including that kernel option. Then you can reload rules all day long and >not have to worry, unless you need the ultra-paranoid protection that >having the default of "deny" gives you. > >-- > I need someone really bad. Are you really bad? > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message