This change helps make Automotive presubmit builds faster. There are no side effects of this change elsewhere, it requires builds to configure said target to take effect and if configured this change only make the test show up in the automotive zip file
BUG: 382649664
Flag: TEST_ONLY
Change-Id: Ibe0cb51911449eb0ae5160c1170c2a28add3be98
Filip Zakrzewskicommited 2025-01-15 16:52:21 -08:00
IWLAN on U 24Q2 release may cause this test to fail, but this was
supposed to be addresed by CarrierConfigSetupTest already.
Add diagnostics on failure to figure out if the IWLAN config is as
expected.
Test: atest
Bug: 253698734
Change-Id: Iddc8975bb473979f9c2769cd178ef75644b82aa7
Instead of only waiting for an IPv6 address, wait for global IPv6
addresses to be routable.
This mirrors the check used for AI_ADDRCONFIG in DnsResolver. Without
this, the later call to network.getAllByName may only return IPv4
addresses if IPv6 global addresses are not reachable.
Test: atest
Change-Id: I2cedd58431eb8abeb5ffd9fb8daedb061586373b
As part of the major tethering refactor to associate every IpServer with
a TetheringRequest, tether()/untether() APIs should be completely
removed in B and all tethering should go through startTethering() (with
the exception of Wifi LOHS and Wifi P2P, which will move to
startTethering() in a future CL).
Bug: 216524590
Test: atest CtsTetheringTests TetheringTests
Change-Id: If7981f1ee7d80ff0a1cc0069ba7a4ebf79144160
Quang Anh Luongcommited 2025-01-15 08:59:42 +09:00
* changes:
Register reserved offer
Add L2capNetworkSpecifier to blanket offer
Add blanket offer to L2capNetworkProvider
Add empty L2capNetworkProvider
Implement matching semantics for L2capNetworkSpecifier
Do not allow L2CAP specifier with ROLE_SERVER and remote address set
Do not redact PSM from L2capNetworkSpecifier
Use IntRange for setPsm
Improve documentation of L2capNetworkSpecifier
Have setRemoteAddress accept a Nullable remoteAddress
Patrick Rohrauthored and Gerrit Code Reviewcommited 2025-01-13 20:26:09 -08:00
V requires 4.19+ and 25Q2+ requires 5.4+
(while 25Q4 will presumably further bump to 5.10+)
On aosp/main we currently have:
ro.build.version.sdk=35
- which is returned by android_get_device_api_level()
ro.build.version.codename=Baklava
- which is looked at by IsAtLeastPreReleaseCodename/GetCodename
This is because we're already past the aosp/main automerge into 25Q1 cutoff.
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I909d63406151fbafc15fa248133b9d1a5dc37bdb
Maciej Żenczykowskicommited 2025-01-13 14:37:56 -08:00
The reserved offer adapts the reservation requests capabilities, and
additionally populates its own capabilities (namely the PSM provided by
the BluetoothServerSocket).
Test: TH
Change-Id: Ida388b6f1e4552242726bd4d7eba6215bb0577a3
update failures to statsd
This will allow it easier to debug the logging logic, without needing to
hit the default threshold of 10.
Flag: com.android.net.ct.flags.certificate_transparency_service
Bug: 378626065
Test: atest NetworkSecurityUnitTests && tested flag behavior manually
Change-Id: I10c652615e78a700bb84aabaa37ddc850e031e56
Change debug counter from DROPPED_IPV6_MULTICAST_PING to DROPPED_IPV6_NS_REPLIED_NON_DAD.
The DROPPED_IPV6_MULTICAST_PING counter is no longer used and scheduled for removal.
Test: atest CtsNetTestCases:android.net.cts.ApfIntegrationTest
Change-Id: I00eac8522b4e18b9bae8bfeab9d451314f88b5f9
Makes saner error if device does not even support APF at all.
Test: TreeHugger
Bug: 385979701
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ided37893d7e0d6b03436064f44d1fa9061f0951d
Maciej Żenczykowskicommited 2025-01-10 18:08:19 -08:00
The blanket offer is used to respond to reservation requests and only
serves ROLE_SERVER networks, as ROLE_CLIENT networks are not reserved.
Test: TH
Change-Id: I9ed00a76fa0d61caf27e321ea17260fb12b69600
Registers a blanket reservation offer which will receive reservation
requests filed using ConnectivityManager#reserveNetwork.
Test: TH
Change-Id: I2d37fe564a6c40f2c6dee1f6f7aa655c47628b85
The network provider is registered when BLE is supported.
Bug: 372936361
Test: L2capNetworkProviderTest
Change-Id: I8163339015f4a3bb0ff8911f6f52a38ec1730f39
A server network is created by using ConnectivityManger#reserveNetwork,
in which the app passes a specifier that sets:
reservationRequest = {
role = server
headerCompression = 6lowpan
remoteAddr = any (null)
psm = any
}
This specifier must subsequently match the blanket reservation offer,
and the reserved offer that is generated as a response:
blanketOffer = {
role = server
headerCompression = any
remoteAddr = any (null)
psm = any
}
reservedOffer = {
role = server
headerCompression = 6lowpan
remoteAddr = any (null)
psm = 0x81
}
And not the client network offer or a client network:
clientOffer = {
role = client
headerCompression = any
remoteAddr = any (null)
psm = any
}
clientNetwork = {
role = client
headerCompression = 6lowpan
remoteAddr = 01:02:03:04:05:06
psm = 0x81
}
Similarly the client request must match both the clientOffer and
clientNetweork, but not the reservedOffer (and technically
blanketOffer):
clientRequest = {
role = client
headerCompression = 6lowpan
remoteAddr = 01:02:03:04:05:06
psm = 0x81
}
Note, a request for TRANSPORT_BLUETOOTH with no specifier matches *any*
specifier per specifier matching semantics in NetworkCapabilities.
Test: L2capNetworkSpecifierTest
Change-Id: Ia16926b463a54530ae6e88278466e92ed82bf852
Updated ApfIntegrationTest to validate APFv6 support and minimum APF RAM
size (4000 bytes) for device with VSR API level 202504, as mandated by
the VSR-16 specification.
Bug: 383959066
Test: TH
Change-Id: I8a54ab696d9633534586e0a2ee9902f3759ca420
Yuyang Huangauthored and Maciej Żenczykowskicommited 2025-01-10 13:44:11 -08:00
This is an invalid combination that never seems useful. Note that this
still allows ROLE_ANY in combination with a remote address. This still
doesn't seem particularly useful, but there is no good reason to
disallow it.
Test: TH
Change-Id: Ib0b7284cb99ee92f14113f8184af978eeb2318e7
Instead of the boolean flag tracking that we are logging only once, use
an int to store the failureReason instead.
Flag: com.android.net.ct.flags.certificate_transparency_service
Bug: 378626065
Test: atest NetworkSecurityUnitTests
Change-Id: Ifcdb599f39bb8e1ce9c8b4a8d27fb4500df23256
Test: verified that when the config is set to `false`, thread won't start up after reboots:
```
➜ main-aosp-2 adb shell ot-ctl state
leader
Done
➜ main-aosp-2 adb reboot
➜ main-aosp-2 adb shell ot-ctl state
/system/bin/sh: ot-ctl: inaccessible or not found
➜ main-aosp-2 adb root
➜ main-aosp-2 adb shell ot-ctl state
disabled
Done
```
Bug: 378587036
Change-Id: I4d1c90ab3121f39219cbaf795879a7ba91db02a3
This reverts commit c3eccf9ef4.
Reason for revert: As we discussed, it might be valid for the chipset to drop BC (non-ARP, non-IPv4) packets in the hardware instead of the firmware. To ensure this test doesn't fail on those chipsets, using unicast packets for testing seems more suitable.
Change-Id: I89debf79965cf3ea62484c443e952bd137818efc
Yuyang Huangauthored and Jimi Chencommited 2025-01-10 07:12:27 +00:00
Bluetooth apex name has changed from com.android.btservices to
com.android.bt. We now need to update the reference in the code.
Bug: 383863941
Flag: Exempt build infra
Test: m .
Change-Id: I92167eb785858565d28b1e72b3b98150378975a6
William Escandecommited 2025-01-09 12:25:16 -08:00
CTLogger
This CL adds a new API that will convert the
DownloadManager.COLUMN_REASON into the relevant proto failure reason
enum value. The reason why it is a new API rather than reusing an
existing one is because the parameter type is the same (int), so a
separate API will keep it clearer when the DownloadManager value vs. proto enum value is directly used.
Flag: com.android.net.ct.flags.certificate_transparency_service
Bug: 378626065
Test: atest NetworkSecurityUnitTests
Change-Id: I9028ba8f2cb95ccc6d21b19c58e0d15a9405c3f7
It's default enabled that it waits for border routing establishment
before starting the SRP server. But there are also use cases where
the user may want to know what are the devices in the Thread network
before actually reach to the devices, or it doesn't depend on border
routing to reach to a Thread device.
Given that, this commit adds the support of starting SRP server
without waiting for border routing by adding a new
Runtime Resource Overlay configuration parameter:
config_thread_srp_server_wait_for_border_routing_enabled
Test: it's difficult to assert on the SRP server starts up timing. But manually verified that the SRP server starts without waiting for the routing manager when the RRO config is flipped:
```
01-09 20:18:35.835 7555 7555 I ot-daemon: [I] RoutingManager: RsSender: Sent RS 1/3
01-09 20:18:35.835 7555 7555 I ot-daemon: [I] RoutingManager: Received RS from fe80:0:0:0:98af:44ff:fe2e:fa80 on infra netif 17
01-09 20:18:35.835 7555 7555 I ot-daemon: [I] RoutingManager: Will evaluate routing policy in 00:00.150 (150 msec)
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] NetDataPublshr: DNS/SRP service - State: Adding -> Added
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] SrpServer-----: Start listening on port 53536
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] NetworkData---: Sent ServerData
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] NetworkData---: Received ServerData
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] NetworkData---: Allocated Service ID = 1
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] NetworkData---: Sent ServerData ack
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] Notifier------: StateChanged (0x00000200) [NetData]
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] Mle-----------: Send Data Response (ff02:0:0:0:0:0:0:1)
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] BbrLeader-----: PBBR state: Unchanged
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] BbrLeader-----: Rloc16:0x8800, seqno:69, delay:5, timeout:3600
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] RoutingManager: Will evaluate routing policy in 00:03.558 (3558 msec)
01-09 20:18:35.926 7555 7555 I ot-daemon: [I] NetDataPublshr: DNS/SRP service (state:Added) in netdata - total:1, preferred:0, desired:2
```
Bug: 378587036
Change-Id: Ib768014f3c44dca89390cec823a1c2acac38ab0d
The task of installing a new log list is now performed by the
CompatibilityVersion class.
Also, each CompatibilityVersion provides the URLs hosting the signature
and log list files. We do not store that information in the DataStore.
Change-Id: I36b585dc6984278de1ab3e6f3dc872e22f06ebea
Flag: com.android.net.ct.flags.certificate_transparency_service
Bug: 377276991
Test: atest NetworkSecurityUnitTests
Filip Zakrzewski
authored and
Gerrit Code Review
commited 
Treehugger Robot
authored and
Remi NGUYEN VAN
commited 
Quang Luong
authored and
Maciej Żenczykowski
commited 
Paul Hu
commited 
Jimi Chen
authored and
Yuyang Huang
commited 
Patrick Rohr
authored and
Bessie Jiang
commited 
Kangping Dong
authored and
Automerger Merge Worker
commited 
William Escande
commited 
Sandro Montanari
authored and