[PATCH] driver_wext.c: Make sure that interface is UP
dimitrysh at google.com
Mon Dec 7 17:25:15 EST 2009
You are right in general. But there are several scenarios where it is
just easier to control interface
from the wpa_supplicant driver layer itself.
For example, you've associated, connected and got IP by dhcp client.
You were disassociated, lost connection and network manager turned off
interface to prevent trying to access it.
Then you are trying to reassociate and key exchange will fail.
My point is that relying on network manager to keep interface in
proper state may cause wpa_supplicant to
fail to complete association.
On Mon, Dec 7, 2009 at 1:59 PM, Jouni Malinen <j at w1.fi> wrote:
> On Mon, Dec 07, 2009 at 01:04:44PM -0800, Dmitry Shmidt wrote:
>> After association in case of key handshake we need to send packets and
>> we want xmit queue to be ON.
>> And sometimes it is possible that interface was turned OFF.
> What would set the interface down? And if it is down and the driver has
> disabled the radio, how would we even get here (e.g., scan results may
> not be available)? Since wpa_supplicant sets the interface UP in the
> start, this patch looks like a workaround for something that should
> probably be fixed at the location of the real problems (i.e., make it
> not set the interface down).
> Jouni Malinen PGP id EFC895FA
> HostAP mailing list
> HostAP at lists.shmoo.com
More information about the HostAP