summaryrefslogtreecommitdiffstats
path: root/include/net
diff options
context:
space:
mode:
authorTobias Waldekranz <tobias@waldekranz.com>2022-03-16 16:08:45 +0100
committerJakub Kicinski <kuba@kernel.org>2022-03-17 16:49:57 -0700
commit122c29486e1ff78033c45d0d31c710e7dc8945a5 (patch)
tree5d7e6fc86ea20ddc47730a81c32534e2acf55c90 /include/net
parent8c678d60562f3e5f6d0a5f5465e27930ffedb8ca (diff)
downloadlinux-122c29486e1ff78033c45d0d31c710e7dc8945a5.tar.bz2
net: bridge: mst: Support setting and reporting MST port states
Make it possible to change the port state in a given MSTI by extending the bridge port netlink interface (RTM_SETLINK on PF_BRIDGE).The proposed iproute2 interface would be: bridge mst set dev <PORT> msti <MSTI> state <STATE> Current states in all applicable MSTIs can also be dumped via a corresponding RTM_GETLINK. The proposed iproute interface looks like this: $ bridge mst port msti vb1 0 state forwarding 100 state disabled vb2 0 state forwarding 100 state forwarding The preexisting per-VLAN states are still valid in the MST mode (although they are read-only), and can be queried as usual if one is interested in knowing a particular VLAN's state without having to care about the VID to MSTI mapping (in this example VLAN 20 and 30 are bound to MSTI 100): $ bridge -d vlan port vlan-id vb1 10 state forwarding mcast_router 1 20 state disabled mcast_router 1 30 state disabled mcast_router 1 40 state forwarding mcast_router 1 vb2 10 state forwarding mcast_router 1 20 state forwarding mcast_router 1 30 state forwarding mcast_router 1 40 state forwarding mcast_router 1 Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com> Acked-by: Nikolay Aleksandrov <razor@blackwall.org> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions