[Olsr-users] OONF equivalent for LinkQualitMult

[Henning Rogge]

On Mon, Oct 15, 2018 at 2:09 PM Gabriel <(spam-protected)> wrote:
>
> Il 2018-10-15 13:11 Henning Rogge ha scritto:
> > Okay...
> >
> > this is my idea:
> >
> > you could run a mesh with two topologies, one with the VPN links and
> > one without the VPN links... if the routing table of the "no VPN"
> > topology is used first, it should always have priority, not depending
> > on the metric values.
> >
> > The only piece that is missing would be a plugin that allow you to
> > block an interface (in this case the VPN one) for one of the two
> > topologies. I could solve this "code" problem.
> >
> > Would you be interested in testing something like this?
>
> This would means to have different domains running in the same deamon?
> I think it would also means to have Policy Routing in every node, right?
> And to update the configuration and the software of all the node
> deployed.
Yes.

Olsrd2 would generate two routing tables full of routes. You would
need two policy rules to activate both of them.

You would not need to update all nodes at the same time, you could
build up the "no vpn" topology as an optional one with node after node
(multi-topology capability is already built into each olsrd2).

> Unfortunately is quite unfeasbile in our scenario.
> We need something easy to deploy only in the nodes connected on the VPN.

I don't have an easy solution for this.

Henning