[Olsr-dev] feature request for on demand interface discovery

cstorch (spam-protected)
Tue May 6 13:55:25 CEST 2014

hi there,

we have a pretty special setup here at Freifunk Weimar - "Weimarnetz".
Our root server is our vpn gateway for internet providing dsl gateways.

There is olsr version
"(spam-protected):~$ olsrd -v
 *** olsr.org - ***
 Build date: 2013-12-05 15:48:04 on weimar2

To keep our vpn setup easy we configured 1000 tap interfaces, one for
each possible vpn client. The olsr config contains also 1000 taps.

When olsr is startet, the load of the server goes up to "2". (it is a vm
on multicore xeon with enough memory)

We did some analysis with strace:
4:24:56.186377 ioctl(3, SIOCGIFFLAGS, {ifr_name="tap635", ???}) = -1
ENODEV (No such device)
this is repeated for all interfaces and takes 12seconds to complete.
After (NicChgsPollInt) the interface discovery is repeated.

Our idea is to switch off the "NicChgsPollInt" and use some kind of
"kill -USR1  pidof olsrd" (like for dd) to trigger a interface discovery.

What is your opinion?


More information about the Olsr-dev mailing list