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] New dissector - FMP

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


From: "ronnie sahlberg" <ronniesahlberg@xxxxxxxxx>
Date: Thu, 1 Feb 2007 21:00:09 +0000

checked in with some changes:

1, C++ style comments removed
2, enum constants changed to have a unique FMP_ prefix
3, several value_strings that were not terminated properly and would
cause crashes


There is probably quite a bit of work to enhance the dissectors to
make them nicer:
1, all switch/case+proto_tree_add_text() would become much better if
they were replaced by a value_string
2, using FT_BOOLEANs and not explicite masking and proto_tree_add_text()


A wiki page and some small example captures for the wiki would be nice.




On 1/31/07, Ian Schorr <ian.schorr@xxxxxxxxx> wrote:
Hello,

Please consider for checkin the following new dissectors, for the FMP
protocol.

FMP (File Mapping Protocol) is the network protocol basis for EMC's HighRoad
(MPFS) technology.  Highroad is used to allow multiple clients to share
access to NAS-shared files while allowing clients to directly access data
volumes (via, for example, Fibre Channel or iSCSI).  EMC currently uses this
technology in our Celerra NAS servers, and we're currently in the process of
open sourcing portions of the technology.

FMP actually consists of two ONC/RPC-based protocols - the core FMP
protocol, and FMP/Notify.  The latter is used as an asynchronous callback to
inform clients of status changes, such as lock revocation.

We'd like to offer these dissectors to Wireshark users for help in debugging
or otherwise troubleshooting MPFS-related problems.  There are still a few
minor changes that need to be made (i.e. a handful of fields that aren't
decoded) but the dissector is overall fairly complete and very usable.

Let me know if there are questions or feedback, or otherwise if other info
is needed (like sample captures, which I don't want to send out to the
mailing list).

Thanks,
Ian Schorr
EMC Corporation


  • Prev by Date: Re: [Wireshark-dev] [Patch] SCSI persistent reserve in - service action
  • Next by Date: [Wireshark-dev] blank makefile generated for custom dissector plugin
  • Previous by thread: [Wireshark-dev] Wireshark MacOS X binary update
  • Next by thread: [Wireshark-dev] blank makefile generated for custom dissector plugin
  • Index(es):
    • Date
    • Thread

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