From owner-freebsd-current@FreeBSD.ORG Mon Aug 1 15:19:06 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE60516A41F for ; Mon, 1 Aug 2005 15:19:06 +0000 (GMT) (envelope-from snow+freebsd-current@teardrop.org) Received: from imladris.teardrop.org (imladris.teardrop.org [66.92.66.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6125043D45 for ; Mon, 1 Aug 2005 15:19:06 +0000 (GMT) (envelope-from snow+freebsd-current@teardrop.org) Received: by imladris.teardrop.org (Postfix, from userid 100) id 65B8EBE76B; Mon, 1 Aug 2005 11:21:56 -0400 (EDT) Date: Mon, 1 Aug 2005 11:21:56 -0400 From: James Snow To: Sam Leffler Message-ID: <20050801152156.GB90588@teardrop.org> References: <42EAD325.60707@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42EAD325.60707@errno.com> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: dhclient and wpa_supplicant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 01 Aug 2005 15:19:06 -0000 On Fri, Jul 29, 2005 at 06:08:53PM -0700, Sam Leffler wrote: > > So the question is what are the outstanding issues with dhclient and > wpa_supplicant? I'm mostly concerned with wireless devices but feel > free to talk about wired interfaces too. My biggest outstanding complaint is when booting with a wired network and no present wireless network, if dhclient has any recorded leases for the wireless interface, it will attempt to use the most recent one and blows away the default gateway for the wired network. I then have to manually 'netif stop ath0' and 'netif restart em0.' Not sure what the best solution is. Perhaps dhclient needs to be aware of the associated/unassociated status of a wireless interface in the same way that it's aware of the link status of a wired interface? > If something doesn't work right please try to give steps to reproduce > the problem. In /etc/rc.conf: ifconfig_WIRED="DHCP" ifconfig_WIRELESS="WPA DHCP" Boot once in the presence of a wireless network. Now reboot with a wired network, but no present wireless network. dhclient will obtain a lease for the wired interface, and when dhclient launches on the wireless interface it will time out, use the recorded lease, and clobber the wired default gateway. I don't know what happens when booting with both a wired and wireless network; I've never tried. In the default case I think the wired network should be preferred, but could there be a knob to change this? (Am I failing to see just such a not in dhclient.conf somewhere?) -Snow