From 0dd6a96ce1bf2cef9140d01a5c49eb92e2f8ec6f Mon Sep 17 00:00:00 2001 From: Guilhem Moulin Date: Mon, 4 Nov 2013 07:27:10 +0100 Subject: Be more specific regarding the protocol in use for IPSec policies. We use ESP only, so other protocols shouldn't be ACCEPTed. --- roles/common/files/etc/network/if-up.d/ipsec | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'roles/common/files/etc/network') diff --git a/roles/common/files/etc/network/if-up.d/ipsec b/roles/common/files/etc/network/if-up.d/ipsec index 98bf42c..a43af6c 100755 --- a/roles/common/files/etc/network/if-up.d/ipsec +++ b/roles/common/files/etc/network/if-up.d/ipsec @@ -40,7 +40,10 @@ case "$MODE" in # If a packet retained its mark that far, it means it has # been SNAT'ed from $ipsec, and didn't have a xfrm - # association. Hence we nullroute it to avoid leaking data. + # association. Hence we nullroute it to avoid to leak data + # intented to be tunneled through IPSec. /!\ The priority + # must be >220 (strongSwan IPSec's policy) since xfrm lookup + # must take precedence. /bin/ip rule add fwmark "$secmark" table 666 priority 666 || true /bin/ip route add prohibit default table 666 || true ;; -- cgit v1.2.3