Ethereal-dev: Re: [Ethereal-dev] more options for decode as...

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: Guy Harris <gharris@xxxxxxxxx>
Date: Wed, 28 May 2003 11:11:05 -0700
On Wed, May 28, 2003 at 01:02:25PM +0200, Lars Ruoff wrote:
> I don't know if i get your point.
> I saw that a conversation_set_dissector-function allready exists.
> But there should be a way to call it from the GUI.

That *is* my point.

> So you need a way of defining conversations from within the GUI

The way you define a conversation from within the GUI is to select a
packet; the conversation is the one to which that packet belongs.

> and assigning dissectors to it.

That's what we'd add to the GUI.

> So, basically this resumes to "Decode [Network1]:[Transport1] <->
> [Network2]:[Transport2] as XXX", doesn't it?

Well, not exactly; the conversation is specified *internally to
Ethereal* using network addresses and port numbers, but the user
wouldn't see that - the option menu in the "Transport" tab of the
"Decode As" dialog box would just have, as items, something such as

	source (XXX) port
	destination (YYY) port
	both ports
	conversation
	conversation (this direction)
	conversation (other direction)