man: document that VirtualEthernetExtra= has nothing to do with Bridge=

Fixes: #15402
This commit is contained in:
Lennart Poettering 2020-04-22 16:42:38 +02:00 committed by Zbigniew Jędrzejewski-Szmek
parent eecf4f7e04
commit 60e16d20a3
1 changed files with 10 additions and 12 deletions

View File

@ -469,18 +469,16 @@
<varlistentry>
<term><varname>VirtualEthernetExtra=</varname></term>
<listitem><para>Takes a colon-separated pair of interface
names. Configures an additional virtual Ethernet connection
(<literal>veth</literal>) between host and the container. The
first specified name is the interface name on the host, the
second the interface name in the container. The latter may be
omitted in which case it is set to the same name as the host
side interface. This setting implies
<varname>Private=yes</varname>. This setting corresponds to
the <option>--network-veth-extra=</option> command line
switch, and maybe be used multiple times. It is independent of
<varname>VirtualEthernet=</varname>. This option is privileged
(see above).</para></listitem>
<listitem><para>Takes a colon-separated pair of interface names. Configures an additional virtual
Ethernet connection (<literal>veth</literal>) between host and the container. The first specified
name is the interface name on the host, the second the interface name in the container. The latter
may be omitted in which case it is set to the same name as the host side interface. This setting
implies <varname>Private=yes</varname>. This setting corresponds to the
<option>--network-veth-extra=</option> command line switch, and maybe be used multiple times. It is
independent of <varname>VirtualEthernet=</varname>. Note that this option is unrelated to the
<varname>Bridge=</varname> setting below, and thus any connections created this way are not
automatically added to any bridge device on the host side. This option is privileged (see
above).</para></listitem>
</varlistentry>
<varlistentry>