Differences

This shows you the differences between two versions of the page.

--- lb:organization:chaosmeetings:2025:cm-2025-04 [2025/08/24 21:40] – Created from the form at organization:chaosmeetings xbr
+++ lb:organization:chaosmeetings:2025:cm-2025-04 [2025/08/25 21:22] (current) – add wiki link to Meshtastic/Meshcore xbr
@@ Line 2: / Line 2: @@
 ^ Date                               | 25/08/2025                      |
-^ Time                               | 20:00                                           |
+^ Time                               | 20:00                           |
-^ Location                           | [[services:nextcloud]]                          |
+^ Location                           | [[services:nextcloud]]          |
-^ Administrative Council Attendees:  | [[user:metalgamer]], [[user:virii]], [[user:xbr]]  |
+^ Administrative Council Attendees:  | [[user:virii]], [[user:xbr]]    |
-^ Minutes Recording                  |                                                    |
+^ Minutes Recording                  | [[user:xbr]]                    |
 ===== Agenda =====
-  *
+  * Freifunk - [[user:xbr]]
+  * Alternative Meshed Networks - [[user:orimpe]], [[user:virii]]
 ===== Minutes =====
+==== Freifunk ====
+=== GitHub Org ===
+[[user:orimpe]] does not have access to the [[https://github.com/Freifunk-Luxembourg|Freifunk-Luxembourg Org]].
+[[user:fantawams]] might have access, looking at [[projects:freifunk:meetup:2019-03|FreiFunk Meetup 2019/03]]. Worst case, [[user:sid]] might have access.
+If the site is mirrored on GitHub, we could make use of GitHub Actions for building. See: [[https://github.com/freifunk-darmstadt/site-ffda/actions/runs/16657953396|Freifunk Darmstadt's usage]].
+=== Jitsi & Ansible ===
+[[https://cloud.c3l.lu|C3L NextCloud's Talk]] works, but it's not great, as such, it would be cool if we could run Jitsi on Freifunk Infrastructure.
+The pain point is using Ansible for fflux: it is so complex that it is never touched, and using Ansible for that makes it difficult.\\
+Setting up gateways via Ansible works, but the main server is too complex.
+fflux-test is now running Debian 13, Ansible configuration has been updated accordingly.
+=== VPN ===
+[[https://mullvad.net/en/blog/reminder-that-openvpn-is-being-removed|OpenVPN will be deprecrated by our VPN provider]], we need to move to WireGuard.
+Currently IPv6 does not work via the VPN, but nodes **only** have IPv6.\\
+This is due to the VPN configuration script (up/down).
+When we move to WireGuard, we'll have to rewrite those configs and the routing things.
+=== Running our own DNS ===
+We should run our own DNS, fflux has been running bind since 2023, we've just never switched over.
+=== gluon ===
+[[user:xbr]] had built experimental v2023.2.5, but wanted to add [[https://gluon.readthedocs.io/en/latest/features/multidomain.html|multi domain support]] for individual gateway testing.
+We looked into a 360 deg. AP, but it seems like the current known option is not stable in busy environments: https://forum.freifunk.net/t/cudy-wr3000-v1-instabile-verbindung/24416/3
+Adding SSH keys to the site config could be useful instead of adding them manually, possibly enabled by default. As such, we would avoid issues of "forgetting" to add keys.
+==== Alternative Meshed Networks ====
+We need to re-do the internal poll to pick a date.
+[[user:orimpe]] is considering doing a [[events:spark-up|Spark-up!]] event regarding those networks.
+In the ChaosStuff, [[user:orimpe]] set up the following:
+  * Meshtastic client
+  * Meshcore room server
+We should have an over-arching project for "network" projects: Freifunk, Meshtastic, Meshcore, ...\\
+We'll try to find a name...
+Again, we still have a wiki page: [[projects:meshtastic|Meshtastic / Meshcore]]