I have set up an access point with Ubuntu 9.10 and a Broadcom BCM4318 PCI card (manufacturer is Buffalo). After an undetermined period of time, the card stops beaconing and even previously connected clients are unable to ping the AP. After the driver hangs, trying to restart hostapd fails with a "Failed to create mon.wlan0". The following commands: #rmmod b43 #modprobe b43 #/etc/init.d/hostapd restart will restart hostapd, and the AP will begin beaconing again. Clients can associate with it, but are unable to ping the AP. Further examination reveals that wlan0 on the AP has not been assigned an IP address. (My AP does not have a DHCP daemon running as of yet; I've been manually configuring the IP address of my clients.) Using ifconfig to assign the IP address appears to work, but clients are still unable to ping the AP. dmesg reveals no message from the b43 or other drivers about the hang; however, upon restarting hostapd the driver appears to create a new "phy". [71500.473241] b43-phy1: Broadcom 4318 WLAN found (core revision 9) [71500.540847] phy1: Selected rate control algorithm 'minstrel' [71500.542002] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ] [71543.312030] b43 ssb0:0: firmware: requesting b43/ucode5.fw [71543.410639] b43 ssb0:0: firmware: requesting b43/pcm5.fw [71543.430040] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw [71543.440062] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw [71543.564029] b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10) [71543.604432] Registered led device: b43-phy1::tx [71543.604459] Registered led device: b43-phy1::rx [71543.604485] Registered led device: b43-phy1::radio [71554.360009] wlan0: no IPv6 routers present Further back in the log, it can be seen where b43-phy0 was created, but there is no record of the driver crashing or any other errors. daemon.log does have several entries like this: Jan 17 15:48:24 hostname avahi-daemon[759]: Invalid query packet. Jan 17 15:49:33 hostname avahi-daemon[759]: last message repeated 2 times Rebooting fixes the problem completely, but only temporarily. Anyone seen this before, or have a suggested fix? Thanks, Eric Volker -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
