systemd/network/80-container-ve.network

#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

# This network file matches the host-side of the virtual Ethernet link
# created by systemd-nspawn's --network-veth switch. See systemd-nspawn(1) for
# details.

[Match]
Name=ve-*
Driver=veth

[Network]
# Default to using a /28 prefix, giving up to 13 addresses per container.
Address=0.0.0.0/28
LinkLocalAddressing=yes
DHCPServer=yes
IPMasquerade=yes
LLDP=yes
EmitLLDP=customer-bridge
Add SPDX license headers to various assorted files 2017-11-18 20:18:16 +03:00			`# SPDX-License-Identifier: LGPL-2.1+`
			`#`
network: always take possession of host side of nspawn veth tunnels and do IPv4LL on them 2014-05-17 23:32:13 +04:00			`# This file is part of systemd.`
			`#`
			`# systemd is free software; you can redistribute it and/or modify it`
			`# under the terms of the GNU Lesser General Public License as published by`
			`# the Free Software Foundation; either version 2.1 of the License, or`
			`# (at your option) any later version.`

network: add automatic configuration for the networks created by nspawn --network-zone= This way, they "just work", similar to --network-veth behaves, as long as networkd is enabled and running on all involved nodes. 2016-05-06 22:03:40 +03:00			`# This network file matches the host-side of the virtual Ethernet link`
			`# created by systemd-nspawn's --network-veth switch. See systemd-nspawn(1) for`
			`# details.`

network: always take possession of host side of nspawn veth tunnels and do IPv4LL on them 2014-05-17 23:32:13 +04:00			`[Match]`
			`Name=ve-*`
			`Driver=veth`

			`[Network]`
doc: network - add comment about default prefix size Should hopefully make it clear that this is not some magic value, just the default we picked. Suggested by Jan Engelhardt. 2015-01-13 20:23:53 +03:00			`# Default to using a /28 prefix, giving up to 13 addresses per container.`
network: automatically assign each container veth link a /28 IP address range 2014-06-18 20:27:55 +04:00			`Address=0.0.0.0/28`
network: fix 'LinkLocal' -> 'LinkLocalAddressing' in network files 'LinkLocal' was renamed to 'LinkLocalAddressing' in: commit 56fd6bf795926409b087bce406ea851ad89f9fe8 Author: Tom Gundersen <teg@jklm.no> Date: Sat Feb 14 00:32:26 2015 +0100 networkd: .network - rename LinkLocal to LinkLocalAddressing ..but apparently the network files were not updated. Fix this. 2015-02-14 17:31:26 +03:00			`LinkLocalAddressing=yes`
network: automatically assign each container veth link a /28 IP address range 2014-06-18 20:27:55 +04:00			`DHCPServer=yes`
networkd: add minimal IP forwarding and masquerading support to .network files This adds two new settings to networkd's .network files: IPForwarding=yes and IPMasquerade=yes. The former controls the "forwarding" sysctl setting of the interface, thus controlling whether IP forwarding shall be enabled on the specific interface. The latter controls whether a firewall rule shall be installed that exposes traffic coming from the interface as coming from the local host to all other interfaces. This also enables both options by default for container network interfaces, thus making "systemd-nspawn --network-veth" have network connectivity out of the box. 2015-01-13 15:47:08 +03:00			`IPMasquerade=yes`
network: turn on LLDP tx+rx for the default container network configuration Containers are relatively trusted and the veth tunnels are small networks, hence let's turn on LLDP both ways for them. 2016-02-21 16:06:08 +03:00			`LLDP=yes`
network: allow LLDP packets to cross non-customer bridges for container network interfaces This changes the default .network files we ship for nspawn containers to set EmitLLDP=customer-bridge in order to allow propagation of the LLDP packets across bridges. This is useful so that "networkctl status" shows all peers connected to a virtual container network, collecting this data via LLDP. This is safe since the default configuration for these interfaces does not bridge these links to external interfaces, but relies on IP routing for this. 2016-05-06 23:44:13 +03:00			`EmitLLDP=customer-bridge`