SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

nspawn: when adding a veth interface to a bridge, use the "vb-" rather than "ve-" interface name prefix

Browse Source 
This way we can recognize the interfaces later on to apply different
host-side configuration to them.
This commit is contained in:
Lennart Poettering
2014-02-21 04:02:12 +01:00
parent 90e633a790
commit 08af0da269
2 changed files with 20 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd-nspawn.xml
+11 -7
View File
@@ -321,13 +321,17 @@
<varlistentry>
<term><option>--network-bridge=</option></term>
<listitem><para>Adds the host side of the
Ethernet link created with
<option>--network-veth</option>
to the specified bridge. Note that
<option>--network-bridge</option>
<listitem><para>Adds the host side of
the Ethernet link created with
<option>--network-veth</option> to the
specified bridge. Note that
<option>--network-bridge=</option>
implies
<option>--network-veth</option>.</para></listitem>
<option>--network-veth</option>. If
this option is used the host side of
the Ethernet link will use the
<literal>vb-</literal> prefix instead
of <literal>ve-</literal>.</para></listitem>
</varlistentry>
<varlistentry>
@@ -466,7 +470,7 @@
destination in the container. The
<option>--bind-ro=</option> option
creates read-only bind
mount.</para></listitem>
mounts.</para></listitem>
</varlistentry>
<varlistentry>