Ethereal-dev: [Ethereal-dev] multiple versions of the same IDL file

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Patnaik, Anjela" <APatnaik@xxxxxxxxx>
Date: Tue, 3 Sep 2002 18:33:44 -0400 
I have built some GIOP plugins using
the Makefiles and idl2eth.

Now, several of my IDL files have newer
versions so I was wondering if I need to
rebuild the whole Ethereal package for
each version.


Say, I had
idlFile1 v1
idlFile2 v1
These are compiled into Ethereal V1

Then, if I also have idlFile2 v2, do I need
a Ethereal V2 or can I just recompile the changed
IDL using a new name and have both versions
available via the same executable?

Thanks let me know...



-----Original Message-----
From: Guy Harris [mailto:gharris@xxxxxxxxx]
Sent: Tuesday, September 03, 2002 6:27 PM
To: Patnaik, Anjela
Cc: 'ethereal-dev@xxxxxxxxxxxx'
Subject: Re: [Ethereal-dev] tethereal filter on specific protocol


On Tue, Sep 03, 2002 at 04:58:33PM -0400, Patnaik, Anjela wrote:
> Actually, I meant a Read Capture filter.

There is no such thing as a "read capture filter".

There are capture filters, which are implemented by libpcap (*NOT*
directly by Ethereal/Tethereal); the syntax and capabilities of those
are described by the tcpdump man page, and they do *NOT* include the
ability to recognize particular GIOP-based protocols.

There are also read filters, which are implemented by
Ethereal/Tethereal; the syntax and capabilities of those are described
by the Ethereal and Tethereal man pages, and they include the ability to
select any particular protocol.

> Basically, if I have 20+ GIOP plugins built,
> how do I capture only packets that dissect
> a given GIOP plugin ??

Packets don't dissect, they are dissected, and plugins aren't dissected,
they dissect.

What you presumably meant is "how do I capture only packets for the
GIOP-based protocol that is dissected by a given GIOP plugin?"

The answer to that is the same as it was in my last message, i.e.:

	You would have to use a "read filter" to select your protocol,
	unless you know the TCP port number your protocol will be using. 
	A "read filter" has the syntax of a display filter, so it'd just
	be the protocol name you assigned to the protocol your plugin
	dissects.

	See the Tethereal man page for information on how to specify a
	read filter.