Porting Libre Mesh into MP02-AWD

List overview All Threads
Download

newer

older

Licensing for the code

Suggestion on spreading knowledge

Carlos Rey-Moreno

27 Jul 2017 27 Jul '17

3:55 p.m.

Hi everyone, I've following the list for quite some time and it was only in the last month that I got myself together and installed LiMe in some Mesh Potatoes (based on Dragino MS14) that I had with me. In Zenzeleni we've been using MPs and VillageTelco firmware from the beginning, and although they are "very Plug & Play" and easy to use for non-geeks, I was pretty impressed by LiMe. What you have done making IP disappear is quite something as it is one of the concepts people struggle with the most. So now, we are seriously considering using LiMe at Zenzeleni. However, we need a bit of guidance on creating a built for the MP02-AWD which is the hardware we have in our networks. It is based on the Dragino MS14, so the internal radio works from scratch after flashing. However, I'd like to add the secondary radio (ralink usb) to the build, and have the wireless config files modified accordingly, so it works directly after being flashed. Anyone keen to guide me about how to do it? Thanks in advance, carlos -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net https://www.youtube.com/watch?v=YxTPSWMX26M Cel: +27 (0) 76 986 3633 <+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym

Attachments:

attachment.html (text/html — 1.9 KB)

Show replies by date

pau

31 Jul 31 Jul

10:40 p.m.

...

Hi everyone, I've following the list for quite some time and it was only in the last month that I got myself together and installed LiMe in some Mesh Potatoes (based on Dragino MS14) that I had with me. In Zenzeleni we've been using MPs and VillageTelco firmware from the beginning, and although they are "very Plug & Play" and easy to use for non-geeks, I was pretty impressed by LiMe. What you have done making IP disappear is quite something as it is one of the concepts people struggle with the most. So now, we are seriously considering using LiMe at Zenzeleni. However, we need a bit of guidance on creating a built for the MP02-AWD which is the hardware we have in our networks. It is based on the Dragino MS14, so the internal radio works from scratch after flashing. However, I'd like to add the secondary radio (ralink usb) to the build, and have the wireless config files modified accordingly, so it works directly after being flashed. Anyone keen to guide me about how to do it? Thanks in advance, carlos -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> https://www.youtube.com/watch?v=YxTPSWMX26M <https://www.youtube.com/watch?v=YxTPSWMX26M> Cel: +27 (0) 76 986 3633 <tel:+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

Carlos Rey-Moreno

6 Aug 6 Aug

8:26 a.m.

Hi Pau, thanks a lot for wanting to help. I've only being able to get to this today. I installed the building environment, and tried to "cook" the firmware following some directions Nico Echaniz gave me over the chat. We ended up agreeing using this command: ./cooker -c ar71xx/generic --flavor=lime_default --profile=dragino2 --extra-pkg="kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb" At the beginning of the output I get: ./cooker: unrecognized option '--extra-pkg=kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb' So, the cooker builds a firmware that works, but only using the primary radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in the section "For a casual cooking on a existing feed repository". ./cooker -f returns -> Feeds already downloaded, doing nothing. Use --force to reinstall but I don't know how to continue from there, as I don't know how to "Modify the source code of the existing feed" Any way to get around this? best, carlos On 1 August 2017 at 00:40, pau <pau(a)dabax.net> wrote:

...

Hi Carlos. I like to help you, but I like to know if you tried already some libremesh firmware. Is the MP02-AWM supported by an official target of LEDE? I see the Dragino2 target [1], have you tried it? For any kind of firmware customization I encourage you to use the lime-sdk "cooker" [2]. Are you familiar with it? Cheers. [1] http://repo.libremesh.org/current/targets/ar71xx/ generic/dragino2/lime_default/ [2] https://github.com/libremesh/lime-sdk On 07/27/17 17:55, Carlos Rey-Moreno wrote: Hi everyone, I've following the list for quite some time and it was only in the last month that I got myself together and installed LiMe in some Mesh Potatoes (based on Dragino MS14) that I had with me. In Zenzeleni we've been using MPs and VillageTelco firmware from the beginning, and although they are "very Plug & Play" and easy to use for non-geeks, I was pretty impressed by LiMe. What you have done making IP disappear is quite something as it is one of the concepts people struggle with the most. So now, we are seriously considering using LiMe at Zenzeleni. However, we need a bit of guidance on creating a built for the MP02-AWD which is the hardware we have in our networks. It is based on the Dragino MS14, so the internal radio works from scratch after flashing. However, I'd like to add the secondary radio (ralink usb) to the build, and have the wireless config files modified accordingly, so it works directly after being flashed. Anyone keen to guide me about how to do it? Thanks in advance, carlos -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net https://www.youtube.com/watch?v=YxTPSWMX26M Cel: +27 (0) 76 986 3633 <+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing listlime-dev@lists.libremesh.orghttps://lists.libremesh.org/mailman/listinfo/lime-dev _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

Pau

2:03 p.m.

On 06/08/17 10:26, Carlos Rey-Moreno wrote:

