Hello meshies
I know everybody is having fun at Battle Mesh, but if someone could take a
look at this I' d really appreciate.
I really have my eyes on the C50, as it seems to be the cheapest dual-band
on the market now. I can get on in Brazil for less than 40 USD! Last week I
bought one which I later found out to be an unsupported V2. But now I got a
V1, and it almost works. If it works, I'll the buy about 10 for an
installation in two weeks.
The problem seems to be with 802.11. The 2.4Ghz radio does not work in
ad-hoc mode - although the 5Ghz radio does. Then I don't know if it's
related, but when it meshes with a WDR3500, the Internet is painfully
slow, with some ping times about 1000-2000 milliseconds. Pinging from the
LiMe gateway at the same time gives me a steady 57ms. Perhaps a different
driver should be used?
Attached is a file with information gathered from the router.
A few other oddities (not as important as the issue above):
- Could not flash from stock directly with the compiled LiMe. I had to
first use this openwrt [1], then LiMe
- When I flash from the firmware above with the LiMe I compiled or the
download Lede, I get the message:
" It appears that you try to flash an image that does not fit into the
flash memory, please verify the image file!
Size: 7.63 MB (7.62 MB available)"
It works fine, tough.
- The firmware I cooked with my community settings (using cooker) won't go
through to the Internet, and gives this ESSID instead of my
community's:{{NETWORK_NAME}} (although it meshes with the LiMe gateway)
- The firmware I cooked without community settings connects to the Internet
through the LiMe gateway with the sluggish times above.
Thanks!
[1]
http://dl.eko.one.pl/luci/chaos_calmer/ramips/luci-15.05-ramips-mt7620-Arch…
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
Hey sisters,
Let me share some good news for community networks -and bad ones for ISPs:
0.- Bitmessage has been working on LAN peer auto-discovery. It is
already in v0.6 branch, we tested it and it works.
1.- Retroshare will finally have asynchronous messaging working
(Retroshare already has LAN peer auto-discovery).
2.- Impressive ZeroNet is aware of the importance of LAN peer
auto-discovery and they are going to add this feature.
Sorry for the spam, but I thought it would be interesting for someone,
it's just the motherboard without antennas nor chassis of a TP-Link
WDR4300 for 23 € on aliexpress
---------- Messaggio inoltrato ----------
Da: Leonardo Maccari <mail(a)leonardo.ma>
Date: 28 giugno 2017 14:41
Oggetto: [Ninux-Wireless] tp-link 4310 refurbished
A: wireless(a)ml.ninux.org
Ciao,
long story short: Dopo il BM qualcuno mi ha chiesto di contattare
Panayotis (un ricercatore che conosco) per sapere dove ha preso le
device che hanno usato per uno workshop ad Atene. Ecco la risposta:
https://www.aliexpress.com/item/openwrt-firmware-5g-wifi-2-port-usb-router-…
ciao,
leonardo.
_______________________________________________
Wireless mailing list
Wireless(a)ml.ninux.org
http://ml.ninux.org/mailman/listinfo/wireless
Buenas,
Más abajo les envío una presentación que hice hace unos años en la lista de
AlterMesh.
Les cuento que actualmente el proyecto tiene instalados 3 routers wdr3600
en 3 instituciones del Barrio Villa Aguirre, Tandil, pero actualmente no se
provee ningún servicio. Estos equipos los instalaron alumnos de la TUPAR en
el marco de un trabajo de la materia Tecnología de Redes 1.
La versión que tienen instalada los equipos es:
lime-tl-wdr3600-v1-r44952-tandillibre-node-factory.bin
lime-tl-wdr3600-v1-r44952-tandillibre-node-sysupgrade.bin
En este momento en una de las instituciones se está instalando un servidor
que hará de portal cautivo y alojará algunos contenidos (wikipedia,
owncloud). El servidor lo están configurando como trabajo final de la
TUPAR.
Estamos teniendo problemas para lograr que el router otorgue como DNS la ip
de servidor.
Pero si te conectas al wifi y le pones manualmente el DNS (10.233.0.55)
funciona perfecto. (video
<https://drive.google.com/open?id=0BzqwAzOcjbGkYVM2V0xyRFpfYTg>)
Si tienen alguna guía de como configurar el equipo para vincularlo al
servidor de DNS del servidor, nos vendría genial.
También me comentaron los chicos que cuando el equipo pierde la corriente
se borra la configuración. ¿Se les ocurre por que puede ser?
Saludos y gracias!
Santiago
---------- Forwarded message ----------
From: Santi Vallazza <rulosanti(a)gmail.com>
Date: 2015-10-05 14:30 GMT-03:00
Subject: Presentación
To: altermesh(a)listas.altermundi.net
Buenas!
Me presento, mi nombre es Santiago Vallazza, vivo en Tandil, Provincia de
Buenos Aires, Argentina y trabajo en la Facultad de Ciencias Exactas
<http://www.exa.unicen.edu.ar/> de la UNICEN <http://unicen.edu.ar/>. En
esta Facultad tenemos varias carreras, las relacionadas con Sistemas son:
Ingeniería de Sistemas, Tecnicatura Universitaria en Programación y
Administración de Redes (TUPAR) y este año arrancó la Tecnicatura
Universitaria en Desarrollo de Aplicaciones Informáticas (TUDAI).
Soy usuario y militante del Software y la Cultura Libre, hace unos años me
metí en redes pero no pude darle mucha continuidad. Ahora tengo ganas de
retomar el tema.
Ahora estamos con un proyecto que propone crear una red inalámbrica de
alcance barrial, que provea contenidos educativos e informativos. La idea
es poder acceder a contenidos que estén en el servidor del proyecto, que
ubicaremos en una sede de la UNICEN, la Universidad Barrial, y en los
servidores de las escuelas que participen (moodle, etc.).
Del proyecto van a participar algunos estudiantes voluntarios y se
trabajará con docentes y cátedras de Comunicación de Datos de la TUPAR de
Ingeniería de Sistemas, y en ese marco algunos estudiantes realizarán
trabajos de cátedra y de final.
Nos gustó el proyecto Altermundi y el alcance territorial que tiene y el
firmware Altermesh, así que intentaremos usarlo como firmware oficial del
proyecto, y si podemos hacer aportes, también lo haremos. Ya he contactado
a algunos miembros de Altermundi por sus correos personales, pero creo que
este será un medio más apropiados.
Eso es todo por ahora, y en otro hilo comienzo con algunas preguntas.
Saludos!
Santiago
Thinking about how we might use the voucher system for access control in
Caimito and other communities in the area...
1) I imagine the process might be that someone connects to the wifi,
opens a browser (or on Android, sees a notification to register on the
network, like in airports), gets caught by the captive portal, and has
an option to use the network without registering, or enter a voucher
code. Correct? Other options?
2) In order to make the voucher code as easy as possible to use, three
options occur to me:
-- 1) the code is 2 or 3 letters (maybe up to 6), case insensitive,
automatically generated by the system. (My favorite)
-- 2) the code is a word or pair of words, automatically generated by
the system. (My least favorite)
-- 3) the code is defined by administrator, and checked by the system to
avoid duplicate codes. (Maybe useful in some cases)
Letters instead of numbers because we get more options for each digit,
thus making a shorter code.
number of letters - unique codes:
1 - 26
2 - 676
3 - 17,576
4 - 456,976
5 - 11,881,376
6 - 308,915,776
Airlines tend to use 6 letters, and I can usually remember those codes.
With 2 letters, we could give unique codes to everyone who comes through
Caimito in a year, and with 4 letters we could cover 87% the province,
and with 6 we could give 19 codes to each person in Ecuador. I imagine
most community networks would be fine with 3 or 4 letters. Maybe the
length of the code can be defined by admin, or it can grow sequentially
as needed (first code is A, 27th code is AA, 677th code is AAA, so on).
3) Codes expire and get recycled, yes?
4) The vouchers are part of Pitbull, or separate-but-connected?
5) Probably "it'll be ready when it's ready, no later than October",
but... Any idea when a functional build might be ready? There are a
number of things that seem not feasible until this system works (e.g.
community library / internet cafe).
6) Can we define roles or profiles in Pitbull / the voucher admin
system? This way I can look at a list of currently active vouchers, and
see who's connected, how much time they have left, and whether they're a
library/network member, library visitor, tourist, or other. When I
create a tourist voucher, they get access to 50% of the available
bandwidth, and by default the voucher lasts 1 day. A library visitor by
default gets 90% access and lasts 1 hour. A member by default gets 100%
of bandwidth and 1 month.
7) When a voucher expires, keep the code reserved in the system for 10%
of the time it was valid, in case the person wants to renew the voucher.
Examples:
-- A 1 hour voucher of a library/ciber visitor expires, and they have a
6-minute grace period to request another hour on their voucher. The
admin interface makes extending the voucher easy.
-- A 1 month voucher has a 3-day grace period. The device doesn't have
access once the voucher expires, but renewing is easy: the admin doesn't
have to create a new voucher, and the person doesn't have to enter a new
code.
If there's a better place to share these ideas, please tell me.
~ Pato
Hi Everyone,
The last LibreMesh release (I don't remember if it was announced or
not, but it is here :) ) brings support for 11s and many other things.
I was wondering... now that the wdr3500/3600/4300 devices are no longer
accessible... which ones can we use?
Now there are a lot of devices with the MTK7601, and others with
QCA6174.
I've tried some Xiaomi device that comes with the MTK7601
processor+radios and it works... but don't have knowledge about
performance and robustness... and if there are any dual radio with
weather enclosure around.
Thanks!
Hi all
I’ve noticed LEDE supports 802.11r and 802.11w and has the respective settings section in LUCI under wireless security. I’m not familiar with these protocols other than knowing they exist and I’m very happy to see them available for use with free and open software. Is there any way we could start some testing for them for LiMe [especially the first one, which would make roaming inside the network even more seamless, since it’s one of the core advantages and of LiMe]? I read that 802.11r requires only one DHCP server to exist on the network and no separate subnets, but I assume that our replication of such a network with every node handing out the same leases on the same subnet perfectly simulates this behavior even in this respect, and the “trickery” works also for this requirement, is this correct?
Also, is there a good rule of thumb to figure out the right way of enabling features available in LuCi from the LiMe configuration in SDK? I’ve been trying to put all nodes on SSH port 42022 [I know, security by obscurity, but it’s better than nothing, and our keys are 4096, so there’s a solid base already ;] and disable password authentication for instance. Or adding hostnames, and so on. If there’s a quick way of figuring these things out, I won’t have to bother any of you for every single customization I need to make ;]
Thank you in advance
Nk
Hi
In order to understand how to start using 802.11s from SDK, I’ve downloaded a pre-built image from http://repo.libremesh.org/lime-17.04/ [downloads.libremesh.org isn’t responding at least for me - I think I need a 17.02 version to compare with an SDK output, no?].
I’ve noticed a few changes such as the directory /etc/config/ becoming /etc/lime-config-firstboot/ and more in luci-defaults and so on.
Do you have a list of changes?
How do I maintain a https://github.com/libremesh/network-profiles/ community in a way that is future-consistent?
I’d like to be able to have details in there that really only override things I’ll always want to override, such as the SSID, but allow for all other file changes [like adhoc becoming 802.11s for instance] from upstream to pour down into my SDK images, with no interference at all and no risk of having conflicts. Also because images I’m building now, once flashed, don’t work at all, so there is a big risk in upstream changes conflicting with network-profiles, don’t you think?
I know this means a line-based granularity and not a file-based one such as now, but there must be a way, no?
In any event, for now, what changes do I have to make to my community files in order to get SDK to cook valid and up-to-date in every way images?
Thank you!
Nk
Hello all
I am new to the LibreMesh hacking community.
I am trying to build the LibreMesh firmware so as to format my router with
it.
I have followed All instructions as stated here
https://github.com/libremesh/lime-sdk
and all seems good.
When I try to build the packages using the command ./cooker -b
ar71xx/generic
I get the error
*make -r world: build failed. Please re-run make with -j1 V=s to see what's
going on/home/nges/lime-sdk/lede/ar71xx/generic/sdk/include/toplevel.mk:200
<http://toplevel.mk:200>: recipe for target 'world' failedmake: *** [world]
Error 1make: Leaving directory
'/home/nges/lime-sdk/lede/ar71xx/generic/sdk'-> Error compiling SDK*
I have tried looking for a solution from the internet but I have not
gotten any concrete solution .
Please anyone with any Idea of how I can solve this problem ??
I am using Ubuntu 15.10 , 64Bits OS
Thanks and waiting to hear from you
At your Service
Nges Brian
"A Goal is a Dream with a Plan and a Dateline"
Do On to Others what you will like them to do on to you.'The Golden Rule'
The CEO of ABEBOH
Computer Software Engineering Student
Music DJ . Artiste at Casky Black's Record
Regional Coordinator and CAC Member at Mozilla Campus Club Program.
Hi all!
Seems that [1] we want to deprecate the use of Tip4commit [2] for
receiving donations.
So we need to re-discuss the way for receiving donations and how to
use them (in tip4commit it was straightforward, 1% of the donations
was delivered for each commit to the committer).
I would suggest to not restrict donations to bitcoin, as it was in tip4commit.
Ideas on how to receive them? Platforms?
Clearly the platform for collecting donations could restrict their use
(e.g. Bountysource [3] gives donations to issues solvers).
How we could use donations?
A few ideas:
* not defined, each time someone needs funds asks and the community decides
* helping developers to survive, dedicate more time to LiMe and
dignify their volunteer work (this is what tip4commit did)
* encourage non developers to get into the code, implement stuff,
debug and write documentation (e.g. I suppose Bountysource would have
this effect)
* contributing to server maintaining costs (up to now we use them as
freeloaders, hosting communities (qMp and Altermundi I think) let us
use their servers for free)
* produce loads of stickers and super cool LiMe t-shirts...
* organize internationals LiMe hackatons and pay travelling (up to now
LiMeCat meetings were zero budget events)
* pay travelling and food for developers attending BattleMesh or other
related events
* buy routers to test support (Pau and Daniel have some)
* build a small real network for continuous testing of develop branch
(it would be great to have an university collaborating on this)
[1] https://github.com/libremesh/lime-packages/pull/165https://github.com/libremesh/lime-web/pull/27
[2] https://tip4commit.com/github/libremesh%2Flime-packages/
the donation fund present in tip4commit will continue working until emptiness
[3] https://www.bountysource.com/
