Tell me more ×
Raspberry Pi Stack Exchange is a question and answer site for users and developers of hardware and software for Raspberry Pi. It's 100% free, no registration required.

One of my Raspberry Pis acts as a general network workhorse, running a Squid proxy server, ntpd, hosting samba shares and bridging the network connection to extend the range of the wireless.

But the wireless dies on average once a day (at various times, though last week it died at the same time twice). I know this may be related to power supply issues, but the syslog always shows the same message as the card dies -

Jan 17 22:36:27 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: authentication OK (open system)
Jan 17 22:36:27 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-AUTHENTICATE.indication(7c:61:93:ff:98:0c, OPEN_SYSTEM)
Jan 17 22:36:27 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-DELETEKEYS.request(7c:61:93:ff:98:0c)
Jan 17 22:36:27 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: authenticated
Jan 17 22:37:28 raspberrypi NetworkManager[2650]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The logs typically indicate that the wired end of the bridge does not fall over, but I cannot do anything more than ping the interface.

This looks like a driver issue to me - could someone enlighten me as to what is going on and is there any way to fix it?

share|improve this question

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.