-
Notifications
You must be signed in to change notification settings - Fork 41
/
Copy pathreport_2023.txt
1525 lines (961 loc) · 62.6 KB
/
report_2023.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
---
title: LibreMesh 2023 Meetings
ref: report 2023
lang: en
---
## 2023-12-02 PROJECT MEETING
*Saturday the 2th of December 2023 at 13:00 UTC (14:00 CET, 10:00 ART).*
Time: 13:00-14:16 UTC
**People:** Cri, Chris
Welcome Chris, he is a Linux System Administrator from Minnesota, U.S.A
Cri shared documentation from antennine network
### Website
we have the possibility to keep the same structure of the old website: jeckyll + ascii-doc but with a different theme: this is good because the content input can be txt file, and we reuse txt file to put the doc in the firmware and be readable by browser.
Cris: I'm happy that we keep the old habits about the structure oof the content, but with this restyl we move in a more fashionable shape. And I think is motivating also to update the documentation :) that probably the next work that we have to do... for the new year
Chris: I think the new theme looks nice. (But I am not a designer)
From this assembly the opinion looks positive to the merge of the "new restyle" of the website. we wait a week to see reaction in mailinglist, and after I(Cris) can accept merge request.
### Testing
two people answered to this call https://lists.autistici.org/message/20231101.163202.5a0742ed.en.html
I, Cris, think that both are trustable people.. I expected that some of them come to this meeting, but this not happen.
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
Pony proposal and devices: https://lists.autistici.org/message/20231126.160655.2b35dc1f.en.html
Cris: good point that the devices are with DSA.. not clear "None of them are running babeld though" and not clear if this is give problem to test, for example the first 2 scenarios:
Hiure https://lists.autistici.org/message/20231106.130003.64e0e1be.en.html
Cris: Good point is that can have a test in a real infrastructure. I would like know if the devices are with DSA or not..
we can wait answer in the mailinglist, if is present DSA on the devices is better to test because is one of the new feature present in openwrt23 and 23.
### Name of the new release
Gio proposed Fantastic Forwarder https://lists.autistici.org/message/20231027.124816.b94a37d1.en.html
For this assembly the name sounds good!
### GSoC2024
we just introduced the topics.. we are happy to listen proposals in the next weeks in the mailinglist.
the last year with the opportunity and money (circa 3k euro) from th GSoC we wrote Ansible roles to automated the build of the Libremesh release candidate. and this was really good for the Libremesh project.
So lets go to think something of improving for the next year. The work will be done in summer 2024 and we need also 2 people that apply as Mentor.
we can propose probably 2 projects.. but all the year depend from freifunk and google how many project can be really realized.
Topics:
* Assign the work-grant for testing the release candidate
* Website restyling, e.g. https://libremesh.antennine.campiinrete.org
* Next release name
* GSoC2024
## 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:
* news
* website and documentation update
* need of a Docker image for unit testing on OpenWrt 22.03
* decide the list of targets for being compiled for release 2020.2 based on OpenWrt 19.07
* upcoming release LibreMesh 2020.2
* News about Altermundi roadmap 2023 ?
* how to use the donations on OpenCollective (e.g. a compilation server, or donation to Battlemesh) https://opencollective.com/libremesh
* news about battlemesh
* next meetings dates
* resume of previous technical meetings and announcement of next technical meeting date
for the next TECH meeting:
* proposal: move the report in the wiki of github? another wiki? what is thi?https://gitlab.com/libremesh
* Check that issues and the label is:issue is:open label:"in progress" is actulized
https://github.com/libremesh/lime-packages/issues/
* future release LibreMesh 2023.1 (based on openwrt-22.03)
* prioritise a list of issues to be resolved for the next LibreMesh 2023.1 release based on OpenWrt 22.03 https://github.com/orgs/libremesh/projects/3/views/1
* decide a list of packages to be included in next LibreMesh 2023.1 https://github.com/libremesh/libremesh.github.io/issues/103
* This question from Elektra during past tech meeting: - How are people porting new devices?
Relevant?:
https://communitynetworks.group/t/expanding-openwrt-libremesh-hardware-support/790/5
https://communitynetworks.group/t/openwrt-libremesh-image-building-learning-group/823
For next project meeting:
* introductions and recent projects and contributions related with LibreMesh
### 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).
== 2023-10-07 PROJECT MEETING
**People & list of Topics**
cri, ilario, mwarning42
* Annuncing the new releases
* Scheduling next meeting
* Testing release candidate
* Checking status of decisions of last meeting
* Communication problem
*Chatting for audio test*
Nice fresh video: https://media.ccc.de/v/camp2023-57058-resilient_solar_energy_autonomous_infrastructure_with_freifunk_openmppt_controllers
=== Annuncing the new releases
\o/ yhuuuu Lime 2023.1 is out!
https://lists.autistici.org/message/20230929.142923.34529fc1.en.html
https://lists.autistici.org/message/20230929.152044.f1940e95.en.html
firmware selector!!
https://repo.libremesh.org/selector
One small problem with the compiled images:
they already include a populated /etc/config/lime-community.
This should create a conflict when someone will include (compiling it in or via OPKG) a network-profile
Gothos will compile them again. He originally included the libremesh-default network-profile
Also, some lines are different from the lime-defaults: https://github.com/libremesh/network-profiles/issues/91
**TO DO:**
- write a News in the news section (Cri, done)
- change the menu item in the website: Get the last release! (ilario, done)
*A new stable release and a release candidate for Openwrt 22!*
We released a new version of Libremesh based on OpenWrt 19!
https://downloads.libremesh.org/releases/2020.4-ow19/
and a new release candidate based on OpenWrt 22:
https://downloads.libremesh.org/releases/2023.1-rc2-ow22/
This means that the release candidate needs testing, bug fixing and
loads of community love so that we can have an amazing release that can
actually ease the creation of community networks everywhere.
Check out the: https://lists.autistici.org/message/20230929.142923.34529fc1.en.html
https://lists.autistici.org/message/20230929.152044.f1940e95.en.html
for more detailed information.
Another great gourgeous news is that from now we have a Firmware Selector, check it out here:
https://repo.libremesh.org/selector
=== Scheduling meetings 2024
Keeping each 2 months, first Saturday of month, but adding some extra infraweek days to ease the participation to people who cannot on Saturdays
Next year we use a new pad XD -> disroot use the plugin to have header and it is possible have a Table of Contents
https://pad.disroot.org/p/LibreMesh_meetup_2024
Adding some meetings matching the Spanish bank holidays...
Remember to invite developers that we never see during 2023 and remember to them about "community meeting": konejo, javier,
Update: https://libremesh.org/communication.html ->
Wednesday the 1st of November 2023 at 13:00 UTC (14:00 CET, 10:00 ART).
Saturday the 2th of December 2023 at 13:00 UTC (14:00 CET, 10:00 ART).
Thursday 4th of January 2024 at 13:00 UTC (14:00 CET, 10:00 ART).
Saturday the 3rd of February 2024 at 13:00 UTC (14:00 CET, 10:00 ART).
Saturday the 6th of April 2024 at 13:00 UTC (15:00 CEST, 10:00 ART).
Saturday the 1st of June 2024 at 13:00 UTC (15:00 CEST, 10:00 ART).
Monday the 24th of June 2024 at 13:00 UTC (15:00 CEST, 10:00 ART).
Saturday the 3rd of August 2024 at 13:00 UTC (15:00 CEST, 10:00 ART).
Wednesday the 11th of September 2024 at 13:00 UTC (15:00 CEST, 10:00 ART).
Saturday the 5th of October 2024 at 13:00 UTC (15:00 CEST, 10:00 ART).
Friday the 1st of November 2024 at 13:00 UTC (14:00 CET, 10:00 ART).
Saturday the 7th of Dicember 2024 at 13:00 UTC (14:00 CET, 10:00 ART).
...
=== Tech topics to discuss:
* firmware signatures
* il server delle releases has barely enough storage space and old software.
=== Donations
* Fatto curioso di donazioni "spontanee" in chat, che ne pensiamo? Good, but it would be better to have them managed via OpenCollective.
* We should announce that the donation money is available for buying hardware for developers
* FSFE sono interessati a community wireless network per sapere che hardware proprietario ma con software libero usiamo, Cristina gli scrive..
== 2023-08-05 PROJECT MEETING
**People & list of topics**
ilario(cat), Cri(it), Troian(br), mwarning(berlin), Arinc(Türkiye), Gothos(it)
15:07 - hope to finish 16:07
* new release based on old OpenWrt
* new release candidate based on recent OpenWrt
* adding and removing people with access to repo server and Github organization
* stickers done for battlemesh - https://repo.libremesh.org/tmp/stickers/
* Starting using Attended SysUpgrade
* Technical meeting: - proposal-
=== New release based on old OpenWrt
* based OpenWrt 19
There is a tag
https://github.com/libremesh/lime-packages/tree/2020.3
https://github.com/libremesh/lime-packages/commits/master
We are waiting to decide whether to increase the default distance parameter
we want relase after decide about "default distance"
https://github.com/libremesh/lime-packages/issues/201
https://github.com/libremesh/lime-packages/blob/v2020.3/packages/lime-system/files/etc/config/lime-defaults#L62-L75
Some data from Gothos and Ilario, with a script for replicating the analysis
https://github.com/ilario/wifi-distance-setting-exploration
Experience on distance parameter:
Cri: in our community with directional links, 10 km is a good default because people can flash the antenna/router by themself and see that Lime works. in other case, they
Troian: we are using omnidirectional routers 80 m away from each other, in a line of 3 to 5 routers, so we flash the firmwares with other distances
=== New release candidate based on recent OpenWrt
* based OpenWrt 22
Possible point for a release: https://github.com/a-gave/lime-packages/tree/v2023.1
Ansible tool used to do this release candidate: https://gitlab.com/a-gave/libremesh-ansible-playbooks
here local community repo with this release, but with name Master, that is not the best..
https://firmware-libremesh.antennine.campiinrete.org/releases/master-ow22/targets/
Let's create the 2023.1 branch, add the commit for setting the release name
https://github.com/libremesh/lime-packages/commit/88251b8dbca19783a24b56d29205f8c1d63244ca
and tag v2023.1-rc1
Ilario will do this.
Gothos will use the new Ansible tools for compiling the release candidate
=== Adding and removing people with access to repo server and Github organization
People with access to the repo.libremesh.org:
* aparcar
* dbellomo
* gio
* gui
* ilario
* nicopace
* pablo
* spiccinini
* daniel
* gferrero
* guido
* joaquin
* nicolas
* p4u
Adding: Gothos, Cri
Ilario asks if it is ok to add them, with a deadline of a week.
People in the LibreMesh organization on Github:
* altergui Gui
* amuuza amuza
* andrenarchy André Gaul
* AngiieOG Angie
* aparcar Paul Spooren
* axn Axel Neumann
* bennlich Benny Lichtner
* brunovianna bruno vianna
* dangowrt Daniel Golle
* fnbellomo fnbellomo
* FreifunkUFO FreifunkUFO
* G10h4ck G10h4ck
* gabri94 Gabriele Gemmi
* germanferrero Germán Ferrero
* hiurequeiroz Hiure
* ilario Ilario Gelmetti
* nicoechaniz nicoechaniz
* nicopace Nicolás Pace
* nordurljosahvida Nicolas North
* p4u Pau
* PabloCastellano Pablo Castellano
* raylas Raymond Douglas
* selankon selankon
* spiccinini Santiago Piccinini
How to add people: once per year sending an email explaining the criteria for applying. Then during the community meetings in August, accept people is there are not contrary reason.
Cri sends the first email
Adding:
* Cri github.com/digitigrafo
* Daniel Golle? https://github.com/dangowrt - let's ask
* Gothos https://github.com/a-gave
* Jorge https://github.com/javierajorge - let's ask
Ilario asks to Jorge, Daniel Golle
Update: I don't have any contact of Jorge
=== Stickers
we have to give back the money to ilario
Ilario will try to collect them from OpenCollective
Update: I managed to request the money on OpenCollective, it is easy!
Some people on the chat asked stickers
If a big community or an event wants to have the stickers they can print them and we pay the printing with the money from donations on OpenCollective
details for printing stickers:
https://lists.autistici.org/message/20230509.143549.d28a5cc1.en.html
files:
https://repo.libremesh.org/tmp/stickers/
some events where we can be and give stickers https://foss.events/:
* https://hackmeeting.org/hackit23/
* https://www.internetfreedomfestival.org/
* https://2k22.balccon.org/
=== Starting using Attended SysUpgrade
ASU is amazing. It uses the OpenWrt ImageBuilder
If we want to use the official ASU server, we need to use ODHCPD for IPv6:
https://github.com/libremesh/lime-packages/issues/294
I we set up our own ASU server, then there are just tiny things to fix:
https://github.com/libremesh/lime-packages/issues/1000
=== Technical meeting: - proposal-
13 UTC Thursday 17th August
finish at 16:20
== 2023-07-03 PROJECT MEETING
**People & list of topics**
Cri, Gio, gothos
Thurdayday the 13rd of July 2023 at 14:00 UTC (16:00 CEST, 11:00 ART).
=== Updates
Gio sta lavorando sul plugin(?) shared state, non è un pacchetto essenziale nell'ultima release LiMe2020, ma lo sarà nel futuro xchè da un sacco di info, in pratica lo si sta riscrivendo da LUA a C++. il tempo per fare altro è poco.
Come supportare Openwrt 22.05? stan cambiando un sacco di cose, si rischia che la prossima non sia di nuovo compatibile con la precedente
dalla comunity antennine.noblogs.org abbiamo sperimentato e funziona LiMe 2023.1 per le tplink CPE 510 v3
, che non supportano la versione 19 di OpenWrt, ora stiam testando anche le mikrotik Router Board Light Head 5 https://openwrt.org/toh/hwdata/mikrotik/mikrotik_lhg_5
Gio per lavorare si basa perlo più su OpenWrt development
Cri dice che pubblicherebbe i devices provati in valle per dare segno dal sito che LiMe sta andando a supportare le nuove release di OpenWrt
Come si fa una release candidate?
in teoria si fa un tag e poi si fa andare una suite di test, e poi un po a mano la lime-app
Individuare il commit che si è testato:
siam sulla master
Commit: 10e9bf65684708d5739ada850fd280a6abf3cc72 di https://github.com/libremesh/lime-packages
ATTENZIONE ci sn differenze di build tra il buildroot e l'imagebuilder: non ci stampa nel banner il commit della versione libremesh usata per buildare, non abbiam indagato sul perchè..
Altro esempio inserisce batctl-tiny invece che completo
Conveniamo che Libremesh è basato sul buildroot, e in realtà non garantiamo da nessuna parte che davvero concluda le build identiche con l'image builder
Architetture da compilare x la Release Candidate:
ath79
mediatek ( per tutti e 2 ? )
qualcom atheros
ralink
x86
usermod linux
verificati in questa lista: https://downloads.openwrt.org/releases/22.03.4/targets/
ath79
mediatek
x86
una volta compilati i pacchetti con la buildroot... o anche la buildroot completa, conviene metterla sul server http che esponiamo: https://downloads.libremesh.org/releases/
Mettere anche i pacchetti volendo tutti buildati uno per uno, però è una mega sbatta, mettendo la buildroot intera, cmq ha tutto. Pacchetti singoli flaggato M, si potrebbe mettere anche nel file di configurazione di opkg.. alcuni device vogliono i pacchetti aggiuntivi compilati nella stessa build con cui è stato compilato il kernel.
https://downloads.libremesh.org/releases/2020.1/targets/ath79/generic/packages/
oppure un tar.gz con tutta la buildroot che ha buildato.
Oppure mettere una immagine docker che ha dentro il tutto, così è riproducibile totalmente.
OK, ci vuole un po di tempo per buildarle tutte.. le mettiamo a fare.
Una volta che si hanno i bin e il tar.gz della buildroot. scrivere in lista LiMe ed o Ilario o .. che possono pubblicare il tutto.
VARIE: rispetto a libremesh curtigghio, è una possibile strada del futuro in quanto 802.11s è una vita che non lo aggiornano.
Gio riprenderebbe più avanti a lavorare su quello. Bello se ci lavorano altri di OpenWrt.. lui può supportare
== 2023-06-03 PROJECT MEETING
**People & list of topics**
Saturday the 3rd of June 2023 at 13:00 UTC (15:00 CEST, 9:00 ART).
Topics:
* Analysis of the implementation status of last meeting's decisions
* Next tech meeting dates
* sending stickers to communities or allowing communities to print stickers and pay them from the donations on the OpenCollective?
* check if communication channel is working and if is clear the decision making workflow (the method is not decided but the workflow yes-> dic 2021 ), write in website.
* write a roadmap of LibreMesh for the next 6month
- release of lime 2020.3 (openwrt19)
- release of lime 2023.1 (openwrt22)
=== To do for next meetings
- check the design of the project after half and 1 year (dic 2021->june 2023)
- checking our web presence match with the design of the project
- update the list of "owners" and "members" on the Github organization "libremesh"
- fix translation from ...
- decide and planning where move the website (we said that github is temporary...)
- fix the list of older release,
- test how publish next release, (2023.1 release based on OpenWrt 22.03 is quite far from being ready)
- annuncing/documenting next release (2020.3 based on OpenWrt 19.07 would be ready to release, but we could release it as 2020.4 with an increased default "distance" parameter for the 5 GHz radios)
- update list of used hardware.. (e.g. adding PlasmaCloud PA1200, Xiaomi MiRouter 4A Gigabit Edition)
=== Long list of topics by the previous meetings: decision making, etc...
https://pad.codigosur.org/LibreMesh_meetup_dic_2021#L1438
- resume of the BattleMesh
- resume of the network installed at Calafou for the BattleMesh with the technical tricks included in its network-profile https://github.com/libremesh/network-profiles/tree/master/calafou
- list of issues observed during BattleMesh and traspassing this list to the LibreMesh issues list
* test OpenWISP with LibreMesh (install both OpenWISP packages https://github.com/openwisp/openwrt-openwisp-monitoring/tree/0.1.0#install-pre-compiled-packages and https://openwisp.io/docs/user/configure-device.html#install-openwisp-config , figure out how to set up an OpenWISP server and set it up, maybe virtualized with Docker Compose)
* analyze the poor performances of the mesh link (maybe due to VHT80 channel width? The routers see each other at -80 dBm that is too low for this very good line of sight)
* get two outdoor routers (PlasmaCloud PA1200, Duy should have some) and flash them as the mesh link, check the speed and check if with different channels, channel width or other things it gets better
* understand how BATMAN_V is getting the master interface (now it does not find it. It runs on a VLAN, but needs info from the original interface) and fix something so that it works in LibreMesh
* (unrelated to Calafou) make a release of LibreMesh 2020.3, still based on old OpenWrt 19.07
* implement Opportunistic Wireless Encryption easy setup in LibreMesh and use it in Calafou. Also, encrypt the mesh link
* fix the super annoying Makefile of hostapd (wpad-*) in OpenWrt (see https://github.com/openwrt/openwrt/issues/8312 )
* set up monitoring with prometheus (in case doing it with OpenWISP is too difficult)
* double check the documentation from Aparcar on the usage of the ImageBuilder
* update unit testing script to work with OpenWrt 22.03
* understand what should we/odhcpd developers do for stopping using dnsmasq-dhcpv6 and start using odhcpd for DHCP on IPv6 as in OpenWrt. Someone (Aparcar? Marek?) said that in LibreMesh we are not using odhcpd because it cannot read the leases list from and external source (e.g. a file). Maybe Daniel Golle can implement that.
* reboot the router once every week only if the internet connectivity is not present https://github.com/libremesh/lime-packages/issues/1023
* txt.file mentioned that there are two settings in OpenWrt that would be useful:1) for telling the clients to use a specific country code (e.g. if the router country code is set to ES, also the clients should use the same)2) for telling the clients which channels are in use in the current network (I hope it can increase the speed of the roaming switching)
* Make sure that from the "events' network" clients cannot ping/reach hosts in "classic network" except the fiber router * Put LibreMesh and BattleMesh stickers on every router of the "events' network" * Label the ports with a marker writing on the router * Coordinate with Konejo for fixing the support of lime-app for OpenWrt 22.03 Please add anything you consider useful :) then we can take this list and use its items to create new tickets-issues on Github :)
* understand why eth1 (wan) in PlasmaCloud PA1200 router used as gateway gets added in br-lan, and this should not happen. Checking network.lua in lime-system. If we don't have time for fixing this, hardcode a fix.
* understand why static IP configuration didn't work as expected. For the gateway LibreMesh node, at some point the dhcp client was not getting anything, so we tried with a static IP but did not do anything. What we added to /etc/config/lime-node is:
config net usingLANasWAN
option linux_name 'eth1'
list protocols 'wan'
list protocols 'static'
option static_ipv4 '172.31.17.254/24'
option static_gateway_ipv4 '172.31.17.1'
== 2023-05-12 TECH MEETING
**People & list of topics**
Cri, Gothos, Arinç, DangoWrt, notplants, Catuaba, Ilario, Ivana, Sergey, robbe, Jesi, Ivan, Cypherhippie, txt.file
* how to connect a new device
* how to use cable connections, wan and mesh
* list of mesh routing protocols
- batman-adv on layer-2
- babeld per default on layer-3, but also bmx6 an bmx7 are in active use, olsrd is also supported but probably not use anywhere
situations for which routing protocol
how to understand which interface is which (example interface list: https://pad.commoninternet.net/p/lr-interfaces)
process to build the firmware on top of OpenWrt 22.03
still present bug on LibreMesh support of OpenWrt 22.03
* web interface bugs, something changed between 19.07 and 22.03 and things are broken now... we will fix it last once everything else works
* thisnode.info (anygw) doesn't work well to connect to next router when conneting via wired link
* diagnostic info (traceroute?)
* thisnode.info (anygw) should have been fixed now by p0ny
* pirania captive portal may need adjustment to nftables
* tell babeld to silently ignore interfaces which are down or without addresses (log spam)
* wireless band names have changed (not very important)
* dependency mess of wpad-*
imagebuiler support status
* x86 images are broken?
* config.buildinfo? => it's next to where you downloaded ImageBuilder
* config.buildinfo? Doesn't it should change if I add feeds and rebuild? => but then you should also have a new ImageBuilder. If you are only building a single feed from source, then this would change config.buildinfo, but it cannot be easily merged or represented again in a single file
* bzImage for x86 (needed for qemu) is missing => using *generic-kernel.bin instead and it works
* BATMAN V protocol doesn't work well in situations when ExpectedThroughput is not available from the hardware. Also hidden-link behind a wifi-link can limit bandwidth and is not discovered by BATMAN V.
Altermundi roadmap
how to isolate your home network if you do not want to have people from the mesh to see your local shares or reach your printer
=== How to connect a new device
as a community approach of managing mesh, so if you are 1 probably libremesh is overkill, but you can use as range extender for example. you flash 2 devices and you try. minimal configuraion. the difficult is at the begin to flashing the device but after you should not need a tech team. also Lime is modular. double mesh protocol, in layer 2 batman and 3 with babbeld. you isolate the layer 3 in your house or the place that you want isolated.
=== How to use cable connections, wan and mesh
wan just plug and works...
LAN-LAN if you connect two libremesh nodes via their LAN ports with a cable, you should configure the port for not being included in the br-lan bridge, see https://github.com/libremesh/network-profiles/commit/57eeae71781abb2403ff61afda9ca7d2664bfc7e
anyway, modern routers have a chip that cuts the loops or the CPU should realize and stop the loops
=== How to understand which interface is which
ip6tnl created by a kernel module even if not used
ifb0 for traffic shaping
br-lan switch
dummy0 fake interface for having a stable MAC that does not depend on interfaces going up or down
eth0.1 virtual interface with all the LAN ports
anygw a dummy interface, member of br-lan
https://openwrt.org/playground/arinc9/network.interfaces
=== Still present bug on LibreMesh support of OpenWrt 22.03
lime app with some issues, coneco is workin on this.
https://github.com/libremesh/lime-app/issues/378
connecting by cable to a router connected by cable
and using the thisnode.info IP, all the wire-connected nodes answer, breaking ssh connections
bug present also in previous versions!!!
https://github.com/libremesh/lime-packages/issues/1008
it could have been fixed by Pony
we need a filter for babeld over batman
babeld is complaining a lot
https://github.com/libremesh/lime-packages/issues/1003
wpad-* for mesh encryption has a weird Makefile that makes thing complicated to select in menuconfig
https://github.com/openwrt/openwrt/issues/8312
one option, to write what you want in the .config:
https://github.com/libremesh/network-profiles/blob/master/calafou/indoor2/DOTconfig-xiaomi_mirouter_4A_gigabit_edition
=== Imagebuiler support status
aparcar added documentation for using the ImageBuilder in the readme:
https://github.com/libremesh/lime-packages/blob/master/README.md#using-the-imagebuilder
gothos: using it with x86 does not work on qemu
documentation on network-profiles
https://libremesh.org/development-network_profiles.html
https://github.com/libremesh/network-profiles/tree/master/calafou
=== Company for stickers
german company
explain them the project, they are community-friendly
https://www.stickma.de/
== 2023-04-07 TECH MEETING
**People & list of topics**
Cri, Sam, Ilario
=== Updates
Creating the "v2020.2" tag for the release based on OpenWrt 19.07
git pull upstream OpenWrt_19.07_compatible:OpenWrt_19.07_compatible
git tag -a v2020.2
git push upstream-git --tags
And now build!
Build on repo.libremesh.org stops with an error. Maybe due to the old software running on the server??
== 2023-04-01 PROJECT MEETING
**People & list of topics**
Cri, Sam, Ilario
Topics:
* news
* website and documentation update
* need of a Docker image for unit testing on OpenWrt 22.03
* decide the list of targets for being compiled for release 2020.2 based on OpenWrt 19.07
* upcoming release LibreMesh 2020.2
* News about Altermundi roadmap 2023 ?
* how to use the donations on OpenCollective (e.g. a compilation server, or donation to Battlemesh) https://opencollective.com/libremesh
* news about battlemesh
* next meetings dates
* resume of previous technical meetings and announcement of next technical meeting date
for the next TECH meeting:
* proposal: move the report in the wiki of github? another wiki? what is thi?https://gitlab.com/libremesh
* Check that issues and the label is:issue is:open label:"in progress" is actulized
https://github.com/libremesh/lime-packages/issues/
* future release LibreMesh 2023.1 (based on openwrt-22.03)
* prioritise a list of issues to be resolved for the next LibreMesh 2023.1 release based on OpenWrt 22.03 https://github.com/orgs/libremesh/projects/3/views/1
* decide a list of packages to be included in next LibreMesh 2023.1 https://github.com/libremesh/libremesh.github.io/issues/103
* This question from Elektra during past tech meeting: - How are people porting new devices?
Relevant?:
https://communitynetworks.group/t/expanding-openwrt-libremesh-hardware-support/790/5
https://communitynetworks.group/t/openwrt-libremesh-image-building-learning-group/823
For next project meeting:
* introductions and recent projects and contributions related with LibreMesh
=== News
In the Google Summer of Code we have a solid application by "samlo" for the LibreMesh-related project
Resume about the workflow of GsoC for mentors and students: send reports, write posts in the freifunk website
Super nice that Gluon is a new tag standard of hardware supporting openwrt.
Gluon added Librerouter in supported hardware
=== Website and documentation update
There are translations on TranslateWiki that have not been copied to LibreRouterOrg/docs
https://github.com/libremesh/lime-packages/issues/257#issuecomment-1453891582
=== Translations
https://translatewiki.net/wiki/Category:LibreMesh we need to have an appointment with Altermundi and Libremesh so we organize to update translation on the website.
WHEN?
Updates about Home page of website https://libremesh.org/ , update of organizations
Note about website: https://pad.disroot.org/p/libremeshwebsitechecks_ifuemhfjk
- email back the organizations that aswered: Cri
- send to Luandro email to have feedback about: https://www.redfusalibre.org,
https://www.coolab.org/ - https://ibebrasil.org.br/ - https://nupef.org.br (Cri) DONE
- Send email Gio to ask about the names of the 25 new community this year of Semillero (Cri) DONE
---> https://communitynetworks.group/ Chiedo, ? aggiungiamo nei promotori Sì
**Organizations supporting LibreMesh:**
| Guifi.net | Iberian peninsula | http://guifi.net | image:img/guifi-logo.png["Guifi.net",role="right"]
| FreiFunk | Germany | http://freifunk.net | image:img/logo_freifunknet.png["FreiFunk",role="right"]
| FunkFeuer | Austria | https://www.funkfeuer.at | image:img/0xff_logo.png["FunkFeuer",role="right"]
| Ninux.org | Italy | http://ninux.org | image:img/ninux_logo.png["NiNux",role="right"]
| AlterMundi | Argentina | http://altermundi.net | image:img/altermundi_logo.png["Altermundi",role="right"]
| Wakoma | Global | https://wakoma.co/ |
| LibreRouter | Global | https://librerouter.org/ | image:img/librerouter_isologo.png["LibreRouter",role="right"]
**Community mesh networks using Libremesh:**
| Antennine | Appennino Bolognese | https://antennine.noblogs.org | image:img/ninux_logo.png["NiNux",role="right"]
| Janastu CowMesh | Rural Karnataka | https://open.janastu.org/projects/cowmesh|
Several other community networks are using or used LibreMesh on their devices with their own customizations (network profiles), some of these are listed link:https://github.com/libremesh/network-profiles[here].
* Add News on the website? the last is about battlemesh, ok. we can update with the date..( Cri)
* Add list of sure supported device?
https://libremesh.org/docs/hardware/
we have a long list of hardware used in various communities, but we don't know whether they used LibreMesh or not on that!
* Add icon for hardware in documentation page menu
we are using FontAwesome 4.3, which is old. We could use newer FontAwesome...
https://fontawesome.com/v4/icons/
Ilario will update FontAwesome
Ilario rewrites the Get It! page once we have the 2020.2 release
=== Need of a Docker image for unit testing on OpenWrt 22.03
Question: about virtualization for testing Libremesh?-> there is the project of the last year and docker images.. moved the conversation on the next topic: need of a Docker image for unit testing on OpenWrt 22.03
https://github.com/libremesh/lime-packages/pull/938
https://github.com/libremesh/lime-packages/issues/389
Sam can ask to aparcar on Element/Matrix list how to buid a Docker image for that
* decide the list of targets for being compiled for release 2020.2 based on OpenWrt 19.07
ath79/generic
ramips/mt7621
x86/64
??ar71xx/generic??
* Add targets to the firmware? https://downloads.libremesh.org/releases/2020.1/targets/
we can add more target for the new release that will be soon?
sam: I would propose to keep ar71xx/generic targets like
- ubnt-lbe-m5
- ubnt-loco-m-xw
- ubnt-nano-m-xw
- ubnt-nano-m
ar71xx/generic will also be compiled
=== Upcoming release LibreMesh 2020.2
vorremmo compilarla ed esporre dal server da cui esponiamo ora: https://downloads.libremesh.org/releases/
Il server non è aggiornato e non builda, quindi bisogna compilare in locale e poi solo uploadarli.
Una volta che ci sono dalla Valsamoggia possiamo testare alcuni target
Poi facciamo annuncio ufficiale
https://github.com/libremesh/lime-packages/tags
Ilario creates a v2020.2 tag at the commit where G10h4ck created the OpenWrt_19.07_compatible branch.
https://libremesh.org/development-kernel_vermagic.html
=== News about Altermundi roadmap 2023 ?
We have no news, so we can write an email in list and personally to know news.. (Cri)
=== How to use the donations on OpenCollective
(e.g. a compilation server, or donation to Battlemesh) https://opencollective.com/libremesh
Whishlist:
- 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?
- hardware per testare il supporto?
=== News about battlemesh
This year there is not support for the travel
C'è stata un acquisto economico di router per fare la rete di Calafou, c'è il piano di usare Libremesh,
plasmacloud pa1200, che hanno openwrt 22.03(?)
quindi vorremmo arrivare al battlemesh con libremesh basato su openwrt22.03
=== Next meetings dates
* project meeting:
During battlemesh, online and in real life , 13utc, 3rd day of the vent -> 10 may
Saturday the 3rd of June 2023 at 13:00 UTC (15:00 CEST, 9:00 ART).
* technical meeting:
Friday the 7th of April 2023 at 13:00 UTC (15:00 CEST, 9:00 ART).
Closing at 17:24 CEST