dhclint wlan0 fails since 2.6.27.19-170.2.35.fc10.x86_64

[fam]

Since 2.6.27.19-170.2.35.fc10.x86_64, dhclient wlan0 doesn't seem to work any more.
However, bizarrely, dhclient eth0 does (to the same D-link wireless router).

The AP shows connected - tail /var/log/messages

wlan0: associate with AP 00:0f:3d:65:40:0c
wlan0: RX ReassocResp from 00:0f:3d:65:40:0c (capab=0x431 status=0 aid=2)
wlan0: associated

# dhclient -d -v wlan0
Internet Systems Consortium DHCP Client 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:90:96:7b:45:f1
Sending on LPF/wlan0/00:90:96:7b:45:f1
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

WINXP connects just fine. This (B43) has worked nicely ever since FC10 came out, and I was able to use the WiFi at all kinds of places on a recent trip. Other than a couple of yum updates, I don't think anything else has changed since. Other devices on the wlan are getting their DHCP requests satisfied correctly.

Is anyone else having this problem since about a week ago? Perhaps there's something really obvious I'm missing. I can manually assign an IP address to wlan0, manually edit the routing tables and edit /etc/resolv.conf, and then Wifi seems to work OK, so it doesn't seem to be b43 itself unless it is dropping DHCPOFFERS. If this isn't a regression, does anyone have any tips about how to debug this?

TIA!

[ozjd]

A number of people have had various problems with a recent NetworkManager update. It was fixed for most people by reverting to the previous version. See post 5 in http://forums.fedoraforum.org/showthread.php?t=216416 for details on how to do that, it is a different problem in that thread but could be the same cause.

[fam]

Thanks for the quick reply. I'm not using Network Manager so I don't really have a way to revert. I never could get NM to work, and doing it from the command line is so much more convenient (one reason not to use M$Windows). Since B43, wpa-supplicant, and dhclient all seem to be working, sort-of, I have no idea what to roll back. I thought I'd ask here before posting a bug report...

[Nushio]

Hey there, I have the same issue on an Acer Aspire 4720z with Broadcom Wireless 4312.

Once I hit that kernel, nothing worked since then.

I tried reverting to a previous kernel, network-manager, broadcom-wl, ndiswrapper, "native broadcom" drivers. No luck so far.

I don't know where to start the debugging... Any help would be appreciated, its been over 2 weeks since I've been trying!

Edit:
My issue is that the card won't find any wireless networks to connect.