-
Notifications
You must be signed in to change notification settings - Fork 3k
Correct mesh network connection status callback functionality. #8439
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
Conversation
@artokin even Seppo already approved this, could you also check this |
Fyi:
|
Now the status callback is only called if the status changed.
6097b01
to
1b1f5e7
Compare
/morph build |
Build : SUCCESSBuild number : 3383 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 3016 |
Test : SUCCESSBuild number : 3186 |
Now the status callback is only called if the status changed.
Description
With the 6lowpan network, lost of border router did cause a loop of NSAPI_STATUS_CONNECTING-NSAPI_STATUS_DISCONNECTED network status indication pairs.
Based on https://confluence.arm.com/display/IoTBU/NetworkInterface+status+callbacks
lost of network should only cause one NSAPI_STATUS_CONNECTING status indication callback.
With these changes only one status indication callback is called.
Tested that both 6lowpan and Thread network status callback's are now working as the should.
Pull request type