| Bug ID |
12317
|
| Summary |
Wireshark 2.0.2 does not capture diameter msgs
|
| Product |
Wireshark
|
| Version |
2.0.2
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14465 [details]
Capture file that shows not recognised Diameter msgs
Build Information:
Version 2.0.2 (v2.0.2-0-ga16e22e from master-2.0)
Copyright 1998-2016 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 (32-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.38.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 7 Service Pack 1, build 7601, 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-3340M CPU @ 2.70GHz (with SSE4.2), with 3975MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
Hello experts,
Pls see in attached capture file the issue.
At first no msg was recognized as Diameter, when I used "decode as" the result
was that only frames 4 and 5 were decoded as Diameter messages and not the
rest.
For example pls see frames 7,8,10 etc. that have the same source/destination
ports and ip addresses.
I would really appreciate your help on this, thanks!
Kind Regards,
Elissw
You are receiving this mail because:
- You are watching all bug changes.