On Mon, 2007-11-12 at 11:47 -0800, Luis Carlos Cobo wrote: > > So if I bring up a mesh interface and don't use SET_MESH_CFG, it won't > > operate at all? > > Yes it would, it would use the wild card, zero-length mesh ID. Oh ok, need to give it more thought then. > > I think I'd prefer if the MESH_ID attribute would be given as part of > > SET_INTERFACE/NEW_INTERFACE instead of a new command. I'm attempting to > > keep nl80211 as object oriented as possible and this single command > > doesn't really fit the picture. > > Will that be the way to specify the SSID for the STA interfaces? No, see below. > If so, > I agree it would be better to use that command instead of an additional > mesh specific command. As by now it's just used to set the interface > type I was not sure it was appropriate to add the mesh configuration > there. The way I've been trying to do things is work in an object oriented fashion. If you look at the beacon and sta commands I did, basically you can add/del a sta or beacon. With association, the way I would want it to work is that we have a virtual "association" object (of which you can have zero or one). Deleting this association object would cause the MLME to disassociate. I don't see any object-oriented way to do the mesh stuff because as you said one *always* has a mesh ID. Is this really what one wants though? Is the broadcast mesh ID actually useful? I think I need to understand more about this to be able to give a good recommendation. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
