| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
Newer kernels export meta-information about the origin of an ifname. Respect this
from the ifname rename logic. We do not rename any interfaces that was originally
named by userspace, nor once which have already been renamed from userspace.
Moreover, we optionally do not (the default) rename interfaces which the kernel
claims to have named in a predictable way.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
IPv4LL on them
|
| |
|
|
| |
Now that we have a graceful handover from IPv4LL to DHCP, there is no longer any reason to leave this off by default.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
|
|
This is private configuraiton, so let's not pollute the namespace (and hence make Debian happy :) ).
|
