| Bug ID |
8823
|
| Summary |
ip.opt.type triggers for TCP NOP option
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.0
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 11023 [details]
screen capture of the bug
Build Information:
--
When using ip.opt.type display filter, tcp packets including NOP options are
displayed even if no ip options are present.
It appears that the TCP dissector recognizes the NOP option type as ip.opt.type
(instead of tcp.option_kind, for example).
Same behaviour is also observed for sub-options (ip.opt.type.copy,
ip.opt.type.class, ip.opt.type.number).
Screen capture is from 1.8.2 on OSX, validated same behaviour on 1.10.0 on
Win32.
You are receiving this mail because:
- You are watching all bug changes.