<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
I am convinced your plugin oriented architecture is awesome.
Nevertheless, here and there I am confused. The wikimedia is not
always too crystal clear about it. Examples would help. Plugin
related questinos must have cropped up quite often, I guess. I would
browse through your archive, but access is a little daunting.<br>
<br>
To have <b>my dlep_modem</b> part <b>interact</b> with the <b>olsr2d</b>,
I need layer2 data communicated to the olsr2d. Therefore I would
like to combine the <b>dlep_router </b>with the<b> olsr2d</b>.
Several router ifaces shall be covered by <b>DLEP</b>. I need an
instance per iface. Yes.<br>
<br>
Well, my approach to cominbe those as I understand things <b>without
perusing</b> in the code:<br>
<br>
1. building olsr2d(-dyn./stat. - does not matter):<br>
2. building plugins as libs (so make all)<br>
3. start olsr2d with plugin from cl<br>
3.1 either with <b>-p</b> cmd-line flag as <b>olsr2d_*
-h</b> tells:<br>
"-p, --plugin=shared-library Load a
shared library as a plugin"<br>
like in shell_cmd: olsrd2_static -p
liboonf_dlep_router.so [-l <conf>]<br>
-> failed with:<br>
"19:43:26.919 WARN(plugins)
src-api/core/oonf_subsystem.c 563: Loading of plugin
liboonf_dlep_router.so failed."<br>
<br>
3.2 or via <b>conf.-file</b>. - following my
conf.-file:<br>
<br>
[global]<br>
plugins dlep_router <br>
[dlep_router=eth0]<br>
local_heartbeat_interval 4.0 <br>
discovery_interval 3.0<br>
[dlep_router=eth1]<br>
local_heartbeat_interval 4.0<br>
discovery_interval 3.0<br>
<br>
-> dameon starts without warning: <br>
<b>I do</b>: ./olsrd2_static -l <conf> eth0<br>
but in simulation <b>NO </b><b>DLEP data</b> is
exchanged betw. dlep_radio instance and olsr2d<br>
only OLSR stuff -> packetbb<br>
<br>
<br>
<br>
---------------------------------------<br>
<br>
Further, I got all of this running as individual components in
combination with several simu. topologies. My own dlep_modem
implementation is talking with your dlep_router enjoyably sleek.
Both of your implementations, that is dlep_router and dlep_radio, do
so all the same. Can trace that.<br>
<br>
But when I ask your components f. destinations or neighbors via
telnet:<br>
> layer2info destination<br>
<br>
I get nothing. Is that the wrong query channel?<br>
<br>
Thanks!<br>
<pre class="moz-signature" cols="72">--
Matthias Tafelmeier</pre>
</body>
</html>