# Managed by Ansible (role: pia-gateway). Do not edit by hand. # # Periodically re-runs the kill-switch seed script (pia-killswitch.sh) so # its invariants — source rule, table default, and specifically the # FORWARD jump's position — are re-asserted on a schedule, not only at # the external trigger points that used to be the only times it ran # (boot, a UFW reload, or an Ansible-detected content change to the # script itself). Needed because other host components that also manage # iptables — kube-router and dockerd — reassert their OWN position-1 # jumps independently, and confirmed live (2026-09-22) to do so more # often than originally assumed: the FORWARD jump drifted twice within # about an hour under this cluster's ordinary CronJob/pod churn (ca-sync, # porkbun-ddns, gitea-backup, ...), not just at boot-scale events. # # The script itself is already fully idempotent (safe to run repeatedly # — see its own header comment); this unit just gives it more chances to # run. Deliberately separate from pia-gateway-recover.timer and NOT # gated by pia_auto_recovery_enabled: this is the kill switch continuing # to assert its own already-established, narrowly-scoped state — the # same kind of thing it already does unconditionally at boot and after a # UFW reload, just on a schedule too — not the higher-level automatic # recovery/registration logic the plan was deliberately cautious about # running unattended. [Unit] Description=Periodically re-assert the PIA gateway kill switch's FORWARD jump position [Service] Type=oneshot ExecStart=/usr/local/sbin/pia-killswitch.sh LimitCORE=0