| Bug ID |
8035
|
| Summary |
Wrong packet bytes are selected for ISUP CUG binary code
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
x86
|
| OS |
All
|
| Status |
CONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 9605 [details]
Test trace
Build Information:
wireshark 1.9.0 (SVN Rev 46333 from /trunk)
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.13, with Cairo 1.12.7, with Pango 1.32.1, with
GLib 2.34.0, with libpcap, with libz 1.2.5, with POSIX capabilities (Linux),
with libnl 1, without SMI, without c-ares, without ADNS, with Lua 5.1, without
Python, without GnuTLS, with Gcrypt 1.4.6, without Kerberos, without GeoIP,
with
PortAudio V19-devel (built Dec 9 2011 17:10:11), without AirPcap.
Running on Linux 3.6.3-ojab, with locale en_RU.UTF-8, with libpcap version
1.3.0, with libz 1.2.5, Gcrypt 1.4.6.
Built using gcc 4.7.2.
--
Please check the attached trace that contains IAM with CUG (It should be
decoded as RUDP).
If you'll select "ISDN User Part" -> "Closed user group interlock code" ->
"Binary code: 0x384" in the Packet Details pane, only second byte ("84") will
be highlighted in the Packet Bytes pane.
You are receiving this mail because:
- You are watching all bug changes.