[Olsr-users] Running olsrd2 from different namespaces

Henning Rogge (spam-protected)
Thu Nov 17 08:05:44 CET 2016

On Wed, Nov 16, 2016 at 6:08 PM, Dani Camps <(spam-protected)> wrote:

> Dear all,
> I have a virtual mesh setup where each node is represented with a net
> namespace (ip netns), and the virtual mesh topology is established
> using veth pairs that connect namespaces with each other.
> My intention was to run olsrd2 inside each namespace. I run olsrd2 in
> the first namespace doing:
> ./olsrd2_static veth_1 veth_2 lo
> But when I try the same in the different namespace, which exposes
> other network interfaces, I get:
> 16:33:36.215 WARN(main) src-api/core/oonf_main.c 248: Could not
> acquire application lock '/var/run/OLSRd2.lock'
> Does anyone know how to run olsrd from different namespaces? Maybe I
> need to launch each instance with a different pid. If you have an
> example configuration to do this it would be helpful for me.
> Olsrd2 uses a "lock file" to prevent people running two routing agents in
the same context (which can be quite a mess). You could either move the
/var/run directory into a namespace specific overlay/filesystem, or you
could use the parameter "global.lockfile" to set your own lockfile (or
disable it completely).


set a new lock file:
olsrd2_static --set global.lockfile=/var/run/olsrd_1.lock  ...

or disable it
olsrd2_static --set global.lockfile=-  ...

use "olsrd2_static --schema", "olsrd2_static --schema=global" and
"olsrd2_static --schema=global.lockfile" to learn about the parameters of

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20161117/141e83af/attachment.html>

More information about the Olsr-users mailing list