sig_cloud/diskimage-builder
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
83b607557e
diskimage-builder/elements/dhcp-all-interfaces
History
Ian Wienand 11128b0673 Use generic "dhcp-client" name 
Every platform has a different name for their DHCP client, so use a
generic name "dhcp-client" in the package name and let everyone choose
their sub-name.  This also brings some consistency across simple-init
& dhcp-all-interfaces

Change-Id: I797aa7aacb13dfb7f35700463dc11d55552eb108
2016-04-22 11:31:54 +10:00
..
install.d Merge "Add Gentoo to the dhcp-all-interfaces element" 2016-04-21 23:03:24 +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 Use generic "dhcp-client" name 2016-04-22 11:31:54 +10: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).