Ethereal-dev: Re: [Ethereal-dev] [possibly bug] RUDP and user specific decodes (Out of the off

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

From: "Greg Morris" <GMORRIS@xxxxxxxxxx>
Date: Wed, 05 May 2004 10:13:06 -0600
I'm sorry but I am not available May 6th - May 7th. If you need
ssistance please call 1-800-858-4000 and ask to have someone else help
you. I will be returning back to the office on May 10th.

I am currently located in the Capelle Netherlands office. Time
difference may make it difficult for me to call you directly if you are
located in the United States. Feel free to email me at any time.

>>> ethereal-dev 05/05/04 10:12 >>>

Hi all,

I have Ethereal 0.10.3 on linux, and I want to decode conversations from
UDP port 7007 to UDP port 7007 as RUDP + SM + MTP3.
RUDP is currently an ethereal plugin, which by defalut binds RUDP to UDP
port 7000.
On this default port (7000), everything goes fine, the traffic is
correctly interpretted as: IP/UDP/RUDP/SM/MTP3/....
If I try "Decode As" menu, and specify that on port UDP 7007 (both) to
be RUDP, a strange thing happens:
The packets are dissected as RUDP, but it does not pass the remaing data
to Cisco SM and after that to MTP3.
I don't know why is this behaviour.

For a quick hack I changed the default port from 7000 to 7007 and
recompiled ethereal. But this is just a quick hack not a fix.


_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev