On 4/3/07, Guy Harris <guy@xxxxxxxxxxxx> wrote:
On Apr 2, 2007, at 3:17 PM, lego@xxxxxxxxxxxxx wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=21303
>
> User: lego
> Date: 2007/04/02 10:17 PM
>
> Log:
> There are odd packet records in k15 generated files where the
> interface record does not match any given one.
>
> I noticed that these records have the first byte changed so When a
> lookup fails mask the byte and lookup again.
Are there any cases where the upper byte of the ID in question is
significant?
It is significant for most files I have. That's why I lookup twice
instead of just using the masked id as key.
(I.e., might that be a 24-bit ID plus a separate 8-bit field?)
I thought that myself i thus I coded it... then the regression test
showed me that it wasn't that.
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
