This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Wireshark 2.0.1 diameter dictionary.xml

0

I have Wireshark 2.0.1 64bit installed on a Windows 10 system (I know Windows 10?); when I attempt to update the diameter dictionary.xml file I get a list of errors. Any assistance would be appreciated.

Examples: (And many, many more)

Diameter Dictionary: AVP 'CHAP-Algorithm' has a list of values but isn't of a 32-bit or shorter integral type (FT_BYTES)

Diameter Dictionary: AVP 'Accounting-Auth-Method' has a list of values but isn't of a 32-bit or shorter integral type (FT_BYTES)

Diameter Dictionary: AVP 'Origin-AAA-Protocol' has a list of values but isn't of a 32-bit or shorter integral type (FT_BYTES)

Diameter Dictionary: AVP 'MIP-Feature-Vector' has a list of values but isn't of a 32-bit or shorter integral type (FT_BYTES)

Diameter Dictionary: AVP 'MIP-Algorithm-Type' has a list of values but isn't of a 32-bit or shorter integral type (FT_BYTES)

Diameter Dictionary: AVP 'MIP-Replay-Mode' has a list of values but isn't of a 32-bit or shorter integral type (FT_BYTES)

asked 11 Jan '16, 09:03

kh00le's gravatar image

kh00le
6●1●1●2
accept rate: 0%

What is the "update" you're attempting to apply to dictionary.xml?

(11 Jan '16, 09:10) grahamb ♦

Thank you for taking the time to look at this question.

I am attempting to add additional AVP for Wireshark to decode. I was able to do this in the pervious versions. I did check the xml formatting and it checked fine.

(13 Jan '16, 11:11) kh00le

Can you give a specific example of what you're trying to add?

Note that the format of the XML has changed significantly in 2.0. In particular vendor IDs can no longer be inside applications (and applications must be in either base or a vendor). I don't think that's your problem but I just wanted to make sure you were aware...

(13 Jan '16, 11:56) JeffMorriss ♦

One Answer:

0

OK, so a quick check in the code suggests that the problem is the AVP you have added is listed as being of type OctetString (or grouped) but then it includes some 'enum' statements. If there are 'enum' statements, of course, the type should be Enumerated.

So, for example, I was able to get the same error by modifying this AVP to be of type OctetString (instead of Enumerated):

<avp name="SL-Request-Type" code="2904" mandatory="must" vendor-bit="must" vendor-id="TGPP">
   <type type-name="OctetString"/>
   <enum name="INITIAL_REQUEST"            code="0"/>
   <enum name="INTERMEDIATE_REQUEST"       code="1"/>
</avp>

(Hopefully this works; the Preview doesn't show the AVP definition...)

answered 22 Jan '16, 18:50

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k●5●72
accept rate: 27%