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▀─█▄██▄▀█▀█▄▌██─█▌█▌
On Monday night through Wednesday we have a training that includes
setting up a 400 meter link (near Puyo, Ecuador, UTC-5).
We have purchased a TP-Link Archer C20 v4. We plan to connect it via
Nanostation2 and NanoLoco2 with a WR840Nv5(ES) that belongs to a small
ISP (why this arrangement? combo of cheapest new and used hardware that
I thought would work). The 840N only has 4MB RAM, which I understand is
not really recommended for LibreMesh.
Neither of the routers are on the list of devices at
http://chef.libremesh.org/ for LibreMesh, but they are on the list for
OpenWrt. The most similar device by name on the LibreMesh list is the
Archer C20i.
If we can LibreMesh-ify the ISPs 840N router in a way that it can easily
be returned to factory firmware, maybe we will do that.
If we can LibreMesh-ify the Archer C20 without a high probability of
bricking it, we will do that (we don't have money in the budget for a
replacement this week).
I can use lime-sdk cooker instead of Chef -- I have done this before to
test a new translation file.
Suggestions on how to proceed?
Here's the C20v4 data:
https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_c20_ac750_v4
Supported Current Rel: snapshot
Unsupported Functions: WiFi 5GHz
Target: ramips
Subtarget: mt76x8
Package architecture: mipsel_24kc
Bootloader: U-Boot
CPU: MediaTek MT7628AN
8 MB flash, 64 MB RAM
Compare to C20i:
https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_c20i_ac750_v1
Supported Current Rel: 17.01.4
Unsupported Functions: WiFi 5GHz
Target: ramips
Subtarget: mt7620
Package architecture: mipsel_24kc
Bootloader: U-Boot
CPU: MediaTek MT7620A
8 MB flash, 64 MB RAM
TL-WR840N v5 (ES) -- belongs to the ISP
https://wikidevi.com/wiki/TP-LINK_TL-WR840N_v5
CPU1: MediaTek MT7628N (575 MHz)
FLA1: 4 MiB (GigaDevice GD25Q32B)
RAM1: 64 MiB (ESMT M14D5121632A)
~ Pato
Continuing my quest to categorize devices based on their LibreMesh compatibility, since the LibreRouter hasn't arrived yet and won't solve all needs....
1) great, (e.g. WDR3500)
2) okay, but fixed antennas
3) some functions not working, (e.g. Archer C20v4)
4) emergencies only (ones that have 4 or 2 MB flash)
5) incompatible (e.g. 841HP)
In Chef, when I type "ubiq" in the router model field, I get a list of Ubiquiti devices supposedly compatible with the latest release of LibreMesh. How is this list generated? Is it reviewed by a human?
Here are examples of why I ask: it says Nano-M and Nano M XW: are these NanoStation or NanoBeam? It says Loco XW but the OpenWrt ToH says that the latest supported release for the Loco is 10.03.1, https://openwrt.org/toh/ubiquiti/nanostationm2....? Flashing LibreMesh onto NanoStation and TP-Link CPE devices could make some networks much easier to maintain.... If it actually works.
This continues a conversation from last year about improving our documentation, such as maintaining a LibreMesh wiki.
~ Patricio
Hello,
Here we are considering again the captive portal thing. It would be a
welcome page with some community news, not real authentication. I guess
we would like a system where MAC addresses of users who just clicked an
"Ok" button of the splash page would be validated for a month. So they
would have to go through this News page once a month.
I've seen Nodogsplash seems to be maintained again, so I can try to make
it work for LiMe. But first I wanted to ask about Pitbull, as I think
that was something similar but specially made for LiMe.
What is the status of Pitbull?
Would it work for the described need?
Thank you!
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,
there are so many dnsmasq issues for LiMe[0] that I though to lower it's
impact a bit. A first step to replace dnsmasq-dhcpv6 with the usually
preinstalled odhcpd-ipv6 only, which should offer even more
functionality. Therefore a small PR on GitHub[1].
Only drawback is for now, that IPv6 addresses are not distributed to
other hosts when roaming, or more precisely, odhcpd-ipv6only doesn't
accept adding leases manually. For now, Daniel Golle will likely fix
this in the early future.
I'd be happy if somebody could test this change, I compiled some targets
on the snapshot server[2], if your favorite target is missing please
ping me.
Best,
Paul
[0]:
https://github.com/libremesh/lime-packages/issues?utf8=%E2%9C%93&q=is%3Aiss…
[1]: https://github.com/libremesh/lime-packages/pull/379
[2]: https://snapshots.libremesh.org/staging/aparcar/targets/
Has anyone set up a system that does this:
When the public power grid cuts off, a backup power supply gives power
to the node and a message is sent to the network saying "Main power cut
off, switched to backup power." Then, when the power comes back on, a
message is sent saying "Main power returned."
I imagine a RaspberryPi could do this, but I don't know how, and I
wonder if there are less expensive ways to do it.
The messages could be sent to the gateway node in our community and
stored on that router, or email or something else.
This would help us because the power goes out about two times per week
at our gateway node, but the only symptom we see is that our internet
connection cuts off, and we don't know if it's because of power outage
or ISP problems. We want to know, because this way we can make official
complaints about the quality of service to the ISP, and we can decide
how much backup battery power we need in order to enable continuous
connectivity.
hi! we just installed lime_mini into our tplink wr841n v11 nodes, but
we're a bit confused about the setup. it created three wifi on radio0,
one is a mesh point and the two others are ap. but when we tried to
disable the aps, the mesh wifi stopped working.
first we disabled the config for the ap wifis on /etc/config/wireless
and after `wifi off` and `wifi on`, the mesh point would be recreated
but without an ssid. later we removed the 'ap' y 'apname' from
/etc/config/lime and ran `lime-config`, which did the same we did
manually, with the same results.
what would be the config for just running mesh points? :D
--
}(:=
I'm using self-cooked version of latest development LiMe, and I run across
quite baffling problem. Routing through AP works fine, I can access
internet normally and everything works - HOWEVER, if I log in to router and
try accessing internet from router shell, using ssh/wget/opkg/whatever -
nope, nothing works. Even ping does not work, although if I use workstation
connected to AP and ping from there, without loggin into router, everything
works as expected.
What am I missing here?
Harri