From simo.magrin a gmail.com  Tue Feb  4 18:22:01 2025
From: simo.magrin a gmail.com (Simone Magrin)
Date: Tue, 4 Feb 2025 17:22:01 -0100
Subject: [Ninux-Wireless] Test Nuovo ML server
In-Reply-To: <CAH-L2tFsoaLix23X2XP+J1iAo0+QHjR-ALUj4GSKY5AJDMCnTQ@mail.gmail.com>
References: <2ce8d64a-58ed-4316-b9a9-eadc15bff726@ninux.org>
 <CAJ5We7rhaedRgYPwgUXsx3O7DMwDNF4yE996kacXTeTdMmXP9w@mail.gmail.com>
 <5ff3b0a177539ee920d791917a0e8a9d1cd44802.camel@marcoc.it>
 <CAJ5We7pO7DVZs5zZPSWojEPJSYADm_ScMFe4jZH73sV=8-yzNg@mail.gmail.com>
 <4054E24C-34FB-4A52-85F8-BB666235B87F@ninux.org>
 <CAH-L2tFsoaLix23X2XP+J1iAo0+QHjR-ALUj4GSKY5AJDMCnTQ@mail.gmail.com>
Message-ID: <CAEBQ1n1fRQGnTAzmFpqV1yYS8BZWJ5SJhmEANcRJJC4+jRMjwg@mail.gmail.com>

niente, alla fine si é spostato tutto in spam

Il giorno lun 13 gen 2025 alle ore 19:52 Fabio Capriati <
fabio.capriati a gmail.com> ha scritto:

> Sembra sia tutto ok, almeno per bigG
>
> Il ven 27 dic 2024, 23:53 Clauz <clauz a ninux.org> ha scritto:
>
>> On 26 December 2024 23:37:19 CET, Marco Tarquini <
>> marco.tarquini a gmail.com> wrote:
>> >Il giorno gio 26 dic 2024 alle ore 23:26 Marco A. Calamari <
>> >marcoc_maillist a marcoc.it> ha scritto:
>> >
>> >Il dominio ninux.org ha il recordo DMARC?
>> >>
>> >
>> >Da quel che ricordo, è una lunga-lunga storia questa dello spam su gmail,
>> >Google pare sia un po' duro di comprendonio.
>> >
>> >Peraltro clauz a tempo perso potrebbe pure ricontrollare per l'ennesima
>> >volta la compliance a DMARC/DKIM/SPF, mandando una mail (da wireless)
>> >all'indirizzo di test generato automaticamente su https://dmarcwise.io/
>>
>> Il sito di cui sopra dice che siamo a posto su tutto, i parametri sono
>> tutti verdissimi \o/
>>
>> E quindi, se non ci sono idee migliori, consiglio di iscriversi alle
>> mailing list ninux con indirizzi non-GAFAM, vista l'aria che tira:
>> https://cfenollosa.com/blog/after-self-hosting-my-email-for-twenty-three-years-i-have-thrown-in-the-towel-the-oligopoly-has-won.html
>>
>> Clauz
>>
>> Ciao!
>> Rispondo sotto.
>> --
>> Sent from my phone with K-9 Mail. Please excuse my brevity.
>> _______________________________________________
>> Wireless mailing list
>> Wireless a ml.ninux.org
>> https://ml.ninux.org/mailman/listinfo/wireless
>>
> _______________________________________________
> Wireless mailing list
> Wireless a ml.ninux.org
> https://ml.ninux.org/mailman/listinfo/wireless
>
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: <http://ml.ninux.org/pipermail/wireless/attachments/20250204/2ca8939a/attachment.htm>

From iochesonome a gmail.com  Wed Feb 12 07:29:39 2025
From: iochesonome a gmail.com (Ilario Gelmetti)
Date: Wed, 12 Feb 2025 08:29:39 +0100
Subject: [Ninux-Wireless] Rilasciata LibreMesh 2024.1 basata su
 openwrt-23.05.5
In-Reply-To: <8dca7105-dfb1-4df7-870d-1def27f65bed@esiliati.org>
References: <8dca7105-dfb1-4df7-870d-1def27f65bed@esiliati.org>
Message-ID: <92F3E02D-D40F-4A15-A87C-B66B09701868@gmail.com>

Ciao genti!
Volevi condividere la notizi(on)a: finalmente abbiamo fatto una nuova versione di LibreMesh, la 2024.1!

Per chi non conoscesse LibreMesh: è un gruppo di pacchetti da installare/compilare su OpenWrt per configurarlo per reti wireless mesh. Una volta installato, si possono configurare varie cosette (tipo mettere una password sulla WiFi), ma la configurazione predefinita è circa "connettiti a tutte le altre antenne LibreMesh e condividi i contenuti locali e internet".
Uno degli obiettivi è di minimizzare la necessità di persone tecniche in una rete comunitaria, semplificando la gestione delle antenne. Per questo, alcune persone di Altermundi hanno anche sviluppato una interfaccia web "lime-app", che è uno dei pacchetti di LibreMesh.
https://libremesh.org

