2015-02-07 10:30:02 +00:00
|
|
|
===================
|
|
|
|
|
dhcp-all-interfaces
|
|
|
|
|
===================
|
2013-03-05 17:34:19 +00:00
|
|
|
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
|
2014-01-21 20:58:45 +00:00
|
|
|
DHCP client on all interfaces with real MAC addresses (except lo) that
|
|
|
|
|
are visible on the first boot.
|
2013-03-05 17:34:19 +00:00
|
|
|
|
2016-03-31 00:48:19 +00:00
|
|
|
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).
|
2017-01-04 17:21:03 +00:00
|
|
|
|
|
|
|
|
Environment Variables
|
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
|
|
DIB_DHCP_TIMEOUT
|
|
|
|
|
:Required: No
|
|
|
|
|
:Default: 30
|
2018-04-05 13:12:09 +00:00
|
|
|
:Description: Amount of time in seconds that the systemd service(or dhclient)
|
|
|
|
|
will wait to get an address. Should be increased in networks such as
|
|
|
|
|
Infiniband.
|
2017-01-04 17:21:03 +00:00
|
|
|
:Example: DIB_DHCP_TIMEOUT=300
|
2022-01-23 22:09:11 +00:00
|
|
|
|
|
|
|
|
DIB_DHCP_NETWORK_MANAGER_AUTO
|
|
|
|
|
:Required: No
|
|
|
|
|
:Default: false
|
|
|
|
|
:Description: When NetworkManager is detected, and this is set to true the
|
|
|
|
|
dhcp-all-interfaces service will not be installed. Only the NetworkManager
|
|
|
|
|
configuration will be added. NetworkManager is quite capable to do automatic
|
|
|
|
|
interface configuration. NetworkManager will by default try to
|
|
|
|
|
auto-configure any interface with no configuration, it will use DHCP for
|
|
|
|
|
IPv4 and Router Advertisements to decide how to initialize IPv6.
|
|
|
|
|
:Example: DIB_DHCP_NETWORK_MANAGER_AUTO=true
|
2022-06-28 18:02:03 +00:00
|
|
|
|
|
|
|
|
DIB_DHCP_CLIENT
|
|
|
|
|
:Required: no
|
|
|
|
|
:Default: internal
|
|
|
|
|
:Description: When NetworkManager is in use, this setting conveys which DHCP
|
|
|
|
|
client is in use for acquiring a DHCP address for the node. In some specific
|
|
|
|
|
cases, where known that dhclient is the tested or most compatible default,
|
|
|
|
|
specifically for Centos 7, 8, and 8-Stream, as well as derived distributions.
|
|
|
|
|
Otherwise, the "internal" dhcp client is the default.
|
|
|
|
|
:Example: DIB_DHCP_CLIENT
|
