Comment # 3
on bug 11866
from Michael Jones
The attached pcap file includes a sample ICE session.
The first 6 STUN (TURN, really) protocol packets set up a TURN relay to send
and receive data through.
>From there, all of the packets are embedded inside of Send or Data Indications.
Packets number 157 158 and 161 should contain an embedded STUN BindingRequest
packet
Packet 162 should contain an embedded STUN BindingResponse packet.
The majority of the packets are going to contain RTP packets wrapped in DTLS.
My major interest is in being able to see that the DATA Attribute of the STUN
packet contains a BindingRequest / BindingResponse, and the relevant data
inside that, but TURN Data and Send indications can be used for any kind of
packet, so if Wireshark isn't able to auto-detect, being able to manually
specify what kind of data is contained would be greatly useful.
Another packet type to keep in mind is the ChannelData packets, which are a 2
byte "Channel Number", 2 bytes to indicate length, and then the rest of the
packet is the data being embedded.
ChannelData packets will normally be preceded by a ChannelBind Request message:
https://tools.ietf.org/html/rfc5766#section-11.1
You are receiving this mail because:
- You are watching all bug changes.