Johannes, On Tue, Jun 16, 2009 at 12:37 PM, Johannes Berg<johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2009-06-16 at 12:32 -0700, Javier Cardona wrote: > >> There are some mesh parameters that you would probably want to be >> uniform across the mesh network (timeouts, number of retries, etc). >> But the only mesh parameter that would result in a different mesh >> network is the mesh_id, and that's only settable when the mesh >> interface is created. >> >> Do you have a specific configuration parameter in mind? > > 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). Cheers, Javier -- 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
