El 2023-02-15 10:56, cri via LibreMesh escribió:
> On 21/01/23 15:54, cri via LibreMesh wrote:
>> we see again the next Tech meeting
>>
>> wednesday 15 of February 13UTC
Hi!
Today I will not manage to connect but I am writing here some stuff
about the topics below:
> ## support for OpenWrt 22.03, updates about:
> https://github.com/libremesh/lime-packages/pull/959 ?
When I wrote that pull request, I thought that the new configuration
format was due to the swconfig-DSA migration.
But instead it is due to the OpenWrt 19.07 vs >19.07 versions, so I have
to rewrite the pull request.
Considering this small issue (would be easy to rewrite that) and the big
issue of the new firewall used in OpenWrt 22.03 (iptables and ebtables
have been abandoned in favor of nftables) we had a short discussion in
the Element chat and in the linked pull request about supporting only
OpenWrt 22.03 in the lime-packages' "master" branch. So we would create
a "target_OpenWrt_19.07" branch for the extended support to OpenWrt
19.07 and a tag with a minor release "2020.2" which can be considered as
an updated version of the 2020.1 LibreMesh release "Expansive
Emancipation".
Can you discuss also this in the meeting?
Other relevant issues for using OpenWrt 22.03 are:
https://github.com/libremesh/lime-packages/pull/971 (Dnsmasq now can
access only specific folders)
https://github.com/libremesh/lime-packages/pull/950 (we were creating a
file that now is provided by an OpenWrt package)
And the need to migrate all our iptables and ebtables commands and
dependencies to nftables (supposedly, nftables commands are
backcompatible in OpenWrt with iptables commands, but the dependencies
are quite different, and the result is that installing a trivial package
like lime-proto-wan pulls a crazy amount of dependencies).
We can use this issue for keeping track of the updates (I am going to
copy and paste this there):
https://github.com/libremesh/lime-packages/issues/951
> ## QoS,using TC (traffic control)
My (too complex) dream-solution would be to have an integrated solution
with:
* if you access the AP via a WPA interface, you access a VPN made with
Tinc (or Wireguard) and have max priority access to the gateway you own
in your house, and mid priority access to the other gateways
* if you access the AP via an open interface, you get Pirania captive
portal, if you have granted access, you have mid-priority access to all
the gateways
* instead, if you Pirania does not grant you the access, you have low
priority access to all the gateways
> ## Hardware support
>
> ## Update doc & homepage
>
> ## GSoC news
>
> ## Next meeting
Ciao!!!!
Ilario
