Riverbed Cascade Pilot Personal Edition: Take Wireshark to the Next Level - Advanced Triggers and Alerts; Web and VoIP Analytics; Long-Term Trending and Forensics; Deep Packet Analysis with Wireshark

Wireshark-users: Re: [Wireshark-users] [Dissector bug, protocol DIAMETER: proto.c:1044: failed assertion"DISSECTOR_ASSERT_NOT_REACHED"]

Date Index Thread Index Other Months All Mailing Lists

Date Prev Date Next Thread Prev Thread Next

From: "Anders Broman" <anders.broman@xxxxxxxxxxxx>
Date: Thu, 11 Jun 2009 16:53:00 +0200

Hi,

AVP: Unknown(904) l=16 f=VM- vnd=11971 val=00000000

Vedor 11971 -> { 11971, "Peter-Service Ltd." }, we do not have any knowledge of AVP:s from this vendor,

The 3GPP vendor ID is { 10415, "3GPP" },

The first problem(not present in the enclosed trace?) may be due to the problem described in a comment in the file:

<!--

These AVP:s collide(share AVP code number) with other 3GPP AVP:s (3GPP Cx imscxdx.xml)

comment those out if you want to use these.

-->

Regards

Anders

From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Elvis Presley
Sent: den 11 juni 2009 13:38
To: wireshark-users@xxxxxxxxxxxxx
Subject: [Wireshark-users] [Dissector bug,protocol DIAMETER: proto.c:1044: failed assertion"DISSECTOR_ASSERT_NOT_REACHED"]

Hello. During dump analysis I found that Wireshark can’t parse DIAMETER packet properly:

[Dissector bug, protocol DIAMETER: proto.c:1044: failed assertion "DISSECTOR_ASSERT_NOT_REACHED"]

(source line can be different different, because I tried versions 1.08, 1.13 and 1.20 pre1 and don’t remember the exact version-line number)

I made some analysis and found that it can be fixed by editing TGPPGmb.xml file in "diameter" folder by removing the following entry:

</avp>

It fixed the error, but DIAMETER AVP fields still can’t be parsed properly, i.e. AVP code 904 still can’t be displayed, but it does exist in TGPPGmb.xml.

Dump attached.

This error (Dissector bug) is not seen in Wireshark 1.02, but AVP code problem exists in 1.02 too

Best regards,

Alexander

Follow-Ups:
- Re: [Wireshark-users] [Dissector bug, protocol DIAMETER: proto.c:1044: failed assertion"DISSECTOR_ASSERT_NOT_REACHED"]
  - From: Joerg Mayer

References:
- [Wireshark-users] [Dissector bug, protocol DIAMETER: proto.c:1044: failed assertion "DISSECTOR_ASSERT_NOT_REACHED"]
  - From: Elvis Presley

Prev by Date: Re: [Wireshark-users] Wireshark-users: Merging a bunch of PCAP files
Next by Date: Re: [Wireshark-users] TLSv1 vs SSL3.0 decoding issue
Previous by thread: [Wireshark-users] [Dissector bug, protocol DIAMETER: proto.c:1044: failed assertion "DISSECTOR_ASSERT_NOT_REACHED"]
Next by thread: Re: [Wireshark-users] [Dissector bug, protocol DIAMETER: proto.c:1044: failed assertion"DISSECTOR_ASSERT_NOT_REACHED"]
Index(es):
- Date
- Thread