> -----Original Message----- > From: Michael Wu [mailto:flamingice@xxxxxxxxxxxx] > Sent: 12 June 2007 17:46 > To: Mark Powell > Cc: David Lamparter; Johannes Berg; David Lamparter; Dan > Williams; linux-wireless > Subject: Re: [RFC] {cfg,nl}80211 API > > On Tuesday 12 June 2007 06:58, Mark Powell wrote: > > Very interesting. It raised a question in my mind... > > When associating to a WPA network, at what point should the driver > > open the controlled port? > > With wext/wpa_supplicant, the driver relies on knowing that the > > supplicant sets the pairwise key first and group key second and can > > open the controlled port after the second key. > > > > Can we tie down the correct behaviour more tightly in > cfg80211/nl80211? > > > 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. Mark To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview - 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
