| Bug ID |
8692
|
| Summary |
Wireshark combines two diameter messages (RAA & CCR-U) in one
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.6.11
|
| Hardware |
Other
|
| OS |
Fedora
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 10783 [details]
trace file that displays the problem
Build Information:
wireshark 1.6.11 (SVN Rev Unknown from unknown)
Copyright 1998-2012 Gerald Combs <[email protected]> and contributors.
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 GTK+ 2.24.8, with GLib 2.30.3, with libpcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, without
SMI, without c-ares, without ADNS, without Lua, without Python, without GnuTLS,
without Gcrypt, without Kerberos, without GeoIP, without PortAudio, without
AirPcap.
Running on Linux 3.1.0-7.fc16.x86_64, with libpcap version 1.1.1, with libz
1.2.5.
Built using gcc 4.6.3 20120306 (Red Hat 4.6.3-2).
--
Hello,
We have noticed that in some cases, when two different diameter messages from
the same source to the same destination are being sent in a very short time one
another, they are not being displayed correctly in wireshark.
What actually happens is that wireshark puts the two messages in one. Hence the
difficulty for our automation system to analyze the trace.
The two messages that are being combined are RAA and CCR-U, see frame 566 of
the attachment.
Thanks,
Georgia
You are receiving this mail because:
- You are watching all bug changes.