Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

The TURN Channel dissector has a table for heuristic dissectors for protocols running on top of TURN, but nothing is registered in that table - which is especially weird, as the change that introduced that dissector, complete with that table, didn't change anything to register in it, even though the RTP and RTCP dissectors were modified in that change.

This means that there is no mechanism in the UI to say "please dissect the TURN payload as X", for any value of X.

I see no reason not to have the RTP and RTCP dissectors register there, so I'll make that change, and backport it, so the next release should support that.

This requires that the RTP and RTCP heuristic dissectors be enabled; the heuristics are weak, so the heuristic dissectors may be disabled by default.

If that doesn't suffice, we may want to add "Decode As..." support to the TURN Channel dissector (the "Decode As..." support you were using affects the UDP dissector, not the TURN Channel dissector, so it forces the UDP payload to be dissected as RTP).

The TURN Channel dissector has a table for heuristic dissectors for protocols running on top of TURN, but nothing is registered in that table - which is especially weird, as the change that introduced that dissector, complete with that table, didn't change anything to register in it, even though the RTP and RTCP dissectors were modified in that change.

This means that there is no mechanism in the UI to say "please dissect the TURN Channel payload as X", for any value of X.

I see no reason not to have X, if the TURN Channel protocol is being dissected by the TURN Channel dissector.

Confusingly, there is, however, a separate dissector for the TURN Channel protocol, inside the STUN dissector. That one appears to be the one dissecting the protocol in your capture.

For that protocol, the RTP and RTCP dissectors register there, so I'll make that change, and backport it, so the next release should support that.

This requires that are registered as heuristic dissectors, but the RTP and RTCP heuristic dissectors be enabled; the heuristics are weak, so the heuristic dissectors may be dissector is disabled by default.

If that doesn't suffice, we may want to add "Decode As..." support to the TURN Channel dissector (the "Decode As..." support default; you were using affects the UDP dissector, not the TURN Channel dissector, so have to enable it forces the UDP payload to be dissected as RTP).

manually, by going to Analyze -> Enabled Protocols and enabling the "rtp_stun" dissector.

I'll look at reducing the number of TURN Channel dissectors to 1, to make this less confusing.