Lwm2m: upstream updates #1489
Merged
Lwm2m: upstream updates #1489
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
|
Compliance check failing for changes that are already in Zephyr. |
SeppoTakalo
force-pushed
the
lwm2m_upstream_updates
branch
from
c0e1a52 to
4bd7eef
Compare
|
Dropped the commit that caused failure in compliance check. We can fix this in next upmerge. |
SeppoTakalo
force-pushed
the
lwm2m_upstream_updates
branch
from
4bd7eef to
79bd6f6
Compare
rlubos
approved these changes
Feb 12, 2024
SeppoTakalo
force-pushed
the
lwm2m_upstream_updates
branch
from
79bd6f6 to
f87b42f
Compare
jukkar
approved these changes
Feb 12, 2024
Add new kconfig CONFIG_LWM2M_QUEUE_MODE_NO_MSG_BUFFERING. When enabled and device is sleeping, Reqistration Update message is skipped and messages from send operation and notifications are sent right away. Reqistration update message is also skipped when lwm2m_engine resumes from pause state. Signed-off-by: Juha Ylinen <[email protected]> (cherry picked from commit 9eee8d2)
If bootstrap fails, RD client will call lwm2m_engine_stop() which will close the context. The socket loop, however still contains a call to hint_socket_state(context, NULL) which has a null pointer now. Fix the segfault by allowing nullpointer on hint_socket_state(). Signed-off-by: Seppo Takalo <[email protected]> (cherry picked from commit bf87287)
When ENABLED flag is used, we generate 32 byte DTLS Connection Identifier and include that in our DTLS Client HELO. This has no benefit as client only has one connection toward the server, it does not need any identification. When SUPPORTED flag is used, we just include zero length Connection Identifier in the handshake, which tell server that we support Connection Identifier and server can generate one for it. We then use the CID in the packets that we send towards server, but response packets don't contain any CID. This gives all the benefit of CID as server is able to identify us even when NAT mapping have changed. Signed-off-by: Seppo Takalo <[email protected]> (cherry picked from commit 9929363)
SeppoTakalo
force-pushed
the
lwm2m_upstream_updates
branch
from
f87b42f to
abfd948
Compare
|
BLE/Ant samples break on a new CONCAT() macro, so I'll drop the LWM2M_ON_INIT(). That is not mandatory for the release. |
Fix lwm2m_message initialization. Pending struct was NULL. Signed-off-by: Juha Ylinen <[email protected]> (cherry picked from commit c84dc7e)
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.
One critical fix (segfault) needed for the 2.6.0 release, so I'll pull in few other changes to keep in synch.
ZCBOR changes are in separate PR #1471 so I'll skip those.