On 3 December 2013 19:03, Jim Thompson <j...@netgate.com> wrote:
> On Dec 3, 2013, at 7:56 PM, Adrian Chadd <adr...@freebsd.org> wrote:
>> Now, ideally it'd actually check the channel for interference and
>> channel busy status, and use _that_ metric.
> Ideally, it would attempt to get co-channel with other APs on the same
> Especially in 2.4GHz (or any of the 5GHz bands).
> Because you would *much* rather share the air (via collision avoidance) than
> raise the noise floor for someone (everyone) else.
> And, given that everyone has a DC receiver these days, there are NO
> “non-overlapping channels”.
Right. Hence, interference and channel busy. The Atheros NIC channel
busy tells you % busy with signal in the air _AND_ % busy receiving
frames. So you can get an idea of what's actually going on.
The basics are in the Atheros HAL. We just need a nice way to wrap it
up and hand off channel survey results to the net80211 layer so it can
make these decisions.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"