This is an old revision of the document!
ChaosMeeting 2025/06
| Date | 17/11/2025 |
|---|---|
| Time | 20:00 |
| Location | nextcloud / ChaosStuff |
| Administrative Council Attendees: | virii, xbr |
| Minutes Recording | xbr |
Agenda
Minutes
ChaosStuff Network
We use a FritzBox to do PPPoE, and it also splits it into 2 VLANs: ours and a guest.
The WAN on the Omnia is the "ours" output on the FritzBox.
Turris might have some static leases with names, but probably can't resolve the names to IPs.
We should get 500 Mbit, but only get 100 Mbit, even on the Turris device. We should look into replacing the orange uplink cable that goes into the FritzBox from the Attic, through a plug in the Lab.
We have a lot of un-used equipment in the rack, we should verify what is used and clean it up. In this, we also should start thinking about future router thigns
Request Tracker
virii has reinstalled Request Tracker completely.
The code of RT is quite bad, things were broken after an update and this required a reinstall.
Passwords were reset, contact virii to get an account.
ChaosStuff Updates
Zigbee Pi's fan was broken, and was shaking the whole rack. We replaced it with a janky big fan.
The UPS has been beeping since November 5, we unplugged it and put it aside, we should change the battery on it. orimpe noted down what kinds of battery were used.
The big red button did not work, we had to manually turn on every single plug, even when turning on the SpaceAPI via the web, it didn't turn on any of the plugs. This should be a priority and this should just work.
BSides
virii has not sent an email yet asking if we can do 1 day.
Meshnet
virii accidentally bought 2x 30W solar panels, he's already actively using the 10W panels.
… TODO: virii explaining about the hardware he has, where he plans to put it, and how a combined node could look like …
Both virii and orimpe like the RakWireless hardware, but orimpe highlights the importance of a RTC clock, as otherwise, in case of a chat room, it will refuse to forward data as it's "too old/expired".
Doing both Meshtastic/MeshCore is a risk as we explode the budget for less coverage. The hardware is independent of the protocol though, which means that if MeshCore ends up being bad, we can disperse more Meshtastic nodes, or switch them to Reticulum.
We will not show the exact coordinates of the devices, but rather choose a "close enough" point which will anonymize the original coordinates.
We still don't have a logo!