Files
infrastructure/llm-server/monitoring/ansible/roles/gnmon_firewall

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.