From owner-freebsd-questions@FreeBSD.ORG Fri Jan 28 21:59:05 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 181EE16A4CF for ; Fri, 28 Jan 2005 21:59:05 +0000 (GMT) Received: from 26.mail-out.ovh.net (26.mail-out.ovh.net [213.186.42.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id E659B43D2D for ; Fri, 28 Jan 2005 21:59:03 +0000 (GMT) (envelope-from lists@serpe.org) Received: (qmail 16222 invoked by uid 503); 28 Jan 2005 21:59:01 -0000 Received: (QMFILT: 1.0); 28 Jan 2005 21:59:01 -0000 Received: from b6.ovh.net (HELO mail49.ha.ovh.net) (213.186.33.56) by 26.mail-out.ovh.net with DES-CBC3-SHA encrypted SMTP; 28 Jan 2005 21:59:01 -0000 Received: from b0.ovh.net (HELO queue-out) (213.186.33.50) by b0.ovh.net with SMTP; 28 Jan 2005 21:58:56 -0000 Received: from m111.net81-66-254.noos.fr (HELO ?192.168.0.2?) (lists%serpe.org@81.66.254.111) by ns0.ovh.net with SMTP; 28 Jan 2005 21:58:56 -0000 Message-ID: <41FAB5A0.2000909@serpe.org> Date: Fri, 28 Jan 2005 22:58:56 +0100 From: Nicolas User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: dhclient stops trying to get a new lease X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jan 2005 21:59:05 -0000 Hi, I have a cable modem with dynamic IP, and a FreeBSD 5.3 server just behind. This server gets its IP with the help of dhclient. Today I got a huge down because of a problem on the ISP side. During that time, dhclient made his job trying to get a lease every 4 minutes, unsuccessfully of course. But at 10 AM, after 10 hours of trying to get a lease every 4 minutes (unsuccessfully of course), dhclient completely stopped trying. Thus, when the line came back up, it didn't got its lease. I had to manually tell him to get that new lease... Why did it stopped trying ? What should I do to tell him to try forever until it can acquire a lease ? Here is a part of my /var/log/messages : /* the line went down at midnight. dhclient gets a "fake" IP */ Jan 28 00:00:44 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 00:00:44 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 00:00:44 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* 4 minutes later, it retries */ Jan 28 00:04:55 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 00:04:55 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 00:04:55 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* [...same thing repeating over and over...] */ /* another time... */ Jan 28 09:57:59 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 09:57:59 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 09:57:59 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* the last dhclient-related block.. This time it's a bit different. ** after that block dhclient no more tries anything... */ Jan 28 10:00:45 sun kernel: vr0: Using force reset command. Jan 28 10:00:45 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 10:00:45 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 10:00:45 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* finally I had to restart dhclient to get my "real" IP, once the ** cable came back */ Jan 28 19:34:18 sun kernel: vr0: Using force reset command. Jan 28 19:34:57 sun dhclient: New IP Address (vr0): 81.66.254.111 Jan 28 19:34:57 sun dhclient: New Subnet Mask (vr0): 255.255.254.0 Jan 28 19:34:57 sun dhclient: New Broadcast Address (vr0): 81.66.255.255 Jan 28 19:34:57 sun dhclient: New Routers: 81.66.254.1