La versione anteriore, la LibreMesh 2020.4, era rimasta un po' indietro con le versioni di OpenWrt, mentre la 2024.1 gira sopra OpenWrt 23.05.5 (ma non ancora sulla OpenWrt 24.10 rilasciata due settimane fa).

Nell'email citata qui sotto potete trovare la e-mail di Gothos in cui ci stanno tutti i link per scaricare le immagini o perfino per crearne una personalizzata con una interfaccia online.
Ciao!
Ilario

-------- Original Message --------
From: gothos via LibreMesh <libremesh a krutt.org>
Sent: February 11, 2025 11:55:43 PM GMT+01:00
To: libremesh a krutt.org
Cc: gothos <gothos a esiliati.org>
Subject: [lime] Published the pre-compiled firmware images for the release 2024.1 based on openwrt-23.05.5

Hi,

I published the pre-compiled firmware images for the release 2024.1 based on openwrt-23.05.5

To download the 2024.1 images, navigate to:
https://downloads.libremesh.org/releases/2024.1-ow23.05.5/targets
Or use Firmware Selector to download:
https://downloads.libremesh.org/selector/?version=2024.1-ow23.05.5-default

The release is available in two flavors:
- mini: correspond to selecting 'profile-libremesh-suggested-packages-tiny'
- default: correspond to selecting 'profile-libremesh-suggested-packages'

Using the firmware-selector is also possible to request custom builds
based on the openwrt imagebuilder via an Attendedsysupgrade server https://github.com/openwrt/asu
For the time being only based on openwrt-23.05.5.
I will also add some versions of 24.10.x for possible testing (probably starting from 24.10.2, after increasing the storage of the server)


Additional notes
==============

I used this code to do the compilation with docker, where I left some notes about the usage:
https://github.com/a-gave/libremesh_openwrt_buildroot_docker

I published some of the docker images also here:
https://hub.docker.com/r/agave0/openwrt-buildroot/tags
They weigh a little bit (3-4GB of compressed archive, 9-10GB extracted),
but it can still be convenient in terms of time to download them, rather than build everything

Of 75 targets in 23.05.5 only 56 are built
the list of excluded, that is valid for both openwrt-23.05 and openwrt-24.10 is at:
https://github.com/a-gave/libremesh_openwrt_buildroot_docker/blob/main/excluded_targets
Some of these are simply empty (like realtek/rtl931x) or contains only profiles too small to fit the mini versions (like ath79/tiny)
others are removed because considered exotic (i.e. only nas devices, or microchip) or unrealistic that people that own those boards want to run libremesh on them.
If too many have been removed let me know.

I published a development build based on current git head ^ca6328347b97728b796fa28d243e02f95f7c6616
https://downloads.libremesh.org/development/master-ow23.05.5-ca63283-20250203/targets
Using the same docker containers referred to above,
In these there is a leftover and it has not been removed the default unused feed repo for the openwrt-kmods
to avoid downloading them since they are not used just run
sed -i '/libremesh_core/d' /etc/opkg/distfeeds.conf

Ciao!
gothos
-- 
LibreMesh mailing list
LibreMesh a krutt.org
https://www.autistici.org/mailman/listinfo/libremesh

From mikysal78 a gmail.com  Wed Feb 12 22:23:27 2025
From: mikysal78 a gmail.com (Michele Salerno)
Date: Wed, 12 Feb 2025 23:23:27 +0100
Subject: [Ninux-Wireless] Sostituzione OLSRd2 con Bird2
Message-ID: <5bb9a4f5-88a6-4967-bfc5-b2b010d4c256@gmail.com>

Ciao raga,

finalmente la ML operativa... mi mancava tanto!

Con Francesco @EliAran (su Telegram) abbiamo provato e funziona bene 
Bird2 con vari protocolli per sostitire olsrd2 che ormai non era più 
supportato.

Per la rete mesh abbiamo usato il pacchetto avahi-autoip che assegna un 
ip random al bridge br-mesh

In Basilicata abbiamo usato per la VPN zerotier e la config di bird è 
predisposta anche per il routing su IPv6 per quando tutti i nodi avranno 
up IPv6 pubblico.

Condivido qui la config se può servire a qualcuno e se si vuole iniziare 
ad usarlo migliorandolo... anche perchè con Bird2 si possono fare tante 
altre cose, come BGP etc..

Sul server ho questa config

