Use ProtonVPN internal DNS and direct IP healthcheck to diagnose VPN
This commit is contained in:
@@ -112,6 +112,12 @@ spec:
|
||||
value: "25s"
|
||||
- name: FIREWALL_OUTBOUND_SUBNETS
|
||||
value: "10.42.0.0/16,10.43.0.0/16"
|
||||
- name: HEALTH_TARGET_ADDRESS
|
||||
value: "1.1.1.1:443"
|
||||
- name: DOT
|
||||
value: "off"
|
||||
- name: DNS_ADDRESS
|
||||
value: "10.2.0.1"
|
||||
volumeMounts:
|
||||
- name: gluetun-data
|
||||
mountPath: /tmp/gluetun
|
||||
@@ -324,6 +330,12 @@ spec:
|
||||
value: "25s"
|
||||
- name: FIREWALL_OUTBOUND_SUBNETS
|
||||
value: "10.42.0.0/16,10.43.0.0/16"
|
||||
- name: HEALTH_TARGET_ADDRESS
|
||||
value: "1.1.1.1:443"
|
||||
- name: DOT
|
||||
value: "off"
|
||||
- name: DNS_ADDRESS
|
||||
value: "10.2.0.1"
|
||||
volumeMounts:
|
||||
- name: gluetun-data
|
||||
mountPath: /tmp/gluetun
|
||||
|
||||
Reference in New Issue
Block a user