Hi all!
Here goes the log of yesterday's meeting:
## Saturday the 7th of March 2026 at 13:00 UTC (14:00 CET, 10:00 ART).
### People
Ilario, Cri, Franco, Constanza
### Topics
. Updates about repo server and DNS
. Status of inclusion of GSoC 2025 contributed code
. DSA pull request
. Approve and merge the remade of the libremesh website in vitepress.
https://a-gave.github.io/libremesh.github.io
- Introduce a reference with detailed options of lime configuration
files.
- Rewritten some pages including more remands to the openwrt
documentation.
- Rewritten some pages of the guide trying to follow an approach less
discoursive and more descriptive. To have less words to read.
- Maintain the possibility to have an overview of packages also from
the website menu, included also the network-profiles
. Libremesh Testbed in UNC, argentina
### Introduction about LibreMesh testbed in UNC, Argentina
Franco explains the OpenWrt test framework and shows the rack they
assembled in Argentina. They plan to expand the testing suite to support
multi-node tests (e.g. checking if nodes are connected to each other).
OpenWrt test uses VLAN to isolate devices, but we need the devices to
see each other, so we will have to edit the OpenWrt test code.
Ilario: amazing, it would be awesome to contribute to OpenWrt test, so
that also Paul can help us reviewing the code.
Cri: very useful also for checking if the normal firmware and the "mini"
version (LibreMesh with minimal list of packages) work on our favourite
routers
Franco: the hardware that we have in the rack is:
* Belkin RT3200/ Linksys E8450 (x3)
* Glinet Mango (x1)
* Libre Router V1 (x1)
* Openwrt One (x1)
* Banana Pi R4 (1)
* Swich TPLink SG2016P
These tests are very powerful for spotting regressions, including the
currently working features in the testing.
Issue with the Belkin routers:
https://openwrt.org/toh/linksys/e8450#recovery_from_openwrt_kiss_of_death_okd
This issue should be already fixed in OpenWrt 24, but Franco mentions
that it depends on which firmware image file you use.
Please add the working hardware here:
https://libremesh.org/docs/hardware/
Cri: we are using the hardware listed here:
https://toh.antennine.org/?filter=antennine&view=normal
### Updates about repo server and DNS
We are waiting for Luandro to talk to Nico Echaniz or Jessi (Altermundi)
for understanding how to go on with the domain registar and DNS.
Gothos bougth a cheap VPS (approx 4 euros/month) that will be paid with
the money from donations collected on OpenCollective. For now Ilario and
Gothos are the ones with SSH access.
Ilario: at some point we can migrate the website hosting from Github to
the new VPS.
Cri: Gothos is also trying to update the website.
### Status of inclusion of GSoC 2025 contributed code
Ilario: I still have to test shared-state-odhcpd. Victor said he will
have time in March, I am going to write him.
### DSA pull request
https://github.com/libremesh/lime-packages/pull/1214
### Approve and merge the remade of the libremesh website in vitepress.
https://a-gave.github.io/libremesh.github.io
There will be a redirect with all the pages, but it currently does not
work on github.io, so it will work when we will move the website to the VPS.
We like the new website, please Gothos install it on the VPS :D
Then we have to decide if the website will be updated by the Github
actions continuous integration or by a periodic "git pull" made from the
VPS (second option is easier, we believe).
Once the DNS is updated, the old website will be accessible at
libremesh.github.io
### Libremesh Testbed in UNC, argentina
Why does OpenWrt test use one VLAN for device? Because all the connected
devices (more than one, so that they can test on several different
hardware types at once) share the same IP.
Franco: We will need 2 different exporters as we will have 2 labs
(openwrt-test and LibreMesh tests) one will be connected to the global
coordinator (managed by Aparcar) and the other one is going to be hosted
on a local machine. The issue is to switch on the VLAN (for OpenWrt
tests, on isolated devices) and off (for LibreMesh tests, where the
devices would be connected).
Ilario: you could try removing the VLAN for both sets of tests.
OpenWrt-test could contact the routers using IPv6 link-local, rather
than IPv4, and then hopefully the tests can run without VLAN. We should
have a call with Aparcar.
Franco: we need a specific kind of image that can be provided to uboot
for loading directly in RAM, and LibreMesh's Firmware Selector currently
does not expose this kind of images. OpenWrt's Firmware Selector does
expose also these files, so it should be possible to expose them also
from LibreMesh's one.
Ilario: please write to Gothos, is very likely that he can fix this easily.
Franco: we want to specify on which devices to run the tests, also for
tests on multiple devices. Javier proposes to use the Github actions UI,
so that you configure these parameters from there. There would be a
checklist to fulfill before running the tests. The tesing system would
check the checklist and wait for the hardware to be available. OpenWrt
tests is not much parameterizable or configurable, all the tests run on
all the routers.
Ilario: keeping low the number of parameters is good, so that the same
system works on every testbed. The multi-devices tests could be based on
an algorithmic selection of the routers, for example having an
alphabetic list of routers and grouping them following the list (e.g.
for multi-node tests with 2 nodes, first+second, then third+fourth...).
Franco: maybe up to 3 nodes is enough for multi-nodes tests.
Franco: Also, we would like to add the option to use a custom image for
testing, not only coming from the current integration. What happens now
is that only merged commits get tested. It would be nice to be able to
test things beforehand.
Ilario: what could be an easy way to do this, is to give access to some
developers so that they can use the same Github action in their
repositories for testing a specific branch. So that they can push their
drafted commits to that branch and have them tested also.
Ilario: Javier is organizing a meeting with Aparcar, let's discuss this
further there.
On 3/3/26 1:57 PM, Ilario wrote:
> Dear all,
> This Saturday 7th of March there is a project meeting!!!
>
> The list with all scheduled meetings is here:
> https://libremesh.org/communication.html#online_meetings
>
> As always, participation of the whole LibreMesh community is encouraged :)
>
> It will be on Saturday at 13:00 UTC (14:00 CET, 10:00 ART).
>
> Here the link for joining: https://meet.exo.cat/LibreMesh
>
> And here the link where you can start proposing topics to be discussed:
> https://pad.exo.cat/code/#/2/code/edit/-i0SKeDo4jvTtOc3atbN3lI6/
>
> Ciao!
>
--
Ilario
iochesonome@???
ilario@???
