On Fri, 2011-03-04 at 11:01 -0800, Javier Cardona wrote: > On Fri, Mar 4, 2011 at 3:36 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > On Thu, 2011-03-03 at 19:11 -0800, Thomas Pedersen wrote: > >> From: Javier Cardona <javier@xxxxxxxxxxx> > > > > [snip (maybe more changelog would be nice)] > > > > So .. a more "traditional" approach, like we do in AP, would be to let > > userspace manage the lifetime of STA entries in this case. In managed > > mode, we don't, but there mac80211 currently handles the authentication. > > > > I think you should explore doing mesh more like the AP case. OTOH, I > > don't know how the managed case with SAE would work. > > I see. Instead of setting the AUTH flag, just create the station. We > would like to do this only for secure meshes, and continue letting the > kernel manage mesh peers for "open" meshes without the need of > userspace intervention. Sure. I might argue that even in the "open" mesh case sometimes userspace would like to manage it, so I wouldn't make it depend on a "secure mesh" flag but rather on a "userspace manages peers" flag, but from a programming POV those would be the same, just a bit differently semantically. OTOH, that might not work when the mesh isn't secure since then there's no clear point like the auth handshake when the station needs to be added? Not quite sure here. johannes -- 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
