Johannes, On Tue, Jun 16, 2009 at 11:56 AM, Johannes Berg<johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2009-06-16 at 11:55 -0700, Andrey Yurovsky wrote: > >> > Ok, fair enough. There are a lot of quirks in the mesh API, one of these >> > days I'd like to make it less like wext and have you join/leave like the >> > ibss commands instead of setting each parameter one by one... >> >> Thanks. We'd like to hear about any quirks/issues as we have some >> bandwidth to work on mesh again and we would like to address the >> configuration/API issues. > > Well mostly it's the thing with configuration parameters affecting the > interface "on the fly". But I'm not familiar enough with all of the > parameters to actually know which ones _can_ change on the fly, and > which ones change and thereby make you part of a different mesh. 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? 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
