On Wed, 2017-03-01 at 11:22 +0100, Jiri Benc wrote:
> On Tue, 28 Feb 2017 20:07:37 +0000, Zaboj Campula wrote:
> > Well it is impossible to draw a simple tree showing the configuration
> > exactly with all details. May be it is too ambitious to draw a tree
> > at all.
>
&
On Mon, 2017-02-27 at 10:55 -0800, Stephen Hemminger wrote:
>
> Another alternative format would be to make -tree a output modifier and ident
> (like ps tree options).
>
> $ ip -t link
> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
> DEFAULT group default qlen 1
> link/loopback 00:00:
On Mon, 2017-02-27 at 17:38 +0100, Jiri Benc wrote:
>
> 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
ind of output useful when troubleshooting a complex
> > configuration with many interfaces. It may show relations among
> > interfaces.
>
> Did you see https://github.com/jbenc/plotnetcfg ?
>
Thanks for the link. I haven't
nk
> > eth0
> > bond0
> > eth1
> > bond0
> > eth2
> > bond1
> > eth3
> > bond1
>
>
> Hmm, what is this good for? I'm probably missing something...
I consider this kind of output useful when troubleshooting a complex
configuratio
Add the argument '-tree' to ip-link to show network devices dependency tree.
Example:
$ ip -tree link
eth0
bond0
eth1
bond0
eth2
bond1
eth3
bond1
Signed-off-by: Zaboj Campula
---
include/utils.h | 1 +
ip/ip.c | 5 ++-
ip/ipaddre