46d12ae7d3
NetworkManager takes a distinctly differnet network management approach and the bulk of the dhcp-all-interfaces code is largely targetted at distribution specific configuration. Some which may or may not override settings, or only partially assert desirable settings. As such, we need to set appropriate configuration, such as the correct client to be used, and timeouts based upon user supplied settings. By default this change sets the client to be dhclient on redhat styled machines, as the packaging default, while it works for ramdisk usage, it does not reset the interface between retries, which can be critical if the infrastucture operator is attempting to configure LACP trunks to the end node. Change-Id: I0e0cfbdbf7ef2b2861b934ccd7dab9d83a35c8f0 Story: 2008001 Task: 40648
25 lines
1.2 KiB
Plaintext
25 lines
1.2 KiB
Plaintext
# WARNING: This file has been modified by the diskimage-builder
|
|
# dhcp-all-interfaces element as this machine is likely running
|
|
# a ramdisk or needs to attempt auto-configuration on all interfaces.
|
|
[main]
|
|
# This makes sense even with dhcp on all interfaces in the event
|
|
# that the configuration has been or is being supplied via external means.
|
|
ignore-carrier=*
|
|
# Use dhclient as was done previously to the Centos8/RHEL8 RPM defaults.
|
|
# This is because dhclient shuts the interface down after a retry attempt
|
|
# which allows the link state to reset with some switches, which may be
|
|
# important for the ramdisk to recover networking.
|
|
dhcp=DIB_DHCP_CLIENT
|
|
|
|
[connection]
|
|
# Keep retrying, this is important for this important espescialy for
|
|
# ramdisks in environments where varying switch configurations may
|
|
# cause traffic to be blocked or intermittent connectivity failures
|
|
# such as those at an edge site may cause issues.
|
|
autoconnect-retries=-1
|
|
# Set the timeout. Diskimage-builder dhcp-all-interfaces has a 30
|
|
# second default. NetworkManager, by default, is 45 seconds.
|
|
# In some cases where ramdisks are in use, 60 seconds is advisable.
|
|
ipv4.dhcp-timeout=DIB_DHCP_TIMEOUT
|
|
ipv6.dhcp-timeout=DIB_DHCP_TIMEOUT
|