Files

Waldemar Znoinski bc80572061 don't configure 'lo' for dhcp

On systemd-based operating systems that don't
use /etc/sysconfig/network-scripts
dhcp-all-interfaces configures 'lo' for dhcp.
This causes errors and fails networking.target
causing system-wide issues. This change excludes
'lo' at dhcp-all-interfaces udev rules level.

Closes-bug: #1621501
Change-Id: I7563b766827bedbea7ae1de35e5bdfcbf1fc0d1e
Co-Authored-By: Jeremy Stanley <fungi@yuggoth.org>

2016-09-09 09:01:59 +00:00

install.d

don't configure 'lo' for dhcp

2016-09-09 09:01:59 +00:00

element-deps

dhcp-all-interfaces depends on dib-init-system

2016-04-22 09:23:11 +10:00

package-installs.yaml

Use generic "dhcp-client" name

2016-04-22 11:31:54 +10:00

pkg-map

Fix OpenSUSE support

2016-05-03 22:23:51 -07:00

README.rst

Add Gentoo to the dhcp-all-interfaces element

2016-04-21 16:40:06 -05:00

README.rst

dhcp-all-interfaces

Autodetect network interfaces during boot and configure them for DHCP

The rationale for this is that we are likely to require multiple network interfaces for use cases such as baremetal and there is no way to know ahead of time which one is which, so we will simply run a DHCP client on all interfaces with real MAC addresses (except lo) that are visible on the first boot.

On non-Gentoo based distributions the script /usr/local/sbin/dhcp-all-interfaces.sh will be called early in each boot and will scan available network interfaces and ensure they are configured properly before networking services are started.

On Gentoo based distributions we will install the dhcpcd package and ensure the service starts at boot. This service automatically sets up all interfaces found via dhcp and/or dhcpv6 (or SLAAC).