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. So you need a way of defining conversations from within the GUI and assigning dissectors to it. (or is there already???) So, basically this resumes to "Decode [Network1]:[Transport1] <-> [Network2]:[Transport2] as XXX", doesn't it? (where Network1/2 + Transport 1/2 are filled by default with the values of the selected packet) Then there should be a checkbox for uni-/bi-directional also. (see post of Tomas Kukosa)
----- Original Message ----- From: "Guy Harris" <[EMAIL PROTECTED]> To: "Lars Ruoff" <[EMAIL PROTECTED]> Cc: "Ethereal-Dev" <[EMAIL PROTECTED]> Sent: Wednesday, May 28, 2003 7:54 AM Subject: Re: [Ethereal-dev] more options for decode as... > On Tue, May 27, 2003 at 03:45:06PM +0200, Lars Ruoff wrote: > > Wouldn't it be nicer to have the possibility to assign user decodes to > > conversations, i.e. > > "Decode all UDP traffic from IP:port to IP:port as XXX" ? > > Yes, but what you *really* would want with that would be something like > "Decode this conversation/circuit as XXX", as the IP addresses and port > numbers are just details - you presumably care just about the > conversation. > > That could also be used with the circuit mechanism to specify that, for > example, a particular X.25 VC be dissected as a particular type of > traffic.
