-
Notifications
You must be signed in to change notification settings - Fork 66
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
Bootstrap server security flag changes between the initial client write and server response #299
Comments
I've added printfs to the NetworkSocket_Read and NetworkSocket_Send commands, you can find the log at the end of this message. From what I can see the moment a packet arrives the Secure flag switches for destAddress->Secure and (*sourceAddress)->Secure from 1 to 0. The workaround above [DEBUG] [coap_abstraction_erbium.c:249] Coap PUT for /0 |
See #296 |
This might be caused by the workaround described in #296, however I cannot say that with full certainty.
I managed to get the bootstrap going with the workaround at mtusnio/AwaLWM2M@17d8926. After the initial client write is done, the security flag changes from 1 to 0, and the subsequent read of the bootstrap server response is treated like a plaintext read instead of an encrypted message, which obviously derails the process. Again, this might be due to the workaround causing the resolution to kick in every time the ServerIsBootstrap call is made. I quickly got this to work by doing the changes as found in mtusnio/AwaLWM2M@ca225d6, however this is just a quick workaround the issue as far as I can tell.
I'll put up some more logs on Monday with proper debug messages to show exactly where the issue pops up.
The text was updated successfully, but these errors were encountered: