diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2015-07-24 23:04:57 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2015-07-24 23:44:42 -0400 |
| commit | 072f9e4af4cf465aca6e263f4dfd6e07786786d2 (patch) | |
| tree | dcab1e8e730988af460f6ff3d3b73805d3feb0f5 /man | |
| parent | 84c3409631f48869dcb59c0a74eba6d4ac40ad93 (diff) | |
networkd: turn UnicastFlood on by default
Looking at the kernel commit, "on" seems to be the default value:
commit 867a59436fc35593ae0e0efcd56cc6d2f8506586
Author: Vlad Yasevich <vyasevic@redhat.com>
Date: Wed Jun 5 10:08:01 2013 -0400
bridge: Add a flag to control unicast packet flood.
Add a flag to control flood of unicast traffic. By default, flood is
on and the bridge will flood unicast traffic if it doesn't know
the destination. When the flag is turned off, unicast traffic
without an FDB will not be forwarded to the specified port.
... and it seems to be the reasonable thing to do by default.
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.network.xml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/man/systemd.network.xml b/man/systemd.network.xml index 0dab96d127..196e57dd57 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -672,8 +672,9 @@ <varlistentry> <term><varname>UnicastFlood=</varname></term> <listitem> - <para>A boolean. UnicastFlood configures whether a given port will flood - unicast traffic for which there is no FDB entry. Defaults to off. + <para>A boolean. Controls whether the bridge should flood + traffic for which an FDB entry is missing and the destination + is unknown through this port. Defaults to on. </para> </listitem> </varlistentry> |