| Bug ID |
8994
|
| Summary |
Field value is wrong
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
x86-64
|
| OS |
Ubuntu
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 11301 [details]
Example recording
Build Information:
wireshark 1.11.0 (SVN Rev 51022 from /trunk)
Copyright 1998-2013 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.17, with Cairo 1.12.14, with Pango 1.32.5,
with
GLib 2.36.0, with libpcap, with libz 1.2.7, without POSIX capabilities, without
libnl, without SMI, without c-ares, without ADNS, without Lua, without Python,
without GnuTLS, with Gcrypt 1.5.0, with MIT Kerberos, without GeoIP, without
PortAudio, with AirPcap.
Running on Linux 3.8.0-27-generic, with locale sl_SI.UTF-8, with libpcap
version
1.3.0, with libz 1.2.7, Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Built using gcc 4.7.3.
--
There seems to be wrong value displayed when the protocol is dissected. I am
not able to find an error in the ASTERIX dissector. The hex dump of the data
shows value 0x20 while the value dissected is 0x00.
I am attaching a sample file which shows the wrong value and the picture of
Wireshark showing wrong values. They are marked with red rectangle.
You are receiving this mail because:
- You are watching all bug changes.
