Re: [PATCH] iproute2: show network device dependency tree

2017-03-02 Thread Zaboj Campula
On Wed, 2017-03-01 at 11:22 +0100, Jiri Benc wrote: > On Tue, 28 Feb 2017 20:07:37 +, 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. > > I tried that and failed.

Re: [PATCH] iproute2: show network device dependency tree

2017-03-01 Thread Jiri Benc
On Tue, 28 Feb 2017 20:07:37 +, 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. I tried that and failed. I didn't want to have something that would work only "somehow"

Re: [PATCH] iproute2: show network device dependency tree

2017-02-28 Thread Jiri Pirko
Tue, Feb 28, 2017 at 09:19:23PM CET, zaboj.camp...@post.cz wrote: >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

Re: [PATCH] iproute2: show network device dependency tree

2017-02-28 Thread Zaboj Campula
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 >   

Re: [PATCH] iproute2: show network device dependency tree

2017-02-28 Thread Zaboj Campula
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

Re: [PATCH] iproute2: show network device dependency tree

2017-02-27 Thread Stephen Hemminger
On Sat, 25 Feb 2017 16:59:00 + Zaboj Campula wrote: > dd the argument '-tree' to ip-link to show network devices dependency tree. > > Example: > > $ ip -tree link > eth0 > bond0 > eth1 > bond0 > eth2 > bond1 > eth3 > bond1 Maybe use format similar to

Re: [PATCH] iproute2: show network device dependency tree

2017-02-27 Thread Stephen Hemminger
On Sat, 25 Feb 2017 16:59:00 + Zaboj Campula wrote: > 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 Another alternative format

Re: [PATCH] iproute2: show network device dependency tree

2017-02-27 Thread Stephen Hemminger
On Sun, 26 Feb 2017 08:56:33 +0100 Jiri Pirko wrote: > Did you see https://github.com/jbenc/plotnetcfg ? Cool, thanks.

Re: [PATCH] iproute2: show network device dependency tree

2017-02-27 Thread Jiri Benc
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

Re: [PATCH] iproute2: show network device dependency tree

2017-02-26 Thread Jiri Pirko
Sun, Feb 26, 2017 at 03:00:14PM CET, zaboj.camp...@post.cz wrote: >On Sun, 2017-02-26 at 08:56 +0100, Jiri Pirko wrote: >> Sat, Feb 25, 2017 at 09:22:22PM CET, zaboj.camp...@post.cz wrote: >> > On Sat, 2017-02-25 at 18:39 +0100, Jiri Pirko wrote: >> > > > Sat, Feb 25, 2017 at 05:59:00PM CET,

Re: [PATCH] iproute2: show network device dependency tree

2017-02-26 Thread Zaboj Campula
On Sun, 2017-02-26 at 08:56 +0100, Jiri Pirko wrote: > Sat, Feb 25, 2017 at 09:22:22PM CET, zaboj.camp...@post.cz wrote: > > On Sat, 2017-02-25 at 18:39 +0100, Jiri Pirko wrote: > > > > Sat, Feb 25, 2017 at 05:59:00PM CET, zaboj.camp...@post.cz > > > > wrote: > > > > Add the argument '-tree' to

Re: [PATCH] iproute2: show network device dependency tree

2017-02-25 Thread Jiri Pirko
Sat, Feb 25, 2017 at 09:22:22PM CET, zaboj.camp...@post.cz wrote: >On Sat, 2017-02-25 at 18:39 +0100, Jiri Pirko wrote: >> > Sat, Feb 25, 2017 at 05:59:00PM CET, zaboj.camp...@post.cz wrote: >> > Add the argument '-tree' to ip-link to show network devices dependency >> > tree. >> > >> > Example:

Re: [PATCH] iproute2: show network device dependency tree

2017-02-25 Thread Zaboj Campula
On Sat, 2017-02-25 at 18:39 +0100, Jiri Pirko wrote: > > Sat, Feb 25, 2017 at 05:59:00PM CET, zaboj.camp...@post.cz wrote: > > Add the argument '-tree' to ip-link to show network devices dependency tree. > > > > Example: > > > > $ ip -tree link > > eth0 > >    bond0 > > eth1 > >    bond0 > >

Re: [PATCH] iproute2: show network device dependency tree

2017-02-25 Thread Jiri Pirko
Sat, Feb 25, 2017 at 05:59:00PM CET, zaboj.camp...@post.cz wrote: >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 Hmm, what is this good for? I'm probably missing

[PATCH] iproute2: show network device dependency tree

2017-02-25 Thread Zaboj Campula
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/ipaddress.c | 97