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-commits: [Wireshark-commits] rev 25415: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-ifcp.c

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


From: jake@xxxxxxxxxxxxx
Date: Tue, 03 Jun 2008 20:41:14 GMT

http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=25415

User: jake
Date: 2008/06/03 01:41 PM

Log:
 From Frank Schorr:
 RFC 4172 section 5.3.1 shows a chart of the iFCP encapsulated Header Format.
 It says that bytes 4-7 MUST be zeros.  In reality most vendors are putting some
 information in these 4 bytes, particularly Nishon. This caused almost all iFCP
 packets to not be decoded for this vendor.

Directory: /trunk/epan/dissectors/
  Changes    Path             Action
  +7 -4      packet-ifcp.c    Modified


  • Prev by Date: [Wireshark-commits] rev 25422: /trunk/tools/lemon/ /trunk/tools/lemon/: lempar.c
  • Next by Date: [Wireshark-commits] rev 25424: /trunk/epan/ /trunk/epan/: Makefile.am
  • Previous by thread: [Wireshark-commits] rev 25422: /trunk/tools/lemon/ /trunk/tools/lemon/: lempar.c
  • Next by thread: [Wireshark-commits] rev 25424: /trunk/epan/ /trunk/epan/: Makefile.am
  • Index(es):
    • Date
    • Thread

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