[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170226144610.GB2071@nanopsycho.orion>
Date: Sun, 26 Feb 2017 15:46:10 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Zaboj Campula <zaboj.campula@...t.cz>
Cc: netdev@...r.kernel.org, jbenc@...hat.com
Subject: Re: [PATCH] iproute2: show network device dependency tree
Sun, Feb 26, 2017 at 03:00:14PM CET, zaboj.campula@...t.cz wrote:
>On Sun, 2017-02-26 at 08:56 +0100, Jiri Pirko wrote:
>> Sat, Feb 25, 2017 at 09:22:22PM CET, zaboj.campula@...t.cz wrote:
>> > On Sat, 2017-02-25 at 18:39 +0100, Jiri Pirko wrote:
>> > > > Sat, Feb 25, 2017 at 05:59:00PM CET, zaboj.campula@...t.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 something...
>> >
>> > I consider this kind 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 seen plotnetcfg and I like it.
>It is handy when the analyzed system has GUI.
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.
Powered by blists - more mailing lists