From owner-freebsd-net@FreeBSD.ORG Fri Jul 13 18:20:39 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E13ED106566B for ; Fri, 13 Jul 2012 18:20:39 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id AF9AE8FC0A for ; Fri, 13 Jul 2012 18:20:39 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q6DIKbb1006540; Fri, 13 Jul 2012 11:20:39 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <500066F4.2030102@rawbw.com> Date: Fri, 13 Jul 2012 11:20:36 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120702 Thunderbird/13.0.1 MIME-Version: 1.0 To: Peter Jeremy References: <4FFF3683.7020107@rawbw.com> <20120713094830.GA83006@server.rulingia.com> In-Reply-To: <20120713094830.GA83006@server.rulingia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: System doesn't detect unplugged network cable and doesn't set interface up properly with DHCP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 18:20:40 -0000 On 07/13/2012 02:48, Peter Jeremy wrote: > This is a bug in dhclient - see PR bin/166656, which includes a fix. I think this PR addresses part of the problem: dhclient doesn't exit when the link goes down. But even if it exits, it leaves the IP address that it has set, which is wrong. This IP address survives through the next DHCP setup process and ends up being the second IP address. Should be very easy to on exit remove any IP address that was set during dhclient process lifetime. Yuri