From 070cd12dfb074ca31cf6508986b3f0a6f479aa7d Mon Sep 17 00:00:00 2001 From: Tobias Brunner Date: Thu, 19 Mar 2020 16:08:07 +0100 Subject: [PATCH] android: Check the current path using DPD after a roaming event A new NAT mapping might be created even if the IP stays the same. Due to the DPD fallback with NAT keep-alives this might only be necessary in corner cases, if at all. --- .../android/app/src/main/jni/libandroidbridge/charonservice.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/frontends/android/app/src/main/jni/libandroidbridge/charonservice.c b/src/frontends/android/app/src/main/jni/libandroidbridge/charonservice.c index e766b34ea9..5a3435a11c 100644 --- a/src/frontends/android/app/src/main/jni/libandroidbridge/charonservice.c +++ b/src/frontends/android/app/src/main/jni/libandroidbridge/charonservice.c @@ -504,6 +504,8 @@ static void set_options(char *logfile) "charon.initiator_only", TRUE); lib->settings->set_bool(lib->settings, "charon.close_ike_on_child_failure", TRUE); + lib->settings->set_bool(lib->settings, + "charon.check_current_path", TRUE); /* setting the source address breaks the VpnService.protect() function which * uses SO_BINDTODEVICE internally. the addresses provided to the kernel as * auxiliary data have precedence over this option causing a routing loop if -- 2.47.2