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.

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 e766b34ea9c9f3153045c0a9ab282040423dfaa0..5a3435a11cb522aeeff17b67951382d5aa54de37 100644 (file)
--- 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