[Olsr-users] Maybe problem when disabling all olsr network interfaces

[Joerg Pommnitz]

Hannes,
I don't think this will work. have a look at your code:

In olsr_calculate_routing_table () this is what happens:

364:   /*
365:    * Check if there was a change in the main IP address.
366:    * Bail if there is no main IP address.
367:    */
368:   olsr_change_myself_tc();
369:   if (!tc_myself) {
370:     return;
371:   }

With this code in place we *NEVER* reach:

505:   /* move the route changes into the kernel */
506: 
507:   olsr_update_kernel_routes();

And this is the onliest place (except from olsr_delete_all_kernel_routes
called on exit) that changes the kernel routes. Am I wrong?

-- 
Regards
       Joerg


--- Hannes Gredler <(spam-protected)> schrieb am Mi, 2.7.2008:

> Von: Hannes Gredler <(spam-protected)>
> Betreff: Re: [Olsr-users] Maybe problem when disabling all olsr network interfaces
> An: (spam-protected)
> CC: (spam-protected), "olsr-dev" <(spam-protected)>
> Datum: Mittwoch, 2. Juli 2008, 12:27
> Joerg Pommnitz wrote:
> > 2) go with Hannes' patch, but flush all the
> information associated with a
> >    given interface when it goes down. This solution
> feels right, but I'm
> >    not sure how to implement this.
> 
> you just need to engage an additional SPF calculation (set
> changes_neighbors)
> to TRUE then the SPF calculation should do the needful. if
> not then pls let me
> look at your testbed to see whats wrong there.
> 
> /hannes


      __________________________________________________________
Unglücklich mit Ihrer Mail-Adresse?

Millionen neuer Mail-Adressen - jetzt bei Yahoo!

http://de.docs.yahoo.com/mail/wunschmailadresse/index.html