- Nov 21, 2023
-
-
Mark authored
Instead of passing state machine to UpstreamNetworkMonitor, wrapped it by an interface would have two benefits: 1. Easier for testing. 2. Isolate state machine operation in callback. Test: atest TetheringTests Change-Id: I2a97fd5cbc8c49df8c3c98428c6570916ab31ea5
-
- Nov 20, 2023
-
-
Chalard Jean authored
Bug: 308519360 Test: CarrierPrivilegeAuthenticatorTest Change-Id: I59164be00a9e1fcced8538537c1dcabd214f2170
-
Jean Chalard authored
-
Ken Chen authored
-
Chalard Jean authored
This tests that the network providers are subject to appropriate limitations as to what they can set as allowedUids – both in the positive (can do) case, and the negative (can't do) case. Test: this Change-Id: I115e2a4bc02ddcd03ecf2f35130fcb0378da22bd
-
Lorenzo Colitti authored
-
- Nov 19, 2023
-
-
Treehugger Robot authored
-
- Nov 17, 2023
-
-
Michał Brzeziński authored
-
Michał Brzeziński authored
This reverts commit 30fb9b1c. Reason for revert: Potential culprit for CtsLibcoreTestCases test failures b/311612650 Change-Id: Ie7de97159f92a174476a8fa8ea83e3e01914aea1
-
Handa Wang authored
-
Chiachang Wang authored
-
Junyu Lai authored
-
Junyu Lai authored
This change only outputs thread count differences instead of listing all threads. Additionally, it ignores threads with 1 count, which effectively filter out threads created by the test runner or other system components, such as hwuiTask*, queued-work-looper, SurfaceSyncGroupTimer, RenderThread, and Time-limited test. Sample Output: [1122/3060] android.net.connectivity.com.android.server.CSLocalAgentCreationTests#ThreadLeakMonitor: FAILED (1ms) STACKTRACE: java.lang.IllegalStateException: Unexpected thread changes: removed=[] added=[] updated=[TestAlarmManager=25,CSTestHandler=25] Test: atest ConnectivityCoverageTests (with shouldThreadLeakFailTest set to true) Bug: 310581973 Bug: 307693729 Change-Id: I085799ebbd69c29f833335684de208105302e012
-
Handa Wang authored
This CL lets ThreadNetworkControllerService calls the LocalNetworkConfig API to set up border routing between Thread and infrastructure network. Bug: 299552948 Bug: 305861411 Test: Verified on Cuttlefish that forwarding is set up. Change-Id: I8b2f015d9d6248bfb1cd9ac806dc8664970a26d2
-
Jean Chalard authored
-
Yang Sun authored
-
Remi NGUYEN VAN authored
The previous message is not clear about the fact that there is a SIM card inserted. Clarify it. Change-Id: I2391d9fa7762b6225438049199f9f178a8b24d41
-
Motomu Utsumi authored
-
Chiachang Wang authored
Bug: 161776767 Test: atest FrameworksNetTests Change-Id: Id2cef626c5893a4ff29161c801e497b7de551136
-
Maciej Żenczykowski authored
-
- Nov 16, 2023
-
-
Yan Yan authored
Add xfrm_address_t and xfrm_usersa_id structs Bug: 308011229 Test: atest NetworkStaticLibTests:com.android.net.moduletests.util.netlink (new tests added) Change-Id: I552983d7e768e7fb8ba307ffc55060c8b35e7436
-
Ivo Kay authored
Test: atest FrameworksNetTests CtsNetTestCases Bug: 307217169 Change-Id: I006e3191a8c6100af3d2906d5d37f4e38a3db519
-
Maciej Żenczykowski authored
-
Maciej Żenczykowski authored
-
Hansen Kurli authored
-
Chalard Jean authored
As a specialized network, a network with PRIORITIZE_* is not generally a good default network, and might cause unexpected charges if allowed to become one. Test: CSDefaultNetworkTests Change-Id: I8f7184f80bb987da720bd067862bd7a546a38e26
-
Jean Chalard authored
-
Kangping Dong authored
-
Chalard Jean authored
Ideally the rules should be set up before onAvailable is sent, but onLocalNetworkChanged should be sent after. The previous code had CSLocalAgentTests#testForwardingRules flaky because it was waiting for onAvailable and immediately checking that the routing rules have been set up. There are other ways to fix this flake (e.g. wait for onLocalNetworkChange in the test or add a timeout on the verify(netd) call) but this patch probably implements the best production code behavior. Bug: 309688089 Test: CSLocalAgentTests#testForwardingRules 1'000 times Before this patch : flakes after 50~200 iterations After this patch : no flake in 1'000 iterations Change-Id: I4dcccaa3607c1e28aa89f268f0c721d87b1e9466
-
Chiachang Wang authored
-
Jean Chalard authored
-
Hansen Kurli authored
The profile is modified within startLegacyVpnPrivileged(), e.g. ipsecCaCert, ipsecUserCert. This causes subsequent calls from callers such as LockdownVpnTracker to fail. Add a new test to ensure the VpnProfile is not modified in startLegacyVpn. Add testClone in VpnProfileTest. Bug: 190572822 Bug: 309591931 Test: atest FrameworksNetTests, test before and after fix. Test: Manual test Change-Id: Id090e0dd3b9e74a7461ae90e68c41e802b458744
-
lucaslin authored
This commit verifies that - If VPN network preference is set when - Ikev2VpnRunner is created - Retrying VPN - Updating exclusion list - If VPN network preference is cleared when - Exiting VPN runner - NOT_RECOVERABLE happens Bug: 231749077 Test: atest FrameworksNetTests:VpnTest Change-Id: I71f48f18fd4556e04c131d5939afaa1ef5a0f814
-
Junyu Lai authored
-
Maciej Żenczykowski authored
Networking bpf (including cgroup related portions) was mainlined in Android T. Test: TreeHugger Signed-off-by:
Maciej Żenczykowski <maze@google.com> Change-Id: I779584828f03caa2d61d5081cb3d39566db9b9de
-
Maciej Żenczykowski authored
Since the first mainline eBPF code (for Tethering offload) landed in Android S. Test: TreeHugger Signed-off-by:
Maciej Żenczykowski <maze@google.com> Change-Id: Ifb44a43a98e7f0ff4cd59017b47f64eff30ee715
-
Chiachang Wang authored
-
- Nov 15, 2023
-
-
Ken Chen authored
-
Motomu Utsumi authored
-
Motomu Utsumi authored
* changes: Make ConnectivityService update BatteryStats radio power state Track multiple network activities on V+ Use netId as idleTimer label on V+
-