-
Notifications
You must be signed in to change notification settings - Fork 67
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
Resolve of DNS is not working correctly on contiki. #296
Comments
Just to add up, the steps Awa & Contiki take for this issue to pop up are as follows:
|
It seems that the asynchronous DNS resolution request never updates the security object, which is initially memset to 0. This happens regardless whether encryption is enabled on the device server. [INFO] [lwm2m_bootstrap.c:72] Bootstrap with coap://ds-coap.flowcloud.systems:15683/bs?ep=Carpark1 |
Should be fixed as of this pull request #300 |
It looks like code inside lwm2m_security_object.c is expecting that DNS will be resolved in calls while performing boostratp. However tests shows that bootstraping process might happen before DNS will be resolved. There is no next call to obtain resolved address for network layer. Probably some pulling mechanism is required to update proper structures. We found temporary workaround by adding following lines into mentioned file:
Note: We spotted problem in contiki network layer (async handling of DNS requests) however given workaround is placed in security layer, which might be misleading.
The text was updated successfully, but these errors were encountered: