Wireshark-bugs: [Wireshark-bugs] [Bug 10280] New: FR decodes header correctly, but processes oct
| Bug ID |
10280
|
| Summary |
FR decodes header correctly, but processes octets after EA bit is set to '1'
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.7
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
ton-schoenmakers@nc.rr.com
|
Created attachment 12894 [details]
capture of FR frame decoded beyond EA bit == 1
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
FR Header:
Address Field. Each address field may occupy either octet 2 to 3, octet 2 to 4,
or octet 2 to 5, depending on the range of the address in use. A two-octet
address field comprises the EA=ADDRESS FIELD EXTENSION BITS and the
C/R=COMMAND/RESPONSE BIT.
Wireshark assumes a 4 octet header, and does not interpret the EA Bit
correctly:
Note the second octet has the EA bit set, therefore the following octets are
payload. Wireshark still pulls the next 2 octets as part of the FR header:
You are receiving this mail because:
- You are watching all bug changes.
