Hi!

On Wed, 2008-12-03 at 12:23 +0100, Sven-Ola Tuecke wrote:
[...]
> seems to be a typical scenario recently: the catch-all-routing conficts with 
> some auto-management and/or with unmached/not-though-out requirements. He 
> may use the RtTableDefault to get olsrd's default routing entries out of the 
> way.

If that's the solution to the OPs problem, I can well live with it;-)

Other than that: It's pretty trivial to make the code accept more the
"RtTable" option more than once and add/change/delete not in one but
several (different) routing tables.
But given that one needs working/sane/... `ip rule` settings anyway, I
can't think of a problem which is solved by simply duplicating
routingtable $n identically into routingtable $m (because everything you
do with $m can identically be done with $n).
And even if, then a `ip monitor | ...` script could do that too (and
probably sees only the actually working operations).

[ Full-quote deleted ]

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




