From: Michael Richardson <mcr@sandelman.ca>
To: "Andrew Jeffery" <andrew@aj.id.au>
Cc: "Sui Chen" <suichen6@gmail.com>, openbmc@lists.ozlabs.org
Subject: Re: An IPMI Request Visualization Tool
Date: Sun, 07 Jun 2020 23:07:17 -0400 [thread overview]
Message-ID: <19628.1591585637@localhost> (raw)
In-Reply-To: <36873484-3078-4ec5-981e-88e59e619926@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
Andrew Jeffery <andrew@aj.id.au> wrote:
>> Interestingly, I was not that clearly aware of dbus-pcap :-) I ought
>> to know more, as the lead libpcap maintainer. Is this visualization
>> tool part of openbmc, or is it a generic dbus visualization tool?
> It's not really a visualisation tool so much as a script that will
> interpret the D-Bus-specifics of a D-Bus pcap. It's a commandline
> script that provides filtering based on D-Bus match specifications. You
> can capture all traffic on the system bus in any systemd-based system
> with `busctl capture > /tmp/my.pcap` and then run `dbus-pcap my.pcap`
> to dump the packet contents.
Is this something that you'd like to be able to invoke remotely in order to
get diagnostics/debugging info?
>> We recently brought rpcapd into the mix; it can be invoked via ssh. I
>> wonder if that might help you as a debug tool?
> I'm not sure, I'm not familiar with rpcapd. I'll have a google.
https://www.ca.tcpdump.org/manpages/rpcapd.8.html
>> > If you ask how this user interface might differ from the already >
>> existing dbus visualizers such as bustle, my answer would be: it will
>> > present information in a way that's more relevant to the BMC,
>> putting a > bit more focus on BMC-specific DBus messages, such as
>> HWMon and RedFish > DBus messages, to present information in a high
>> signal-noise ratio way.
>>
>> Would this need to run on the BMC itself?
> Hopefully not given `busctl capture` ?
Understood.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-06-08 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 22:38 An IPMI Request Visualization Tool Sui Chen
2020-05-14 13:57 ` Patrick Williams
2020-05-19 1:36 ` Andrew Jeffery
2020-05-21 16:44 ` Sui Chen
2020-05-21 22:39 ` Michael Richardson
2020-05-26 18:22 ` Brandon Wyman
2020-06-03 12:06 ` Andrew Jeffery
2020-06-08 3:07 ` Michael Richardson [this message]
2020-06-11 0:57 ` Andrew Jeffery
2020-05-26 18:56 ` Vijay Khemka
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=19628.1591585637@localhost \
--to=mcr@sandelman.ca \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=suichen6@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.