~lukeshu/systemd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2015-08-26	network: turn on DHCP timezone passing between container and host	Lennart Poettering
	Let's turn on DHCP timezone passing from the host to a container, so that the timezone is always in sync.
2015-02-14	network: fix 'LinkLocal' -> 'LinkLocalAddressing' in network files	David Herrmann
	'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-09	networkd: generalize IPv4LL to LinkLocal	Tom Gundersen
	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.
2015-01-13	networkd: introduce an AddressFamilyBoolean enum type	Lennart Poettering
	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.
2014-06-29	networkd: merge DHCPv4 and DHCPv6 config	Tom Gundersen
	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.
2014-06-19	net: enable dhcp6 for containers	Lennart Poettering

2014-05-18	network: always take possession of host side of nspawn veth tunnels and do ↵	Lennart Poettering
	IPv4LL on them
2014-04-03	network: default to IPv4LL on host0	Tom Gundersen
	Now that we have a graceful handover from IPv4LL to DHCP, there is no longer any reason to leave this off by default.
2014-02-22	networkd/nspawn: enable dhcp client on veth device created in guest	Tom Gundersen
	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.