[Olsr-dev] Short netmask lenghts
Tue Aug 10 08:18:22 CEST 2010
On Tue August 10 2010 08:12:02 Teco Boot wrote:
> False alarm.
> Now I use fresh copy of stable, modified dyn_gw for accepting all
> routes with metric other than RT_METRIC_DEFAULT. To be verified and
> posted by Caspar.
> I think this doesn't work for configs where hopcount is
> written in kernel routing table as metric. Or RT_METRIC_DEFAULT
> is not used.
Could be, yes !
> Golden rule: OLSR stored routes may not be picked up by dyn_gw.
Additional golden rule: use always "fixed" metrics for OLSRd... writing the
hopcount into the metric field can add problems for removing/setting routes.
> Op 10 aug 2010, om 07:56 heeft Henning Rogge het volgende geschreven:
> > On Mon August 9 2010 18:55:46 Teco Boot wrote:
> >> Hi Henning,
> >> I used also the /1 for a while.
> >> Now I want to add /2. So I'll have 3 def.gw prio's (/0, /1 and /2).
> >> Linux has problems with multiple, independent same routes (0/0 to
> >> different next_hops, maintained independently). Now I use different
> >> metrics: metric=0 # DHCP from eth1
> >> metric=1 # from ppp ip-up / ip-down scripts
> >> metric=2 # from olsrd
> > Is the routing metric not enough to create multiple 0/0 routes ?
> The 0/0 routes have independent originators.
> For example, pppd can replace the dhcp 0/0 route, but old route is not
> restored when pppd dies.
Linux does erase a 0/0 metric 1 rule if you set a 0/0 metric 2 one ?
I thought the kernel could handle multiple rules with the same target but
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961, Fax +49 228 9435 685
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the Olsr-dev