From owner-freebsd-questions@freebsd.org Sat Jan 23 07:11:45 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E587A8D85E for ; Sat, 23 Jan 2016 07:11:45 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56EEC1BA3 for ; Sat, 23 Jan 2016 07:11:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-101-208.dynamic.qsc.de [92.195.101.208]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 049E73CEE3; Sat, 23 Jan 2016 08:11:35 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id u0N7BZC9002347; Sat, 23 Jan 2016 08:11:35 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sat, 23 Jan 2016 08:11:35 +0100 From: Polytropon To: freebsd-questions@freebsd.org Cc: Lowell Gilbert Subject: Re: IPFW deny ip range Message-Id: <20160123081135.8c2ab64f.freebsd@edvax.de> In-Reply-To: <44powt3wd7.fsf@lowell-desk.lan> References: <56A2A4F5.3030907@cloudzeeland.nl> <44powt3wd7.fsf@lowell-desk.lan> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2016 07:11:45 -0000 On Fri, 22 Jan 2016 20:41:56 -0500, Lowell Gilbert wrote: > I've never heard of ipfw.rules, though, so you may be a little confused. It's just an alternative configuration file name, such as /etc/ipfw.conf. You typically use it like this in /etc/rc.conf: firewall_script="/etc/ipfw.rules" This script is actually a valid shell script which will be executed, as _commands_. If you use firewall_type="/etc/ipfw.conf" instead, you need to supply _options_ that can follow a call of the ipfw program. The real difference is _script and _type, not the file name per se. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...