[Guy Harris <gharris@xxxxxxxxx>]

On Sun, May 23, 2004 at 07:40:17AM -0700, Jerry Talkington wrote:
> I've just seen this behavior (or something very similar) with a CVS
> build from yesterday.  ip.add != 10.100.128.81 doesn't properly filter
> out the traffic from that address.

"ip.addr != 10.100.128.81" means "packet has an 'ip.addr' value equal to
something other than 10.100.128.81"; a packet from 10.100.128.81, unless
it's being sent from the machine to itself, has an "ip.addr" value equal
to something other than 10.100.128.81 - the address it's sent to.

"not (ip.addr eq 10.100.128.81)", however, means "packet does not have
an 'ip.addr' value equal to 10.100.128.81", which is not the same as
"packet has an 'ip.addr' value equal to something other than
10.100.128.81", because IPv4 packets normally have at least two
"ip.addr" values - the from address and the to address.

So "ip.addr != 10.100.128.81" won't filter out all traffic to or from
10.100.128.81 (unless all that traffic is from 10.100.128.81 to
10.100.128.81) - but "not (ip.addr eq 10.100.128.81)" will.