Derek Higgins 97399e9bb1 Set the dhclient timeout to match DIB_DHCP_TIMEOUT ... On initial boot when networking is brought up by cloud-init this is the timeout that dhclient adheres to. Centos configures "timeout 300" (for an EC2 bug) in their cloud image, which results in a 5 minutes delay to boot in cases where no dhcp available (e.g. IPv6 SLAAC). To reduce this boot delay and to provide consistency with places where we have set other dhcp timeouts set this to DIB_DHCP_TIMEOUT. Change-Id: I119a002070501c3dfe7c6730b07ee25f422b85b0 Related-Bug: #1758324		2018-04-05 14:29:22 +01:00
..
50-dhcp-all-interfaces	Set the dhclient timeout to match DIB_DHCP_TIMEOUT	2018-04-05 14:29:22 +01:00
60-remove-cloud-image-interfaces	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
dhcp-all-interfaces-udev.rules	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
dhcp-all-interfaces.conf	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
dhcp-all-interfaces.init	Merge remote-tracking branch 'origin/master' into merge-branch	2016-11-18 13:53:56 +11:00
dhcp-all-interfaces.sh	Checking link status according to DIB_DHCP_TIMEOUT	2018-02-21 12:52:57 +00:00
dhcp-interface@.service	Fix cylical systemd config for dhcp-all-interfaces	2017-08-25 15:51:23 +10:00