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▀─█▄██▄▀█▀█▄▌██─█▌█▌
Hi!
Are there plans for branches of the lime feeds corresponding to the
upcoming openwrt-18.06 release? I reckon we should have that.
Also, it'd be great for chef.libremesh.org to already offer plain
OpenWrt 18.06-rc1 images as well as with lime-18.?? on top.
Cheers
Daniel
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
Who has used LibreMesh on MicroTik devices? Are they easier to flash
than Ubiquiti? (Ubq require downgrading and then flashing, and finding
the correct files can take time). I'm interested in common devices, not
the newest devices, and also interested in returning them to stock
firmware after testing LibreMesh on them. Why? A friend who runs a small
family ISP wants to test LibreMesh, and mostly uses MicroTik, with some
NanoStation M2. Also, if this works well, I might shift some planned
installations from Ubiquiti to MikroTik. Common devices in Ecuador include:
- Sxt 5ndr2 Lite
- Sxt-2
- Lhg 5
https://listado.mercadolibre.com.ec/mikrotik
~ Pato
We all share two 1Mb satellite connections here in our mesh. But since mine
is always more hops aways from most of the users they tend to go to the
single 1Mb gateway, so we're starting to experience really slow, some
times, unusable internet.
We're already using a captive-portal system to block unwanted users, so now
all I can think of is of controlling the bandwidth traffic. So I came
across the sqm
<https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm> package.
Seems to be easy way to controlling the traffic.
Anyone have any experience with using this package? Any other solutions,
like using squid? Ideally we'd want to throttle videos, Bittorrent and
other bandwidth suckers.
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
It's there a way to build LibreMesh images based on 17.06 right now via lime-sdk?
El 23 de agosto de 2018 1:53:53 GMT-05:00, Paul Spooren <mail(a)aparcar.org> escribió:
>Are you sure the message is not:
>
>Unknown package in request: zz-libremesh-default
>
>At least that's what I get when following your configuration.
>
>The libremesh-default network profile is only usable and relevant for
>an (hopefully soon) upcoming change in libremesh which will improve the
>overall configuration possibilities.
>
>BestOn Aug 22, 2018 4:58 PM, William Fleurant via lime-users
><lime-users(a)lists.libremesh.org> wrote:
>>
>> Hello,
>>
>> re: https://chef.libremesh.org/
>>
>> When cooking LiMe firmware with network-profile set to
>libremesh-default:
>> Unknown package in request: lime-full
>>
>> -w
>>
>>
>>
>> Sent with ProtonMail Secure Email.
>>
>_______________________________________________
>lime-users mailing list
>lime-users(a)lists.libremesh.org
>https://lists.libremesh.org/mailman/listinfo/lime-users
I had the same issue not long ago. Which network profile should we use for
a basic configuration?
Le jeu. 23 août 2018 02 h 54, Paul Spooren <mail(a)aparcar.org> a écrit :
> Are you sure the message is not:
>
> Unknown package in request: zz-libremesh-default
>
> At least that's what I get when following your configuration.
>
> The libremesh-default network profile is only usable and relevant for an
> (hopefully soon) upcoming change in libremesh which will improve the
> overall configuration possibilities.
>
> BestOn Aug 22, 2018 4:58 PM, William Fleurant via lime-users <
> lime-users(a)lists.libremesh.org> wrote:
> >
> > Hello,
> >
> > re: https://chef.libremesh.org/
> >
> > When cooking LiMe firmware with network-profile set to libremesh-default:
> > Unknown package in request: lime-full
> >
> > -w
> >
> >
> >
> > Sent with ProtonMail Secure Email.
> >
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
Hello all. I'm working with a community initiative in Nigeria who would
like to implement a community-wide wifi network. I'm looking at LibreMesh
as a possible solution Nodes would be solar powered, and would share
connection to public internet through only a couple gateways.
I'm interested in connecting with anyone on the list who has implemented
LibreMesh in a similar way, and I'm also looking for recommendations on
hardware considerations. I'm thinking a dual radio device with the 5ghz
radio dedicated to the mesh backhaul, and the 2.4ghz dedicated to end users.
Also, I'm located in Verona, Italy and could easily meet-up with any active
users nearby.
With best regards.
Roland Wells
Founder http://hellohub.org | http://kruufm.com
Are you sure the message is not:
Unknown package in request: zz-libremesh-default
At least that's what I get when following your configuration.
The libremesh-default network profile is only usable and relevant for an (hopefully soon) upcoming change in libremesh which will improve the overall configuration possibilities.
BestOn Aug 22, 2018 4:58 PM, William Fleurant via lime-users <lime-users(a)lists.libremesh.org> wrote:
>
> Hello,
>
> re: https://chef.libremesh.org/
>
> When cooking LiMe firmware with network-profile set to libremesh-default:
> Unknown package in request: lime-full
>
> -w
>
>
>
> Sent with ProtonMail Secure Email.
>