7 Apr
2015
7 Apr
'15
5:19 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi everyone ;) I'm writing to the users list of Libre Mesh to announce
that we are starting a mesh network in Oaxaca de Juarez, Mexico.
I met Guido some months ago, and after hearing what has been done with
Alter Mundi in Argentina we decided to base our network on the Libre
Mesh firmware.
We already got 10 TL-WDR3500 to start experimenting. We did some
initial tests with flashing the standard firmware and everything seems
to work es expected :)
We'll try to go with the default network topology and see if it scales
appropriately. Any tips/tricks/insights? What are the canonical next
steps?
Cheers
Ciaby
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVJBGCAAoJEPU83OtbD4fQUw0P/j/qidZK0xSZ0BnYcgzlAw4F
Lf9/1qySn/ZrqVl9AxCUNMgabQf0wnMR/qyn4m/doDQm+rZFnTj12eSt2RkGb3Ab
bjzBhVzsbkUmrXvaGvqJGJ2SmmaiiKPck/FtZAts0Pr6Z3Lxy9QiGHhnkBg2hkUL
XJIZ25pHm9CEmP9cU5NcDiV2POSIgx0VqEcX4GRje1M2T6LQn9wnjIThKdK8z5yj
d/N5KPfXFllSTbPQilHEbQEydBf1gJPbmR/hcGNE7VV2DgFlLVlCgKZDkqbeNcKP
CP0tOiKHX6UFZNEIHDT7gNu1yQqM/LSmFegem+gfeCUFHUpKTBBga7fIs2pw0DSh
z+DV1Cho4L+OTpL0+QVP9oZ6gkVkUJxaT4TahJOcJGQzITpeq+e2ZgD+tmDgkB06
tJMjeFhNVd+aHTAHss7hIQIr6OOcwx0NLSPvRkpP1bawiqXG9nXXLgEPLTBGf7xu
KFPe3GmWEWvVlzmbxFEmBONpX6fYtg29kccwteuvtSCxdmkte/dME3GkmjyXFJSz
4n9BM5g6Ix99nwwuJX9Ln7E/N+DtGOkdm3FwdcgNZdWqd8TywFgpP5L4tVqAAYqa
oEuMo7bqqRvhkxBNG1xawQstt2QXKEaZCx13aw7m5E0dlP/QVqn5nQMM0mw2aSp6
VY1dmXCCrGnYH2DSBN2m
=IFzl
-----END PGP SIGNATURE-----
7 Apr
7 Apr
7:14 p.m.
Hello Ciaby.
Congratulations for your new mesh network project.
The next steps are just find locations to install nodes and build the
actual network :)
If the network grows big (lets say >50 nodes) you should start splitting
the layer2 by changing the libre-mesh SSID or the libre-mesh network ID.
Something you can test in your laboratory. Batman advance should not see
all the nodes in the network but Bmx6 should do it. So from a layer3
vision everything will work as expected.
Good luck and tell us more please.
On 07/04/15 19:19, Ciaby wrote:
Hi everyone ;) I'm writing to the users list of
Libre Mesh to announce
that we are starting a mesh network in Oaxaca de Juarez, Mexico.
I met Guido some months ago, and after hearing what has been done with
Alter Mundi in Argentina we decided to base our network on the Libre
Mesh firmware.
We already got 10 TL-WDR3500 to start experimenting. We did some
initial tests with flashing the standard firmware and everything seems
to work es expected :)
We'll try to go with the default network topology and see if it scales
appropriately. Any tips/tricks/insights? What are the canonical next
steps?
Cheers
Ciaby
_______________________________________________
users mailing list
users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
--
./p4u
24 May
24 May
8:40 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 04/07/2015 02:14 PM, Pau wrote:
Hello Ciaby. Congratulations for your new mesh network
project.
The next steps are just find locations to install nodes and build
the actual network :)
If the network grows big (lets say >50 nodes) you should start
splitting the layer2 by changing the libre-mesh SSID or the
libre-mesh network ID. Something you can test in your laboratory.
Batman advance should not see all the nodes in the network but
Bmx6 should do it. So from a layer3 vision everything will work as
expected.
Good luck and tell us more please.
Ok, we're trying to setup the first nodes,
and it's not working...
Doesn't matter what I do with the web interface, the configuration is
not applied.
I can see the /etc/config/lime file being updated, but running
manually lime-config produces this:
root@LiMeNode-5e925b:/etc/config# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:37: attempt to call field 'Hex' (a nil
value)
stack traceback:
/usr/lib/lua/lime/network.lua:197: in function 'Hex'
/usr/lib/lua/lime/network.lua:37: in function 'generate_host'
/usr/lib/lua/lime/network.lua:67: in function 'primary_address'
/usr/lib/lua/lime/proto/lan.lua:14: in function 'configure'
/usr/lib/lua/lime/network.lua:196: in function
</usr/lib/lua/lime/network.lua:196>
[C]: in function 'xpcall'
/usr/lib/lua/lime/network.lua:196: in function
</usr/lib/lua/lime/network.lua:182>
[C]: in function 'xpcall'
/usr/bin/lime-config:13: in function 'main'
/usr/bin/lime-config:29: in main chunk
[C]: ?
/usr/lib/lua/lime/network.lua:37: attempt to call field 'Hex' (a nil
value)
stack traceback:
/usr/lib/lua/lime/network.lua:197: in function 'Hex'
/usr/lib/lua/lime/network.lua:37: in function 'generate_host'
/usr/lib/lua/lime/network.lua:67: in function 'primary_address'
/usr/lib/lua/lime/proto/anygw.lua:15: in function 'configure'
/usr/lib/lua/lime/network.lua:196: in function
</usr/lib/lua/lime/network.lua:196>
[C]: in function 'xpcall'
/usr/lib/lua/lime/network.lua:196: in function
</usr/lib/lua/lime/network.lua:182>
[C]: in function 'xpcall'
/usr/bin/lime-config:13: in function 'main'
/usr/bin/lime-config:29: in main chunk
[C]: ?
/usr/lib/lua/lime/network.lua:37: attempt to call field 'Hex' (a nil
value)
stack traceback:
/usr/lib/lua/lime/network.lua:197: in function 'Hex'
/usr/lib/lua/lime/network.lua:37: in function 'generate_host'
/usr/lib/lua/lime/network.lua:67: in function 'primary_address'
/usr/lib/lua/lime/proto/bmx6.lua:18: in function 'configure'
/usr/lib/lua/lime/network.lua:196: in function
</usr/lib/lua/lime/network.lua:196>
[C]: in function 'xpcall'
/usr/lib/lua/lime/network.lua:196: in function
</usr/lib/lua/lime/network.lua:182>
[C]: in function 'xpcall'
/usr/bin/lime-config:13: in function 'main'
/usr/bin/lime-config:29: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Googling around, I found out that the .Hex method has been removed
from luci.ip. That probably means that LiMe is broken at the moment.
Any bugfix/workaround?
We're using the latest compiled firmware from
http://downloads.libre-mesh.org on the TL-WDR3500. (this ->
http://downloads.libre-mesh.org/firmware/TplinkWDR3500-LiMe_develop-sysu
pgrade-20150430_1629.bin).
Btw, the /etc/rc.d/lime-rc script seems a bit pointless to me:
RCDIR=/etc/lime-rc.d
start() {
for s in $RCDIR/*; do
[ -x "$s" ] && {
echo "Executing script $s"
$s
}
done
}
And then:
root@LiMeNode-5e925b:/etc/init.d# ls /etc/lime-rc.d
ls: /etc/lime-rc.d: No such file or directory
Cheers
Ciaby
P.S. Is there a stable branch somewhere? Or at least the last known
working revision? :)
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVYjdWAAoJEPU83OtbD4fQX7UP/iNUlbz9OjTLdRG2jCrTtFia
Dszmx1vJkBZm5Xvow0UylmUheQ/lCLyFgLOur4u32Wy7l2+Sm6mRxZHJHDWGKumV
IEApoCk2QVkxEK+pafdHWUb32kmjpobaG0DSA52ugKmcXIJuId2WcP4eSGMu7Wsz
iEswFIUE7H79yq1XiBBOkqtB0qEyLwOFo1OOTRNj8LmXhfSTqrUaEpcDY6a+2V0D
y6gtSxNmVBP6PSW9CTPBYf1ti7+G2hs339DT76rVfFTEnz5TOJvVE25pQqmNURKq
ETI/VIQgg5qCacAPFTrNP2uBx73zVze1ps4SDU36EZ7WoeOYACzWaQTr/CyM3hBj
DWtdzwEIXuDqUT61X4xgjMLY1zihfahUioO8O6SAKIqgoF6VFvjHiER6RmPYe0s1
2uJDp9G6Ua3RThkJjVDTHz3I4BkU7U8cjrtCYPJ+OSTE3zlvKdrb23was4qq10cP
okhxWjzvJGfbuI8xlkqFWnGpk8nqChL/ABXTIsWh8rKUCDTp1X/LOCBkaeBffIy5
8SonnEaiKRbsFLmdk9RyGIbxKckFnOt0d0qjRgJZg6FvmjI4SdqkJh9k+4q2FiHw
UPJV73ZEpKhMbz2/to7oPO7xoWhCC+VIhVuvLDfTqCTj0Z8bvpE+fGNKU+NJDHNb
tVAlHl2NefbPs05r76xa
=icas
-----END PGP SIGNATURE-----
10:34 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 24/05/15 17:40, Ciaby wrote:
:( that's the broken-by-definition daily
builds...
> Cheers
> Ciaby P.S. Is there a stable branch
somewhere? Or at least the
> last known working revision? :)
i've been working precisely on this for the past week, and hope to be
done by today or tomorrow,
this is the most recent public build i've done
https://chef.altermundi.net/fwprofile/deltalibresocial-r42398-l2l3/
you can flash that, and then change /etc/config/lime-defaults
(you won't be able to telnet or ssh in, since it has authorized_pubkeys,
but you can login through the web interface with empty root password,
set one, and then ssh in)
and only if you're feeling brave... ;)
https://github.com/libre-mesh/lime-build/tree/sandbox/release/14.08
>
_______________________________________________ users mailing list
> users(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/users
-----BEGIN PGP
SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCgAGBQJVYlH2AAoJEIJqNBvBfxrIhYUP/1TW2/6GWBcs2PsNffnl7oWI
BVJtY7zwUEqXKL+QM1KUeBTkx44AiAQ5v9jWAWGS0fleHyrZHa2WASqyL2eYkl+7
NXbTKf4S308Ym6MwOGJob40gzMztnu78bFHlsu1CaHuyGERFMbVHhDJfesdoPSUk
+yG/Ngq2GUqgXD95QYD2eb6cPId1WhvvhzSYJhXgyotIBgpXt+JQWzZp5ke+ON0S
tTr6WJNKY6Qo+lVMd9pPCRBtuJYPzEbjP1D+JDSYhBybzVFb8l7NVkUsHV9qFj0x
qNrzVG0jaeWfnrcS4Xh4I2xpVbMrA7r06uaMgM6ycg1P1FNJZbzffnHuEyv/xgzg
jNqblfBKEDcYwJCw7/u1OD3pNGcJokAGKgg8gL2Iu26NMoCgT16U/N2yq5lDlNGK
JPFf4XuNxJkqbbKOQtVH4W1eo4ulOpIM5RycdqU0mCz0Wl9b4G8khM3VEeN8QKQp
jneVMmGB6QTpoIlsNcK5DwdRh5bPVuqn233wkxAJAAuFwFvcnZIAidyE5yuRLeej
QDBO51wGsPJ49uCFO3Ixn25THzicaIaoZ3Rnh2bGvCqQPLvLw7GIoTvJjkkiKP50
MDEhlnNR0veWLuov4qLU0CwSmbDG0OCyu9peqad4Ouh5xhQhl/T6wjDG2sIrIRqX
JrkOKAOtJ/ad5ZuzVLu2
=v0Yy
-----END PGP SIGNATURE-----
On 04/07/2015 02:14 PM, Pau wrote:
Hello Ciaby. Congratulations for your new mesh
network project.
We're using the latest compiled firmware from
http://downloads.libre-mesh.org on the TL-WDR3500. (this -
http://downloads.libre-mesh.org/firmware/TplinkWDR3500-LiMe_develop...
yeah
25 May
25 May
5:02 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 05/24/2015 05:34 PM, Gui Iribarren wrote:
Nice! Can I help in any way?
see... ;)
Cheers
Ciaby
On 24/05/15 17:40, Ciaby wrote:
yeah
On 04/07/2015 02:14 PM, Pau wrote:
> Hello Ciaby. Congratulations for your new mesh network
> project.
We're using the latest compiled firmware
from
http://downloads.libre-mesh.org on the TL-WDR3500. (this -
http://downloads.libre-mesh.org/firmware/TplinkWDR3500-LiMe_develop..
>
:( that's the broken-by-definition daily builds...
Great! :D
Ciaby P.S. Is
there a stable branch somewhere? Or at least the
last known working revision? :)
i've been working precisely on this for the past week, and hope to
be done by today or tomorrow, this is the most recent public build i've done
https://chef.altermundi.net/fwprofile/deltalibresocial-r42398-l2l3/
you can flash that, and then change /etc/config/lime-defaults (you
won't be able to telnet or ssh in, since it has
authorized_pubkeys, but you can login through the web interface
with empty root password, set one, and then ssh in)
Ok, I'll try this one
tonight.
I assume that the /etc/config/lime file is not working as expected... :)
and only if you're feeling brave... ;)
https://github.com/libre-mesh/lime-build/tree/sandbox/release/14.08
Let's
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVY1WsAAoJEPU83OtbD4fQ8IcP/2L6P89Q6EZfjYlzTKQpaTOt
13lJGqEnnmWO5DhtQ9ZrPUKrLaM576h+fMcbn1TLImvgxKC/YpPCeSpMHIStg7aX
6ZLlL3aujVtLvrLK7Y40SwQrAGegi/+Es8eIaFwg0ciuTADZiuxJ8O4SogBkcVmE
GohOq/NSYykCOtS0oVHSQZ/5JKAO6hADtRj0JbkOwXWMEhdHlx8hbw4eX9Vi+Kp0
W6SRc0R1HoenIsIBXi3Oqd9ueSw/eYufR1UVvdTWFxIvlaotpDf9Nrv7CzHPAf8r
dig3vu3cmRhNmN8ww33MLvNlXzWPYP9qDQMZEymt1FVVMl74ecSAcvYzAXZciZrC
byWomFvYPlFD7xKZyzvyprBhxaGHa8Vcr6HeVOtdwN0LF0cxlUVDe8/Jza3D8ecQ
ZgxB4YA7opJphdZPtA+s0LTY2lqakaiP5lGokLLFzOQmuilMxlhNd3zkhcTC4bWb
yd8qkTauxw6RXTHErvOmbGo0xs9SzbdE5iyIj0hgOuzFXBm4t6u8fQu3VOu/ESBJ
RqX74X5Jdh8M5JlopJZCKoe1coOf9e3dLT7UU4g3uqMiJSWdF305zf/mXepcdgvX
zuYlhEu8lYyFnGZkYcD/OjcA7q0bIRBY1vNqgmFxHVi2nbyyjjsJZa3NRsiMCVBb
wZrsm1ZFDLWGuqwQeWjC
=RBO5
-----END PGP SIGNATURE-----
26 May
26 May
12:01 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 25/05/15 14:02, Ciaby wrote:
Let's
see... ;) Cheers
Ciaby
_______________________________________________ users mailing list
users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCgAGBQJVY7fAAAoJEIJqNBvBfxrItpoQAJRi3D8DRi2+ujvMc7Y8a8jX
UgndsaoMy6/tDhPN9W6EYY00lPriIPiDYcs03SlZdDnRS/ee1Z3cE/pusZwFVW42
OOiEdLo3QJRDqz2ydJG/GtUGjCc9f87cfvzfS+opKjpLUPhFwvsBGy7/qUcp6m2Q
F227bx93/lnAQi+Y6UU4BDvBeQmZclydZ2GwrxjEGNMNHO7KwNHZ1rm4qLTK1qxQ
zimggp6it6MKsf8+sPa8RhC72cU8dnkN7pWjPUGvaBoD3kFF7aWtnUUkSYwvl2Ew
FMmPesKqWgr2lCKS7hp9klesPOuQLqPQ2OY6D78+vReyn8W25RR1EYj20pTkv6/8
cyTwlOdKii42suD2iyatnwRLPmY2dmFiUD+BPzJTR5vRhOjQKNGDiYOkKl/p0Fgr
L3yyYlsq5R4m/77LHvRF7UZj6deObyQfuO/izTtHWRQAN09TTqlmDXXyzYi0n0lA
Pnt17T45umNhrBggs/tBVxTVt+Z5/YPNe69Q0eogf/Mb8PdVdDtoN4BB28WWWI/F
sVZJRAef7s6vrBDo2W96Kl81Y75uyiNkVpiUHvt3NiUVNJF/DRHyTigmg7u5WORZ
1440oHFSMN8DS4dk4I1IIbRbCwnDTcwfPcAED7kJbonaYSNKgp19wsFMS2dt1IPX
3POZIJS8/mGMManzkyhX
=g5KQ
-----END PGP SIGNATURE-----
On 05/24/2015 05:34 PM, Gui Iribarren wrote:
wait, /etc/config/lime is working fine for setting node-specific options
but general options are supposed to be set in
/etc/config/lime-defaults (i.e., the network-wise options, i.e. every
node of a particular cloud has an identical /etc/config/lime-defaults)
cheers and good luck!
gui
On 24/05/15 17:40, Ciaby wrote:
> On 04/07/2015 02:14 PM, Pau wrote:
>> Hello Ciaby. Congratulations for your new mesh network
>> project.
yeah
:( that's the broken-by-definition daily
builds...
Great! :D
> Ciaby P.S. Is there a stable branch
somewhere? Or at least the
> last known working revision? :)
i've been working precisely on this for the
past week, and hope
to be done by today or tomorrow,
Nice! Can I help in any way?
you can flash that, and then change /etc/config/lime-defaults (you
won't be able to telnet or ssh in, since it
has
authorized_pubkeys, but you can login through the web interface
with empty root password, set one, and then ssh in)
Ok, I'll try this one
tonight. I assume that the /etc/config/lime
file is not working as expected... :) and only if you're feeling brave... ;)
https://github.com/libre-mesh/lime-build/tree/sandbox/release/14.08
3:15 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
On 05/25/2015 12:02 PM, Ciaby wrote:
Ok, I just
followed your instructions, flashed the new firmware and
erased the old config. Ssh-ed in, modified /etc/config/lime-defaults,
run lime-config, and... it doesn't work ;)
Well, it doesn't throw an error, either, but most of the stuff in
/etc/config is untouched, and the only two modified files are 0 bytes each:
-rw-r--r-- 1 root root 220 Aug 13 2014 luci-bmx6
-rw-r--r-- 1 root root 717 Aug 13 2014 ucitrack
-rw-r--r-- 1 root root 1.2K Aug 14 2014 lime
-rw-r--r-- 1 root root 142 Feb 18 03:13 alfred
-rw-r--r-- 1 root root 0 Feb 18 03:13 ubootenv
-rw------- 1 root root 537 Feb 18 03:13 uhttpd
-rw-r--r-- 1 root root 141 Feb 18 03:13 batman-adv
-rw-r--r-- 1 root root 733 Feb 18 03:13 system
-rw-r--r-- 1 root root 1.6K Feb 18 03:13 snmpd
-rw-r--r-- 1 root root 1.5K Feb 18 03:13 wireless
-rw-r--r-- 1 root root 3.6K Feb 18 03:13 network
-rw-r--r-- 1 root root 645 Feb 18 03:13 luci
-rw-r--r-- 1 root root 436 Feb 18 03:13 libremap
-rw-r--r-- 1 root root 2.2K Feb 18 03:13 firewall
-rw-r--r-- 1 root root 919 Feb 18 03:13 dhcp
-rw-r--r-- 1 root root 62 Feb 18 03:16 dropbear
-rw-r--r-- 1 root root 1.6K Feb 18 03:19 lime-defaults
-rw-r--r-- 1 root root 0 Feb 18 03:23 bmx6
-rw-r--r-- 1 root root 0 Feb 18 03:23 6relayd
Am I doing something wrong?
this is the
most recent public build i've done
https://chef.altermundi.net/fwprofile/deltalibresocial-r42398-l2l3/
you can flash that, and then change /etc/config/lime-defaults (you
won't be able to telnet or ssh in, since it
has
authorized_pubkeys, but you can login through the web interface
with empty root password, set one, and then ssh in)
Ok, I'll try this one
tonight.
I assume that the /etc/config/lime file is not working as expected... :) > and only if you're feeling brave... ;)
> https://github.com/libre-mesh/lime-build/tree/sandbox/release/14.08
Ok, seems
like the only option now.
Cheers
Ciaby
P.S. attached is my lime-defaults file.
5:05 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 05/25/2015 10:15 PM, Ciaby wrote:
[...]
Ok, seems like the only option now.
...and I (kind of) bricked it! But good old failsafe mode helped me
recover it.
So, the image you linked works, but it's configured for Delta Libre
and lime-config doesn't do his job. Building a firmware from git only
makes things worse... Is there, anywhere, a decently stable version
with lime-config working?
Otherwise I'll go with the manual route, editing all the config files
by hand and repackaging it as an image. But, considering the fact that
I'm probably the only person technical enough to do it in my group,
and I'm about to leave, I would really, really like to give them
something more like:
flash this image, configure these parameters on the web interface, and
off you go!
If I can help in any way to make it happen, just let me know where to
start ;)
Cheers
Ciaby
> and only
if you're feeling brave... ;)
> https://github.com/libre-mesh/lime-build/tree/sandbox/release/14.08
>> -----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVY/78AAoJEPU83OtbD4fQUmsP/jGkMZZLPatcd05VWKVP1fSu
tQPpqIFgkMn3ae0e3jgOzNPIbP9K02Gm2tjKknL0m6MOTtRiMM5UNclMC9wZL9x2
DB1XxIf+8rg+ka/uZa9Fr0qib0MKAMz6t9FP57Ua1StQamP2tiH/y1lQlVkt2U7V
HjsVYFk6ULOskZ29VkLcuSAn4ysx6dHDt3dFQJbmlIP5WWRfEit3CoP31q/8QT7d
snbmBJdpljxlS97JBTeQtcrEAXITZwBF9e5Oa6eFYtsyJJFGCU6CrQQTVmmGFvn2
Um113+BVsp4oJt6Xftv8dtFjhqdOKYHtTo3Zy72AcyGnDLL6geiJo3JAnQGwqugg
qfAiV8FoHizKCR1XkKMHUqgWyc4lXwl0p0pT89aYpcMr0dEu+yJZzr7wXSqG4S7Q
mVHIOJQ9QBVJJVeGWI3+shHN+Z4GFK3dc7x2MH9pgEdVWEPFkCD5NC9NXNazZmWL
ZO8Q9jT0nB2i+J9NcGCByJziEMBcu3ax+zgLvbLLeTagPLX0o6bhvdOzuR3XEw0P
pBKsHQ9Csor35UWamigjZHpO1Rgu5uN/STrsFJDFSzdsTWdb8074oooovbDDEa//
pyx1S1/j4ud4cxoDOGR5wEgfX9zzOMk9+MF4kQMlLWnAhD4gecoeaTJenZEJR8x7
qYroNCR0ofQn8IQrHDYL
=YjnM
-----END PGP SIGNATURE-----
8:47 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
Hi all,
2015-05-26 5:15 GMT+02:00 Ciaby <ciaby(a)autistici.org>rg>:
On 05/25/2015 12:02 PM, Ciaby wrote:
> Gui wrote:
>> you can flash that, and then change /etc/config/lime-defaults
the correct file to modify is
/etc/config/lime
and not
/etc/config/lime-defaults
Modifying the file lime-defaults should have no effect when running lime-config.
I think that lime-defaults file is useless and we should remove it
from lime-system.
> I assume that the /etc/config/lime file is not
working as expected... :)
Which file are you modifying? lime or lime-defaults?
Ok, I just followed your instructions, flashed the new
firmware and
erased the old config. Ssh-ed in, modified /etc/config/lime-defaults,
run lime-config, and... it doesn't work ;)
Yep, lime-defaults is ignored by lime-config
So, the image you linked works, but it's
configured for Delta Libre
and lime-config doesn't do his job. Building a firmware from git only
makes things worse...
Worse... maybe... anyway you could try following this guide for
compiling your own image (without using lime-build):
[ENG] http://libre-mesh.org/projects/libre-mesh/wiki/Compile_Manually
[ITA] http://wiki.ninux.org/Libre-Mesh
Ciao!
Ilario
31 May
31 May
10:44 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
On Tuesday, May 26, 2015 10:47:44 AM Ilario wrote:
Right, you usually want to edit /etc/config/lime and not /etc/config/lime-
defaults
> Gui
wrote:
>> you can flash that, and then change /etc/config/lime-defaults
the correct file to modify is
/etc/config/lime
and not
/etc/config/lime-defaults Modifying the file lime-defaults should have no effect
when running
lime-config. I think that lime-defaults file is useless and we should
remove it from lime-system.
Wrong!
/etc/config/lime-defaults is not ignored, it is used often more than
/etc/config/lime, the difference is that lime-defaults is not supposed to be
edited by the user while /etc/config/lime is supposed to be edited by the user,
and that if a configuration is present both on lime and lime-defaults the one
in /etc/config/lime is preferred as it is supposed to be set by the user
> I assume that the /etc/config/lime file is
not working as expected... :)
Which file are you modifying? lime or lime-defaults?
Ok, I just followed your instructions, flashed
the new firmware and
erased the old config. Ssh-ed in, modified /etc/config/lime-defaults,
run lime-config, and... it doesn't work ;)
Yep, lime-defaults is ignored by lime-config
12:02 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
2015-05-31 12:44 GMT+02:00 Gio <gio(a)diveni.re>re>:
On Tuesday, May 26, 2015 10:47:44 AM Ilario wrote:
Oops, sorry for my wrong answer.
Yep, lime-defaults is ignored by lime-config
Wrong! /etc/config/lime-defaults is not ignored, it is used
often more than
/etc/config/lime, the difference is that lime-defaults is not supposed to be
edited by the user while /etc/config/lime is supposed to be edited by the user,
and that if a configuration is present both on lime and lime-defaults the one
in /etc/config/lime is preferred as it is supposed to be set by the user
Thanks, now it's quite clear.
I can't find any documentation about LiMe configuration (apart the
very basic one that I wrote in Italian [1] where there's also
explained that configuration from lime-defaults is always applied,
LOL! There is also another document in Italian written by NinuxBO
[2]).
I think it's time to have such a documentation, so I started a new
wiki page about configuration on libre-mesh website [3], you're
invited to contribute :D
Ciao!
Ilario
[1] http://wiki.ninux.org/Libre-Mesh#Configurazione
[2] https://wiki.bologna.ninux.org/mediawiki/index.php/CompilareDaOpenWrt
[3] https://libre-mesh.org/projects/libre-mesh/wiki/Configuration
1 Jun
1 Jun
9:54 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
hello libremesh team.
I've been following this thread and reading some comments. If the downloads from
libre-mesh server are broken because they are development builds, an image compiled
following this proccess
http://dev.libre-mesh.org/projects/libre-mesh/wiki/Compile_Manually will be broken too ?
thanks in advance.
From: iochesonome(a)gmail.com
Date: Sun, 31 May 2015 14:02:12 +0200
To: users(a)lists.libre-mesh.org
Subject: Re: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
2015-05-31 12:44 GMT+02:00 Gio <gio(a)diveni.re>re>:
On Tuesday, May 26, 2015 10:47:44 AM Ilario
wrote:
Oops, sorry for my wrong answer.
Yep, lime-defaults is ignored by lime-config
Wrong! /etc/config/lime-defaults is not ignored, it is
used often more than
/etc/config/lime, the difference is that lime-defaults is not supposed to be
edited by the user while /etc/config/lime is supposed to be edited by the user,
and that if a configuration is present both on lime and lime-defaults the one
in /etc/config/lime is preferred as it is supposed to be set by the user
Thanks, now it's quite clear.
I can't find any documentation about LiMe configuration (apart the
very basic one that I wrote in Italian [1] where there's also
explained that configuration from lime-defaults is always applied,
LOL! There is also another document in Italian written by NinuxBO
[2]).
I think it's time to have such a documentation, so I started a new
wiki page about configuration on libre-mesh website [3], you're
invited to contribute :D
Ciao!
Ilario
[1] http://wiki.ninux.org/Libre-Mesh#Configurazione
[2] https://wiki.bologna.ninux.org/mediawiki/index.php/CompilareDaOpenWrt
[3] https://libre-mesh.org/projects/libre-mesh/wiki/Configuration
_______________________________________________
users mailing list
users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
26 May
26 May
2:12 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 26/05/15 00:15, Ciaby wrote:
On 05/25/2015 12:02 PM, Ciaby wrote:
Ok, I just followed your
instructions, flashed the new firmware and
erased the old config. Ssh-ed in, modified
/etc/config/lime-defaults, run lime-config, and... it doesn't work
;) Well, it doesn't throw an error, either, but most of the stuff
in /etc/config is untouched, and the only two modified files are 0
bytes each:
"run lime-config" ... aaaand uci commit!
i.e.
lime-config && uci commit
all "uci set" done by lime-config are not actually applied, but only
staged so you can see them with "uci changes".
this is not actually documented anywhere, AFAIK, sorry :(
we should probably change this behaviour, and make lime-config do an uci
commit by default, unless told not to by some --no-commit argument or
whatever
this is
the most recent public build i've done
https://chef.altermundi.net/fwprofile/deltalibresocial-r42398-l2l3/
you can flash that, and then change /etc/config/lime-defaults
(you won't be able to telnet or ssh in, since it has
authorized_pubkeys, but you can login through the web interface
with empty root password, set one, and then ssh in)
Ok, I'll try this one
tonight. I assume that the
/etc/config/lime file is not working as expected... :)
-rw-r--r-- 1 root root 220 Aug 13 2014 luci-bmx6
-rw-r--r-- 1 root root 717 Aug 13 2014 ucitrack
-rw-r--r-- 1 root root 1.2K Aug 14 2014 lime
-rw-r--r-- 1 root root 142 Feb 18 03:13 alfred
-rw-r--r-- 1 root root 0 Feb 18 03:13 ubootenv
-rw------- 1 root root 537 Feb 18 03:13 uhttpd
-rw-r--r-- 1 root root 141 Feb 18 03:13 batman-adv
-rw-r--r-- 1 root root 733 Feb 18 03:13 system
-rw-r--r-- 1 root root 1.6K Feb 18 03:13 snmpd
-rw-r--r-- 1 root root 1.5K Feb 18 03:13 wireless
-rw-r--r-- 1 root root 3.6K Feb 18 03:13 network
-rw-r--r-- 1 root root 645 Feb 18 03:13 luci
-rw-r--r-- 1 root root 436 Feb 18 03:13 libremap
-rw-r--r-- 1 root root 2.2K Feb 18 03:13 firewall
-rw-r--r-- 1 root root 919 Feb 18 03:13 dhcp
-rw-r--r-- 1 root root 62 Feb 18 03:16 dropbear
-rw-r--r-- 1 root root 1.6K Feb 18 03:19
lime-defaults -rw-r--r-- 1 root root 0 Feb 18
03:23 bmx6 -rw-r--r-- 1 root root 0 Feb 18 03:23
6relayd
Am I doing something wrong?
Ok, seems like the only option now.
> and only if you're feeling brave... ;)
> https://github.com/libre-mesh/lime-build/tree/sandbox/release/14.08
>>
>> Cheers
Ciaby P.S. attached is my lime-defaults file.
_______________________________________________ users mailing list
users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCgAGBQJVZH9OAAoJEIJqNBvBfxrI6YQP/0Vp3Xsl2C07nnWUgHxqb08i
sMN0/zfot2L3ZbkdkQq2mfZ3Rnun1pOUqyRdtHYfruyT8k78bxIGZWO9lFw7K8/e
dK9W/DhW9lTcisbrovRXjHPMlIvA7nbyAoXyMZzACVAi7qMdmkHrgOk7HsR63bpt
t4so/EkylQMa/FRDbtt9ORrvG3nFPX7ZE6E+Lh+taZ0WQbKcL6ljOcbSgq218yux
P8FY8MS5U6YzPJ9Vj/0rdM2mehN31dWfcRWEimljPPnB5Ic+ZpSxZvyQ+MlhTKvT
NTFxcvFn0dcmC1LqopvI+PPCnMLQs5oAHhKVcfBHpeI8heqlhdeU161ggHQ0sKNe
w/NP81aUpUIf0CvrscnYfQCILrhzZDKN+2/2fBAfM/OL6u8f8TcEXE+qho438RLa
Z2IzWagtl9EwLIH/smXcE2ki7wxgYFNTR7PxfMqqIE5sXYEd9yAeOZgwdseRpzlX
4OxCCRVCE0rt2hvSFYsOUX1B0rPIUq0lnpCX2FBWzrqSx3q4ANXs0UllfokZkWwq
io7iYOn9aQbQdEcBGSnMrEvLWjxi8yRCUsQi5PEh9SyViqw6l9AnqFcj/YB+E0RP
Nw7ab3Dpk1L1eXCXcNJtgZO43dnClgH6RqX5JP+SpGqW8k0R3590PGYSM3JZUFr5
AoNw0Zyo25hBYMhtM32Q
=YT8+
-----END PGP SIGNATURE-----
27 May
27 May
6:35 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 05/26/2015 09:12 AM, Gui Iribarren wrote:
"run lime-config" ... aaaand uci commit!
i.e.
lime-config && uci commit
all "uci set" done by lime-config are not actually applied, but
only staged so you can see them with "uci changes".
this is not actually documented anywhere, AFAIK, sorry :(
we should probably change this behaviour, and make lime-config do
an uci commit by default, unless told not to by some --no-commit
argument or whatever
Yep, seems like a good idea to me ;)
Anyway, following your instructions I got it working.
Is there a more "stable" branch/build that I can follow?
Cheers
Ciaby
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVZg5pAAoJEPU83OtbD4fQIHIP/jDK8KbpzU8ZAjlZ+98aAgKs
8FNWum3n9qA3AyK4PJ0AIDSDNa3Xn4GzzZAICJHvguTNaSpqgj/zXgQb4lkjgKUX
3vwEpLDyc9C7xk7YTpMtnHZshXqRAPTHr/tzZb/mz04I4unsod3QcgXz8j0o8gkx
XizrEwGOuvm9RLkIrwrfooF3o3xzw0Y/wlSA3czGkawQvurBBGUT3j+DUSrmI6/m
qq4aXoUfDEw3hHrluLmQonHIZB0Ga9NuDULYqx9hNsj2415Jar8BAKr0bpwbsJ8X
WcTx0X1ziTKvH8x4IokNqlzdBLNhnt3qhT7P2C0sOfv6FsAHhwQvP7BphPZyG2Jd
FgdA8OrsXIgBh+/yYoH1IQBKbOGNCNW/BwyPTADCcyo1s6LnzppafCIEuf9K+Dz2
/vS5CL2BxUV7VqAbU59bbpCWEgyfoIpYOywQz+Ds3FYcVZCoWv0bhpw8EWA5QWj/
tbS68JOFrCZaENi9JvEyvHcPhhlLto0DNlyA/3MRrwrSNV5L2k/uC+Pl6Zrg3R+4
OGtAkpKoHEZLC70tA78Jr0KI7dcx4viV0DXtREwpUyh4YXICaJBxVYuOTw5D4a9D
3/bVYU9V3K7irv0J0B4GAwXep6FBTuiTZSKLnjdQ++B45Y0lGjiTOJjI/UaHN8+G
3S+/faMNoEf0GkANg2gr
=2U1G
-----END PGP SIGNATURE-----
13 Jun
13 Jun
2:30 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 27/05/15 15:35, Ciaby wrote:
On 05/26/2015 09:12 AM, Gui Iribarren wrote:
fixed!
https://github.com/libre-mesh/lime-packages/commit/b71fcdcf9ab93aa7992cd
1d366bb5747530cd9e7
"run lime-config" ... aaaand uci
commit! i.e.
lime-config && uci commit
all "uci set" done by lime-config are
not actually applied, but
only staged so you can see them with "uci changes".
this is not actually documented anywhere, AFAIK,
sorry :(
we should probably change this behaviour, and
make lime-config do
an uci commit by default, unless told not to by some --no-commit
argument or whatever
Yep, seems like a good idea to me ;) Anyway, following your instructions I got it working.
Is there a
more "stable" branch/build that I can follow?
http://blog.altermundi.net/article/libre-mesh-1504/
:D
will send a proper announcement later tomorrow
Cheers
Ciaby _______________________________________________ users mailing
list users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCgAGBQJVe5W3AAoJEIJqNBvBfxrImksP/0T4E0h/odO4QO0vdU3yaI4t
NbV2Hmt/mhOzop2rVs7v/NOYewofOddMTeQFdQwVaTBjdGSKHps56nwOySxp+tgP
zNqEB2CuInxlL+1PSxQ9pRPxGN7ips/Q4S5LssubGbwubSdJDVRi45jh3admHS90
F7WEh5t4ykKcbsrzePvRKwV/T4M0VukuRlIEO/ZQBJmiPWO+Gi/4KlJi7IvnSouV
+5Gv0Keq3idHXAeiWoC/gyY9CsxrTIQnOFmJMcbixPAr56qstmbDhHZS2o0JBacs
sTJV0hEL6wz0SlS2P/Mh58l/8vex4BNAPYL6NUDFZVcdbgwg2DRkZXq8leny09+l
/SfmydVAh+au5lMLsTNITMfHXiMJnzZOzHyeK2RTV9DLsjQp4149R2+xQHRTcXKH
Lsmcwepjs3YVtNMhrUqneb4UoNLsF0MGeK1mYxLb7w80M6l56yiWKFnsTS3qgeDe
+7VMq0viQ8TrKtzORDhlDX0p4bU5IPhu9jhx45L9U7lYuxIPLgHk7KfjPIc92aFj
sZMXdyT/6EwBtA60vvciSPI1jZheIzebNJ+sW16mU7q1PfePMzqewrlGbiIqHGSO
W/9nQVeenFo5fF7ltWxXkqu8l3+/lpRdoGhqkJcQvyuzaZc+Mfk6LgQ5VLRiAXZ7
yzs30WqY3PhUEUod0Q6J
=7k0E
-----END PGP SIGNATURE-----
12:29 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
really good news to see the first stable version of libre-mesh, congrats ! compiling from
sources.
regards
Leonardo Taborda
networkbogota.org
Date: Fri, 12 Jun 2015 23:30:16 -0300
From: gui(a)altermundi.net
To: users(a)lists.libre-mesh.org
Subject: Re: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 27/05/15 15:35, Ciaby wrote:
On 05/26/2015 09:12 AM, Gui Iribarren wrote:
fixed!
https://github.com/libre-mesh/lime-packages/commit/b71fcdcf9ab93aa7992cd
1d366bb5747530cd9e7
"run lime-config" ... aaaand uci
commit! i.e.
lime-config && uci commit
all "uci set" done by lime-config are
not actually applied, but
only staged so you can see them with "uci changes".
this is not actually documented anywhere, AFAIK,
sorry :(
we should probably change this behaviour, and
make lime-config do
an uci commit by default, unless told not to by some --no-commit
argument or whatever
Yep, seems like a good idea to me ;) Anyway, following your instructions I got it
working. Is there a
more "stable" branch/build that I can follow?
http://blog.altermundi.net/article/libre-mesh-1504/
:D
will send a proper announcement later tomorrow
Cheers
Ciaby _______________________________________________ users mailing
list users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCgAGBQJVe5W3AAoJEIJqNBvBfxrImksP/0T4E0h/odO4QO0vdU3yaI4t
NbV2Hmt/mhOzop2rVs7v/NOYewofOddMTeQFdQwVaTBjdGSKHps56nwOySxp+tgP
zNqEB2CuInxlL+1PSxQ9pRPxGN7ips/Q4S5LssubGbwubSdJDVRi45jh3admHS90
F7WEh5t4ykKcbsrzePvRKwV/T4M0VukuRlIEO/ZQBJmiPWO+Gi/4KlJi7IvnSouV
+5Gv0Keq3idHXAeiWoC/gyY9CsxrTIQnOFmJMcbixPAr56qstmbDhHZS2o0JBacs
sTJV0hEL6wz0SlS2P/Mh58l/8vex4BNAPYL6NUDFZVcdbgwg2DRkZXq8leny09+l
/SfmydVAh+au5lMLsTNITMfHXiMJnzZOzHyeK2RTV9DLsjQp4149R2+xQHRTcXKH
Lsmcwepjs3YVtNMhrUqneb4UoNLsF0MGeK1mYxLb7w80M6l56yiWKFnsTS3qgeDe
+7VMq0viQ8TrKtzORDhlDX0p4bU5IPhu9jhx45L9U7lYuxIPLgHk7KfjPIc92aFj
sZMXdyT/6EwBtA60vvciSPI1jZheIzebNJ+sW16mU7q1PfePMzqewrlGbiIqHGSO
W/9nQVeenFo5fF7ltWxXkqu8l3+/lpRdoGhqkJcQvyuzaZc+Mfk6LgQ5VLRiAXZ7
yzs30WqY3PhUEUod0Q6J
=7k0E
-----END PGP SIGNATURE-----
_______________________________________________
users mailing list
users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
15 Jun
15 Jun
10:13 p.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 06/12/2015 09:30 PM, Gui Iribarren wrote:
[...]
fixed!
https://github.com/libre-mesh/lime-packages/commit/b71fcdcf9ab93aa7992cd
1d366bb5747530cd9e7
Great!
<3
Cheers
Ciaby
we should probably change this behaviour, and make
lime-config
do an uci commit by default, unless told not to by some
--no-commit argument or whatever
Yep, seems like a good idea to me ;) Anyway,
following your instructions I got it working. Is there a
more "stable" branch/build that I can follow?
http://blog.altermundi.net/article/libre-mesh-1504/
:D
will send a proper announcement later tomorrow -----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVf03uAAoJEPU83OtbD4fQ3vQP/0z+G1PMc75HTUULO9JNl0re
SIMiSS47pwWXBtyT6QrjiZ6X9oXOy6xENWl+BhKR5xZK+I/PjguMueICrgexqD6P
m1nzPgkxbJ79j5yBw/qL+9x3Tfg/WNlhtSrJWluEwkAIqYkv51oB4davXdeR447/
KbuEh/DkV60ISMLWgiVcOz0h34Ysv6xW4qSUu2FVSJLkB7Br+ykrdR2bCSg0bMCG
WL9iStHjIWkL19bFcmfQB/XYeOAMLPo0igZ/W2e4j7C0ZRydeRBpNpYOIxabYmhn
2fwiaT50JMCeq69u0nVlbNajUUIbMQUvXPa9CnnxL3hqBoMFpl3Q01ymNs+1FTKI
tBesYHEXh+G0+RMgdhGPrkD9kCSTQy2zYbYeix48clVBlkqNZR6DKaRjinVroPea
BJyJIgjuvtTimdTBFlCQRYRPuf17sZa+tzoTmM621LV+/RorTlSHabwjw29G1n/s
TwwB3O35+be898zA78CBF2UakThV6+rt7pWUntjuDfb6QYEqXj1H3tXLTQBRgDsU
jC3V1dxE8Gh6EzxEik0FcfDuId7FHgqidPcdHiQrQaE9uDJ4zYVA1kuf9zIjAJmD
KB/j9IVivwqv+xb4pR7ocxNTJ7NzNET5v8z0Yq3ssfrUrruEws9hPezHu3kwKOZs
I0M8UXtC2nZEmxaxcv/S
=ljvI
-----END PGP SIGNATURE-----
17 Jun
17 Jun
10:18 a.m.
New subject: [lime-users] LiMe broken. (was Re: New mesh network in Oaxaca)
On Sat, Jun 13, 2015 at 4:30 AM, Gui Iribarren <gui(a)altermundi.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 27/05/15 15:35, Ciaby wrote:
Hi Gui,
I'm trying to build with lime-build on a fresh debian 8.0.
Following this guide
http://dev.libre-mesh.org/projects/libre-mesh/wiki/Compile_Manually#Using-l…
with the proper limer build branch (15.04)
the compilation failed at first because "unzip" package was not installed.
Please add this on the first command on the tutorial( apt-get install
... + unzip)
After installing unzip and "make clean" I get the following error:
touch
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/build_dir/target-mips_34kc_uClibc-0.9.33.2/gmp-6.0.0/.built
make V=ss -j1 clean-staging
make[5]: Entering directory
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/package/libs/gmp'
rm -f
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/stamp/.gmp_installed
make[5]: Leaving directory
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/package/libs/gmp'
rm -rf /home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp
mkdir -p /home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp/host
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/packages
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/host/packages
install -d -m0755
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp/usr/include
cp -fpR
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/build_dir/target-mips_34kc_uClibc-0.9.33.2/gmp-6.0.0/ipkg-install/usr/include/gmp*
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp/usr/include/
install -d -m0755
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp/usr/lib
cp -fpR
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/build_dir/target-mips_34kc_uClibc-0.9.33.2/gmp-6.0.0/ipkg-install/usr/lib/libgmp.{a,so*}
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp/usr/lib/
find /home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp
-name '*.la' | xargs -r rm -f; find
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp
-name '*.la' | xargs -r rm -f;
if [ -f
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/packages/gmp.list
]; then
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/scripts/clean-package.sh
"/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/packages/gmp.list"
"/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2";
fi
if [ -d /home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp
]; then (cd /home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp;
find ./ >
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp.files);
SHELL=
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/host/bin/flock
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/.staging-dir.flock
-c ' mv
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp.files
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/packages/gmp.list
&& cp -fpR
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp/*
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/;
'; fi
rm -rf /home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/tmp/stage-gmp
touch
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/stamp/.gmp_installed
make[4]: Leaving directory
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/package/libs/gmp'
make[3]: Leaving directory
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker'
package/Makefile:170: recipe for target
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/stamp/.package_compile'
failed
make[2]: ***
[/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/staging_dir/target-mips_34kc_uClibc-0.9.33.2/stamp/.package_compile]
Error 2
make[2]: Leaving directory
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker'
/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker/include/toplevel.mk:171:
recipe for target 'world' failed
make[1]: *** [world] Error 2
make[1]: Leaving directory
'/home/thegamer/sviluppo/lime/lime-build/build/barrier_breaker'
Makefile:237: recipe for target 'build' failed
make: *** [build] Error 2
I saw the GMP disclaimer about is ability to crash compilers, but I
don't know how to check if the problem is related to my gcc version
Info about my machine:
gcc version 4.9.2 (Debian 4.9.2-10)
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux
Anyway, following your instructions I got it
working. Is there a
more "stable" branch/build that I can follow?
http://blog.altermundi.net/article/libre-mesh-1504/
7 Apr
7 Apr
7:18 p.m.
Hello Ciaby.
Congratulations for your new mesh network project.
The next steps are just find locations to install nodes and build the
actual network :)
If the network grows big (lets say >50 nodes) you should start splitting
the layer2 by changing the libre-mesh SSID or the libre-mesh network ID.
Something you can test in your laboratory. Batman advance should not see
all the nodes in the network but Bmx6 should do it. So from a layer3
vision everything will work as expected.
Good luck and tell us more please.
On 07/04/15 19:19, Ciaby wrote:
Hi everyone ;) I'm writing to the users list of
Libre Mesh to announce
that we are starting a mesh network in Oaxaca de Juarez, Mexico.
I met Guido some months ago, and after hearing what has been done with
Alter Mundi in Argentina we decided to base our network on the Libre
Mesh firmware.
We already got 10 TL-WDR3500 to start experimenting. We did some
initial tests with flashing the standard firmware and everything seems
to work es expected :)
We'll try to go with the default network topology and see if it scales
appropriately. Any tips/tricks/insights? What are the canonical next
steps?
Cheers
Ciaby
_______________________________________________
users mailing list
users(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/users
--
./p4u
8:55 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 07/04/2015 19:19, Ciaby ha scritto:
Hi everyone ;) I'm writing to the users list of
Libre Mesh to
announce that we are starting a mesh network in Oaxaca de Juarez,
Mexico.
congrats! :)
- --
lilo
http://wiki.debian.org/LILO
####
e' tutto calcolato, ma non funziona niente.
bit in rebels => devuan.org
*nuova* PGP-KEY-ID [RSA4096]: 0x0A0E6F2A
FINGERPRINT: 0CDE C1F3 4961 0B26 5B7A 3F1E 7033 7472 0A0E 6F2A
server: hkp pool.sks-keyservers.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJVJEQ8AAoJEHAzdHIKDm8qVZQP/1XgcbuVvFYloIbzUgCRnX2f
G0Gsyec0Eu7aV2r+TEV64Yowt4vh/GAHgw2OCSI/9Tp/MRoe8OnwZ2OhchHnz5aN
DX88j5ovyjKn1eKNK01aGj1kRkNEKHcwkQ4iQPshJWGNF17AibzpoUGlf9OOR6Eh
2MDZsjo7q3flI6wbniF1fzJqzXSTLVlhB2bITQ+JQplegOXu9iVbluXMXuk6f5HR
hEA89Wz566S3nndoo3dOYBYfIdMQCYggcdMmoTqEi0qNPMq7kTlRa5emeavJtSI6
+tTKFbpjR6NDIYr6jL0g58Ht9zBHFzzj8+r4rgvuwotPrXQYCHYE+vjGL685zTsG
ctrkKM5OcwGJK1PLvdfoSLtcNtk0SAPOQy53/6TuxLa6V5I+vSpRCO3HGg7dkgjW
Bj3cGd4Yftr4xayK0vR6ZwhFjH989/WKnsmveTKsvT5WJEo2zYFUqGq/WrX9nUs6
ijgnM41+w7qerZRsdEkzgxU6lVscHQ6eC315chYOF8wL/6v3/+hrxGRVpeUR+bMz
MnEHRudrUBj1y02vxZPIWgtFl46IG/qccp1xgmZw+A71301Y1QZjNs3vGlEXJBKH
XOh0b8DQ+VwwdxhexbEijhyXezk85UyBk8fyXQtxzsRpivcvz3XFLgJVXM893ZCc
Mi1iSVQZnfiPFOobd3Dy
=10Xc
-----END PGP SIGNATURE-----
3236
days inactive
3307
days old
lime-users@lists.libremesh.org
20 comments
9 participants
participants (9)
-
Ciaby -
Gio -
Gio -
Gui Iribarren -
Ilario -
Leonardo Taborda -
lilo -
Pau -
ThEgAmEr