On Wed, 2010-12-01 at 12:09 -0800, Javier Cardona wrote: > 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). Makes sense. > 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. It looks like one can modify the mesh ID on the fly right now -- that I'm going to remove, the other things can stay for all I care :-) johannes -- 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
