From owner-freebsd-questions Sun Oct 7 13:12:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from warsaw.scl.ameslab.gov (warsaw.scl.ameslab.gov [147.155.137.63]) by hub.freebsd.org (Postfix) with ESMTP id 9C37B37B401 for ; Sun, 7 Oct 2001 13:12:50 -0700 (PDT) Received: (from kparz@localhost) by warsaw.scl.ameslab.gov (8.11.6/8.11.6) id f97KE0218152; Sun, 7 Oct 2001 15:14:00 -0500 (CDT) (envelope-from kparz) Date: Sun, 7 Oct 2001 15:13:59 -0500 From: Krzysztof Parzyszek To: questions@FreeBSD.ORG Cc: Tim Erlin Subject: Re: IPFW rules question Message-ID: <20011007151359.A90569@warsaw.scl.ameslab.gov> References: <20011007194900.97491.qmail@web11702.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011007194900.97491.qmail@web11702.mail.yahoo.com>; from tperlin@yahoo.com on Sun, Oct 07, 2001 at 12:49:00PM -0700 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 On Sun, Oct 07, 2001 at 12:49:00PM -0700, Tim Erlin wrote: > two quick questions: > > 1. How do I get ipfw to read rc.firewall without > restarting? It's not listed as a process, so I can't > send it a HUP signal... Just invoke /etc/rc.firewall. Make sure all of the shell variables that rc.firewall references are properly set. You may want to create a shell script that does it, or create a shell script that completely takes over IPFW configuration and run it from rc.firewall/rc.local/whatever on startup. In the latter case you'd basically rerun that script... > 2. What's wrong with this rule? > > ipfw add deny all from any to 192.168.40.7 587 Protocol ``any'' means IP, and IP does not have a concept of port. Port numbers only make sense for TCP and UDP. Krzysztof To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message