Date: Thu, 7 Feb 2008 11:34:41 -0500 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: Nathan Butcher <n-butcher@fusiongol.com>, Brooks Davis <brooks@freebsd.org> Subject: Re: dhclient problem Message-ID: <200802071134.43696.jkim@FreeBSD.org> In-Reply-To: <3a142e750802070129m70122720p30a98368491356d9@mail.gmail.com> References: <20080206234520.787F016A469@hub.freebsd.org> <47AA9556.2020709@fusiongol.com> <3a142e750802070129m70122720p30a98368491356d9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802071134.43696.jkim>