From owner-freebsd-questions@FreeBSD.ORG Wed Mar 26 08:39:43 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28AD437B404 for ; Wed, 26 Mar 2003 08:39:43 -0800 (PST) Received: from blacklamb.mykitchentable.net (207-173-231-121.bras01.elk.ca.frontiernet.net [207.173.231.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46F1443F75 for ; Wed, 26 Mar 2003 08:39:42 -0800 (PST) (envelope-from drew@mykitchentable.net) Received: from tagalong (unknown [165.107.42.110]) by blacklamb.mykitchentable.net (Postfix) with SMTP id 65DD9EE559; Wed, 26 Mar 2003 08:39:39 -0800 (PST) Message-ID: <001801c2f3b6$4bd0d590$6e2a6ba5@tagalong> From: "Drew Tomlinson" To: "Dan Pelleg" References: <00cc01c2f303$07ec8df0$6e2a6ba5@tagalong> Date: Wed, 26 Mar 2003 08:39:38 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Status: No, hits=-12.9 required=5.0 tests=ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,REFERENCES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: FreeBSD Questions Subject: Re: IPFW - Why Doesn't This Rule Match? -- SOLVED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 16:40:14 -0000 ----- Original Message ----- From: "Dan Pelleg" To: "Drew Tomlinson" Cc: "FreeBSD Questions" Sent: Tuesday, March 25, 2003 12:27 PM Subject: Re: IPFW - Why Doesn't This Rule Match? > "Drew Tomlinson" writes: > > > I am using the following rules to match traffic on my home network with a > > FBSD 4.8 firewall. The first rule matches but the second doesn't. Here's > > the rules: > > > > # Match this specific traffic > > 00700 288 329708 count ip from 192.168.1.3 8080 to any > > > > # Match everything else > > 00800 0 0 count ip from not 192.168.1.3 8080 to any > > > > Can anyone tell me what I am missing? > > > > Thanks, > > > > Drew > > Probably because the "not" applies just to the address, and not to the port > number. Thanks, that was it. By changing the rule to 'not 192.168.1.3 not 8080', the rule started matching packets as I expected. I appreciate the help! Drew