[Olsr-dev] Olsrd2, version 0.2.1

[Jeremy Lakeman]

That's pretty much what I just implemented for Serval's new link state
router.
Each node only repeats links that are used in their routing table, one link
per possible destination. You also need a "no active link" message to force
a deletion so that other nodes can quickly choose an alternative and start
telling you about it.
I threw together a dodgy, overly simplistic simulator last year to explore
how it should work. But only got around to implementing it properly in the
last month or so.


On Fri, May 24, 2013 at 5:35 PM, Teco Boot <(spam-protected)> wrote:

> My concerns are scalability. Major improvements on what we have now would
> be smart flooding (flooding MPRs) and topology reduction. A single TC
> summary for each router would help a lot. Links are identified by 2 peering
> router IP addresses. Could be the summary addresses or link-locals. use
> those that have higher compression ratio?
>
> Other optimization: links with next-hops that are not in own routing table
> can be removed from TC. Don't tell anyone else what you don't use yourself.
> Only tell the better routes: next-hops that are *in* the routing table.
>
> I'll run your code first and respond later.
>
> T.
>
>
>
>
> Op 24 mei 2013, om 07:43 heeft Henning Rogge <
> (spam-protected)> het volgende geschreven:
>
> > On 05/23/2013 10:30 PM, Teco Boot wrote:
> >>
> >> Op 23 mei 2013, om 20:51 heeft Henning Rogge <(spam-protected)>
> het volgende geschreven:
> >>
> >>> I would like to
> >>> get to the point where interface addresses can be "linklocal only" and
> >>> you need only a single "routable" address on the localhost interface
> >>> for the whole node.
> >> Great!
> >>
> >> Next: auto configuration and source address based routing (BRDP or
> similar).
> >
> > I plan to add a filter-callback between the dijkstra and the setting of
> the kernel routes that allows plugins to prevent the core from setting
> routes that match the filter.
> >
> > This way a SmartGateway or BRDP plugin could take over the handling of
> the gateway routes completely without any code-change in the core.
> >
> > Do you think that will be sufficient to implement BRDP support?
> >
> > Henning Rogge
> >
> > --
> > Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> > Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> > Kommunikationssysteme (KOM)
> > Fraunhofer Straße 20, 53343 Wachtberg, Germany
> > Telefon +49 228 9435-961,   Fax +49 228 9435 685
> > mailto:(spam-protected) http://www.fkie.fraunhofer.de
> >
> > --
> > Olsr-dev mailing list
> > (spam-protected)
> > https://lists.olsr.org/mailman/listinfo/olsr-dev
>
>
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20130525/f47e6cc7/attachment.html>