From owner-freebsd-current@FreeBSD.ORG  Thu Feb  7 16:34:50 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 5BC1816A420;
	Thu,  7 Feb 2008 16:34:50 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-current@FreeBSD.org
Date: Thu, 7 Feb 2008 11:34:41 -0500
User-Agent: KMail/1.6.2
References: <20080206234520.787F016A469@hub.freebsd.org>
	<47AA9556.2020709@fusiongol.com>
	<3a142e750802070129m70122720p30a98368491356d9@mail.gmail.com>
In-Reply-To: <3a142e750802070129m70122720p30a98368491356d9@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200802071134.43696.jkim@FreeBSD.org>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Nathan Butcher <n-butcher@fusiongol.com>, Brooks Davis <brooks@freebsd.org>
Subject: Re: dhclient problem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2008 16:34:50 -0000

On Thursday 07 February 2008 04:29 am, Paul B. Mahol wrote:
> Sorry for noise, but there is actually no problem at all.
>
> Probably net80211 code is improved so dhclient will not send
> useless packet, instead it reports that there is no link.

Yes.  See this:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/dhclient/dispatch.c.diff?r1=1.2;r2=1.3

Previously dhclient(8) was assuming wireless controller is already 
associated with a correct AP and safe to broadcast packets.

Jung-uk Kim

> On Feb 7, 2008 6:21 AM, Nathan Butcher <n-butcher@fusiongol.com> 
wrote:
> > >> All you have to do is issue "ifconfig rum0 up" to get your
> > >> device UP, and then try dhclient. It should work.
> > >
> > > The standard scripts should be running "ifconfig xxx up" on any
> > > interface that has an ifconfig_xxx variable in rc.conf.  Has
> > > that been broken?
> > >
> > > -- Brooks
> >
> > My USB wireless dongle doesn't have any rc.conf config line, but
> > it used to be automatically UP without the config line at boot
> > time at one point.
> >
> > I remember doing an csup update on my box at one point and
> > discovering this change.