On Mon, 2011-03-07 at 18:11 -0800, Javier Cardona wrote: > Notify userspace when a beacon/presp is received from a suitable mesh > peer candidate for whom no sta information exists. Userspace can then > decide to create a sta info for the candidate. If userspace is not > ready to authenticate the peer right away, it can create the sta info > with the authenticated flag unset and set it later. I'm a little worried about this creating lots of bogus stations if somebody is attacking the mesh. Will that be relevant? Would it be better to just pass up any beacon that matches the mesh ID, trading CPU resources for memory? Also, this goes back to the "authenticate station" rather than full station management in userspace, right? 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
