From owner-freebsd-current@FreeBSD.ORG Wed Jun 22 15:03:55 2005 Return-Path: X-Original-To: freebsd-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 3AD6116A41C for ; Wed, 22 Jun 2005 15:03:55 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F23A943D1F for ; Wed, 22 Jun 2005 15:03:52 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j5MF3paK071440 for ; Wed, 22 Jun 2005 10:03:51 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42B97DD3.3040109@centtech.com> Date: Wed, 22 Jun 2005 10:03:47 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: New dhclient - supposed to 'down'/'delete'? 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: Wed, 22 Jun 2005 15:03:55 -0000 Is the new dhclient code supposed to down and delete an interface when it has been disconnected from the media? For instance: I boot up, use my wireless for a while (which dhclient handles), then disable my wireless card, and plug in the cable to my ethernet jack (bge0). I see bge0 come up, and get an IP. Everything looks good. Now, I unplug the cable from bge0, and enable my wireless again. Wireless gets an IP, but bge0 is still 'up' and has an IP configured, along with the routes that go with it. I have to manually do an 'ifconfig bge0 down ; ifconfig bge0 delete', then restart dhclient on ath0 (wireless) or disable/enable ath0 to force it to try again.. Is this the expected behaviour? Do I need to tweak some settings? Here's what my rc.conf looks like (relevant parts): ifconfig_bge0="DHCP" ifconfig_ath0="DHCP ssid MYSSIDHERE wep wepkey 0xWEPKEYHERE weptxkey 1" devd_enable="YES" Running -current from about a week ago. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------