[pull] main from openthread:main #183
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
This commit updates DNS client to add `otDnsServiceMode` to the `otDnsQueryConfig`. This new config property determines which records to query and allow the API user to control the behavior during service resolution: We can query for SRV record only or TXT record only, or query for both SRV and TXT records in the same message, or in parallel in different messages, or an "optimized" mode where client will first try to query for both records together in the same message but if server responds with an error, it then retries using two parallel separate queries. This gives flexibility and control to the API user. It also helps address situations where the server (DNS resolver) may not accept queries with more than one questions. To support this new feature, this commit updates and enhances the internal design of the `Dns::Client`. A new mechanism is added to allow multiple `Query` instances to be associated with each other under a main `Query` and responses for the related queries are saved until all are received and validated before finalizing the main `Query` and invoking the callback and allowing caller to retrieve the info. This commit also adds a detailed unit test `test_dns_client` which covers DNS client browse and service resolution validating behavior under all service modes. In order to test `Client` functionality, this commit also adds a `TestMode` in `Dns::ServiceDiscovery::Server` allowing us to change server behavior, e.g., reject messages with more than one question in query.
This commit adds the openthread config header file to the spinel config file to allow developers to configure the spinel configurations in the openthread config file.
This commit adds a helper function `UriToString<Uri>()` to convert a given `Uri` enumeration value to a human-readable string. This is used for logging.
When compiling the otbr-agent in Android, Android will link the function debuggerd_init() and call it before calling the function main(). The function debuggerd_init() sets signal handlers to catch signals. This commit resets the signal actions to default and re-raises the original signal to let the pre-configured functions to catch signals.
This commit adds two small changes to address new warnings when building with clang-14. It also updates `mbedtls` CMakeLists to set `MBEDTLS_FATAL_WARNINGS` option as `OFF` (so that compiler warnings are not treated as errors). This avoid issues with new warning for `unused-but-set-variable` emitted by clang-14.
This commit adds overloads of commonly used methods in `Coap` and `MessagePool` replacing default parameter values. This helps reduce code size.
) This commit adds new IPv6 header DSCP values which indicate a TMF message priority. This allows intermediate routers forwarding TMF message to be able to determine and use the TMF message priority that originator of the message selects (e.g., address query/notification use net-level priority whereas network diagnostics message use normal priority). This replaces the previous behavior where on intermediate routers all TMF messages were treated as net-level priority. The new DSCP values are allocated from local codepoint range `0bxxxx11` (per RFC 2474 - section 6). If the sender does not use TMF-specific DSCP values, we use `kPriorityNet` as default on intermediate router. This ensures that senders that are using older code (do not use the new) experience the same behavior as before.
This commit introduces `Server` and `Client` classes breaking the `NetworkDiagnostic` module into two components. The `Server` responds to queries and requests (handling Net Diag TMF commands), while `Client` issues queries/requests and processes responses. The `Server` is available under both FTD and MTD (which follows the requirement of Thread spec). The client is enabled using newly added `OPENTHREAD_CONFIG_TMF_NETDIAG_CLIENT_ENABLE` config option which is also available as `OT_NETDIAG_CLIENT` CMake option or the autoconf build switch `NETDIAG_CLIENT`. The client functionality is by default enabled on Border Routers (tied to `CONFIG_BORDER_ROUTING_ENABLE` config). The previous `TMF_NETWORK_DIAG_MTD_ENABLE` config is now removed along with its CMake `OT_MTD_NETDIAG` and autoconf switch. This commit adds checks to trigger build error if the previous config and/or its related CMake option are used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 馃挅 Please sponsor : )