[Olsr-users] viewing radio layer2info from the router

[Ed Kfir]

Hi Henning,

Thank you for your response. I did try the configuration examples listed
above as you described with the olsrd2_static (with dlep_router plugin)
running on both routers and dlep_radio_static (with the dlep_radio plugin)
running on both radios. Looking at the layer2info from the radios with the
above setup, I can see data that makes sense for the destination,interface,
and neighbor subcommands. The destination subcommand key %dst_addr% for
radio1 shows radio 2's wifi interfaces's mac address in its first entry and
router 2's ethernet interface's mac address in its 2nd entry. On radio 2
the same key shows router 1's mac and radio 1's wifi interface mac.

However, running the same commands on both routers, I see no reference to
anything related to the connected radios. The neighbor subcommand shows the
other router (but not the connected radio) and the destination subcommand
has no output.  The same theme appears to be the case for
nhdpinfo,olsrv2info,netjsoninfo,etc. Is there anything else that I could
possibly be missing here?

thanks,
Ed

On Mon, Jul 23, 2018 at 10:55 PM, Henning Rogge <(spam-protected)> wrote:

> Hi,
>
> you need DLEP (dlep radio/router pair) to transfer the data to the router.
>
> Did you try to run the configuration examples for radio and router
> from the wiki?
> http://www.olsr.org/mediawiki/index.php/DLEP_Plugins#
> Configuration_examples
>
> the radio part uses the "dlep_radio_static" executable, the router
> part is a normal olsrd2 router with "dlep_router" plugin.
>
> Henning
> On Tue, Jul 24, 2018 at 4:27 AM Ed Kfir <(spam-protected)> wrote:
> >
> > Hi everyone,
> >
> > I am new to olsr and dlep. I cloned the project at
> https://github.com/OLSR/OONF (currently using commit 312d09d) and have
> the following set up.
> >
> > Router 1 --(ethernet adapter)-- Radio 1 ---- (wifi adapter) ---- Radio 2
> ----(ethernet adapter) ---- Router 2
> >
> > I have the nl80211_listener running on both radios and am able to see
> data when I do something like echo "/layer2info neighbor"  | nc 127.0.0.1
> 2009 on the radios. However, I am still clueless as to how to see the
> radio's layer2info data from the routers. Is there a particular plugin
> aside from dlep_router that I need running on the router?
> >
> > Any help would be much appreciated.
> >
> > thanks,
> > Ed
> >
> >
> > This correspondence may contain technical data, as defined in ITAR 22
> CFR or the EAR 15 CFR.  The recipient is advised and hereby acknowledges
> that such technical data, relating to export controlled items under the
> ITAR or the EAR may not be exported, disclosed or transferred to any
> foreign person whether in the United States or abroad, without first
> complying with all relevant requirements including the requirement for
> obtaining any written export authorization from the U.S. Department of
> State, Directorate of Defense Trade Control or the Department of Commerce’s
> Bureau of Industry & Security or otherwise make and document the
> determinations that an export licensing exemption applies, as the case may
> be. Diversion contrary to U.S. law is prohibited.
> >
> > --
> > Olsr-users mailing list
> > (spam-protected)
> > https://lists.olsr.org/mailman/listinfo/olsr-users
>

-- 


This correspondence may contain technical data, as defined in ITAR 22 CFR 
or the EAR 15 CFR.  The recipient is advised and hereby acknowledges that 
such technical data, relating to export controlled items under the ITAR or 
the EAR may not be exported, disclosed or transferred to any foreign person 
whether in the United States or abroad, without first complying with all 
relevant requirements including the requirement for obtaining any written 
export authorization from the U.S. Department of State, Directorate of 
Defense Trade Control or the Department of Commerce’s Bureau of Industry & 
Security or otherwise make and document the determinations that an export 
licensing exemption applies, as the case may be. Diversion contrary to U.S. 
law is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20180724/f53658b3/attachment.html>