jazzymc/infrastructure
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
194 Commits 1 Branch 0 Tags
4d5ce8e915ed167998e0c0decb87c47a03720382
Commit Graph
7 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Kaloyan DanchevandClaude Opus 5 4c1517884b wifi: set country=Bulgaria on all radios, remove TKIP from cfg-xtrm 
The country=United States override existed to reach UNII-3 (5745 MHz),
which is not permitted in the EU. It cost more than it gained: clients in
the BG regulatory domain were power-restricted on those channels.

Setting country=Bulgaria raised the test client from 241 to 295 Mbps
immediately and ~451 Mbps once rate adaptation settled, with client signal
improving from -72 to -67 dBm. Total gain this session: 38 -> 451 Mbps.

Also:
- cfg-xtrm security.encryption tkip -> ccmp (provisioning rule 0 would
  have handed TKIP to any new 5GHz CAP interface, forcing legacy rates)
- cap-wifi1 moved to 5220 MHz (ch 44, non-DFS, legal in BG); still disabled
- Corrected: HAP wifi2 is disabled with encryption="", not tkip
- Noted that country does NOT hard-block an illegal frequency

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 2026-09-27 17:32:15 +03:00
Kaloyan DanchevandClaude Opus 5 1fba4673be wifi: move hAP 5GHz from ch 149 to ch 36, fix doc drift 
Channel 149 (UNII-3) is not permitted in Bulgaria/EU. The radio reached it
via country=United States, but BG-domain clients were power-restricted
there, giving a badly asymmetric link and ~38 Mbps at the desk.

Moving to 5180 MHz (ch 36), legal in BG and non-DFS, raised the same
client to ~241 Mbps.

Also corrected:
- CAP capdp datapath is vlan-id=30, not 40
- RouterOS versions: hAP, cAP XL and cAP AC are all on 7.23.3
- Added WAN baseline: ~880 Mbps down / ~720 Mbps up on a 1 Gbps ONT link

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 2026-09-27 16:55:29 +03:00
jazzymc 21ff7f5c12 [IMMICH] Deploy Immich v3 photo server (Google Photos replacement)
ci/woodpecker/push/woodpecker Pipeline was successful
Details 
- Compose stack at appdata/immich, exposed via Traefik at photos.xtrm-lab.org
- Library on cache NVMe (raidz1), Postgres on cache
- Nightly backup (DB dump + originals rsync) to parity-protected array disk1
- Google Takeout import ready via immich-go v0.32.0
 2026-07-08 15:15:14 +00:00
jazzymc 08874ca0b3 autokuma: fix v1->v2 config and label syntax 
- Replace v1 AUTOKUMA_DOCKER=1 with v2 env vars (ENABLED, HOSTS, SOURCE)
- Rewrite traefik-manager labels in v2 4-part syntax: kuma.<id>.<type>.<setting>
- Delete manually-created monitor #38; AutoKuma recreates it (now #39) cleanly
- Document v2 label requirements and the remaining v1-label migration

Default AUTOKUMA__DOCKER__SOURCE is Swarm Services — must be set to
Containers for standalone Docker. v2 also doesn't accept the v1 shorthand
(kuma=URL + kuma.name=... + kuma.type=...), only the explicit 4-part form.
 2026-05-18 12:45:19 +03:00
jazzymc 980df5517d dockerproxy: pin traefik-manager to .4, add direct TCP monitor for traefik 
- Pinned traefik-manager to 172.18.0.4 (was floating in the dynamic pool)
- Added Uptime Kuma monitor id=38 "Traefik Container (direct)" — TCP probe
  at 172.18.0.3:80, decoupled from the routing-layer HTTP probe so a
  Traefik container failure is distinguishable from a routing breakage
- Documented that AutoKuma v2 is silently broken; monitor was created via
  direct SQL insert as a workaround
 2026-05-17 11:54:29 +03:00
jazzymc dd1c15cf6b dockerproxy: redesign IPAM with static block + dynamic /25 pool 
Recreated dockerproxy network with --ip-range 172.18.0.128/25 so Docker
auto-allocations are isolated from the .2-.127 static reservation block.
Eliminates IP-collision class that caused the 2026-05-17 Traefik outage.

Adds 13-DOCKERPROXY-NETWORK.md as the canonical reference for the
network spec, recreate command, and current IP assignments.
 2026-05-17 08:36:46 +03:00
jazzymc 6506b22aea incident: traefik IP collision on dockerproxy (2026-05-17) 2026-05-17 08:10:39 +03:00