Found live, 2026-09-22: after fixing pia-killswitch.sh's FORWARD-jump repositioning and getting one pia-gateway register attempt past the safety check, the very next attempt - roughly an hour later, no reboot, no UFW reload, no script content change in between - hit the identical "FORWARD jump to kill-switch chain is not first" failure again. This disproves the earlier assumption that kube-router/dockerd reassert their own position-1 jumps only at boot/restart scale: kube-router resyncs on ordinary Kubernetes API events, and this cluster's CronJobs (ca-sync, porkbun-ddns, gitea-backup) each create/delete a Pod every few minutes - plausible triggers for kube-router's own reconciliation loop, and therefore plausible triggers for this drift, recurring on a timescale of minutes. The reposition logic itself (previous commit) is correct - it just only ran on the existing triggers (boot, UFW reload, an Ansible-detected script content change), none of which fired between the two attempts. Adds pia-killswitch-reassert.timer/.service: re-runs the already fully idempotent pia-killswitch.sh every pia_healthcheck_interval_sec (same cadence as the health check), giving it regular chances to run instead of only sporadic ones. 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 (source rule, table default, FORWARD jump position), 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. Unblocked live in the meantime with a manual `sudo systemctl restart pia-killswitch.service`. Offline checks: yamllint, ansible-playbook --syntax-check, rendered templates (Jinja2 + bash -n on the updated script), ansible-lint (diffed against main - no new finding categories), full pia_gateway.py test suite (94/94, unaffected by this change) all pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
75 lines
2.3 KiB
YAML
75 lines
2.3 KiB
YAML
---
|
|
# Part of role: pia-gateway
|
|
# Included by: tasks/main.yaml
|
|
# Description: Registers the dedicated PIA policy-routing table and
|
|
# installs+enables the boot-time kill-switch service that seeds it
|
|
# (rule, terminal unreachable route, static drop rule) before
|
|
# wg-quick@{{ pia_wg_interface }} is allowed to start. See
|
|
# templates/pia-killswitch.sh.j2 for what the seeded state actually is.
|
|
|
|
- name: Register the PIA routing table name
|
|
ansible.builtin.lineinfile:
|
|
path: /etc/iproute2/rt_tables
|
|
line: "{{ pia_route_table_id }}\t{{ pia_route_table_name }}"
|
|
regexp: "^[0-9]+\\s+{{ pia_route_table_name }}$"
|
|
create: true
|
|
mode: "0644"
|
|
|
|
- name: Deploy the kill-switch seed script
|
|
ansible.builtin.template:
|
|
src: pia-killswitch.sh.j2
|
|
dest: /usr/local/sbin/pia-killswitch.sh
|
|
mode: "0700"
|
|
owner: root
|
|
group: root
|
|
notify: Restart pia-killswitch
|
|
|
|
- name: Deploy the pia-killswitch systemd unit
|
|
ansible.builtin.template:
|
|
src: pia-killswitch.service.j2
|
|
dest: /etc/systemd/system/pia-killswitch.service
|
|
mode: "0644"
|
|
owner: root
|
|
group: root
|
|
notify:
|
|
- Reload systemd daemon
|
|
- Restart pia-killswitch
|
|
|
|
- name: Enable and start the kill-switch service now
|
|
ansible.builtin.systemd:
|
|
name: pia-killswitch.service
|
|
enabled: true
|
|
state: started
|
|
|
|
- name: Deploy the kill-switch periodic reassertion systemd service
|
|
ansible.builtin.template:
|
|
src: pia-killswitch-reassert.service.j2
|
|
dest: /etc/systemd/system/pia-killswitch-reassert.service
|
|
mode: "0644"
|
|
owner: root
|
|
group: root
|
|
notify:
|
|
- Reload systemd daemon
|
|
- Restart pia-killswitch reassertion timer
|
|
|
|
- name: Deploy the kill-switch periodic reassertion systemd timer
|
|
ansible.builtin.template:
|
|
src: pia-killswitch-reassert.timer.j2
|
|
dest: /etc/systemd/system/pia-killswitch-reassert.timer
|
|
mode: "0644"
|
|
owner: root
|
|
group: root
|
|
notify:
|
|
- Reload systemd daemon
|
|
- Restart pia-killswitch reassertion timer
|
|
|
|
- name: Enable and start the kill-switch reassertion timer
|
|
ansible.builtin.systemd:
|
|
name: pia-killswitch-reassert.timer
|
|
enabled: true
|
|
state: started
|
|
daemon_reload: true
|
|
# Unconditional — not gated by pia_auto_recovery_enabled. See the
|
|
# service unit's own header for why this is scoped differently from
|
|
# the automatic recovery/registration timers.
|