| Bug ID |
12947
|
| Summary |
LAPD ISDN trace inconsistencies
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86
|
| OS |
Windows 10
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Capture file support (libwiretap)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14946 [details]
LAPD ISDN Wireshark trace
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
The trace LAPD ISDN shows different hex values within the Control field 0xEA01
and the hex dump 01ea (see attachment.
In order to not confuse the wireshark user or students who has to use wireshark
for analysis of protocls, please use in teh Controlfield the same order of
bytes as in the hexdump.
The hex values for the SAPI and TEI are also not twisted.
Let me have your comments. I have to explain this to my student in Germany.
Regards
Wolfgang Schulte
[email protected]
You are receiving this mail because:
- You are watching all bug changes.
