Set HEALTH_ICMP_TARGET_IPS to WireGuard gateway for periodic health check

ProtonVPN does not NAT ICMP to external IPs (1.1.1.1, 8.8.8.8), causing
the periodic small health check to always fail and restart the VPN loop.
10.2.0.1 (WireGuard gateway) responds to ICMP at ~28ms and remains
reachable as long as the WireGuard tunnel itself is up.
This commit is contained in:
Will Anderson
2026-04-14 22:08:40 -05:00
parent 214afed0a2
commit ef8dc293e5
2 changed files with 6 additions and 0 deletions
@@ -87,6 +87,8 @@ spec:
value: "10.43.0.10:53"
- name: HEALTH_TARGET_ADDRESS
value: "api.protonvpn.ch:443,account.proton.me:443"
- name: HEALTH_ICMP_TARGET_IPS
value: "10.2.0.1"
- name: FIREWALL_OUTBOUND_SUBNETS
value: 10.42.0.0/16,10.43.0.0/16
ports:
@@ -116,6 +116,8 @@ spec:
value: "10.43.0.10:53"
- name: HEALTH_TARGET_ADDRESS
value: "api.protonvpn.ch:443,account.proton.me:443"
- name: HEALTH_ICMP_TARGET_IPS
value: "10.2.0.1"
- name: FIREWALL_OUTBOUND_SUBNETS
value: "10.42.0.0/16,10.43.0.0/16"
volumeMounts:
@@ -334,6 +336,8 @@ spec:
value: "10.43.0.10:53"
- name: HEALTH_TARGET_ADDRESS
value: "api.protonvpn.ch:443,account.proton.me:443"
- name: HEALTH_ICMP_TARGET_IPS
value: "10.2.0.1"
- name: FIREWALL_OUTBOUND_SUBNETS
value: "10.42.0.0/16,10.43.0.0/16"
volumeMounts: