From: "Daniel P. Berrange" <berrange@redhat.com>
To: Richard Sharpe <realrichardsharpe@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Did anything ever come of the Wireshark dissector generator that was being worked on
Date: Tue, 3 Jan 2017 09:46:53 +0000 [thread overview]
Message-ID: <20170103094653.GC5715@redhat.com> (raw)
In-Reply-To: <CACyXjPxZePbjS-zm1CeCLpzEuYkXSmVZ6w8vJpw8zO2iRyoZoA@mail.gmail.com>
On Thu, Dec 29, 2016 at 10:51:55AM -0800, Richard Sharpe wrote:
> Hi folks,
>
> I saw on this page
> http://wiki.qemu.org/Features/LibvirtWiresharkDissector that someone
> was planning on writing a dissector generator for XDR.
It is complete and included in libvirt git for a couple of years now.
> I wish I had known about it when I started the following effort, which
> is now at a Version 1 level:
>
> https://gitlab.com/realrichardsharpe/wireshark_rpcgen
>
> As far as I am aware it handles all of XDR and is able to handle
> protocols that are specified across multiple XDR files (as that is
> what I needed.)
>
> However, I would be interested in following up with the athor of the
> libvirt version.
The original author was a google summer of code student and no longer
active in the libvirt community. It is now maintained collaboratatively
by the libvirt developers.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
prev parent reply other threads:[~2017-01-03 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 18:51 [Qemu-devel] Did anything ever come of the Wireshark dissector generator that was being worked on Richard Sharpe
2017-01-03 9:46 ` Daniel P. Berrange [this message]
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=20170103094653.GC5715@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=realrichardsharpe@gmail.com \
/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.