CEPH filesystem development
 help / color / mirror / Atom feed
From: Kevin Cox <kevincox@kevincox.ca>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Wireshark Dissector Preview
Date: Fri, 06 Jun 2014 15:51:58 -0400	[thread overview]
Message-ID: <53921BDE.5050006@kevincox.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]

Hello,

I am pleased to announce an alpha version of the Ceph Wireshark
Dissector.  As some you you may know I am working on this dissector as a
GSOC project this summer.  I have gotten some initial work completed and
wanted to share in case someone finds it useful.

So far the dissector can parse the protocol and display the messages,
however there are currently very few messages that are dissected
themselves.  This means that you can see who is sending what messages
but the contents of those messages will just be binary data.

I imagine that this basic level of dissection will still be useful to
some people, especially those working on the network protocol as they
can see exactly what is being sent, and sysadmins who can gain useful
information from just the message types.

You can find the current code on my github account[0] in the "ceph"
branch.  You can also download a tarball[1] if you prefer.  The code
should build using CMake although you may need to add the
-DDISABLE_WERROR=1 flag.

[0] https://github.com/kevincox/wireshark/tree/ceph
[1] https://github.com/kevincox/wireshark/archive/ceph.tar.gz

Any feedback would be appreciated, especially things that are not being
dissected properly or that can be improved.

Also, I am looking for captures of ceph network traffic.  If you could
provide captures it would allow be to focus on the messages that are
being used the most and implement those first.  Please be careful
however, and ensure there is no sensitive information in your capture.
Captures can be uploaded here[2] or mailed to me directly.

[2] https://seafile.kevincox.ca/u/d/2dd934002d/

Cheers,
Kevin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

                 reply	other threads:[~2014-06-06 19:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53921BDE.5050006@kevincox.ca \
    --to=kevincox@kevincox.ca \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox