On Mon, 2008-02-04 at 11:34 -0800, Luis Carlos Cobo wrote: > This file implements mesh discovery and peer link establishment support using > the mesh peer link table provided in mesh_plinktbl.c. > > Secure peer links have not been implemented yet. How would you design implementing support secure peer links? It seems that to do that much of the mesh bookkeeping would need to be done by wpa_supplicant instead of the kernel. In fact, maybe it should always do it and much of this code be migrated into wpa_supplicant's userspace MLME? Peer link establishment, mesh path updating etc. could all be done in wpa_supplicant's userspace MLME, no? If we add all this to the kernel now, would we have to reimplement it in the userspace MLME to support secure peer links? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
