| Bug ID |
11907
|
| Summary |
The is a problem with Diameter decoding - AVP Code: 100 Unknown
|
| Product |
Wireshark
|
| Version |
2.0.0
|
| Hardware |
x86-64
|
| OS |
Windows 10
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14161 [details]
Example packet
Build Information:
Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 10240, with locale C, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz (with SSE4.2), with 8084MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 31101
--
I have a problem with decoding Diameter packets.
I have defined additional AVPs but referring them in dictionary.xml, but it
doesn't work in 2.0.0.
Same definitions added to 1.12.8 work and I can fully decode Diameter packets.
Code 100 for vendor 28458 is defined in dia02.xml and dia02bas.xml.
Now both definitions are referred in dictionary.xml, but also when included
separately, same problem can be seen.
I'm attaching exemplary Diameter packet and files defining additional AVPs with
dictionary.xml.
Regards,
Piotr
You are receiving this mail because:
- You are watching all bug changes.