Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| lb:organization:chaosmeetings:2025:cm-2025-04 [2025/07/28 23:42] – removed xbr | lb:organization:chaosmeetings:2025:cm-2025-04 [2025/10/28 17:16] (current) – ↷ Links adapted because of a move operation 187.62.87.230 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ChaosMeeting 2025/04 ====== | ||
| + | ^ Date | 25/ | ||
| + | ^ Time | 20:00 | | ||
| + | ^ Location | ||
| + | ^ Administrative Council Attendees: | ||
| + | ^ Minutes Recording | ||
| + | |||
| + | ===== Agenda ===== | ||
| + | |||
| + | * Freifunk - [[user: | ||
| + | * Alternative Meshed Networks - [[user: | ||
| + | |||
| + | ===== Minutes ===== | ||
| + | |||
| + | ==== Freifunk ==== | ||
| + | |||
| + | === GitHub Org === | ||
| + | |||
| + | [[user: | ||
| + | |||
| + | [[user: | ||
| + | |||
| + | If the site is mirrored on GitHub, we could make use of GitHub Actions for building. See: [[https:// | ||
| + | |||
| + | === Jitsi & Ansible === | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | 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:// | ||
| + | |||
| + | 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: | ||
| + | |||
| + | We looked into a 360 deg. AP, but it seems like the current known option is not stable in busy environments: | ||
| + | |||
| + | 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 " | ||
| + | |||
| + | ==== Alternative Meshed Networks ==== | ||
| + | |||
| + | We need to re-do the internal poll to pick a date. | ||
| + | |||
| + | [[user: | ||
| + | |||
| + | In the ChaosStuff, [[user: | ||
| + | * Meshtastic client | ||
| + | * Meshcore room server | ||
| + | |||
| + | We should have an over-arching project for " | ||
| + | We'll try to find a name... | ||
| + | |||
| + | Again, we still have a wiki page: [[projects: | ||