systemd-stable/network/80-container-host0.network

#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  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 container-side of the virtual Ethernet link
# created by systemd-nspawn's --network-veth switch. See systemd-nspawn(1) for
# details.

[Match]
Virtualization=container
Name=host0

[Network]
DHCP=yes
LinkLocalAddressing=yes
LLDP=yes
EmitLLDP=customer-bridge

[DHCP]
UseTimezone=yes
license: LGPL-2.1+ -> LGPL-2.1-or-later 2020-11-09 13:23:58 +09:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
Add SPDX license headers to various assorted files 2017-11-18 18:18:16 +01:00			`#`
network: always take possession of host side of nspawn veth tunnels and do IPv4LL on them 2014-05-17 21:32:13 +02: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 21:03:40 +02:00			`# This network file matches the container-side of the virtual Ethernet link`
			`# created by systemd-nspawn's --network-veth switch. See systemd-nspawn(1) for`
			`# details.`

networkd/nspawn: enable dhcp client on veth device created in guest When starting systemd-nspawn with --network-veth, we create a veth device called host0 in the guest. Pick up on this and start a dhcp client on it. We will also pick up host0 netdevs created by other containers should they chose to use the same name. 2014-02-21 22:44:42 +01:00			`[Match]`
			`Virtualization=container`
			`Name=host0`

			`[Network]`
networkd: introduce an AddressFamilyBoolean enum type This introduces am AddressFamilyBoolean type that works more or less like a booleaan, but can optionally turn on/off things for ipv4 and ipv6 independently. THis also ports the DHCP field over to it. 2015-01-13 19:48:19 +01:00			`DHCP=yes`
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 15:31:26 +01:00			`LinkLocalAddressing=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 14:06:08 +01: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 22:44:13 +02:00			`EmitLLDP=customer-bridge`
network: turn on DHCP timezone passing between container and host Let's turn on DHCP timezone passing from the host to a container, so that the timezone is always in sync. 2015-08-26 19:38:15 +02:00
			`[DHCP]`
			`UseTimezone=yes`