# Configure logging
log syslog all;
log "/var/log/bird.log" all;
log stderr all;
router id from "ztknuuh73j";
# Sync bird routing table with kernel
protocol kernel kernel4 {
     description "Kernel protocol for IPv4";
     metric 50;
     ipv4 {
         export all;
         import all;
     };
};
protocol kernel kernel6 {
     description "Kernel protocol for IPv6";
     metric 300;
     ipv6 {
         table master6;
         export all;
         import all;
     };
};
protocol device {
     description "Device protocol";
};
protocol babel {
     description "Babel protocol for NINUX network";
     ipv4 {
         export where source = RTS_BABEL;
   import filter {
             if net = 0.0.0.0/0 then reject;
             accept;
   };
     };
     ipv6 {
         export where source = RTS_BABEL;
   import filter {
             if net = ::/0 then reject;
             accept;
   };
     };
     interface "ztknuuh73j" {
         check link yes;
         rxcost 600;
     };
}

Sul router ho questa

# Configure logging
log syslog all;
#log "/var/log/bird.log" all;
log stderr all;
router id from "br-lan";

# Sync bird routing table with kernel
protocol kernel kernel4 {
     description "Kernel protocol for IPv4";
     scan time 20;
     learn yes;
     metric 50;
     merge paths yes;
     ipv4 {
         table master4;
         export filter {
             if (proto = "lan") then reject;
             accept;
         };
         import filter {
             if (net = 0.0.0.0/0) && (ifname != "br-mesh") then accept;
             reject;
         };
     };
};

protocol kernel kernel6 {
     description "Kernel protocol for IPv6";
     scan time 20;
     learn yes;
     metric 300;
     merge paths yes;
     ipv6 {
         table master6;
         export filter {
             if proto = "lan" then reject;
             accept;
         };
         import filter {
             if (net = ::/0) then accept;
             reject;
         };
     };
};

protocol device {
     description "Device protocol";
     scan time 10;
};

protocol direct lan {
     description "LAN protocol";
     ipv4;
     ipv6;
     interface "br-lan";
     check link no;
}

protocol babel ninux {
     description "Babel protocol for NINUX network";
     ipv4 {
         export where (source = RTS_DEVICE) || (source = RTS_BABEL) || (net != 0.0.0.0/0);
         import where (net != 0.0.0.0/0);
     };
     ipv6 {
         export where (source = RTS_DEVICE) || (source = RTS_BABEL) || (net != ::/0);
         import where (net != ::/0);
     };
     interface "owzt0192af" {
         check link yes;
         rxcost 600;
     };
## Used to connect with other neighbours on the same layer 2 network.
## Decomment the config to use it, not this comments of course!
## Use the correct name interface, not the logical openwrt/(l)uci one.
## You can define more interfaces maches using * in regex (like "ifnet*")
## or "ifnet1", "ifnet2", "ifnetN", "otherifnetnames" form.
## You can also define more interfaces with other parameters, please refer to:
##https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.1
## After, reload the bird daemon with: /etc/init.d/bird reload
## or if you perefer, reastart with: /etc/init.d/bird restart
     interface "br-mesh" {
         type wireless; # or wired
         check link yes;
     };
}

protocol bfd {
     interface "br-mesh" {
         min rx interval 20 ms;
         min tx interval 50 ms;
         idle tx interval 300 ms;
     };
}

protocol ospf v3 internet_v4 {
     ipv4 {
         import filter {
             if (net = 0.0.0.0/0) && (ifname = "br-mesh") then accept;
             reject;
         };
         export filter {
             if (source = RTS_INHERIT) && (net = 0.0.0.0/0) then accept;
             if (source = RTS_OSPF) && (net = 0.0.0.0/0) then accept;
             reject;
         };
     };
     ecmp yes;
     merge external yes;
     area 0 {
         interface "br-mesh" {
             type broadcast;
             check link yes;
             bfd no;
         };
         interface "wan" {
             check link yes;
             stub yes;
         };
     };
};

## Ninux network currently does not deploy v6 global addresses,
## when it will happen, this config can be used to reach the ipv6 enabled
## routers for default IPv6 route (usually, to Internet).
## Simply uncomment all below to use.
#protocol ospf v3 internet_v6 {
#    ipv6 {
#        import filter {
#            if (net = ::/0) && (ifname = "br-mesh") then accept;
#            reject;
#        };
#        export filter {
#            if (source = RTS_INHERIT) && (net = ::/0) then accept;
#            if (source = RTS_OSPF) && (net = ::/0) then accept;
#            reject;
#        };
#    };
#    ecmp yes;
#    merge external yes;
#    area 0 {
#        interface "br-mesh" {
#            type broadcast;
#            check link yes;
#            bfd no;
#        };
#        interface "wan" {
#            check link yes;
#            stub yes;
#        };
#    };
#};
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: <http://ml.ninux.org/pipermail/wireless/attachments/20250212/4774ccc9/attachment.htm>