No DHCP lease with iwi(4)/wlan(4); works with an(4) at r197399

Paul B Mahol onemda at
Wed Nov 11 17:31:54 UTC 2009

On 11/11/09, David Wolfskill <david at> 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 9.0-CURRENT FreeBSD 9.0-CURRENT #1172 r199134:
> Tue Nov 10 10:47:11 PST 2009
> root at  i386
> FreeBSD  9.0-CURRENT FreeBSD 9.0-CURRENT #1173 r199179: Wed Nov 11 06:50:22
> PST 2009     root at
> 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.)

How scan results look now? Try sysctl debug options for your driver (debug.iwi).

More information about the freebsd-current mailing list