[PATCH] driver_wext.c: Make sure that interface is UP

Jouni Malinen j
Tue Dec 8 05:34:05 PST 2009

On Mon, Dec 07, 2009 at 02:25:15PM -0800, Dmitry Shmidt wrote:

> 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.

If a network manager turned off the interface, why would it not turn it
on when the connection is supposed to be used? I would assume there was
a reason for setting the interface down in this case and it does not
sound like a good idea for wpa_supplicant to just turn it back on.

> My point is that relying on network manager to keep interface in
> proper state may cause wpa_supplicant to
> fail to complete association.

I would be fine with making wpa_supplicant not try to associate if the
interface is set down while wpa_supplicant is running (and then
re-enable wpa_supplicant when the interface is set up again).

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list