On Tue, Dec 06, 2011 at 04:01:34PM +0100, Simon Wunderlich wrote:
Hey there,
On Mon, Dec 05, 2011 at 03:25:53PM +0100, Andrew Lunn wrote:
Here comes the chicken & egg problem: We can't have bat0 and its routing algorithm selection before we did not add at least one hard-interface.
an alternative we may consider:
We could just write the name of the algorithm in a debugfs file called "routing_algorithm". It is filled with batmanIV as the default algorithm to start with, and whatever is written there is used for the next soft interface to be created.
sounds good IMHO! I think this would be a really nice solution.
This would be backward compatible and changes are only made upon creation of a soft interface. It would also allow different soft interfaces using different routing algorithms (if someone really needs it). Putting it into debugfs may be not the worst idea, as changing routing algorithms is (currently) only done for debugging purposes anyway.
What do you think?
I agree on this solution...it merges nearly all the ideas we discussed so far.
Cheers,