Appearance

2023-11-01 PROJECT MEETING ​

Wednesday the 1st of November 2023 at 13:00 UTC (14:00 CET, 10:00 ART).

People

SAn, Ilario, Ger, Cri, Gothos, Maden

Topics

  • How to use donations (buying hardware?)
  • News about Altermundi roadmap 2023
  • Where to store the log of the meetings
  • OpenWrt 22 or OpenWrt 23 as a base for the next release candidate?
  • Outdated release server
  • Free discussion about other projects and LibreMesh
  • Firmware signatures
  • Next meeting

Past meeting topics:

How to use donations (buying hardware?) ​

Old decision: stickers to be printed by people attending events.

Currently we have 617 $ https://opencollective.com/libremesh#category-BUDGET

We need to write an email defining for what the money can be spent. The decision would be taken in the project meetings.

From the meeting minute of 2023-04-01:

  • pay the travel to the battlemesh for some of librerouter/altermundi (maybe next year or another event)
  • pay the travel for the travel to battlemesh for some people of Antennine (maybe next year or another event)
  • pay the update of the server of downloads CodigoSur? Chiede Cri
  • buy some stickers LibreMesh YES
  • donation for the domain name? for the newsletter?
  • email @libremesh.org? [20231101 nah]
  • hardware per testare il supporto?

Ger: the priority should be having a release

New proposals:

  • Pay someone for some testing hours
    • Gothos? (Ilario asks)
    • Proposing to everyone in the mailing list (Ilario writes) and the final decision is taken in the project meeting
    • We can offer 550 $, keeping 67 $ for stickers
    • Define object for payment: make a release
    • Test on two different router models
    • Report the observed issues
    • Solve the issues if possible
    • Define price per hour: 20 $/h
    • This could also attract more donations, as now they will have a clear use
  • Pay hardware for testing for the release

Minimum testing scenario:

internet1 --wire-- dual_band#1 --wifi-- dual_band#2 --wire-- single_band#1 --wifi-- single_band#2 --wire or wifi-- internet2

Requirements for dual_band router:

  • at least 1 radio at 2.4 GHz
  • at least 1 radio at 5 GHz
  • DSA supported

Requirements for single_band router:

  • maximum 1 radio at either 2.4 GHz or 5 GHz
  • DSA supported

Requirements for internet connections:

  • internet1 and internet2 should preferably be two different internet connections, but if they are the same it is ok

Physical setup requirements:

  • none, even if all the routers are on the same table it is ok
  • wifi channels have to be selected for avoiding wifi connections between routers that are not indicated as connected (i.e. dual_band#1 and dual_band#2 should be on the same channels. single_band#1 and single_band#2 should be on the same channel, but a different one from the one used by the dual band routers)

Scenarios to check:

  • checking if the internet connection internet1 goes down, if the wifi clients (common AP name) still have connection
  • checking if the internet connection internet2 goes down, if the wifi clients (common AP name) still have connection
  • checking if the internet connection internet1 goes down, if the cabled clients (on dual_band#2) still have connection
  • checking if the internet connection internet2 goes down, if the cabled clients (on dual_band#2) still have connection
  • checking roaming, e.g. with an audio call
  • define exactly how router wire to router is connected: LAN to LAN with mesh configuration e.g. https://github.com/libremesh/network-profiles/tree/master/calafou#lime-community-configuration-3

Additional tasks:

  • document how to set ethernet interfaces for mesh only or clients only

News about Altermundi roadmap 2023 ​

Cri asked in the ML SAn answered that is working in the hardware of LibreRouter2

Where to store the log of the meetings ​

ML is ok Website also ok (the archive of the ML is public anyway, so public is ok) Cri will copy the info to the website

OpenWrt 22 or OpenWrt 23 as a base for the next release candidate? ​

Currently, the release candidate 2023.1 is based on OpenWrt 22

Ilario: 23 SAn: 23 Madez: 23 Cri: 22 or 23 are ok Gothos: 23

Ilario: let's name the new release candidate 2024.1-rc1

SCENARIO ESISTENTE:

rete mista openwrt & libremesh, feedback that the developing of libremesh is not enought fast as openwrt to releasing. Which relation there is with gluon? and which different?

IMAGES ARE ALREADY AVAILABLE: https://firmware-libremesh.antennine.campiinrete.org/releases/master-ow23/

Free discussion about other projects and LibreMesh ​

Discussing technical solutions in Gluon Gothos: Would be good to have a network-profile compatible with Gluon Discussing the problem of slow release cycle in LibreMesh

Outdated release server ​

The server is outdated and is impossible to install anything. For some next meetings we need to think about it!

Firmware signatures ​

Check the "## Add new signing keys" section of this email: https://lists.autistici.org/message/20230929.142923.34529fc1.en.html

Screenshots from Github:

Seems that the keys cannot be accessed, so we either find who has the original key or we upload a new one.

Ilario writes to the people who could have the original key. If noone has it, we will just upload a new one/pair during the next project meeting. Maybe the key on Github is the same also on the repo server. Gothos will check.

Next meeting ​

Saturday the 2th of December 2023 at 13:00 UTC (14:00 CET, 10:00 ART).