Might be related to things like this:
http://patchwork.kernel.org/patch/38530/There seem to be a few post about "No probe response from AP" timeouts since 2.6.30-rc3. Apparently fixed at 2.6.31.2. But they may be driver-specific (and neither is RTL8187).
My scripts to re-associate (which are at least a workaround) are these:
5-min crontab job (
/etc/cron.d/WifiCheck)
# Check the Wifi status
#
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/local/bin
01-58/5 * * * * root /local/bin/wireless-check
The actual script (
/local/bin/wireless-check):
#!/bin/sh
#
if=wlan0
if iwconfig $if | grep -q Not-Associated; then
: Not associated, so get it to retry
else
exit # All OK
fi
iwconfig $if | Mail -s 'Wifi lost association on plug' {my-mail-address}
# Force re-association
iwconfig $if ap auto
(I've got mail setup...)
The result, earlier today, showed this in in dmesg (as well as mailing me the Not-Associated details):
wlan0: no probe response from AP 00:02:cf:xx:xx:xx - disassociating
wlan0: direct probe to AP 00:02:cf:xx:xx:xx try 1
wlan0: direct probe to AP 00:02:cf:xx:xx:xx try 2
wlan0: direct probe to AP 00:02:cf:xx:xx:xx try 3
wlan0: direct probe to AP 00:02:cf:xx:xx:xx timed out
wlan0: direct probe to AP 00:02:cf:xx:xx:xx try 1
wlan0: direct probe to AP 00:02:cf:xx:xx:xx try 2
wlan0 direct probe responded
wlan0: authenticate with AP 00:02:cf:xx:xx:xx
wlan0: authenticated
wlan0: associate with AP 00:02:cf:xx:xx:xx
wlan0: RX ReassocResp from 00:02:cf:xx:xx:xx (capab=0x431 status=0 aid=4)
wlan0: associated
Show Posts
