Re: No ProbeResp - assume out of range

[Christoph Hellwig <hch@infradead.org>]

On Sun, Nov 02, 2008 at 01:05:56PM -0800, Luis R. Rodriguez wrote:
> I'm curious if others are getting this frequently as I am:
> 
> No ProbeResp from current AP 00:DE:AD:BE:EE:FF - assume out of range
> 
> I get this with ath5k and ath9k, can be triggered easily in ath5k by
> doing a lot of consecutive:
> 
> iwlist wlan0 scan
> 
> I have to check if I can trigger this with ath9k by scanning too. We
> were seeing this with ath9k but were thinking it was ath9k related as
> it can be triggered on it after doing a large TX. Wondering if this is
> more of a generic and mac80211 issue.

I'm seeing this all the time with ath9k.  For now I'm running with the
following local hack:

Index: linux-2.6/net/mac80211/mlme.c
===================================================================
--- linux-2.6.orig/net/mac80211/mlme.c	2008-11-04 18:10:41.000000000 +0100
+++ linux-2.6/net/mac80211/mlme.c	2008-11-04 18:10:56.000000000 +0100
@@ -972,7 +972,7 @@ static void ieee80211_associated(struct 
 				       "current AP %s - assume out of "
 				       "range\n",
 				       sdata->dev->name, print_mac(mac, ifsta->bssid));
-				disassoc = 1;
+//				disassoc = 1;
 			} else
 				ieee80211_send_probe_req(sdata, ifsta->bssid,
 							 ifsta->ssid,

which makes the problem of an actual disassociation after this message
go away which made wireless completely unuseable with -rc3 for.  Given
that the message never appears a second time just increasing the time
it appears that just increasing IEEE80211_MONITORING_INTERVAL should
fix the problem, too.