[Olsr-users] Testing DLEP plugin without WiFi

Tue Aug 30 08:08:17 CEST 2016

Hi,

forget DLEP for a moment, if your data source (nl80211_listener plugin) has
a problem, DLEP will just replicate the problem.

If I understand you correctly you are using a Debian for the Radio, right?
Did you compile the DLEP-radio executable locally or did you copy it from a
different machine?

what version of libnl* do you have installed?

what kernel are you using on the Radio node?

(you can test that libnl is working by running "iw <wlan-dev-name> station
dump")

Henning

On Tue, Aug 30, 2016 at 8:04 AM, Anderson Huang <
(spam-protected)> wrote:

> No. Therein lies the problem. When I query with layer2info on the radio
> side, a segmentation fault occurs within the program, and the program
> exits. The router executable continues to run but reports the error i
> stated above.
>
> 14:25:12.946 WARN(stream_socket) src-plugins/subsystems/oonf_stream_socket.c
> 812: Error while writing to communication stream with
> fe80::a2ce:c8ff:fe07:d669: Broken pipe (32)
>

It is the warning that the DLEP (TCP) session suddenly disconnected (when
the DLEP radio executable stopped).

Henning

>
>
> I am thinking that maybe my configuration file is wrong? It seems that
> there may be some problem in communicating across the mesh point I set up.
>
> Regards,
>
> Anderson Huang
>
> On Mon, Aug 29, 2016 at 10:28 PM, Henning Rogge <(spam-protected)> wrote:
>
>> Hi,
>>
>> but you get layer2info data on the radio, right? especially for
>> "layer2info neighbors".
>>
>> Henning
>>
>>
>> On Mon, Aug 29, 2016 at 9:24 PM, Anderson Huang <
>> (spam-protected)> wrote:
>>
>>> Hi,
>>>
>>> I am not using OpenWRT, but I executed the commands that I found
>>> relevant under this section. They make no difference. layer2info still does
>>> not output anything in the telnet interface.
>>>
>>> Regards,
>>>
>>> Anderson Huang
>>>
>>> On Sun, Aug 28, 2016 at 4:28 AM, Henning Rogge <(spam-protected)> wrote:
>>>
>>>> Hi,
>>>>
>>>> did you use the iptables/ebtables settings proposed on the olsr.org
>>>> webpage (or something equivalent)?
>>>>
>>>> http://www.olsr.org/mediawiki/index.php/DLEP#DLEP-radio_on_a
>>>> n_embedded_router_with_OpenWRT
>>>>
>>>> Henning
>>>>
>>>> On Thu, Aug 25, 2016 at 11:55 PM, Anderson Huang <
>>>> (spam-protected)> wrote:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> If you could, disregard the last email I sent as I have made some
>>>>> progress in establishing a working mesh network with dlep capabilities. I
>>>>> feel like I am very close, and am just missing a very small detail. Below
>>>>> is a summary of my setup and the error I run into.
>>>>>
>>>>> Router 1 --(ethernet adapter)-- Radio 1 ---- (802.11s mesh network)
>>>>> ---- Radio 2 ----(ethernet adapter) ---- Router 2
>>>>>
>>>>> Each of these nodes is running Linux, but not all versions of OONF are
>>>>> the same on each (if this is the problem, I can easily fix this). I have
>>>>> created a mesh network using open80211s tutorials. Radios 1 and 2 can
>>>>> successfully see each other through the mesh network.
>>>>>
>>>>> Next, I have bridged the ethernet interface on each radio with the
>>>>> mesh point interface. Let's call the mesh interface mesh0 and the bridge
>>>>> br0. My configuration files, then, for the router looks like so.
>>>>>
>>>>> [dlep_router=<ethernet enterface>]
>>>>>
>>>>> and for the radio
>>>>>
>>>>> [dlep_radio=mesh0]
>>>>>     datapath_if    br0(also tried using <ethernet interface>)
>>>>>
>>>>> In the terminal, I run on the router side,
>>>>>
>>>>> ./olsrd2_dlep_static <ethernet interface> lo --load=router.cfg
>>>>>
>>>>> and on the radio side,
>>>>>
>>>>> ./dlep_radio_static --load=radio.cfg
>>>>>
>>>>> Routers 1 and 2 are able to see each other across the mesh network,
>>>>> through routing tables using route -n. When I use br0 as the item to feed
>>>>> into datapath_if, the telnet interface gives me nothing when I query with
>>>>> the layer2info commands. In fact, when I try to do this on the router side,
>>>>> an unusual error pops up on the radio side, specifically of the kind as
>>>>> shown below. However, the correct neighbor shows up (e.g. the correct
>>>>> router on the other side of the mesh network).
>>>>>
>>>>> 14:25:12.946 WARN(stream_socket) src-plugins/subsystems/oonf_stream_socket.c
>>>>> 812: Error while writing to communication stream with
>>>>> fe80::a2ce:c8ff:fe07:d669: Broken pipe (32)
>>>>>
>>>>> When I use an ethernet interface as the argument to datapath_if, the
>>>>> telnet interface gives me no response when I query with layer2info
>>>>> commands.
>>>>>
>>>>> Let me know if there is any fix. Thank you for your help.
>>>>>
>>>>> On Wed, Aug 24, 2016 at 3:01 PM, Anderson Huang <
>>>>> (spam-protected)> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> So I am testing your plugins, specifically layer2, layer2info, and
>>>>>> layer2_config. I am secondly confused on what the result of running such
>>>>>> plugins should do - should I see test data in the OONF telnet plugin? May i
>>>>>> have some clarification on which executable I should be running this plugin
>>>>>> on top of (./olsrd2_dlep_static or ./dlep_radio_static)? For reference, my
>>>>>> setup still looks as such (you can disregard the wifi).
>>>>>>
>>>>>> Router 1 --(ethernet adapter)-- Radio 1 ---- (wifi & ethernet
>>>>>> adapter) ---- Radio 2 ----(ethernet adapter) ---- Router 2
>>>>>>
>>>>>> The problem is that I cannot seem to achieve Router 1 *to see *Router
>>>>>> 2 through the telnet interface. Through bridging ethernet interfaces, I am
>>>>>> able to see the logical IP addresses I assign through the end nodes'
>>>>>> routing tables, but I do not think this is what I wanted.
>>>>>> 802.11s is not supported on all my nodes unfortunately. If anyone has
>>>>>> successfully created a mesh network with Linksys WRT54GL routers, I would
>>>>>> appreciate any help with that as well.
>>>>>>
>>>>>> Anderson Huang
>>>>>>
>>>>>>
>>>>>> On Wed, Aug 24, 2016 at 1:24 AM, Anderson Huang <
>>>>>> (spam-protected)> wrote:
>>>>>>
>>>>>>> I am using a normal PC. I am able to compile and generate all
>>>>>>> executables as you have stated; however, the problem occurs because i am
>>>>>>> unable to follow through on the 802.11s mesh set-up (only one of my nodes
>>>>>>> has the network card capabilities to do this). Therefore, I was resorted to
>>>>>>> using OpenWRT to alleviate this problem. However, I bricked one of my
>>>>>>> routers today trying... I will most likely stick with a normal PC, but it
>>>>>>> seems like I will not be able to test the capabilities of the dlep_radio
>>>>>>> plugin using normal bridging. I will try using the layer 2 generator plugin
>>>>>>> and the layer 2 config plugins and report back to you on those results.
>>>>>>> Thank you for your help, and I will keep you updated.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Aug 23, 2016 at 11:01 PM, Henning Rogge <(spam-protected)>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Tue, Aug 23, 2016 at 11:13 PM, Anderson Huang <
>>>>>>>> (spam-protected)> wrote:
>>>>>>>>
>>>>>>>>> I am unsure how to run the binaries with the layer-2 generator
>>>>>>>>> plugin, however. I try to run it with the --plugin= option to no avail.
>>>>>>>>>
>>>>>>>>
>>>>>>>> You could add the plugin name to the OpenWRT build file...
>>>>>>>>
>>>>>>>> yes, I know its not perfect but the build system of OpenWRT is a
>>>>>>>> headache... so I only have a list of "usual plugins" to be optionally added
>>>>>>>> to OpenWRT by default.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> I am trying to experiment with OpenWRT now and am confused as to
>>>>>>>>> how OONF ties in. Am I correct in assuming that the OpenWRT must be running
>>>>>>>>> on a PC, not per se a Linksys WRT54GL router?
>>>>>>>>>
>>>>>>>>
>>>>>>>> OONF = Olsr.org Network Framework.
>>>>>>>>
>>>>>>>> Both my Olsrd2 and DLEP implementation are part of OONF.
>>>>>>>>
>>>>>>>> If you are using a normal PC, just forget about OpenWRT and compile
>>>>>>>> the executables yourself, you will find a description how to do this in the
>>>>>>>> wiki.
>>>>>>>>
>>>>>>>> Henning
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Olsr-users mailing list
>>>>> (spam-protected)
>>>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20160830/c7c70611/attachment.html>