-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
download_client: Allow use of DTLS CID #11493
Conversation
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
4c20f0e
to
995e25e
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
Are there any updates required in the library documentation? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but please rebase
995e25e
to
3049b7a
Compare
3049b7a
to
b441cad
Compare
actually, you are right. Kconfig options are not mentioned in documentation, so I added a short note there as well. |
rebased. |
e48e265
to
bedf7db
Compare
When connecting to DTLS service, enable Connection-ID. Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
When transmission of a new block starts, clear timeouts. Otherwise previous CoAP transmission timeouts might be left. Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
Using POSIX API directly brings some portability issues with headers, so it is safer to use zsock API on libraries. Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
bedf7db
to
0bce520
Compare
Build failures on test application:
Not sure who is responsible of fixing test-ci-nrfconnect-boot-fw-update test job and its related test app. |
What is the use-case for DTLS CID in the download client which doesn't keep the connection? |
@@ -134,7 +128,7 @@ static int set_recv_socket_timeout(int fd, int timeout_ms) | |||
.tv_usec = (timeout_ms % 1000) * 1000, | |||
}; | |||
|
|||
err = setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, &timeo, sizeof(timeo)); | |||
err = zsock_setsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, &timeo, sizeof(timeo)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine in principle, but we should try to keep this aligned throughout the codebase, at least in sdk-nrf
. It would be a bit messy if some libraries used zsock_
and others the POSIX names; what guideline do we set for ourselves? Is it up to personal preference which one to use?
Few changes to the download client: