| commit | fa79f38c02787ae0887ba53433bae15c6fb67e4d | [log] [tgz] |
|---|---|---|
| author | Simon Lin <simonlin@google.com> | Tue Mar 01 07:55:35 2022 +0800 |
| committer | GitHub <noreply@github.com> | Mon Feb 28 15:55:35 2022 -0800 |
| tree | 1e901ffb8111ed14a20f68e15084eddc2df9e59a | |
| parent | 56873fe4922870dee9f19b9a4f1e4a7e01cb82ac [diff] |
[routing-manager] fix small OMR prefix election issue (#7405)
This commit fixes two small issues regarding OMR prefix election:
- This commit handles the case where `mLocalOmrPrefix` is already in
Leader's Network Data, but not locally added. It is possible when
the BR restores the Network Data from Leader. In such case the BR
should re-add `mLocalOmrPrefix` to local Network Data so that it
keeps advertising OMR Prefix. Otherwise, the OMR Prefix will be
removed from Leader's Network Data because of Network Data
inconsistentency, and then all BRs start to re-elect OMR Prefix. So,
the change will make the OMR Prefix more stable in some corner
cases.
- The change here checks if `mLocalOmrPrefix` was added to the Local
Network Data, instead of checking if `mLocalOmrPrefix` is added to
the Leader's Network Data. Here the BR has already decided that it
should not be advertising `mLocalOmrPrefix`. Whether or not
`mLocalOmrPrefix` is in Leader's Network Data is relevant. The BR
only needs to remove `mLocalOmrPrefix` from Local Network Data and
eventually Local Network Data will synchronize with Leader's Network
Data. The original code also has a potential issue that the BR may
send `NET_DATA.ntf` to Leader indefinitely when these conditions are
met:
- `mLocalOmrPrefix` was added to Local Network Data
- `mLocalOmrPrefix` is not added to Leader' Network Data because
there is no more space in Leader's Network Data
OpenThread released by Google is...
...an open-source implementation of the Thread networking protocol. Google Nest has released OpenThread to make the technology used in Nest products more broadly available to developers to accelerate the development of products for the connected home.
...OS and platform agnostic, with a narrow platform abstraction layer and a small memory footprint, making it highly portable. It supports both system-on-chip (SoC) and network co-processor (NCP) designs.
...a Thread Certified Component, implementing all features defined in the Thread 1.2 specification, including all Thread networking layers (IPv6, 6LoWPAN, IEEE 802.15.4 with MAC security, Mesh Link Establishment, Mesh Routing) and device roles, as well as Border Router support.
More information about Thread can be found at threadgroup.org. Thread is a registered trademark of the Thread Group, Inc.
All end-user documentation and guides are located at openthread.io. If you're looking to do things like...
...then openthread.io is the place for you.
Note: For users in China, end-user documentation is available at openthread.google.cn.
If you're interested in contributing to OpenThread, read on.
We would love for you to contribute to OpenThread and help make it even better than it is today! See our Contributing Guidelines for more information.
Contributors are required to abide by our Code of Conduct and Coding Conventions and Style Guide.
OpenThread follows the Semantic Versioning guidelines for release cycle transparency and to maintain backwards compatibility. OpenThread's versioning is independent of the Thread protocol specification version but will clearly indicate which version of the specification it currently supports.
OpenThread is released under the BSD 3-Clause license. See the LICENSE file for more information.
Please only use the OpenThread name and marks when accurately referencing this software distribution. Do not use the marks in a way that suggests you are endorsed by or otherwise affiliated with Nest, Google, or The Thread Group.
There are numerous avenues for OpenThread support:
openthread tagThe openthread-users Google Group is the recommended place for users to discuss OpenThread and interact directly with the OpenThread team.