shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-26 03:22:00 +03:00
Code
baa90b4b81
systemd/network/80-container-ve.network

32 lines
1.0 KiB
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: always take possession of host side of nspawn veth tunnels and do IPv4LL on them
2014-05-17 23:32:13 +04: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-ve.network.d/ directory and creating a
# new .conf file there.
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
# 2. copy this file into /etc/systemd/network/ or one of the other paths checked
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
# by systemd-networkd and edit it there.
# This file should not be edited in place, because it'll be overwritten on upgrades.
network: always take possession of host side of nspawn veth tunnels and do IPv4LL on them
2014-05-17 23:32:13 +04:00
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
# This .network file matches the host-side of the virtual Ethernet link
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
# 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]
network: use Kind= instead of Driver= networkd ignores errors in reading driver through ethtool. The kind of network interface is retrieved through netlink, and networkd checks checks many failures. So, using Kind= should be safer. No functional change, just for safety.
2023-11-08 16:59:33 +03:00
Kind=veth
network: always take possession of host side of nspawn veth tunnels and do IPv4LL on them
2014-05-17 23:32:13 +04:00
Name=ve-*
[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
network: use IPMasquerade=both instead of yes Follow-up for 4c72d851cd007e945a85811f89376a2675daa1a5.
2021-02-24 14:29:24 +03:00
IPMasquerade=both
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
network: disable IPv6AcceptRA= in several default config Also, - drop DHCP=no, as it is the default setting, - enable IPv6SendRA= for wifi access point, - enable MulticastDNS= for wifi adhoc mode.
2023-11-02 07:29:45 +03:00
IPv6AcceptRA=no
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