I just loaded these 2 captures into my svn-current build, and it
decodes fine (all are decoded either as STUN or ICMP unreachable
replies containing STUN requests.
I do have heuristics turned on for both RTP and RTCP ("try to decode
outside of a conversation"), but neither of these are claiming any of
the frames in the captures you posted.
Regards,
Martin
On 4/20/07, Pedro Gonçalves <[EMAIL PROTECTED]> wrote:
> Hi
>
> I'm having some trouble while decoding STUN Binding Request and Responses.
> Sometimes they get decoded the right way, sometimes STUN packets are
> decoded as DNP 3.0, RTP or RTCP (?!).
>
> I'm sending two captures I made so you can check for yourself:
> for example, in problems_wireshark_1.pcap, odd packets are STUN Binding
> Request and even packets are STUN Binding Responses.
>
> Why are the first two packets decoded as DNP 3.0 and the rest of them
> are decoded ok?
>
> Best Regards
> Pedro
>
>
_______________________________________________
Wireshark-users mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-users