Re: [Wireshark-dev] Calculating CRC5 of 11-bit data

2019-07-20 Thread Tomasz Moń
On Sat, Jul 20, 2019 at 8:42 PM John Sullivan wrote: > One of the properties of LFSRs is that a 1 bit in the input toggles a > completely predictable set of register bits *at any point in the > future*. This isn't often useful for most CRC caculations on variable > sized input, as the cost of

Re: [Wireshark-dev] Calculating CRC5 of 11-bit data

2019-07-20 Thread John Sullivan
On Saturday, July 20, 2019, 9:10:36 AM, Tomasz Mon wrote: > On Sat, Jul 20, 2019 at 5:37 AM Tomasz Mon wrote: >> The advantage of 1) over 2) is the ability to be able, if the CRC is >> incorrect, to tell what the correct CRC should have been. >> Approach 2) allows only to veify if the CRC is

[Wireshark-dev] Request to become an editor, name VadimZakharine

2019-07-20 Thread Vadim Zakharine via Wireshark-dev
The immediate purpose is to share my github contribution (Lua post-dissector) at https://wiki.wireshark.org/Contrib May have more later ___ Sent via:Wireshark-dev mailing list Archives:

Re: [Wireshark-dev] Calculating CRC5 of 11-bit data

2019-07-20 Thread Tomasz Moń
On Sat, Jul 20, 2019 at 5:37 AM Tomasz Moń wrote: > The advantage of 1) over 2) is the ability to be able, if the CRC is > incorrect, to tell what the correct CRC should have been. > Approach 2) allows only to veify if the CRC is correct - but at the > advantage of being able to take full bytes