> > Shouldn't wpa_supplicant know when the connection is ready? > > It has support for dormant mode, so the link can be held down > > by userspace until it is ready. > > The driver shouldn't need to figure out when the link is > > ready to go up. > > This is to do with the operation of the "Controlled Port" as specified > by 802.1x, which is handled by the driver. When the key exchanges are > complete and the link is secure, then data is allowed to flow. With > wext, the driver has to guess when this state is reached, based on > knowledge of how wpa_supplicant uses wext. I don't know too much about WPA, so, er... is it possible for a device to have a set of keys configured and still not be operational? Basing operational state on a sequence of set-key operations is obviously weird, but basing it on having a full set of keys might actually be right, IF and only IF those two statements are equivalent, so - are they? -David P.S.: anyone got some WPA doc/spec pointer for me? - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
