[lime-users] 802.11s config

Pau pau at dabax.net
Thu May 11 14:22:09 UTC 2017


Hi.

I added a snippet to patch the current lime-sdk.

https://github.com/libremesh/lime-sdk/commit/7971d28d40ba456b73214bb482f8d97d156ff66e

Snippet must be executed like this: bash snippets/patch_sdk_11s.sh

On 11/05/17 16:02, Pau wrote:
> I think this will solve your dependency issue
> 
> https://github.com/libremesh/lime-packages/commit/178e21bc65f0fadb544ca8864955d88e928580bf
> 
> On 11/05/17 11:02, Ruairi Hickey wrote:
>> Hi ,
>> 	Success !!!  I patched the cooker files and built the lime-zero & lime-mini builds....  All the interfaces are up correctly
>>  
>> phy#0 
>>        Interface wlan0-apname 
>>                ifindex 16 
>>                wdev 0x4 
>>                addr 82:16:f9:d9:40:40 
>>                ssid LibreMesh.org/LiMe-d94040 
>>                type AP 
>>                channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz 
>>                txpower 20.00 dBm 
>>        Interface wlan0-ap 
>>                ifindex 14 
>>                wdev 0x3 
>>                addr 86:16:f9:d9:40:40 
>>                ssid LibreMesh.org 
>>                type AP 
>>                channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz 
>>                txpower 20.00 dBm 
>>        Interface wlan0-mesh 
>>                ifindex 13 
>>                wdev 0x2 
>>                addr 84:16:f9:d9:40:40 
>>                type mesh point 
>>                channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz 
>>                txpower 20.00 dBm
>>
>> root at LiMe-d94040:~# iw wlan0-mesh mpath dump 
>> DEST ADDR         NEXT HOP          IFACE       SN      METRIC  QLEN    EXPTIME         DTIM    DRET    FLAGS 
>> 84:16:f9:d9:18:6e 84:16:f9:d9:18:6e wlan0-mesh  2051    224     0       3610    100     0       0x15 
>> 84:16:f9:d9:44:80 84:16:f9:d9:44:80 wlan0-mesh  1619    257     0       0       100     0       0x14 
>> root at LiMe-d94040:~#
>>  
>>  
>> 	With the Lime-Zero build there was a missing dependency when running lime-config (possibly uci but I didnt copy the error ) - I will reflash one tonight and try fix / post the error.
>>  
>> Thanks for all the help....
>>  
>> Ruairi
>>  
>>
>>
>> On Wednesday 10 May 2017 17:40:54 IST Pau wrote:
>>> On 10/05/17 15:19, Ruairi Hickey wrote:
>>>> Hi,
>>>>
>>>>    I downloaded the patch from Daniel below and applied to the latest
>>>>    lime-build tree> 
>>>> however when I build this with a make v=S T=ar71xx-mini P=basic
>>>> the images dont include a specific image for the tlink tl-wr841n - is
>>>> there a specific image I should use instead ?
>>>>
>>>> Thanks,
>>>>
>>>> 	Ruairi
>>>
>>> I've not tested lime-build with LEDE cause the idea is to use lime-sdk
>>> instead.
>>>
>>> You can clone lime-sdk (use Master branch) and execute:
>>>
>>> ./cooker -d ar71xx/generic
>>> ./cooker -f
>>>
>>> Then navigate to 17.01.1/ar71xx/generic/sdk, and copy the patch files.
>>>
>>> Compile:
>>>
>>> ./cooker -b ar71xx/generic
>>>
>>> Generate firmware
>>>
>>> ./cooker -c ar71xx/generic --flavor=lime_mini --profile=tl-wr841n-v1
>>> # check correct profile name with ./cooker --profiles=ar71xx/generic
>>> # if you don't care about having LuCi use lime_zero as flavor instead
>>>
>>> Cheers.
>>>
>>>> On Tuesday 9 May 2017 16:41:29 IST Daniel Golle wrote:
>>>>> Hi Pau,
>>>>>
>>>>> sorry for the late reply. See my comment below.
>>>>>
>>>>> On Fri, May 05, 2017 at 03:21:36PM +0200, Pau wrote:
>>>>>> Hi Again.
>>>>>>
>>>>>> I've been testing 802.11s support on LibreMesh develop branch. These are
>>>>>> the conclusions:
>>>>>>
>>>>>> 1) I fixed a bug related to the network configuration:
>>>>>>
>>>>>> https://github.com/libremesh/lime-packages/commit/3163e6ed15079e2c760824
>>>>>> c6
>>>>>> d1f81837345e2093
>>>>>>
>>>>>> This is already comited and soon the binaries available on
>>>>>> http://repo.libremesh.org will have this patch applied (the compilation
>>>>>> process is already running).
>>>>>>
>>>>>> 2) Good news are that I managed to create a mesh network using 802.11s.
>>>>>> In addition to `mode ieee80211s` also `proto ieee80211s` must be enabled
>>>>>> in the configuration file.
>>>>>>
>>>>>> This is my /etc/config/lime
>>>>>>
>>>>>> config lime network
>>>>>>
>>>>>> 	list protocols ieee80211s
>>>>>> 	list protocols lan
>>>>>> 	list protocols anygw
>>>>>> 	list protocols batadv:%N1
>>>>>> 	list protocols bmx6:13
>>>>>>
>>>>>> config lime wifi
>>>>>>
>>>>>> 	list modes ieee80211s
>>>>>>
>>>>>> Then run: lime-config && lime-apply
>>>>>>
>>>>>> This configuration works for me and the two routers are connected.
>>>>>>
>>>>>> 3) Bad news is that, for some point I don't understand, if "AP" is
>>>>>> enabled in addition to 80211s, the mesh point is not enabled and it does
>>>>>> not work.
>>>>>>
>>>>>> So the right configuration (to mesh and AP at same time) would be:
>>>>>>
>>>>>> config lime wifi
>>>>>>
>>>>>> 	list modes ieee80211s
>>>>>> 	list modes ap
>>>>>> 	list modes apname
>>>>>>
>>>>>> But it does not work.
>>>>>>
>>>>>> According to "iw list" information, Mesh point + AP is possible, but I
>>>>>> think there is something wrong on LEDE. So I'll investigate a bit more
>>>>>> and talk with LEDE developers if it is an actual LEDE bug.
>>>>>>
>>>>>> PS: add Daniel as CC, maybe he can add some extra information for the
>>>>>> resolution of this problem.
>>>>>
>>>>> I've been in touch with neoraider and he made a fix for this:
>>>>> https://git.lede-project.org/?p=lede/neoraider/staging.git;a=commit;h=6db
>>>>> 7dc d74aaf23865ff19b515daf8c534414adaf
>>>>>
>>>>> I also updated the ticket on github, just in case you missed that.
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>>
>>>>> Daniel
>>>>>
>>>>>> On 20/04/17 20:04, Ruairi Hickey wrote:
>>>>>>> On Thursday 20 April 2017 11:34:09 IST you wrote:
>>>>>>>> On 19/04/17 20:46, Ruairi Hickey wrote:
>>>>>>>>> On Wednesday 19 April 2017 19:29:59 IST Ilario Gelmetti wrote:
>>>>>>>>>> On 04/19/2017 05:25 PM, Ruairi Hickey wrote:
>>>>>>>>>>> While the mesh appears to be up and the stations can see each other
>>>>>>>>>>> there is no ip connectivity - if a client is connected to the
>>>>>>>>>>> libremesh.org
>>>>>>>>>>> via AP node d9:18:6e it can not connect to the internet / outside
>>>>>>>>>>> via AP
>>>>>>>>>>> d9:44:80.
>>>>>>>>>>
>>>>>>>>>> Hi Ruairi!
>>>>>>>>>> Have you plugged an internet connection to a WAN port of your
>>>>>>>>>> router?
>>>>>>>>>> If your router doesn't have a WAN port you will have to configure
>>>>>>>>>> another one as WAN (check out /etc/config/lime-example and
>>>>>>>>>> http://libremesh.org/docs/changing_network_behavior.html ).
>>>>>>>>>> If this doesn't work: can you post the content of
>>>>>>>>>> /etc/config/network
>>>>>>>>>> on
>>>>>>>>>> your LibreMesh router?
>>>>>>>>>> And the output of the "ip address show" commend.
>>>>>>>>>>
>>>>>>>>>>> Are there additional steps required to enable this (it works
>>>>>>>>>>> out of the box on ad- hoc) ?
>>>>>>>>>>
>>>>>>>>>> No, it should automagically work when you plug the WAN port of the
>>>>>>>>>> LiMe
>>>>>>>>>> router into a LAN port of a router offering a DHCP server and a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> lime-users mailing list
>>>>>>>>>> lime-users at lists.libremesh.org
>>>>>>>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>
>>
>> _______________________________________________
>> lime-users mailing list
>> lime-users at lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>
> 
> 
> 
> _______________________________________________
> lime-users mailing list
> lime-users at lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
> 

-- 
./p4u

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.libremesh.org/pipermail/lime-users/attachments/20170511/57e2f821/attachment.sig>


More information about the lime-users mailing list