...

I'll check this, maybe it is a bug. Meanwhile you can use the system variable PKG export PKG="kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb" ./cooker -c ar71xx/generic --flavor=lime_default --profile=dragino2 Cheers.

...

So, the cooker builds a firmware that works, but only using the primary radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in the section "For a casual cooking on a existing feed repository". ./cooker -f returns -> Feeds already downloaded, doing nothing. Use --force to reinstall but I don't know how to continue from there, as I don't know how to "Modify the source code of the existing feed" Any way to get around this? best, carlos On 1 August 2017 at 00:40, pau <pau(a)dabax.net> wrote:

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

-- ./p4u

Carlos Rey-Moreno

10 Aug 10 Aug

2:27 p.m.

Hi Pau, thanks a lot! It does work that way and the 2 radios are up and configured automatically. However, the firmware does the same with both, i.e. create the APs and the mesh. I could modify that by tweaking the /etc/config/wireless, but is there anyway that can be done from the "cooker"? I believe that requires creating a community. What are the steps to do that? Lastly, Elektra and Felix worked in tweaking the driver to allow to set the Coverage Class for the Ralink driver. Is there any way I can use in the cooker command their driver packages (that I have stored locally) instead of the ones in the repos? I guess it is just by replacing those within the binaries of the particular target, right? Thanks in advance carlos On 6 August 2017 at 16:03, Pau <pau(a)dabax.net> wrote:

...

On 06/08/17 10:26, Carlos Rey-Moreno wrote:

kmod-rt2800-usb

kmod-rt2x00-lib kmod-rt2x00-usb'

So, the cooker builds a firmware that works, but only using the primary radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in the section

"For

a casual cooking on a existing feed repository". ./cooker -f returns -> Feeds already downloaded, doing nothing. Use --force to reinstall but I don't know how to continue from there, as I don't know how to

"Modify

the source code of the existing feed" Any way to get around this? best, carlos On 1 August 2017 at 00:40, pau <pau(a)dabax.net> wrote: > Hi Carlos. > > I like to help you, but I like to know if you tried already some

libremesh

> firmware. Is the MP02-AWM supported by an official target of LEDE? I see > the Dragino2 target [1], have you tried it? > > For any kind of firmware customization I encourage you to use the

lime-sdk

> "cooker" [2]. Are you familiar with it? > > Cheers. > > [1] http://repo.libremesh.org/current/targets/ar71xx/ > generic/dragino2/lime_default/ > > [2] https://github.com/libremesh/lime-sdk > > > On 07/27/17 17:55, Carlos Rey-Moreno wrote: > > Hi everyone, > > I've following the list for quite some time and it was only in the last > month that I got myself together and installed LiMe in some Mesh

Potatoes

> (based on Dragino MS14) that I had with me. In Zenzeleni we've been

using

> MPs and VillageTelco firmware from the beginning, and although they are > "very Plug & Play" and easy to use for non-geeks, I was pretty

impressed by

> LiMe. What you have done making IP disappear is quite something as it is > one of the concepts people struggle with the most. > > So now, we are seriously considering using LiMe at Zenzeleni. However,

> need a bit of guidance on creating a built for the MP02-AWD which is the > hardware we have in our networks. It is based on the Dragino MS14, so

the

> internal radio works from scratch after flashing. However, I'd like to

add

> the secondary radio (ralink usb) to the build, and have the wireless

config

> files modified accordingly, so it works directly after being flashed. > > Anyone keen to guide me about how to do it? > > Thanks in advance, > > carlos > > -- > Carlos Rey-Moreno, PhD > PostDoctoral Fellow University of the Western Cape > Zenzeleni Networks: zenzeleni.net > https://www.youtube.com/watch?v=YxTPSWMX26M > Cel: +27 (0) 76 986 3633 <+27%2076%20986%203633> > Skype: carlos.reymoreno Twitter: Creym > > > _______________________________________________ > lime-dev mailing listlime-dev@lists.libremesh.orghttps://

lists.libremesh.org/mailman/listinfo/lime-dev

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

-- ./p4u _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

pau

12 Aug 12 Aug

6:16 p.m.

On 08/10/17 16:27, Carlos Rey-Moreno wrote:

...

