ACS seems not to select the best channel in 2.4GHz.

[Jeremy Ward]

Quick question: does this weighted logic need to be applied to 5GHz ACS as
well, or is there a different methodology at play here due to DFS
requirements in certain portions of the band, regulatory domain dependent?

Thanks for your time, as always.

Jeremy D. Ward, CWNE
(954) 661-4965
On Feb 6, 2015 2:26 PM, "Jouni Malinen" <j at w1.fi> wrote:

> On Thu, Feb 05, 2015 at 05:45:10PM -0800, Fumikazu Yobimoto wrote:
> > I understood that's reasonable, agreed your idea.
> > I tried to test ACS using your latest patch, and I was able to see a good
> > result
> > as I hoped. In addition, I tested other value witch Eduard mentioned.
> >
> > #define ACS_ADJ_WEIGHT 0.85
> > #define ACS_NEXT_ADJ_WEIGHT 0.55
> >
> > The experiment result shows it works fine. I attach on the bottom.
>
> Thanks!
>
> > -An error about patch-
> > adj_chan->interference_factor;
> > +                               if (adj_chan &&
> acs_usable_chan(adj_chan)) {
> > +                                       factor += ACS_NEXT_ADJ_WEIGHT +
> >             <= This line.
>
> > it should be
> >
> > +                                       factor += ACS_NEXT_ADJ_WEIGHT *
> > +
> >  adj_chan->interference_factor;
>
> Indeed. Fixed in the current version in the pending branch.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at lists.shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20150208/ef6845d4/attachment.htm>