Adds CTS to verify that the tunnel migration based on replacing
SAs can handle changes of encap type.
Verified on kernel 5.10.149 and 5.10.104
Bug: 266149275
Test: atest IpSecManagerTunnelTest(new tests added)
Change-Id: I33e945f8be2a472603c5f1b64697f62f2d69a186
This commit adds tests to verify that SAs with UDP encapsulation
can be updated from current IPv6 addresses to new IPv6 addresses.
This commit also improves CTS to verify that SA update can work
properly when the UDP encapsulation socket is rebinded to a
new network.
Verified on kernel 5.10.149 and 5.10.104
Bug: 266149275
Test: atest IpSecManagerTunnelTest(new tests added)
Change-Id: I9b5c961808c2f368911192003974a95643aa5181
Add CTS tests to verify migrating IPsec tunnels by
updating the existing IpSecTransforms
This commit also updates the input list of
the #getIpSecTunnelTestRunnable and #run method for
supporting the new tests.
Bug: 266149275
Test: atest IpSecManagerTunnelTest(new tests added)
Change-Id: If23c4268f56ab45a4443fa4435507b776bb5fbba
This commit is a preparation CL for testing the ability to update
IpSecTransform with new addresses. This commit adds three supports
in utility classes:
- Support verifying outbound v6 encap packets
- Allow awaitEspPacketNoPlaintext to wait for a packet with expected
length until timeout. Previously this method would fail
immediately when it received an ESP packet with incorrect length.
This old behavior would make the tests flaky since the test device
might send ESP containing RA message instead of the test data.
- Support checking the existence of XFRM_MIGRATE feature
Bug: 266149275
Test: atest CtsNetTestCases
Change-Id: Ia50aeda8d134c5edd2d1b86bf43a521084ce9866
Build from source and remove need for virtualenv to
make it self-contained.
Test: presubmit, forrest (https://android-build.googleplex.com/builds/abtd/run/L76600000954930260)
Bug: 234458076
Ignore-AOSP-First: nearby_not_in_aosp_yet
Change-Id: Ib0afb414fdeb510577345afd650fa6f0f5b3c721
(cherry picked from commit 7599806e06)
Merged-In: Ib0afb414fdeb510577345afd650fa6f0f5b3c721
Instead of NetworkStackApiStableShims, use NetworkStackApiCurrentShims
as this is a development branch.
Use java_defaults in the "merge conflicts expected" section, so that
module release branches can use the same defaults, but set it to
NetworkStackApiStableShims.
The shims are removed from FrameworksNetIntegrationTests, as they are
already available there through service-connectivity-pre-jarjar. Keeping
them as a dependency would make FrameworksNetIntegrationTests use both
Stable shims (directly) and Current shims
(through service-connectivity-pre-jarjar).
Bug: 266205506
Test: m
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:921290b49d109360aae5dc39effaa3b0e691f65a)
Merged-In: I88228152834a1c06830fb51e868fb8e3d8c47519
Change-Id: I88228152834a1c06830fb51e868fb8e3d8c47519
Keep using NetworkStackApiStableShims as this is a module release
branch.
Use java_defaults in the "merge conflicts expected" section, so that
module release branches can use the same defaults, but set it to
NetworkStackApiStableShims.
The shims are removed from FrameworksNetIntegrationTests, as they are
already available there through service-connectivity-pre-jarjar. Keeping
them as a dependency would make FrameworksNetIntegrationTests use both
Stable shims (directly) and Current shims
(through service-connectivity-pre-jarjar).
Ignore-AOSP-First: this needs to be submitted separately in each branch,
with downstream branches first as there are merge
conflicts in Tethering/apex/Android.bp that cannot be
automerged.
Bug: 266205506
Test: m
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:921290b49d109360aae5dc39effaa3b0e691f65a)
Merged-In: I88228152834a1c06830fb51e868fb8e3d8c47519
Change-Id: I88228152834a1c06830fb51e868fb8e3d8c47519
This file was added when there was only Cronet/tests/cts directory.
We now have move directories inside Cronet/tests hence the move
Test: m
Change-Id: Ib9b4af307f7085844060b4aed3b7c153a64ff962
The system polls TCP connections every 2 minutes for the auto
on/off keepalives. For some carriers, the NAT-T keepalive delay
is lower than this, which means it's possible a TCP connection
is opened seconds after the poll. This may cause connections
being disconnected because keepalive timed-out.
The minimal acceptable value should be the same as the keepalive
delay. But the system may take time to restart keepalive. Adjust
the delay of the polling alarm to be lower than the keepalive
delay to preserve some time for the system to restart the
keepalive.
Bug: 273411114
Test: atest FrameworksNetTests
Change-Id: I28f71ceb7b72d83e6e0f8f7d22d3d1e9dbdaa467
This option deletes gclient dependencies that were remove upstream, so
it makes sense to always set this flag for the import (since the import
directoy is reused to speed up the process).
This change also fixes setup_folder_origin to run in a subshell to
contain the directory change it performs.
Test: none
Change-Id: I87c60690be81843c3947acc0251967372ed4c34a
* I've investigated turning off `allocator_shims` globally for all of Cronet but
this didn't sound like a good option. allocator_shims are used for security measures,
where sometimes malloc caller forget to check for NULL which happens on oom. allocator_shims would
instantly kill the app instead of depending on the caller to do the validity check.
* The solution here was to manually remove the files and add them to `android` and `glibc` only so allocator_shims
is never compiled for musl.
* Chromium does not support musl so there's no flag for `musl` with allocator_shims.
Test: mma
Change-Id: I2a63b14482a526d06a089647e6f61eea9f1691dc
