[Bug 414560] Re: ath9k disassociates/reassociates a lot

findepi piotr.findeisen at gmail.com
Sun Nov 1 08:34:18 UTC 2009


On Sun, Nov 1, 2009 at 07:58, Howard Chu <hyc at symas.com> wrote:

> @Kunal,
> Yes, scanning is required to find a network to connect to, when you
> initially have no connection at all. My point is that once you're
> successfully associated to a network, automatic/background scanning should
> stop. You don't need scanning to happen any more unless the environment
> changes - either the AP is deactivated, or you're using a mobile computer
> and you move to a different location. In most cases, people using wifi are
> stationary for the majority of the time they're connected.
>

Howard, you're right: in "most cases" but not always.
Often in one place there is more than one WiFI network you can join
(example: university campus). You may be forced to join your
less-preferred-one in absence of the more-preferred, but you still you will
want background scans to know when the more-preferred becomes accessible.

Of course, once you're connected scans are much, much less important. But if
NM would totally stop scanning, I would consider it a bug :)

best regards,
Piotr

-- 
ath9k disassociates/reassociates a lot
https://bugs.launchpad.net/bugs/414560
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list