From owner-freebsd-ipfw@FreeBSD.ORG Mon Jul 18 09:09:01 2005 Return-Path: X-Original-To: freebsd-ipfw@freebsd.org Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6038516A41C for ; Mon, 18 Jul 2005 09:09:01 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 272AD43D49 for ; Mon, 18 Jul 2005 09:09:01 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id j6I9906L013254 for ; Mon, 18 Jul 2005 02:09:00 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id j6I990K0013253 for freebsd-ipfw@freebsd.org; Mon, 18 Jul 2005 02:09:00 -0700 (PDT) (envelope-from rizzo) Date: Mon, 18 Jul 2005 02:09:00 -0700 From: Luigi Rizzo To: freebsd-ipfw@freebsd.org Message-ID: <20050718020900.D13026@xorpc.icir.org> References: <200507131557.j6DFvrSY024295@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <200507131557.j6DFvrSY024295@lurza.secnetix.de>; from olli@lurza.secnetix.de on Wed, Jul 13, 2005 at 05:57:53PM +0200 Subject: Re: "or" blocks in IPFW2 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 09:09:01 -0000 On Wed, Jul 13, 2005 at 05:57:53PM +0200, Oliver Fromme wrote: > Hi, ... > # ipfw add allow tcp from any to any \{ in recv fxp0 or out xmit fxp0 \} > 04400 allow tcp from any to any in { recv fxp0 or out } xmit fxp0 surely the parser is not very robust and should complain :) This said, the 'or' is a conjunction of individual options, and 'in' is one option and 'recv fxp0' is another one. if you need something different you probably have to write separate rules. cheers luigi > Of course, now the rule does something completely different > which doesn't even make any sense. Most confusingly, I > don't get an error message or even a warning from the parser. > > Is this a bug in ipfw, or a bug in the manpage, or do I > just misunderstand things? Do I have to write two separate > rules? > > Thanks in advance! > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "Unix gives you just enough rope to hang yourself -- > and then a couple of more feet, just to be sure." > -- Eric Allman > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org"