Yes, the best is to create a community. You can use your own repository (and modify cooker's options.conf) or use the default one [1]. # clone the communities and list them ./cooker --communities # create your own and the /etc/config directory mkdir -p communities/YOUR_COM_NAME/mp02-awd/etc/config/ # Any file you put on communities/YOUR_COM_NAME/mp02-awd will be added to the resulting firmware. # download the last default lime-config wget https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/… -O communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # modify it to your own needs, here some tips about this file [2] nano communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # And finally cook ./cooker ... --community=YOUR_COM_NAME/mp02-awd Once you are happy with the result, you can send a pull request to the network-profiles git repository [1] (so others can also use your tweaks). [1] https://github.com/libremesh/network-profiles [2] http://libremesh.org/docs/en_config.html

...

Lastly, Elektra and Felix worked in tweaking the driver to allow to set the Coverage Class for the Ralink driver. Is there any way I can use in the cooker command their driver packages (that I have stored locally) instead of the ones in the repos? I guess it is just by replacing those within the binaries of the particular target, right?

If the kernel is the same, then yes. As last libremesh release is using LEDE 17.02.2, it should be the case. But better ask them. Cheers.

...

Thanks in advance carlos On 6 August 2017 at 16:03, Pau <pau(a)dabax.net <mailto:pau@dabax.net>> wrote: On 06/08/17 10:26, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot for wanting to help. I've only being able

to get to

this today. I installed the building environment, and tried to

"cook" the

firmware following some directions Nico Echaniz gave me over the

chat.

We ended up agreeing using this command: ./cooker -c ar71xx/generic --flavor=lime_default --profile=dragino2 --extra-pkg="kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb" At the beginning of the output I get: ./cooker: unrecognized option '--extra-pkg=kmod-rt2800-lib

kmod-rt2800-usb

kmod-rt2x00-lib kmod-rt2x00-usb'

So, the cooker builds a firmware that works, but only using the

primary

radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in the

section "For

to "Modify

the source code of the existing feed" Any way to get around this? best, carlos On 1 August 2017 at 00:40, pau <pau(a)dabax.net

<mailto:pau@dabax.net>> wrote:

> Hi Carlos. > > I like to help you, but I like to know if you tried already

some libremesh

> firmware. Is the MP02-AWM supported by an official target of

LEDE? I see

> the Dragino2 target [1], have you tried it? > > For any kind of firmware customization I encourage you to use

the lime-sdk

> "cooker" [2]. Are you familiar with it? > > Cheers. > > [1] http://repo.libremesh.org/current/targets/ar71xx/

<http://repo.libremesh.org/current/targets/ar71xx/>

> generic/dragino2/lime_default/ > > [2] https://github.com/libremesh/lime-sdk

<https://github.com/libremesh/lime-sdk>

> > > On 07/27/17 17:55, Carlos Rey-Moreno wrote: > > Hi everyone, > > I've following the list for quite some time and it was only in

the last

> month that I got myself together and installed LiMe in some

Mesh Potatoes

> (based on Dragino MS14) that I had with me. In Zenzeleni we've

been using

> MPs and VillageTelco firmware from the beginning, and although

they are

> "very Plug & Play" and easy to use for non-geeks, I was pretty

impressed by

> LiMe. What you have done making IP disappear is quite something

as it is

> one of the concepts people struggle with the most. > > So now, we are seriously considering using LiMe at Zenzeleni.

However, we

> need a bit of guidance on creating a built for the MP02-AWD

which is the

> hardware we have in our networks. It is based on the Dragino

MS14, so the

> internal radio works from scratch after flashing. However, I'd

like to add

> the secondary radio (ralink usb) to the build, and have the

wireless config

> files modified accordingly, so it works directly after being

flashed.

> > Anyone keen to guide me about how to do it? > > Thanks in advance, > > carlos > > -- > Carlos Rey-Moreno, PhD > PostDoctoral Fellow University of the Western Cape > Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> > https://www.youtube.com/watch?v=YxTPSWMX26M

<https://www.youtube.com/watch?v=YxTPSWMX26M>

> Cel: +27 (0) 76 986 3633

<tel:%2B27%20%280%29%2076%20986%203633> <+27%2076%20986%203633>

> Skype: carlos.reymoreno Twitter: Creym > > > _______________________________________________ > lime-dev mailing

listlime-dev@lists.libremesh.orghttps://lists.libremesh.org/mailman/listinfo/lime-dev <http://lists.libremesh.org/mailman/listinfo/lime-dev>

> > > > _______________________________________________ > lime-dev mailing list > lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> > https://lists.libremesh.org/mailman/listinfo/lime-dev

<https://lists.libremesh.org/mailman/listinfo/lime-dev>

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org

https://lists.libremesh.org/mailman/listinfo/lime-dev

<https://lists.libremesh.org/mailman/listinfo/lime-dev>

-- ./p4u _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev> -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> https://www.youtube.com/watch?v=YxTPSWMX26M Cel: +27 (0) 76 986 3633 Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

Carlos Rey-Moreno

14 Aug 14 Aug

9:33 a.m.

Thanks a lo Pau, I've gone through the steps and played with some options, but I seem to be doing something wrong. I created two new firmwares (in both changing LibreMesh.org for Zenzeleni in the SSID to make sure it worked, which it did): 1. Added the following at the end of lime-defaults config wifi radio0 list modes 'ieee80211s' option channel_5ghz '157' config wifi radio1 list modes 'ap' option channel_2ghz '1' And it had no effect. Both radios appeared configured for AP and Mesh 2. Similar to the above but comments the following of lime-defaults config lime wifi # option channel_2ghz '11' # option channel_5ghz '48' option htmode_5ghz 'HT40' option distance '1000' # list modes 'ap' # list modes 'apname' # list modes 'ieee80211s' And I couldn't enter the router via WiFi anymore... any suggestion? Thanks again, carlos On 12 August 2017 at 20:16, pau <pau(a)dabax.net> wrote:

...

On 08/10/17 16:27, Carlos Rey-Moreno wrote: Hi Pau, thanks a lot! It does work that way and the 2 radios are up and configured automatically. However, the firmware does the same with both, i.e. create the APs and the mesh. I could modify that by tweaking the /etc/config/wireless, but is there anyway that can be done from the "cooker"? I believe that requires creating a community. What are the steps to do that? https://raw.githubusercontent.com/libremesh/lime-packages/ develop/packages/lime-system/files/etc/config/lime-defaults Yes, the best is to create a community. You can use your own repository (and modify cooker's options.conf) or use the default one [1]. # clone the communities and list them ./cooker --communities # create your own and the /etc/config directory mkdir -p communities/YOUR_COM_NAME/mp02-awd/etc/config/ # Any file you put on communities/YOUR_COM_NAME/mp02-awd will be added to the resulting firmware. # download the last default lime-config wget https://raw.githubusercontent.com/libremesh/lime-packages/ develop/packages/lime-system/files/etc/config/lime-defaults -O communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # modify it to your own needs, here some tips about this file [2] nano communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # And finally cook ./cooker ... --community=YOUR_COM_NAME/mp02-awd Once you are happy with the result, you can send a pull request to the network-profiles git repository [1] (so others can also use your tweaks). [1] https://github.com/libremesh/network-profiles [2] http://libremesh.org/docs/en_config.html Lastly, Elektra and Felix worked in tweaking the driver to allow to set the Coverage Class for the Ralink driver. Is there any way I can use in the cooker command their driver packages (that I have stored locally) instead of the ones in the repos? I guess it is just by replacing those within the binaries of the particular target, right? If the kernel is the same, then yes. As last libremesh release is using LEDE 17.02.2, it should be the case. But better ask them. Cheers. Thanks in advance carlos On 6 August 2017 at 16:03, Pau <pau(a)dabax.net> wrote:

On 06/08/17 10:26, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot for wanting to help. I've only being able to get to this today. I installed the building environment, and tried to "cook"

the

firmware following some directions Nico Echaniz gave me over the chat. We ended up agreeing using this command: ./cooker -c ar71xx/generic --flavor=lime_default --profile=dragino2 --extra-pkg="kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb" At the beginning of the output I get: ./cooker: unrecognized option '--extra-pkg=kmod-rt2800-lib

kmod-rt2800-usb

kmod-rt2x00-lib kmod-rt2x00-usb'

So, the cooker builds a firmware that works, but only using the primary radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in the section

"For

"Modify

libremesh

> firmware. Is the MP02-AWM supported by an official target of LEDE? I

see

> the Dragino2 target [1], have you tried it? > > For any kind of firmware customization I encourage you to use the

lime-sdk

Potatoes

> (based on Dragino MS14) that I had with me. In Zenzeleni we've been

using

> MPs and VillageTelco firmware from the beginning, and although they are > "very Plug & Play" and easy to use for non-geeks, I was pretty

impressed by

> LiMe. What you have done making IP disappear is quite something as it

> one of the concepts people struggle with the most. > > So now, we are seriously considering using LiMe at Zenzeleni. However,

> need a bit of guidance on creating a built for the MP02-AWD which is

the

> hardware we have in our networks. It is based on the Dragino MS14, so

the

> internal radio works from scratch after flashing. However, I'd like to

add

> the secondary radio (ralink usb) to the build, and have the wireless

config

<+27%2076%20986%203633>

> Skype: carlos.reymoreno Twitter: Creym > > > _______________________________________________ > lime-dev mailing listlime-dev@lists.libremesh.orghttps://

lists.libremesh.org/mailman/listinfo/lime-dev

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

-- ./p4u _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

-- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net https://www.youtube.com/watch?v=YxTPSWMX26M Cel: +27 (0) 76 986 3633 <+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing listlime-dev@lists.libremesh.orghttps://lists.libremesh.org/mailman/listinfo/lime-dev _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

pau

15 Aug 15 Aug

11:38 a.m.

On 08/14/17 11:33, Carlos Rey-Moreno wrote:

...

Can you fork the repository network-profiles (to your github account or any other git server) and upload (push) the files you are using to create your community firmware? So I can reproduce it on my local setup and check what's going on. How do you flash the routers? Do you use "sysupgrade -n"? or uncheck the option "keep settings" from the web interface?

...

Thanks again, carlos On 12 August 2017 at 20:16, pau <pau(a)dabax.net <mailto:pau@dabax.net>> wrote: On 08/10/17 16:27, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot! It does work that way and the 2 radios are up and configured automatically. However, the firmware does the same with both, i.e. create the APs and the mesh. I could modify that by tweaking the /etc/config/wireless, but is there anyway that can be done from the "cooker"? I believe that requires creating a community. What are the steps to do that? https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/… <https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/lime-system/files/etc/config/lime-defaults>

Yes, the best is to create a community. You can use your own repository (and modify cooker's options.conf) or use the default one [1]. # clone the communities and list them ./cooker --communities # create your own and the /etc/config directory mkdir -p communities/YOUR_COM_NAME/mp02-awd/etc/config/ # Any file you put on communities/YOUR_COM_NAME/mp02-awd will be added to the resulting firmware. # download the last default lime-config wget https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/… <https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/lime-system/files/etc/config/lime-defaults> -O communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # modify it to your own needs, here some tips about this file [2] nano communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # And finally cook ./cooker ... --community=YOUR_COM_NAME/mp02-awd Once you are happy with the result, you can send a pull request to the network-profiles git repository [1] (so others can also use your tweaks). [1] https://github.com/libremesh/network-profiles <https://github.com/libremesh/network-profiles> [2] http://libremesh.org/docs/en_config.html <http://libremesh.org/docs/en_config.html>

If the kernel is the same, then yes. As last libremesh release is using LEDE 17.02.2, it should be the case. But better ask them. Cheers.

Thanks in advance carlos On 6 August 2017 at 16:03, Pau <pau(a)dabax.net <mailto:pau@dabax.net>> wrote: On 06/08/17 10:26, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot for wanting to help. I've only being

able to get to

this today. I installed the building environment, and tried

to "cook" the

firmware following some directions Nico Echaniz gave me

over the chat.

We ended up agreeing using this command: ./cooker -c ar71xx/generic --flavor=lime_default

--profile=dragino2

--extra-pkg="kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb" At the beginning of the output I get: ./cooker: unrecognized option '--extra-pkg=kmod-rt2800-lib

kmod-rt2800-usb

kmod-rt2x00-lib kmod-rt2x00-usb'

So, the cooker builds a firmware that works, but only using

the primary

radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in

the section "For

a casual cooking on a existing feed repository". ./cooker

-f returns

-> Feeds already downloaded, doing nothing. Use --force to

reinstall

but I don't know how to continue from there, as I don't

know how to "Modify

the source code of the existing feed" Any way to get around this? best, carlos On 1 August 2017 at 00:40, pau <pau(a)dabax.net

<mailto:pau@dabax.net>> wrote:

> Hi Carlos. > > I like to help you, but I like to know if you tried

already some libremesh

> firmware. Is the MP02-AWM supported by an official target

of LEDE? I see

> the Dragino2 target [1], have you tried it? > > For any kind of firmware customization I encourage you to

use the lime-sdk

> "cooker" [2]. Are you familiar with it? > > Cheers. > > [1] http://repo.libremesh.org/current/targets/ar71xx/

<http://repo.libremesh.org/current/targets/ar71xx/>

> generic/dragino2/lime_default/ > > [2] https://github.com/libremesh/lime-sdk

<https://github.com/libremesh/lime-sdk>

> > > On 07/27/17 17:55, Carlos Rey-Moreno wrote: > > Hi everyone, > > I've following the list for quite some time and it was

only in the last

> month that I got myself together and installed LiMe in

some Mesh Potatoes

> (based on Dragino MS14) that I had with me. In Zenzeleni

we've been using

> MPs and VillageTelco firmware from the beginning, and

although they are

> "very Plug & Play" and easy to use for non-geeks, I was

pretty impressed by

> LiMe. What you have done making IP disappear is quite

something as it is

> one of the concepts people struggle with the most. > > So now, we are seriously considering using LiMe at

Zenzeleni. However, we

> need a bit of guidance on creating a built for the

MP02-AWD which is the

> hardware we have in our networks. It is based on the

Dragino MS14, so the

> internal radio works from scratch after flashing. However,

I'd like to add

> the secondary radio (ralink usb) to the build, and have

the wireless config

> files modified accordingly, so it works directly after

being flashed.

<https://www.youtube.com/watch?v=YxTPSWMX26M>

> Cel: +27 (0) 76 986 3633

<tel:%2B27%20%280%29%2076%20986%203633> <+27%2076%20986%203633>

> Skype: carlos.reymoreno Twitter: Creym > > > _______________________________________________ > lime-dev mailing listlime-dev(a)lists.libremesh

<mailto:listlime-dev@lists.libremesh>.orghttps://lists.libremesh.org/mailman/listinfo/lime-dev <http://lists.libremesh.org/mailman/listinfo/lime-dev>

> > > > _______________________________________________ > lime-dev mailing list > lime-dev(a)lists.libremesh.org

<mailto:lime-dev@lists.libremesh.org>

> https://lists.libremesh.org/mailman/listinfo/lime-dev

<https://lists.libremesh.org/mailman/listinfo/lime-dev>

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org

<mailto:lime-dev@lists.libremesh.org>

https://lists.libremesh.org/mailman/listinfo/lime-dev

<https://lists.libremesh.org/mailman/listinfo/lime-dev>

-- ./p4u _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev> -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> https://www.youtube.com/watch?v=YxTPSWMX26M <https://www.youtube.com/watch?v=YxTPSWMX26M> Cel: +27 (0) 76 986 3633 <tel:+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev>

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev> -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> https://www.youtube.com/watch?v=YxTPSWMX26M Cel: +27 (0) 76 986 3633 Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

Carlos Rey-Moreno

8:20 p.m.

Hi Pau, thanks again, answers below carlos On 15 August 2017 at 13:38, pau <pau(a)dabax.net> wrote:

...

On 08/14/17 11:33, Carlos Rey-Moreno wrote: Thanks a lo Pau, I've gone through the steps and played with some options, but I seem to be doing something wrong. I created two new firmwares (in both changing LibreMesh.org for Zenzeleni in the SSID to make sure it worked, which it did): 1. Added the following at the end of lime-defaults config wifi radio0 list modes 'ieee80211s' option channel_5ghz '157' config wifi radio1 list modes 'ap' option channel_2ghz '1' And it had no effect. Both radios appeared configured for AP and Mesh 2. Similar to the above but comments the following of lime-defaults config lime wifi # option channel_2ghz '11' # option channel_5ghz '48' option htmode_5ghz 'HT40' option distance '1000' # list modes 'ap' # list modes 'apname' # list modes 'ieee80211s' And I couldn't enter the router via WiFi anymore... any suggestion? Can you fork the repository network-profiles (to your github account or any other git server) and upload (push) the files you are using to create your community firmware? So I can reproduce it on my local setup and check what's going on.

https://github.com/creym/network-profiles

...

How do you flash the routers? Do you use "sysupgrade -n"? or uncheck the option "keep settings" from the web interface?

I uncheck the option "keep settings" from the web interface

...

Thanks again, carlos On 12 August 2017 at 20:16, pau <pau(a)dabax.net> wrote:

On 08/10/17 16:27, Carlos Rey-Moreno wrote: Hi Pau, thanks a lot! It does work that way and the 2 radios are up and configured automatically. However, the firmware does the same with both, i.e. create the APs and the mesh. I could modify that by tweaking the /etc/config/wireless, but is there anyway that can be done from the "cooker"? I believe that requires creating a community. What are the steps to do that? https://raw.githubusercontent.com/libremesh/lime-packages/de velop/packages/lime-system/files/etc/config/lime-defaults Yes, the best is to create a community. You can use your own repository (and modify cooker's options.conf) or use the default one [1]. # clone the communities and list them ./cooker --communities # create your own and the /etc/config directory mkdir -p communities/YOUR_COM_NAME/mp02-awd/etc/config/ # Any file you put on communities/YOUR_COM_NAME/mp02-awd will be added to the resulting firmware. # download the last default lime-config wget https://raw.githubusercontent.com/libremesh/lime-packages/de velop/packages/lime-system/files/etc/config/lime-defaults -O communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # modify it to your own needs, here some tips about this file [2] nano communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # And finally cook ./cooker ... --community=YOUR_COM_NAME/mp02-awd Once you are happy with the result, you can send a pull request to the network-profiles git repository [1] (so others can also use your tweaks). [1] https://github.com/libremesh/network-profiles [2] http://libremesh.org/docs/en_config.html Lastly, Elektra and Felix worked in tweaking the driver to allow to set the Coverage Class for the Ralink driver. Is there any way I can use in the cooker command their driver packages (that I have stored locally) instead of the ones in the repos? I guess it is just by replacing those within the binaries of the particular target, right? If the kernel is the same, then yes. As last libremesh release is using LEDE 17.02.2, it should be the case. But better ask them. Cheers. Thanks in advance carlos On 6 August 2017 at 16:03, Pau <pau(a)dabax.net> wrote:

On 06/08/17 10:26, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot for wanting to help. I've only being able to get

this today. I installed the building environment, and tried to "cook"

the

kmod-rt2800-usb

kmod-rt2x00-lib kmod-rt2x00-usb'

So, the cooker builds a firmware that works, but only using the primary radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg appears in the section

"For

"Modify

libremesh

> firmware. Is the MP02-AWM supported by an official target of LEDE? I

see

> the Dragino2 target [1], have you tried it? > > For any kind of firmware customization I encourage you to use the

lime-sdk

last

> month that I got myself together and installed LiMe in some Mesh

Potatoes

> (based on Dragino MS14) that I had with me. In Zenzeleni we've been

using

> MPs and VillageTelco firmware from the beginning, and although they

are

> "very Plug & Play" and easy to use for non-geeks, I was pretty

impressed by

> LiMe. What you have done making IP disappear is quite something as it

> one of the concepts people struggle with the most. > > So now, we are seriously considering using LiMe at Zenzeleni.

However, we

> need a bit of guidance on creating a built for the MP02-AWD which is

the

> hardware we have in our networks. It is based on the Dragino MS14, so

the

> internal radio works from scratch after flashing. However, I'd like

to add

> the secondary radio (ralink usb) to the build, and have the wireless

config

lists.libremesh.org/mailman/listinfo/lime-dev

> > > > _______________________________________________ > lime-dev mailing list > lime-dev(a)lists.libremesh.org > https://lists.libremesh.org/mailman/listinfo/lime-dev > _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

-- ./p4u _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

pau

20 Aug 20 Aug

7:19 p.m.

Hi Carlos. I've tested it and I found the problem. The file /etc/config/lime-defaults has the default options for the system, but specific options (like config wifi radio0) are not taken into account. The specific options must go to /etc/config/lime (I'll check with the others developers if we should change this behavior). So in addition to lime-defaults you have to include also a lime config file in your network-profile with the specific options for the radios and the empty entries for the global options. The rest of the options will be taken from lime-defaults on the first boot (when running lime-config command). So here the two files that worked for me: ##### /etc/config/lime config lime system config lime network config lime wifi config wifi radio1 list modes 'ap' option channel_2ghz '1' option channel_5ghz '48' config wifi radio0 list modes 'ieee80211s' option channel_2ghz '1' option channel_5ghz '157' ##### /etc/config/lime-defaults config lime system option hostname 'LiMe-%M4%M5%M6' option domain 'lan' option keep_on_upgrade 'libremesh base-files-essential /etc/sysupgrade.conf' config lime network option primary_interface eth0 option main_ipv4_address '10.%N1.0.0/16' option main_ipv6_address '2a00:1508:0a%N1:%N200::/64' option bmx6_mtu '1500' list protocols ieee80211s list protocols lan list protocols anygw list protocols batadv:%N1 list protocols bmx6:13 list resolvers 4.2.2.2 # b.resolvers.Level3.net list resolvers 141.1.1.1 # cns1.cw.net list resolvers 2001:470:20::2 # ordns.he.net option bmx6_over_batman false option bmx6_pref_gw none option bmx7_over_batman false option anygw_mac "aa:aa:aa:%N1:%N2:aa" config lime wifi option channel_2ghz '11' option channel_5ghz '48' option htmode_5ghz 'HT40' option distance '1000' list modes 'ap' list modes 'apname' list modes 'ieee80211s' option ap_ssid 'Zenzeleni' option apname_ssid 'Zenzeleni/%H' option adhoc_ssid 'LiMe' option adhoc_bssid 'ca:fe:00:c0:ff:ee' option adhoc_mcast_rate_2ghz '24000' option adhoc_mcast_rate_5ghz '6000' option ieee80211s_mesh_fwding '0' option ieee80211s_mesh_id 'LiMe' On 08/15/17 22:20, Carlos Rey-Moreno wrote:

...

Hi Pau, thanks again, answers below carlos On 15 August 2017 at 13:38, pau <pau(a)dabax.net <mailto:pau@dabax.net>> wrote: On 08/14/17 11:33, Carlos Rey-Moreno wrote:

Can you fork the repository network-profiles (to your github account or any other git server) and upload (push) the files you are using to create your community firmware? So I can reproduce it on my local setup and check what's going on. https://github.com/creym/network-profiles How do you flash the routers? Do you use "sysupgrade -n"? or uncheck the option "keep settings" from the web interface? I uncheck the option "keep settings" from the web interface

Thanks again, carlos On 12 August 2017 at 20:16, pau <pau(a)dabax.net <mailto:pau@dabax.net>> wrote: On 08/10/17 16:27, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot! It does work that way and the 2 radios are up and configured automatically. However, the firmware does the same with both, i.e. create the APs and the mesh. I could modify that by tweaking the /etc/config/wireless, but is there anyway that can be done from the "cooker"? I believe that requires creating a community. What are the steps to do that? https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/… <https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/lime-system/files/etc/config/lime-defaults>

Yes, the best is to create a community. You can use your own repository (and modify cooker's options.conf) or use the default one [1]. # clone the communities and list them ./cooker --communities # create your own and the /etc/config directory mkdir -p communities/YOUR_COM_NAME/mp02-awd/etc/config/ # Any file you put on communities/YOUR_COM_NAME/mp02-awd will be added to the resulting firmware. # download the last default lime-config wget https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/… <https://raw.githubusercontent.com/libremesh/lime-packages/develop/packages/lime-system/files/etc/config/lime-defaults> -O communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # modify it to your own needs, here some tips about this file [2] nano communities/YOUR_COM_NAME/mp02-awd/etc/config/lime-defaults # And finally cook ./cooker ... --community=YOUR_COM_NAME/mp02-awd Once you are happy with the result, you can send a pull request to the network-profiles git repository [1] (so others can also use your tweaks). [1] https://github.com/libremesh/network-profiles <https://github.com/libremesh/network-profiles> [2] http://libremesh.org/docs/en_config.html <http://libremesh.org/docs/en_config.html>

If the kernel is the same, then yes. As last libremesh release is using LEDE 17.02.2, it should be the case. But better ask them. Cheers.

Thanks in advance carlos On 6 August 2017 at 16:03, Pau <pau(a)dabax.net <mailto:pau@dabax.net>> wrote: On 06/08/17 10:26, Carlos Rey-Moreno wrote:

Hi Pau, thanks a lot for wanting to help. I've only

being able to get to

this today. I installed the building environment, and

tried to "cook" the

firmware following some directions Nico Echaniz gave

me over the chat.

We ended up agreeing using this command: ./cooker -c ar71xx/generic --flavor=lime_default

--profile=dragino2

--extra-pkg="kmod-rt2800-lib kmod-rt2800-usb

kmod-rt2x00-lib

kmod-rt2x00-usb" At the beginning of the output I get: ./cooker: unrecognized option

'--extra-pkg=kmod-rt2800-lib kmod-rt2800-usb

kmod-rt2x00-lib kmod-rt2x00-usb'

So, the cooker builds a firmware that works, but only

using the primary

radio, the Ralink one does not get configured. In the github link that you sent me --extra-pkg

appears in the section "For

a casual cooking on a existing feed repository".

./cooker -f returns

-> Feeds already downloaded, doing nothing. Use

--force to reinstall

but I don't know how to continue from there, as I

don't know how to "Modify

the source code of the existing feed" Any way to get around this? best, carlos On 1 August 2017 at 00:40, pau <pau(a)dabax.net

<mailto:pau@dabax.net>> wrote:

> Hi Carlos. > > I like to help you, but I like to know if you tried

already some libremesh

> firmware. Is the MP02-AWM supported by an official

target of LEDE? I see

> the Dragino2 target [1], have you tried it? > > For any kind of firmware customization I encourage

you to use the lime-sdk

> "cooker" [2]. Are you familiar with it? > > Cheers. > > [1] http://repo.libremesh.org/current/targets/ar71xx/

<http://repo.libremesh.org/current/targets/ar71xx/>

> generic/dragino2/lime_default/ > > [2] https://github.com/libremesh/lime-sdk

<https://github.com/libremesh/lime-sdk>

> > > On 07/27/17 17:55, Carlos Rey-Moreno wrote: > > Hi everyone, > > I've following the list for quite some time and it

was only in the last

> month that I got myself together and installed LiMe

in some Mesh Potatoes

> (based on Dragino MS14) that I had with me. In

Zenzeleni we've been using

> MPs and VillageTelco firmware from the beginning, and

although they are

> "very Plug & Play" and easy to use for non-geeks, I

was pretty impressed by

> LiMe. What you have done making IP disappear is quite

something as it is

> one of the concepts people struggle with the most. > > So now, we are seriously considering using LiMe at

Zenzeleni. However, we

> need a bit of guidance on creating a built for the

MP02-AWD which is the

> hardware we have in our networks. It is based on the

Dragino MS14, so the

> internal radio works from scratch after flashing.

However, I'd like to add

> the secondary radio (ralink usb) to the build, and

have the wireless config

> files modified accordingly, so it works directly

after being flashed.

<https://www.youtube.com/watch?v=YxTPSWMX26M>

> Cel: +27 (0) 76 986 3633

<tel:%2B27%20%280%29%2076%20986%203633> <+27%2076%20986%203633>

> Skype: carlos.reymoreno Twitter: Creym > > > _______________________________________________ > lime-dev mailing listlime-dev(a)lists.libremesh

<mailto:listlime-dev@lists.libremesh>.orghttps://lists.libremesh.org/mailman/listinfo/lime-dev <http://lists.libremesh.org/mailman/listinfo/lime-dev>

> > > > _______________________________________________ > lime-dev mailing list > lime-dev(a)lists.libremesh.org

<mailto:lime-dev@lists.libremesh.org>

> https://lists.libremesh.org/mailman/listinfo/lime-dev

<https://lists.libremesh.org/mailman/listinfo/lime-dev>

> _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org

<mailto:lime-dev@lists.libremesh.org>

https://lists.libremesh.org/mailman/listinfo/lime-dev

<https://lists.libremesh.org/mailman/listinfo/lime-dev>

-- ./p4u _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev> -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> https://www.youtube.com/watch?v=YxTPSWMX26M <https://www.youtube.com/watch?v=YxTPSWMX26M> Cel: +27 (0) 76 986 3633 <tel:+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev>

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev> -- Carlos Rey-Moreno, PhD PostDoctoral Fellow University of the Western Cape Zenzeleni Networks: zenzeleni.net <http://zenzeleni.net> https://www.youtube.com/watch?v=YxTPSWMX26M <https://www.youtube.com/watch?v=YxTPSWMX26M> Cel: +27 (0) 76 986 3633 <tel:+27%2076%20986%203633> Skype: carlos.reymoreno Twitter: Creym _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org <mailto:lime-dev@lists.libremesh.org> https://lists.libremesh.org/mailman/listinfo/lime-dev <https://lists.libremesh.org/mailman/listinfo/lime-dev>

2680

days inactive

2704

days old

lime-dev@lists.libremesh.org

Manage subscription

9 comments

3 participants

tags (0)

participants (3)

Carlos Rey-Moreno
pau
Pau