All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Jones <k.j.jonez@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Wireshark
Date: Thu, 27 Jun 2013 11:22:50 +0100	[thread overview]
Message-ID: <51CC127A.3090701@gmail.com> (raw)

Hi,

I have done some work on a version of the Wireshark plugin to 
re-structure it so it may be possible to push upstream at some point. At 
the moment it handles connection establishment, setting up some 
conversational state tracking and decoding a few of the message types. 
Supporting other message types is now fairly straight forward but will 
take some time to work through to double check the decoding logic is up 
to date and change to a new decoding style.

At this point I was thinking maybe would be better to check-in as an 
alternative to the existing plugin so there is a base to work 
incrementally towards the upstream goal. Sound like a good approach?

Regards
Kev


             reply	other threads:[~2013-06-27 10:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 10:22 Kevin Jones [this message]
2013-06-27 12:33 ` Wireshark Sage Weil
     [not found]   ` <51CC801F.30303@gmail.com>
     [not found]     ` <alpine.DEB.2.00.1306271245320.397@cobra.newdream.net>
2013-07-04 16:15       ` Wireshark Kevin Jones
  -- strict thread matches above, loose matches on Subject: below --
2014-11-12 22:04 wireshark akuster808
2014-10-27 22:08 wireshark J. Bruce Fields
2014-10-31 20:20 ` wireshark J. Bruce Fields
2012-09-28 13:07 Wireshark Michal.Labedzki
2012-09-28 13:39 ` Wireshark Johan Hedberg
2012-09-28 14:30   ` Wireshark Marcel Holtmann
2012-09-28 13:57 ` Wireshark Andrei Emeltchenko
2012-10-03  7:17   ` Wireshark Michal.Labedzki
2012-10-03  8:04     ` Wireshark Johan Hedberg
2012-10-08 14:19       ` Wireshark Michal.Labedzki
2012-10-08 14:26         ` Wireshark Marcel Holtmann

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=51CC127A.3090701@gmail.com \
    --to=k.j.jonez@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.