From 97f27f8a1690cdf32f34edd43121eeda6452676a Mon Sep 17 00:00:00 2001 From: Santa Wiryaman Date: Mon, 3 May 2021 18:48:26 -0400 Subject: 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 | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'man/systemd.network.xml') diff --git a/man/systemd.network.xml b/man/systemd.network.xml index 74f416cf39..52d017bb78 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -2960,6 +2960,15 @@ Token=prefixstable:2002:da8:1:: receiving port. When unset, the kernel's default will be used. + + Isolated= + + Takes a boolean. Configures whether this port is isolated or not. Within a bridge, + isolated ports can only communicate with non-isolated ports. When set to true, this port can only + communicate with other ports whose Isolated setting is false. When set to false, this port + can communicate with any other ports. When unset, the kernel's default will be used. + + UseBPDU= -- cgit v1.2.3