On Mon, Dec 05, 2011 at 03:38:48 +0100, Andrew Lunn wrote:
What about specifying the routing algorithm directly on "soft-iface creation" and deny any further change?
Emails crossed in the post....
- specify the soft-iface name => create the interface and allocate all the
structure (that are not dependant on the routing algo)
1.1) the interface is in ALGO-WAITING state, any action that tries to enable it is denied and EBUSY (?) is returned.
We should try to keep backwards compatibility. So rather than having ALGO-WAITING, i would suggest using the first available routing algorithm as the default.
So the backwards compatible way would be:
- Add a hard interface, which automagically creates the soft interface with the first available routing algorithm.
For those who want to play with new routing algorithms:
- Create the soft interface
- Change the routing algorithm away from the default
- Add the first hard interface.
I think that currently point 1) and 3) are joint. So adding something in between means redesign the initialisation part.
Cheers,