From owner-freebsd-current@FreeBSD.ORG Thu Feb 27 23:59:22 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 102177FA for ; Thu, 27 Feb 2014 23:59:22 +0000 (UTC) Received: from mail.modirum.com (mail.modirum.com [31.185.27.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF6CF158D for ; Thu, 27 Feb 2014 23:59:21 +0000 (UTC) Received: from [77.87.241.103] (helo=desktop.reztek) by mail.modirum.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1WJArC-0002fU-Oo; Thu, 27 Feb 2014 23:59:14 +0000 From: Matthew Rezny To: Lyndon Nerenberg Subject: Re: BSD XXI Manifesto [mDNS proposal] Date: Fri, 28 Feb 2014 00:59:15 +0100 Message-ID: <2130557.6Hv9SgOJ3f@desktop.reztek> Organization: RezTek, s.r.o. User-Agent: KMail/4.12.2 (FreeBSD/10.0-STABLE; KDE/4.12.2; amd64; ; ) In-Reply-To: <6D589C89-941E-4F75-8050-C2366E709557@orthanc.ca> References: <1424978.vEyl8RcM2T@desktop.reztek> <6D589C89-941E-4F75-8050-C2366E709557@orthanc.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-SA-Authenticated: Yes X-SA-Exim-Connect-IP: 77.87.241.103 X-SA-Exim-Mail-From: matthew@reztek.cz X-SA-Exim-Scanned: No (on mail.modirum.com); SAEximRunCond expanded to false X-Mailman-Approved-At: Fri, 28 Feb 2014 02:35:04 +0000 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 23:59:22 -0000 On Thursday 27 February 2014 14:55:55 Lyndon Nerenberg wrote: > On Feb 27, 2014, at 12:20 PM, Matthew Rezny wrote: > > If IPv4LL is in active use, the DHCP > > client should continue to periodically look for a DHCP server and obtain a > > lease without manual user intervention (which is unfortunately required on > > both OS X and Windows, leading to sub-optimal experience in cases of > > temporary unavailability of the DHCP server). > > That's not true for Mac OS. If you have an interface configured to use > DHCP, and the Mac is unable to renew the lease, it will automatically > configure a 169.254.x.y address on the interface. All the while it > continues its attempts to renew the DHCP lease and, once successful, > removes the 169.254.x.y address from the interface. > > --lyndon If they corrected that, it was after I abandoned the platform years ago. I remember repeatedly pushing the Renew Lease button in the Network section of System Settings in frustration, waiting to see the address change.