On Tue, 2009-06-16 at 12:51 -0700, Javier Cardona wrote: > > No, I don't have any in mind. I wasn't aware that only the mesh_id > > defines the mesh, I was under the impression that more needs to match, > > as codified in mesh_matches_local(). > > In addition to the mesh id, a successful peering requires that peer > candidates use the same methods for path selection, congestion > control, synchronization and authentication. None of these are > configurable via iw (essentially because only one single option for > each method is implemented). Ahh! Ok, goes to show how little I understand the mesh code. IIRC somebody had a patch to make those configurable though. I guess as long as those need to be configured while creating the interface the API is actually very good and much better than I thought :) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
