Files
spektr fd8e1a5559 GNMON-001 M6 abgenommen: Dashboard oeffentlich via mon.ghostnet.selfhost.eu (Keycloak-OIDC)
Kette: Browser -> https://mon.ghostnet.selfhost.eu (NPM CT-103 ID 14, LE-TLS,
Force SSL, WS-Support, X-Forwarded-Proto/Host + 32k-Puffer) -> 10.0.0.90:8080
(nftables gnmon_firewall: nur von 10.0.0.10) -> Blazor v0.3.2 -> Keycloak
Realm Ghost.net, Client gnai-dashboard, Rollen gnai-dashboard-user/-admin.

Neu/geaendert:
- Rolle gnmon_firewall (nftables auf ghostnet-ki, Policy ACCEPT, 8080 nur
  von NPM, Monitoring-Ports non-loopback-drop), Tag firewall in monitor.yml
- Dashboard-Bind 10.0.0.90:8080 (Assertion: LAN-Bind nur mit Firewall-Tag);
  Image v0.3.2; Playbook-Verifikation akzeptiert 200/302 mit Forwarded-Headern
- App: ClientId gnai-dashboard, Auth:AllowedRoles konfigurierbar,
  KnownNetworks/KnownProxies per .Clear() (leere Initializer = Loopback-Default),
  GetClaimsFromUserInfoEndpoint=true (realm-roles-Mapper-Flags im Realm unset),
  SaveTokens=true (Logout: id_token_hint), Cookie AccessDeniedPath
  /access-denied + Page (sonst Redirect-Loop), csproj PrunePackageData=false +
  Containerfile ohne --no-restore (sonst fehlt blazor.web.js im Image ->
  Blazor-Circuit startet nicht)
- KeycloakRealmRolesClaimTransformation auf ClaimTypes.Role + [gnmon-auth]-Log
- CT-100: Adoption 09.11. (pct exec), Split-DNS mon -> 10.0.0.10 live;
  Befunde gefixt: dns_pihole_hosts_records in allen 3 Inventaren gespiegelt,
  FTLCONF_dns_hosts als eine ';'-gejointe Environment-Zeile (systemd: letzter
  Key gewinnt); gnmon_alloy doppelte Key korrigiert
- Doku: GNMON-000 M6 abgenommen (alle Befunde), GNMON-001 v2.2, GNAI-000
  Monitoring/DNS-Zeilen, GNAI-006 v3.1 (Proxy-Host 14), GNAI-012 Stand

E2E 09.11.2026: unauth -> 302 mit PAR request_uri; Direktzugriff 10.0.0.90:8080
gedroppt; blazor.web.js 200 text/javascript; Login ghost -> Dashboard 200 mit
Live-Daten, Unterseiten + WebSocket ok; testuser ohne Rollen -> saubere 403;
/logout ok; monitor.yml gesamt ok=84 changed=0. Server-Image-Store aufgeraeumt
(v0.3.2 + Rollback v0.2.0/v0.1.0).

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-09 19:34:50 +01:00
..

gnmon_firewall

Host-nftables on ghostnet-ki (GNMON-001 section 7), system scope only. The workstation inventory (user scope) is a no-op.

What it enforces

  • Dashboard port 8080 (M6): reachable only from NPM (CT-103, gnmon_firewall_dashboard_allowed_ip = 10.0.0.10). NPM terminates TLS and the OIDC redirect; the dashboard itself binds to the LAN address 10.0.0.90:8080 (gnmon_dashboard_http_listen).
  • Monitoring APIs (Loki 3100/9096, VictoriaMetrics 8428, vmalert 8880, Alertmanager 9093, node_exporter 9100): bound to 127.0.0.1 by the services and additionally dropped for non-loopback traffic (defense in depth).

What it deliberately does NOT do

The input policy stays ACCEPT: the KI host has no other firewall, and a default-drop policy introduced from the monitoring project could lock out SSH management. A full host firewall is a separate sprint (GNAI-001 M1). flush ruleset in the managed /etc/nftables.conf removes every other table — do not maintain foreign nftables content on this host.

Operations

  • Preview: ansible-playbook -i inventories/testing/hosts.yml playbooks/monitor.yml --tags firewall --check --diff
  • Deploy: same without --check.
  • Verify live: nft list ruleset (root), e.g. on the host sudo nft list table inet gnmon_filter.
  • Negative test from the workstation while the dashboard is LAN-bound: curl -k --max-time 5 https://10.0.0.90:8080/ must time out (dropped), while https://mon.ghostnet.selfhost.eu/ via NPM answers.