|
Description
|
Current dladm scenario is to check whether or not the link is up/down before passing "dladm connect-wifi" command. If it's connected already, dladm will notify user to disconnect-wifi firstly.
For iwi driver, because hardware will connect to none-encryption AP after plumb automaticlly, user need to disconnect-wifi manually.
To expand on the above: it seems that we cannot figure out how to
turn off the iwi hardware's auto-connect feature (as an aside, that
feature may even have legal implications, since some countries may
have laws that prevent connecting to random networks). As a result,
after boot, "dladm connect-wifi" may unexpectedly fail because the
link is already connected to a network.
The simplest "fix" would be to have connect-wifi disconnect first.
However, that would be questionable behavior in the case where the
user *has* explicitly connected to a network via connect-wifi. Thus,
we need some way to tell the two cases apart. One approach would be
to track explicit connection requests in the kernel, and have dladm
check whether the current connection was made explicitly. However,
it would be much much (much!) better if someone could just find a way
to turn off the auto-connect feature entirely.
|