Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 21303: /trunk/wiretap/ /trunk/wiretap/: k12.c

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Mon, 2 Apr 2007 15:44:23 -0700


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?

(I.e., might that be a 24-bit ID plus a separate 8-bit field?)

  • Follow-Ups:
    • Re: [Wireshark-dev] [Wireshark-commits] rev 21303: /trunk/wiretap/ /trunk/wiretap/: k12.c
      • From: Luis Ontanon
  • Prev by Date: Re: [Wireshark-dev] dissector for OpenVPN
  • Next by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 21303: /trunk/wiretap/ /trunk/wiretap/: k12.c
  • Previous by thread: Re: [Wireshark-dev] dissector for OpenVPN
  • Next by thread: Re: [Wireshark-dev] [Wireshark-commits] rev 21303: /trunk/wiretap/ /trunk/wiretap/: k12.c
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation