Search Linux Wireless

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

> First, I was wrong about receiving frames from other STA using same AP. It
> was my fault.

Ok, no worries, just seemed weird to me :)

> Below (see attachment) is a trace from ieee80211_rx_h_sta_process() 
> You can see the frames that will update the last_rx field.

So what's the problem with this trace? It means we update the last_rx
field whenever we receive a frame from the AP, no matter whether it's
for us or not. Is that wrong?

> In my code I have added a feature that monitors BEACONS from 'my' AP.
> When number of received beacons drops below 5 / 2 seconds, I assume out of
> range.
> I do not know if this is necessary but it gives faster roaming in the
> out-of-range scenario.

That is indeed a good feature and some hardware even has offload
capabilities for it, would be interested in seeing patches. Of course,
it can't be fixed to 5/2sec, it should be calculated based on the beacon
interval instead.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux