summaryrefslogtreecommitdiff
path: root/network/80-container-host0.network
Commit message (Collapse)AuthorAgeFilesLines
* network: change license of examples to MIT-0Zbigniew Jędrzejewski-Szmek2022-10-261-2/+2
| | | | | | | | | | | | | | | 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
* network: license all config files as CC0Zbigniew Jędrzejewski-Szmek2022-01-121-6/+10
| | | | | | | | 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.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* Add SPDX license headers to various assorted filesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* network: allow LLDP packets to cross non-customer bridges for container ↵Lennart Poettering2016-05-091-1/+1
| | | | | | | | | | | 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.
* network: add automatic configuration for the networks created by nspawn ↵Lennart Poettering2016-05-091-0/+4
| | | | | | | --network-zone= This way, they "just work", similar to --network-veth behaves, as long as networkd is enabled and running on all involved nodes.
* network: turn on LLDP tx+rx for the default container network configurationLennart Poettering2016-02-211-0/+2
| | | | | Containers are relatively trusted and the veth tunnels are small networks, hence let's turn on LLDP both ways for them.
* network: turn on DHCP timezone passing between container and hostLennart Poettering2015-08-261-0/+3
| | | | | Let's turn on DHCP timezone passing from the host to a container, so that the timezone is always in sync.
* network: fix 'LinkLocal' -> 'LinkLocalAddressing' in network filesDavid Herrmann2015-02-141-1/+1
| | | | | | | | | | | | '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.
* networkd: generalize IPv4LL to LinkLocalTom Gundersen2015-02-091-1/+1
| | | | | | This allows both IPv4 and IPv6 link-local addresses to be enabled or disabled. By default we still enable IPv6LL and disable IPv4LL. The old config option is kept for backwards compatibility, but removed from the documentation.
* networkd: introduce an AddressFamilyBoolean enum typeLennart Poettering2015-01-131-1/+1
| | | | | | 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.
* networkd: merge DHCPv4 and DHCPv6 configTom Gundersen2014-06-291-2/+1
| | | | | | | If there are v4 or v6 specific options we can keep those in separate sections, but for the common options, we will use only one. Moreovere only use DHCP=[yes/both|no/none|v4|v6] to enable or disable the clients.
* net: enable dhcp6 for containersLennart Poettering2014-06-191-0/+1
|
* network: always take possession of host side of nspawn veth tunnels and do ↵Lennart Poettering2014-05-181-0/+7
| | | | IPv4LL on them
* network: default to IPv4LL on host0Tom Gundersen2014-04-031-0/+1
| | | | Now that we have a graceful handover from IPv4LL to DHCP, there is no longer any reason to leave this off by default.
* networkd/nspawn: enable dhcp client on veth device created in guestTom Gundersen2014-02-221-0/+6
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.
View Lorry Controller Status