[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ethereal-dev
Subject:    Re: [Ethereal-dev] Re: [Ethereal-cvs] rev
From:       "Martin Mathieson" <martin.mathieson () ntlworld ! com>
Date:       2005-05-27 19:16:44
Message-ID: 004e01c562f0$a00e6c20$bb970750 () home
[Download RAW message or body]

> > - register a configurable UDP port (off by default, but needed where
setup traffic isn't captured)
> >
> >
> Just wondering: I really don't know RDT, but wouldn't this be the
> classical case for "Decode As"?
>
> Or are there other reasons as well to have a pref here?
>
> Regards, ULFL
>

There is no fixed port for RDT (and none registered with IANA), but I
understand that the helix client always begins at 6970 for both RDT and RTP
(by default RDT is used).  In my tests, the RealPlayer client has always
chosen this port.  Other clients may choose a different (fixed or not) port.
Therefore I made it optionally register a port (off by default) on a given
port number (6970 by default).

If the RTSP traffic that sets up the stream is captured, then the
conversation/session will be decoded as RDT.  Sessions can last for a long
time, so the probability of capturing RDT packets but not the RTSP setup
frame is quite high.  I looked at making it a heuristic dissector (as RTP &
RTCP are), but the protocol doesn't really lend itself to this (no
consistent signature or distinctive packet size).

"Decode As..." is still available if the setup traffic is missed and the
preference isn't switched onto the correct port...

Regards,
Martin


_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@ethereal.com
http://www.ethereal.com/mailman/listinfo/ethereal-dev
[prev in list] [next in list] [prev in thread] [next in thread]