Date: Wed, 26 Mar 2003 08:39:38 -0800 From: "Drew Tomlinson" <drew@mykitchentable.net> To: "Dan Pelleg" <daniel+bsd@pelleg.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: IPFW - Why Doesn't This Rule Match? -- SOLVED Message-ID: <001801c2f3b6$4bd0d590$6e2a6ba5@tagalong> References: <00cc01c2f303$07ec8df0$6e2a6ba5@tagalong> <u2s65q7xkcj.fsf@gs166.sp.cs.cmu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Dan Pelleg" <daniel+bsd@pelleg.org> To: "Drew Tomlinson" <drew@mykitchentable.net> Cc: "FreeBSD Questions" <freebsd-questions@freebsd.org> Sent: Tuesday, March 25, 2003 12:27 PM Subject: Re: IPFW - Why Doesn't This Rule Match? > "Drew Tomlinson" <drew@mykitchentable.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001801c2f3b6$4bd0d590$6e2a6ba5>