Johannes, On Wed, Dec 1, 2010 at 11:35 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Wed, 2010-12-01 at 19:54 +0100, Johannes Berg wrote: > >> If we had a 'start mesh' command, like 'join IBSS', then it'd be natural >> to have just more attributes in it. Maybe it's time to start thinking >> about that again, although backward compatibility could be interesting. > > Ok I started looking at this ... > > I have a feeling I asked this before, but can't remember -- is it > necessary to be able to change the mesh config on the fly, while the > mesh is active? It is convenient to be able to change things like the ttl or the auto peering without having to bring down the interface. People might also want to tune from userspace the different mesh timeouts in response to changes in operating conditions (e.g. mesh density). But right now the only parameter that needs the mesh to be active is plink_action: one can only block or manually initiate peering after a beacon has been received from a suitable neighbor. Javier -- Javier Cardona cozybit Inc. http://www.cozybit.com -- 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
