RE: Roaming issues: Monitoring of a usable link to the AP.

["Lars Ericsson" <Lars_Ericsson@telia.com>]

Hi, 

I have split my issues ito individual disussions:

> Monitoring of a usable link to the AP.
> ======================================
> The ieee80211_rx_h_sta_process() and  ieee80211_associated() are 
> involved in monitors for dead AP connection. A last_rx value is set to 
> indicate a working connection.
> 
> The porblem is the following lines.
> 	if (!is_multicast_ether_addr(hdr->addr1) ||
> 	    rx->sdata->vif.type == IEEE80211_IF_TYPE_STA) {
> 
> Any package that arrives to an STA will update the last_rx value and 
> prohibit a link lost action.
> 
> I have noticed in my system that this function receives the following 
> type of frames:
> 1) Broad cast frames from my BSS (beacons).
> 2) Data frames addressed to me ;)
> 3) Data frames from other STA addressed to other MAC addresses but 
> using the same BSS.
> 
> It is the case 3 that creates the problem. Another STA, closer to my 
> BSS will update my last_rx value even I do not receive the BSS.
>
> I'm pretty sure case 3 can't create a problem there since rx->sta wouldn't
be set to the AP. Can you please print out "rx->sta->addr"
> after the !sta check in ieee80211_rx_h_sta_process and send me the log
indicating that we can actually get into there with sta != our own AP?
> If we can that's a bug elsewhere but I doubt it.
 
Ok. I will come back with a trace.

/Lars