On Fri, 2007-08-24 at 21:48 +0200, Sven-Ola Tuecke wrote:
[...]
104-olsrd-policy-routing.patch
>   This is policy routing with the changes necessary to work with
>   your rt-refactoring.

Hmm, does that contain handling of "route is not present problem" (as
with the recently not existing default route on my node)?
This is a somewhat awkward problem AFAIU since it depends on the actual
configuration because that route may or may be not present (or we have
several).
Hmm, is automagically replacing (or adding) the route with a link-local
one a solution?

> I have at least one soft (olsr-viz) which depends on the metric value. 

Hmm, is is that much effort and/or complicated to support "correct"
metrics (implying much more route changes on that host) via a run-time
config variable?


Another thing if someone dares to read more patches: I somewhat reworked
the incoming part of lq_packet.[ch] (which gave the huge number of
malloc() calls in the gmon.out of "CCCamp-07 results") so that we do not
copy data around more than once and avoid superflous malloc()s and
free()s:
http://bernd.petrovitsch.priv.at/olsr-ng/olsrd-lq-packet-2007-08-24.patch

Seems to work hereover together with your patchset. Doesn't compile on
Win32 BTW: "if_indextoname" and "IF_NAMESIZE" can't be found. 

I didn't look in the incoming part if it makes sense there too.
Opinions?

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



