14 Aug
2017
14 Aug
'17
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:
--
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
Skype: carlos.reymoreno Twitter: Creym
On 06/08/17 10:26, Carlos Rey-Moreno wrote:
--
./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
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'
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:
> 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 <%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
_______________________________________________
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