Comment # 10
on bug 12058
from Jaap Keuter
(In reply to Pierre Fortin from comment #6)
> Turned on checking, and now I see:
> Header checksum: 0x1810 [correct]
> [Calculated Checksum: 0x1810]
> [Good: True]
> [Bad: False]
>
> So "correct", "Good: True" & "Bad: False" isn't overkill...? :)
No, because people want to filter:
To be sure it's good (when checking enabled): proto.checksum_good == true
To find those which are bad (when checking enabled): proto.checksum_bad == true
To find those which are good, or not checked: !(proto.checksum_bad == true)
It opens up a way to craft intelligent filters based on the tuning of
individual protocol dissectors.
You are receiving this mail because:
- You are watching all bug changes.