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

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@:/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?

Peace,
david
--
David H. Wolfskill david@xxxxxxxxxxxxxx
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

Attachment: pgpjZIeYQVIlE.pgp
Description: PGP signature

Relevant Pages

  • Re: SBS 1002 Premium R2 Mangling Port Issues
    ... If you have a decent hardware firewall/router now, ISA ... NIC or 2 NICs) did you finally end up with? ... the WAN NIC so there's only one NIC in the SBS (and then re-run CEICW ... port forward 8016 to the "external" SBS NIC IP ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 1002 Premium R2 Mangling Port Issues
    ... The ADT remote camera view is working ... configure SBS), or you can configure SBS to use both NICs and then re-run ... If choose two NICS, the WAN NIC and the LAN side of the router must ... + Now forward the port 8016 traffic from the external SBS NIC to the LAN ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS, Group Policy errors when enabling second NIC
    ... You're running Sharepoint Portal Server inside your SBS domain and exposing it to the "world"? ... You won't find anyone here supporting the opening of port 80 being passed inside the LAN...huge security hole ... to try putting Sharepoint on port 80 locally, using the second NICs IP ... Unless this one of those unique load balancing nics that has software so ...
    (microsoft.public.windows.server.sbs)
  • Re: Desperate to email; Can you HELP?
    ... so are their two dual port NICs? ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: CEICW failure
    ... The port forward thing I had tried just out of desperation. ... The router is 192.168.1.1 subnet 255.255.255.0 ... > port 80 from the Internet to your Server. ... >> SBS box has the 2 NICs. ...
    (microsoft.public.windows.server.sbs)
Loading