Differences between revisions 3 and 4
Revision 3 as of 2006-06-05 03:19:24
Size: 1427
Editor: localhost
Comment:
Revision 4 as of 2008-04-12 17:50:30
Size: 1431
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
The Real Data Transport protocol is used by realPlayer and other players to transport media samples. RDT frames can either be interleaved within the controlling ["RTSP"] connection or can be setup over a separate ["UDP"] stream. The Real Data Transport protocol is used by realPlayer and other players to transport media samples. RDT frames can either be interleaved within the controlling [[RTSP]] connection or can be setup over a separate [[UDP]] stream.
Line 9: Line 9:
 * ["RTSP"] is used by the client (player) and media server to set up RDT sessions.  * [[RTSP]] is used by the client (player) and media server to set up RDT sessions.
Line 25: Line 25:
A complete list of RDT display filter fields can be found in the [http://www.wireshark.org/docs/dfref/r/rdt.html display filter reference] A complete list of RDT display filter fields can be found in the [[http://www.wireshark.org/docs/dfref/r/rdt.html|display filter reference]]
Line 32: Line 32:
You cannot directly filter RDT protocols while capturing. However, if you know the ["RTSP"] port used ({{{tcp port 554}}} by default), you can filter on that (this will work at least for the case where RDT frames are interleaved within the ["RTSP"] connection) You cannot directly filter RDT protocols while capturing. However, if you know the [[RTSP]] port used ({{{tcp port 554}}} by default), you can filter on that (this will work at least for the case where RDT frames are interleaved within the [[RTSP]] connection)
Line 37: Line 37:
 * There seems not to be full specification of RDT available, but the source for a player and server that implement the protocol are at [http://www.helixcommunity.org/ Helix Community]  * There seems not to be full specification of RDT available, but the source for a player and server that implement the protocol are at [[http://www.helixcommunity.org/|Helix Community]]

RealDataTransport (RDT)

The Real Data Transport protocol is used by realPlayer and other players to transport media samples. RDT frames can either be interleaved within the controlling RTSP connection or can be setup over a separate UDP stream.

Protocol dependencies

  • RTSP is used by the client (player) and media server to set up RDT sessions.

Wireshark

The RDT dissector is very nearly complete.

Preference Settings

  • Show stream setup information (default yes)

  • Register default UDP client port (default no)

  • Default UDP client port (default 6970, the port used by realPlayer)

Display Filter

A complete list of RDT display filter fields can be found in the display filter reference

  • Show only the RDT based traffic:  rdt 

Capture Filter

You cannot directly filter RDT protocols while capturing. However, if you know the RTSP port used (tcp port 554 by default), you can filter on that (this will work at least for the case where RDT frames are interleaved within the RTSP connection)

  • There seems not to be full specification of RDT available, but the source for a player and server that implement the protocol are at Helix Community

Discussion

RDT (last edited 2008-04-12 17:50:30 by localhost)