Date: Fri, 13 Nov 2009 12:20:56 +0000 From: Rui Paulo <rpaulo@freebsd.org> To: David Wolfskill <david@catwhisker.org> Cc: current@freebsd.org Subject: Re: No DHCP lease with iwi(4)/wlan(4); works with an(4) at r197399 Message-ID: <9A74A20E-67E9-4C32-BFDA-B0F6518BFD02@freebsd.org> In-Reply-To: <20091111154359.GB1351@albert.catwhisker.org> References: <20090923140936.GF1320@albert.catwhisker.org> <3a142e750909231508j1a5092f8nfae264f367ba410@mail.gmail.com> <20090925162403.GM1320@albert.catwhisker.org> <20091111154359.GB1351@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 Nov 2009, at 15:43, David Wolfskill wrote: > On Fri, Sep 25, 2009 at 09:24:03AM -0700, David Wolfskill wrote: >> ... >> But I did find one rather curious thing: I was able to get the >> iwi(4) to work OK (while running head) with one of my access points; >> it's the other that seems to have an issue with iwi(4) under head. >> >> I have 2 different access points at home: >> * An original Apple Airport >> * A Linksys WAP-11. >> (Each is, within the bounds of their rather different natures, >> configured the same except for channel: One is on channel 1; the other >> is on channel 6. Neither is a DHCP server: each merely passes the DHCP >> traffic.) >> >> Under stable/6 and stable/7, each works fine with iwi(4). >> >> Under head (presently at r197479), the Linksys WAP-11 works (associates >> & dhclient(8) negotiates a DHCP lease using iwi(4)/wlan(4)). >> >> Under head, the Apple Airport associates, but dhclient(8) cannot see a >> DHCP offer via iwi(4)/wlan(4). >> ... > > This morning, after upgrading head to r199179, I now cannot get a DHCP > lease using teh Linksys WAP-11. > > Prior to the upgrade, I was last running head r199134, which was able to > get a DHCP lease from teh Linksys WAP-11. > > uname strings: > > FreeBSD g1-106.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #1172 r199134: Tue Nov 10 10:47:11 PST 2009 root@d254.dwolf.juniper.net.:/common/S4/obj/usr/src/sys/CANARY i386 > > FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #1173 r199179: Wed Nov 11 06:50:22 PST 2009 root@g1-106.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 > > [The latter has no current hostname, since dhclient-exit-hooks > didn't get an IP address.] > > I verified that the iwi0/wlan0 NIC did associate first. I recall > the UPDATING entry from a couple of days ago: > > 20091109: > The layout of the structure ieee80211req_scan_result has changed. > Applications that require wireless scan results (e.g. ifconfig(8)) > from net80211 need to be recompiled. > > and admit that I did the upgrade with -DNOCLEAN. But it worked OK > for the upgrade yesterday -- and I don't expect that I actually use > scan results in any case. (Recall that association still works.) Well, wpa_supplicant should've been rebuilt even with NOCLEAN (I used NOCLEAN, IIRC). Anyway, you wouldn't be able to associate if wpa_supplicant wasn't updated. BTW, wpa_supplicant uses scan results too. P.S.: if wpa_supplicant is old, it will display empty SSIDs if you run it with the debugging mode enabled. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9A74A20E-67E9-4C32-BFDA-B0F6518BFD02>