]> git.ipfire.org Git - thirdparty/systemd.git/commit
Add support for `isolated` parameter
authorSanta Wiryaman <swiryaman@starry.com>
Mon, 3 May 2021 22:48:26 +0000 (18:48 -0400)
committerYu Watanabe <watanabe.yu+github@gmail.com>
Wed, 9 Feb 2022 08:37:37 +0000 (17:37 +0900)
commit97f27f8a1690cdf32f34edd43121eeda6452676a
treec193aa656355438da976ce7986b16efffc915507
parent10139b4e3c345250dbfc0236475e116a5b76a54d
Add support for `isolated` parameter

Add the "Isolated" parameter in the *.network file, e.g.,

[Bridge]
Isolated=true|false

When the Isolated parameter is true, traffic coming out of this port
will only be forward to other ports whose Isolated parameter is false.

When Isolated is not specified, the port uses the kernel default
setting (false).

The "Isolated" parameter was introduced in Linux 4.19.
See man bridge(8) for more details.
But even though the kernel and bridge/iproute2 recognize the "Isolated"
parameter, systemd-networkd did not have a way to set it.
man/systemd.network.xml
src/network/networkd-network-gperf.gperf
src/network/networkd-network.c
src/network/networkd-network.h
src/network/networkd-setlink.c
test/fuzz/fuzz-network-parser/26-bridge-slave-interface-1.network
test/fuzz/fuzz-network-parser/directives.network
test/fuzz/fuzz-unit-file/directives-all.service
test/networkd-test.py
test/test-network/conf/26-bridge-slave-interface-1.network
test/test-network/systemd-networkd-tests.py