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.
Hi,
Sometimes I explain what this community network thing is to someone in
my district. They likes the idea and they has an ISP router. Then I ask
them if they would like to share their Internet connection and they says
"yes, why not?". But then they asks if users in the community network
could have access to their private home network. I answer they could,
but it can be avoided in different ways -create different VLANs in the
ISP router, configure a firewall, closing ports in the computers...
Then they stops liking this community network thing.
It is frustrating, because many people do not share their Internet
connection because of this, and so we lose the resources we need.
I was wondering if there would be a way that LiMe could come
preconfigured in such a way that, when an Internet gateway is added, it
could only communicate to that ISP router, and no other host in that
private network. I mean to automatically create the proper firewall
rules so that the LiMe network could not access hosts in private networks.
That would not be real security, as that configuration could be removed
by any administrator in the community network, but we would be able to
start our answer saying "by default LiMe cannot enter into your private
network", and then explain what they could do to improve their security.
What do you think of it?
Have you found this obstacle?
What would you reply to that person?
Is my proposal doable?
If so, should I open a Github issue? Where? In lime-packages?
I just cooked a firmware with the cooker for the tp-link cpe-510. It is
similar to the nano loco m5 - 45 degrees horizontal angle, 13dbi, and 5ghz
only in this case. Costs around USD 65 here.
Everything seems to be fine. It uses adhoc mode by default, so it connected
immediately to a wdr3500 with lime 1605 from another network which I had
lying around.
The reason I'm flashing these is that we installed a small network in a
favela here last week, and the wdr3500 didn't have enough reach. Not only
the nearest nods were far (anything from 200m to 2km), but also all the
interference we had (it's a really dense neighborhood) made any link with
more than 100m very poor. The plan now is to connect the most important
nodes with those.
Abraços
Bruno
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
Hi guys, apologize for reorganizing this conversation again. I think it
is better for it to have its own thread.
So, to recap, the conversation comes from the thread "Recommended
devices?":
Patricio Gibbs on 07/27/2017
The conversation in this thread has documented some useful knowledge.
Is there a place to compile this information in a list of
compatible devices?
I see the mostly empty list at:
http://libremesh.org/docs/hardware/
Such a list could be part of a guide about how to choose a device,
or how to guess whether a device might work or is definitely
unsupported.
Bruno Vianna on 07/29/2017
I like the idea too, but it would be much easier if it were a wiki or
some kind of editable page.
I contribute to openwrt's wiki every time when I find out info on a new
device.
I understand the content from libremesh is in github, but it is a lot
more bureaucratic to edit the html, push it, wait for merge...
So, dear libremesh site managers, do you think we can have a wiki or
some open content solution?
We talked with Gui/Gio/Pau/NicoE about this and think that would like
to make a decision that reinforces the community, so instead of pushing
a specific implementation, it is better to share our perspectives on
the subject and consider experimenting something a bit in the way to
the "advice process" http://www.reinventingorganizationswiki.com/Decisi
on_Making, which we are implementing as:
someone who is in a good/the best place to make this decision (can mean
many things but let's consider responsible for implementing and
maintaining, and accountable for the results... who would be me so far)
will lead an "advice process" which means receiving advice from all
those who can have relevant contributions and/on will be affected by
it, meaning you.
So this is a brief of the points of that group, which I'll share since
I consider valuable for all to know them:
Pro "current state"
We left RedMine because it was not working, people was not contributing
and the info was not being updated. Now that it is more code-related
the info is kept in a more coherent way.
On GitHub there is the "Edit" button.
It is not necessarilly bad to have to wait for a Pull Request to be
accepted.
Pro "Wiki"
Now we are a bigger communitty, how do we enhance involvement?
We can make a monthly test with the GitHub wiki with the unnoficial
info like "experiences with hw", "specific tutorials", "cases" and so.
The downside of the github wiki is that it can only be editted by
collaborators of the repository.
So based on this information, which key points would be relevant to
consider to move forwards?
Please share your points of view so we move on to have a definition.
As said, it is an experiment of using a decision making method which
seemed to us can be a good one for the kind of community we work to
build. Please then shared also your feedback about this.
Part of this process has been promoted by a relative new member of the
community (5 months or so), Rodrigo Monelos, who has been mainly acting
as facilitator and Agile coach on the LibreRouter project, so he will
be helping also with the coordination of it.
I hope he can introduce himself to come out of the shadows :)
Regards,
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
Hello! I continue to learn about LiMe, now using SDK. I cooked the image
for a tl-wa701nd v1 because it does not exist in the image repository.
But I do not know which file I should upload. The files in
lime-sdk/output/ar71xx/generic/tl-wa701nd-v1/lime_default/ are:
lede-17.01.1-libremesh-ar71xx-generic-device-tl-wa701nd-v1.manifest
lede-17.01.1-libremesh-ar71xx-generic-root.squashfs
lede-17.01.1-libremesh-ar71xx-generic-uImage-lzma.bin
lede-17.01.1-libremesh-ar71xx-generic-vmlinux.bin
lede-17.01.1-libremesh-ar71xx-generic-vmlinux.elf
lede-17.01.1-libremesh-ar71xx-generic-vmlinux.lzma
lede-17.01.1-libremesh-ar71xx-generic-vmlinux-lzma.elf
sha256sums
I look for ... squashfs-factory.bin but it is not. Then I do not know
where to migrate the firmware.
The * vmlinux * discard them because they are virtual images for a
simulation. Right?
I like .squashfs but it's not .bin
UImage-lzma.bin remains. Is this to do it from OEM?
I am looking in the right directory?
Should I use a form other than oem?
The docs of openwrt have helped me but now I do not see the way :-)
Thanks for the help.
So I've built Libremesh using the sdk for my wrt54gs v3. It boots fine, but the wireless is not working by default. Should I have to do extra configuration? I did notice both ad-hoc and 80211s are on by default.
McL0v1n
hello there,
we try to setup different customized lime installations for a camp.
our routers: tplink 4300.
1) the following configuration is working for ap encryption but not for
the mesh:
* cooking in branch stable (we also tried develop with the latest
working commit):
V=s J=1 ./cooker -c ar71xx/generic --flavor=lime_camp
--profile=tl-wdr4300-v1 --community=camp/commoniee80211s
* flavors.config
lime_camp="lime-full -dnsmasq -wpad-mini wpad authsae"
* etc/config/lime_defaults:
config lime system
option hostname 'CA-%M4%M5%M6'
option domain 'mesh.camp.local'
option keep_on_upgrade 'libremesh base-files-essential
/etc/sysupgrade.conf'
config lime network
option primary_interface eth0
option main_ipv4_address '10.5.0.0/21'
option main_ipv6_address '2801:01e8:2::/64'
option bmx6_mtu '1500'
list protocols ieee80211s
list protocols lan
list protocols anygw
list protocols batadv:%N1
list protocols bmx6:13
list protocols olsr:14
list protocols olsr6:15
list protocols olsr2:16
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'
list modes 'ap'
list modes 'apname'
list modes 'ieee80211s'
option ap_ssid 'Unsecure'
option apname_ssid 'Unsecure | %H'
option adhoc_ssid 'Mesh | Camp'
option adhoc_bssid '16:27:F6:27:57:14'
option adhoc_mcast_rate_2ghz '24000'
option adhoc_mcast_rate_5ghz '6000'
option ieee80211s_mesh_fwding '0'
option ieee80211s_mesh_id 'Mesh_Camp'
option ap_encryption 'psk2+ccmp'
option ap_key 'somepassword'
option apname_encryption 'psk2+ccmp'
option apname_key 'somepassword'
2) if we add to the "config lime wifi"
option ieee80211s_encryption 'psk2+ccmp'
option ieee80211s_key 'someotherpassword'
the mesh disappears.
are there other packages we still need to get it working besides "wpad"
& "authsae" or is there anything else we are missing?
thank you!
