Set the retry value to 60 seconds, this is not attempts, this is seconds before it needs a reply. So if the DHCP server was any sort of slow it would fail to aquire a lease. This was true for my wireless network at home. Plus, on various other lossy links, even cable modems this could be true.

Redmine ticket #2440

retry time;
	     The retry statement determines the time that must pass after the
	     client has determined that there is no DHCP server present before
	     it tries again to contact a DHCP server.  By default, this is
	     five minutes.

1 files changed, 2 insertions, 2 deletions

diff --git a/etc/inc/interfaces.inc b/etc/inc/interfaces.inc
index 1bdca30..c2a155c 100644
--- a/etc/inc/interfaces.inc
+++ b/etc/inc/interfaces.inc
@@ -2108,7 +2108,7 @@ function interface_carpdev_configure(&$vip) {
 		$dhclientconf .= <<<EOD
 interface "{$vipif}" {
 timeout 60;
-retry 1;
+retry 60;
 select-timeout 0;
 initial-interval 1;
 script "/sbin/dhclient-script";
@@ -3487,7 +3487,7 @@ function interface_dhcp_configure($interface = "wan") {
 	$dhclientconf .= <<<EOD
 interface "{$wanif}" {
 timeout 60;
-retry 1;
+retry 60;
 select-timeout 0;
 initial-interval 1;
 	{$dhclientconf_hostname}