[Olsr-users] OLSR2D and DLEP_ROUTER plugin interplay:

[Henning Rogge]

On Sun, Dec 6, 2015 at 8:15 PM, s-mtafel <(spam-protected)> wrote:
> Hello,
>
> I am convinced your plugin oriented architecture is awesome.

Thank you. :)

> Nevertheless,
> here and there I am confused. The wikimedia is not always too crystal clear
> about it. Examples would help.

Yes, I try to add stuff to the wiki when it comes up... but I am the
only one working on the OONF code and maintaining the wiki, so its a
slow progress.

> Plugin related questinos must have cropped up
> quite often, I guess. I would browse through your archive, but access is a
> little daunting.
>
> To have my dlep_modem part interact with the olsr2d, I need layer2 data
> communicated to the olsr2d. Therefore I would like to combine the
> dlep_router with the olsr2d. Several router ifaces shall be covered by DLEP.
> I need an instance per iface. Yes.

Okay...

I also added some description about the data flow through the Layer2 database:
http://www.olsr.org/mediawiki/index.php/OONF_Layer2_Plugin

> Well, my approach to cominbe those as I understand things without perusing
> in the code:
>
> 1. building olsr2d(-dyn./stat. - does not matter):

you are correct

> 2. building plugins as libs (so make all)

> 3. start olsr2d with plugin from cl
>             3.1 either with -p cmd-line flag as olsr2d_* -h tells:
>                   "-p, --plugin=shared-library            Load a shared
> library as a plugin"
>                 like in shell_cmd: olsrd2_static -p liboonf_dlep_router.so
> [-l <conf>]
>                 -> failed with:
>                   "19:43:26.919 WARN(plugins) src-api/core/oonf_subsystem.c
> 563: Loading of plugin          liboonf_dlep_router.so failed."

try without the ".so" at the end, just with the internal name of the plugin.

>             3.2 or via conf.-file. - following my conf.-file:
>
>                 [global]
>                     plugins    dlep_router
>                 [dlep_router=eth0]
>                     local_heartbeat_interval  4.0
>                     discovery_interval    3.0
>                 [dlep_router=eth1]
>                     local_heartbeat_interval  4.0
>                     discovery_interval    3.0
>
>             -> dameon starts without warning:
>                 I do: ./olsrd2_static -l <conf> eth0
>                 but in simulation NO DLEP data is exchanged betw. dlep_radio
> instance and olsr2d
>                 only OLSR stuff -> packetbb

So you are receiving DLEP data through 2 interfaces... I assume your
DLEP radio instance is running on the other side of the eth0/eth1
interface, right? Where does the DLEP radio gets it data from?

when you add

[log]
    debug dlep_router

to your configuration, you should see the state changes of the DLEP
router implementation. Do you see anything unusual there?

Henning Rogge