Re: ACS and Hostapd

[Yogesh Ashok Powar <yogeshp@marvell.com>]

On Thu, Dec 13, 2012 at 12:33:06PM -0800, Luis R. Rodriguez wrote:
> On Thu, Dec 13, 2012 at 10:54 AM, Yogesh Powar <yogeshp@marvell.com> wrote:
> > Hi Jouni/Luis,
> >
> > It seems that, we have some resources that can be utilized to test this
> > feature of ACS for hostapd.
> >
> > Before we begin on this work of Luis and optimize/enhance it further, would you
> > like to recommend some immediate changes from the last test results?
> 
> By my part:
> 
> The algorithm I wrote was pretty complex and although I did review it
> with some folks who liked it and it made sense the algorithm can be
> simplified by taking the input elements and using a multiplier for
> each one and letting the user configure the multiplier. In other words
> all the log stuff I did and linearizing it some way was not all that
> necessary except for mental masturbation.
> 
> Apart from that its just a matter of testing and proving it works.
Hi Luis,
   We tried your code of ACS from hostapd mailing list archieve, after
resolving some merge conflicts, on latest hostapd. Following are some
of our observations

a) The code can work for the drivers that dont support offchannel-tx.
   For such drivers, setting channel_time_tx to zero will make
   interference factor to depend only on busy time from passive
   listener's point of view.
b) HT 40 Mhz might have some issues with current ACS. When primary
   channel with least interference factor is selected secondary channel
   is set to offset from the primary instead of actual secondary
   channel.

Apart from the existing complex logic, explained here
http://wireless.kernel.org/en/users/Documentation/acs, can simple scan
based ACS algorithm feasible?

Lets say one just scans all the channel and gathers the beacons. Based
on the information based on collected beacons one can find out which
channel has least number of APs residing. One can even look into
detail IE informations in the beacons for detail study of wireless
environment.

This could help drivers that do not have access to parameters needed for
interference factor calculation.

Thanks
Yogesh