Wireshark mailing list archives
Re: Checksum filterable fields
From: Christopher Maynard <Christopher.Maynard () gtech com>
Date: Thu, 27 Jun 2013 19:47:08 +0000 (UTC)
Christopher Maynard <Christopher.Maynard@...> writes:
Removing the bad_checksums does have at least 1 drawback though, and that's that several of them are used in default coloring rules, so if they're removed, users will likely end up with several warnings of the form: Warn Could not compile color filter "Checksum Errors" from saved filters: "<protocol>.checksum_bad" is neither a field nor a protocol name.
I suppose in order to avoid that, the <protocol>.checksum_good's could be removed instead of the <protocol>.checksum_bad's, since none of those are used in any of the default coloring rules. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Checksum filterable fields mmann78 (Jun 27)
- Re: Checksum filterable fields Christopher Maynard (Jun 27)
- <Possible follow-ups>
- Re: Checksum filterable fields mmann78 (Jun 27)
- Re: Checksum filterable fields Christopher Maynard (Jun 27)
- Re: Checksum filterable fields Christopher Maynard (Jun 27)
- Re: Checksum filterable fields Christopher Maynard (Jun 27)
- Re: Checksum filterable fields mmann78 (Jun 27)