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

On 9/23/09, David Wolfskill <david_at_catwhisker.org> wrote:
> I normally use wireless NICs on my laptop, especially at home,  I
> swapped the miniPCI wi(4) for an iwi(4) a few weeks ago, and had it
> working in stable/6, stable/7, and head until a few days ago, when it
> seemed that the NIC was associating OK, but dhclient(8) reports:
>
> dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0
> DHCPREQUEST on wlan0 to 255.255.255.255 port 67
> DHCPREQUEST on wlan0 to 255.255.255.255 port 67
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
> ^C
>
> This morning, I had the time to try plugging in a wireless PCcard (an0)
> NIC; after doing that, I see:
>
> dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0
> DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 3
> DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 7
> DHCPOFFER from 172.17.0.1
> DHCPREQUEST on an0 to 255.255.255.255 port 67
> DHCPACK from 172.17.0.1
> bound to 172.17.1.37 -- renewal in 302400 seconds.
>
> which is a bit closer to the desired effect.
>
> I realize that an(4) doesn't use wlan(4), so this could indicate a
> problem with either iwi(4) or wlan(4) -- but it seems to show that
> dhclient(8) itself is working, as is the basic infrastructure (my
> DHCP server; the access point; the ipfw(4) rules I have in place
> before & after DHCP activity).
>
> As I type, I'm running:
>
> FreeBSD g1-37.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #1123 r197399:
> Tue Sep 22 06:16:11 PDT 2009     root_at_:/common/S4/obj/usr/src/sys/CANARY
> i386
>
> and am in the process of building head at r197427.
>
> Is there something I might do to help diagnose what's wrong here?

wlandebug(8)

and also enable iwi debug sysctl.

(Try to enable only few of them at same time, otherwise anabling
everything will cause huge chaos on console)

-- 
Paul