android: Use 0.0.0.0/0 as local traffic selector

This is helpful if the responder also wants to tunnel e.g. multicast
packages.

diff --git a/src/frontends/android/jni/libandroidbridge/backend/android_service.c b/src/frontends/android/jni/libandroidbridge/backend/android_service.c
index 1e9d246ce4febf2888ef285d9fbd6dbc70b54390..fbf5d981a43d4cb8a89e53fb54a615ad88f3ba73 100644 (file)
--- a/src/frontends/android/jni/libandroidbridge/backend/android_service.c
+++ b/src/frontends/android/jni/libandroidbridge/backend/android_service.c
@@ -539,7 +539,8 @@ static job_requeue_t initiate(private_android_service_t *this)
         * libipsec, no PFS for now */
        child_cfg->add_proposal(child_cfg, proposal_create_from_string(PROTO_ESP,
                                                        "aes128-aes192-aes256-sha1-sha256-sha384-sha512"));
-       ts = traffic_selector_create_dynamic(0, 0, 65535);
+       ts = traffic_selector_create_from_string(0, TS_IPV4_ADDR_RANGE, "0.0.0.0",
+                                                                                        0, "255.255.255.255", 65535);
        child_cfg->add_traffic_selector(child_cfg, TRUE, ts);
        ts = traffic_selector_create_from_string(0, TS_IPV4_ADDR_RANGE, "0.0.0.0",
                                                                                         0, "255.255.255.255", 65535);