On Thu, 2007-03-08 at 14:36 -0500, Dan Williams wrote: > So when wpa_supplicant or whatever has to do rekeying, or if I want to > change some parameter but not completely re-associate, how does that > work? I suppose it'll be a different command. But SetKeys() is already an MLME primitive in the specs :) > > What I'd like to see instead is that you give the MLME (whether it's in > > the kernel or in userspace[1]) all the parameters it needs to do one > > action when telling it to do that action. > > I'd basically expected that this was the model we'd be using anyway. A > user tool wouldn't have to: > > set ssid > set key > set authmode > associate > > but instead bundle all those up into one message to netlink with the > "associate" command or something. Right. However, as far as I understood some people at the wireless summit, they'd prefer having one command that bundles all the settings and then another one that applies them. Maybe it's just a misunderstanding on my part and this whole thread is pointless? > I'd much rather conceptually have the following (in python-esque), which > is what I thought it would be more like... > > err = associate(ssid="foo", key=0x435223, auth="shared") > <rekey> > err = set(key=0x235326563) Yup, makes sense to me. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
