Thread (14 messages) 14 messages, 4 authors, 2017-09-10

Re: [PATCH iproute2 3/3] bridge: request vlans along with link information

From: Nikolay Aleksandrov <hidden>
Date: 2017-09-10 10:24:57

On 09/09/17 20:23, Jamal Hadi Salim wrote:
On 17-09-09 12:24 PM, Roopa Prabhu wrote:
quoted
On Fri, Sep 8, 2017 at 2:52 PM, Roman Mashak [off-list ref] wrote:
[snip]
Agree we should be turning on this stuff by default. i.e default stays
compressed; otherwise it a huge dump.

Having said that there is a lot of mess with this stuff.
The bridge link events _already send this IFLA_AF_SPCE info_
so not much choice  there but to print it.
At minimal we need that part because unfortunately there is no
vlanfilter event in existence which will send us summaries of just
vlans added to a port i.e both use XXXLINK.
In general, the XXXLINK interface with these master devices (bridge,
bond etc) continues to get messy. Recently started seeing events with
devices claiming to be of KIND_slave etc on the bridge and bond devices;
yet at the same time my wireless card events are also showing up on the
bridge link even though it is not enslaved there..
Out of curiousity about this one, do you see the wifi card when doing bridge monitor ?
Or are you specifically watching AF_BRIDGE events, because bridge monitor link also can
include AF_UNSPEC ?
cheers,
jamal
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help