Wireshark-bugs: [Wireshark-bugs] [Bug 11350] New: STUN dissector, missing error codes
Date: Thu, 09 Jul 2015 23:20:32 +0000
Bug ID 11350
Summary STUN dissector, missing error codes
Product Wireshark
Version unspecified
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter wireshark@jonesmz.com

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob;f=epan/dissectors/packet-stun.c;h=a8dc531324f861dab573c8d21b6f98acab2f41be;hb=HEAD

Is missing several error code names


This is a more complete list, as far as I can tell. Gathered from here:
http://www.iana.org/assignments/stun-parameters/stun-parameters.xhtml#stun-parameters-6

300  Try Alternate                    from RFC 5389
400  Bad Request                      from RFC 5389
401  Unauthorized                     from RFC 5389
403  Forbidden                        from RFC 5766
420  Unknown Attribute                from RFC 5389
437  Allocation Mismatch              from RFC 5766
438  Stale Nonce                      from RFC 5389
441  Address Family Not Supported     from RFC 6156
441  Wrong Credentials                from RFC 5766
442  Unsupported Transport Protocol   from RFC 5766
443  Peer Address Family Mismatch     from RFC 6156
446  Connection Already Exists        from RFC 6062
446  Connection Timeout Or Failure    from RFC 6062
486  Allocation Quota Reached         from RFC 5766
487  Role Conflict                    from RFC 5245
500  Server Error                     from RFC 5389
508  Insufficient Capacity            from RFC 5766


The list from the dissector
 378     {274, "Disable Candidate"},               /* MS-ICE2BWN */
 379     {275, "Disable Candidate Pair"},               /* MS-ICE2BWN */
 380     {300, "Try Alternate"},                   /* rfc3489bis-15 */
 381     {400, "Bad Request"},                     /* rfc3489bis-15 */
 382     {401, "Unauthorized"},                    /* rfc3489bis-15 */
 383     {420, "Unknown Attribute"},               /* rfc3489bis-15 */
 384     {437, "Allocation Mismatch"},             /* turn-07 */
 385     {438, "Stale Nonce"},                     /* rfc3489bis-15 */
 386     {439, "Wrong Credentials"},               /* turn-07 - collision
38=>39 */
 387     {440, "Address Family not Supported"},    /* turn-ipv6-04 */
 388     {442, "Unsupported Transport Protocol"},  /* turn-07 */
 389     {481, "Connection does not exist"},       /* nat-behavior-discovery-03
*/
 390     {486, "Allocation Quota Reached"},        /* turn-07 */
 391     {500, "Server Error"},                    /* rfc3489bis-15 */
 392     {503, "Service Unavailable"},             /* nat-behavior-discovery-03
*/
 393     {507, "Insufficient Bandwidth Capacity"}, /* turn-07 */
 394     {508, "Insufficient Port Capacity"},      /* turn-07 */
 395     {600, "Global Failure"},
 396     {0x00, NULL}



The specific error code that I was looking for is the RoleConflict error code,
from RFC 5245, Interactive Connectivity Establishment, used in WebRTC.


You are receiving this mail because:
  • You are watching all bug changes.