-
Notifications
You must be signed in to change notification settings - Fork 374
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
Infinite bootstrapping loop when the BS delete its own account. #96
Comments
ieei0214
added a commit
to ieei0214/wakaama
that referenced
this issue
Mar 3, 2016
…e BS delete its own account. Replace STATE_DIRTY with boolean dirty in lwm2m_server_t. Signed-off-by: Ricky Liu <ieei.liu@gmail.com>
STATE_DIRTY is just for tag server which is modified by bootstrap. So I remove it and add bool dirty in lwm2m_status_t. It can pass the server bs process. I'm not sure if it's the best way but it's a simple solution for you reference. Thanks. |
dnav
added a commit
that referenced
this issue
Mar 4, 2016
Fix for issue #96: Infinite bootstrapping loop when the BS delete its…
Fixed by #98 |
vslapik
pushed a commit
to vslapik/wakaama
that referenced
this issue
Apr 20, 2017
…e BS delete its own account. Replace STATE_DIRTY with boolean dirty in lwm2m_server_t. Signed-off-by: Ricky Liu <ieei.liu@gmail.com>
vslapik
pushed a commit
to vslapik/wakaama
that referenced
this issue
Apr 20, 2017
Fix for issue eclipse-wakaama#96: Infinite bootstrapping loop when the BS delete its…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the Bootstrap Server deletes or overwrites its own account, the status of the matching lwm2m_server_t is set to STATE_DIRTY then to STATE_BS_PENDING.
Then the server lists are not refreshed and the changes are not take into account.
The text was updated successfully, but these errors were encountered: