shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-24 21:34:08 +03:00
Code
bdc11d26d1
systemd-stable/network/80-container-vz.network

30 lines
1009 B
SYSTEMD
Raw Normal View History

network: change license of examples to MIT-0 Arguably, CC0 is just fine for examples since they are not code. But it's easier to be consistent and just use MIT-0 for all "documentation". Thus, the license is changed similarly code examples under man/. Based on 'git shortlog -ns network/*' and 'git log -p', the following folks should ack this: Zbigniew Jędrzejewski-Szmek Lennart Poettering Tom Gundersen Yu Watanabe Daan De Meyer Marc-André Lureau
2022-10-26 09:34:13 +03:00
# SPDX-License-Identifier: MIT-0
Add SPDX license headers to various assorted files
2017-11-18 20:18:16 +03:00
#
network: license all config files as CC0 Same justification as the previous commit. $ for i in network/*-*; do git blame $i;done | less shows that those files were written by Tom Gundersen, Lennart Poettering, Yu Watanabe, me, and Marc-André Lureau.
2022-01-11 19:52:35 +03:00
# This config file is installed as part of systemd.
network: change license of examples to MIT-0 Arguably, CC0 is just fine for examples since they are not code. But it's easier to be consistent and just use MIT-0 for all "documentation". Thus, the license is changed similarly code examples under man/. Based on 'git shortlog -ns network/*' and 'git log -p', the following folks should ack this: Zbigniew Jędrzejewski-Szmek Lennart Poettering Tom Gundersen Yu Watanabe Daan De Meyer Marc-André Lureau
2022-10-26 09:34:13 +03:00
# It may be freely copied and edited (following the MIT No Attribution license).
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
#
network: license all config files as CC0 Same justification as the previous commit. $ for i in network/*-*; do git blame $i;done | less shows that those files were written by Tom Gundersen, Lennart Poettering, Yu Watanabe, me, and Marc-André Lureau.
2022-01-11 19:52:35 +03:00
# To make local modifications, one of the following methods may be used:
# 1. add a drop-in file that extends this file by creating the
# /etc/systemd/network/80-container-vz.network.d/ directory and creating a
# new .conf file there.
# 2. copy this file into /etc/systemd/network or one of the other paths checked
# by systemd-networkd and edit it there.
# This file should not be edited in place, because it'll be overwritten on upgrades.
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 bridge interface created by systemd-nspawn's
# --network-zone= switch. See systemd-nspawn(1) for details.
[Match]
Name=vz-*
Driver=bridge
[Network]
# Default to using a /24 prefix, giving up to 253 addresses per virtual network.
Address=0.0.0.0/24
LinkLocalAddressing=yes
DHCPServer=yes
network: use IPMasquerade=both instead of yes Follow-up for 4c72d851cd007e945a85811f89376a2675daa1a5.
2021-02-24 14:29:24 +03:00
IPMasquerade=both
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
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
networkd: Enable IPv6SendRA on builtin network files RAs trigger neighbor discovery which allows users to query the LL address of the container/VM via `ip neighbor get dev`. This is useful as it gives users an easy way to connect to the container without needing LLMNR or mDNS to resolve the hostname of the container to an IP address. In practice, this allows connecting with only networkd enabled and without resolved running in the host/container.
2020-12-26 17:27:55 +03:00
IPv6SendRA=yes
Copy Permalink