From: Jiri Benc <jbenc@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Zaboj Campula <zaboj.campula@post.cz>, netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: show network device dependency tree
Date: Mon, 27 Feb 2017 17:38:25 +0100 [thread overview]
Message-ID: <20170227173825.39e00c61@griffin> (raw)
In-Reply-To: <20170226144610.GB2071@nanopsycho.orion>
On Sun, 26 Feb 2017 15:46:10 +0100, Jiri Pirko wrote:
> You can also run it remotelly. Also I believe that you can catch the
> state into some dump file and process it later on. Not 100% sure though.
> Ccing Jiri Benc who is the original author of plotnetcfg.
It produces dot (graphviz) output or json and has no dependencies on
anything GUI related. Just run it on the remote machine and display the
output locally.
ssh root@remote plotnetcfg | dot -Tpdf | whatever_pdf_viewer
Note that some pdf viewers can't read stdin or require dash as the
parameter to use stdin.
I don't think it's possible to enhance iproute2 to display the network
interface dependencies in an useful way. It's just too complex. It's
not even a (undirected) tree.
Jiri
next prev parent reply other threads:[~2017-02-27 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 16:59 [PATCH] iproute2: show network device dependency tree Zaboj Campula
2017-02-25 17:39 ` Jiri Pirko
2017-02-25 20:22 ` Zaboj Campula
2017-02-26 7:56 ` Jiri Pirko
2017-02-26 14:00 ` Zaboj Campula
2017-02-26 14:46 ` Jiri Pirko
2017-02-27 16:38 ` Jiri Benc [this message]
2017-02-28 20:07 ` Zaboj Campula
2017-03-01 10:22 ` Jiri Benc
2017-03-02 19:51 ` Zaboj Campula
2017-02-27 17:26 ` Stephen Hemminger
2017-02-27 18:52 ` Stephen Hemminger
2017-02-27 18:55 ` Stephen Hemminger
2017-02-28 20:19 ` Zaboj Campula
2017-02-28 21:47 ` Jiri Pirko
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=20170227173825.39e00c61@griffin \
--to=jbenc@redhat.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=zaboj.campula@post.cz \
/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;
as well as URLs for NNTP newsgroup(s).