Wireshark · Ethereal-dev: Re: [Ethereal-dev] ip.addr != display filter does not work withbcasts/mcasts?

Ethereal-dev: Re: [Ethereal-dev] ip.addr != display filter does not work withbcasts/mcasts?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <gharris@xxxxxxxxx>

Date: Mon, 06 Sep 2004 01:05:50 -0700

Alok wrote:

when can i ever use ip.addr!=x.y.z.w in that case??
in other words if we do have an ip.addr!= option should it not be animplicit Source Or Destination

The packet filter code knows nothing of "ip.addr", so it can't treat itdifferently from other fields - "ip.addr != XXX" means "packet containsan 'ip.addr' value that's not XXX", just as "ip.protocol != XXX" means"packet contains an 'ip.protocol' value that's not XXX".

References:
- [Ethereal-dev] ip.addr != display filter does not work with bcasts/mcasts?
  - From: Yaniv Kaul
- Re: [Ethereal-dev] ip.addr != display filter does not work withbcasts/mcasts?
  - From: Martin Regner
- Re: [Ethereal-dev] ip.addr != display filter does not work withbcasts/mcasts?
  - From: Alok

Prev by Date: Re: [Ethereal-dev] ip.addr != display filter does not work withbcasts/mcasts?
Next by Date: [Ethereal-dev] Patch: proto.c - FT_IPv4 and little_endian
Previous by thread: Re: [Ethereal-dev] ip.addr != display filter does not work withbcasts/mcasts?
Next by thread: [Ethereal-dev] Bug report: crash in packet-dcerpc-ndr.c
Index(es):
- Date
- Thread