[Olsr-users] OLSR topology and VPN links

Markus Kittenberger (spam-protected)
Wed Jun 22 23:35:38 CEST 2011

olsrdv1 protocol can not store this infomation.

so olsrd does not (and does not need to know) which interfaces are involved
in remote links

(so it does only know it for its own links)

furthermore, (to get this even more complicated) if nodes have conenctivity
via vpn and wifi, only one of this link is known to the network (the better


On Wed, Jun 22, 2011 at 8:38 PM, Mitar <(spam-protected)> wrote:

> Hi!
> We have started using n2n for VPN in our network. But n2n also creates
> connections directly between nodes. And now we have a problem that
> when we draw topology on the map we do not know how to know which
> links are VPN links (to not draw them) and which are real WiFi links.
> Before we were using centralized VPN server and it was easy not to
> draw links which end with VPN server. But now this approach does not
> work anymore.
> As we use separate IPs on each interface we could draw only those
> links which are made from nodes' primary IPs (which are also on WiFi
> interface) and not additional IPs (which are on VPN interface,
> ethernet interface and so on). Is there a way to get this topology
> information? txtinfo plugin displays topology information with just
> primary IP. Would it be possible to change it to display only those
> links which are really just from primary IP?
> Mitar
> --
> Olsr-users mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20110622/8c5a1504/attachment.html>

More information about the Olsr-users mailing list