-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[WI-SUN] Network loses stored certificates after first connect #12798
Comments
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2630 |
cc @artokin |
Hi @artokin, any comments regarding this issue? |
I have the same problem here with an STM32WB55 custom board. I tried removing the certificates and setting them again, but still after the Network Interface disconnects and reconnects back, I get "no own cert" error. |
We will start working on this issue sorry for the delay. |
@felipeLeast and @eriknayan I created pull request to fix this could you check that is fixes the issue you are having |
PR Fixed issue! |
Description of defect
I've developed a routine in my program that check's for internet connectivity. When some time goes by without response I reset my wi-sun connection, the problem I'm facing is that when I attepmt to disconnect and connect again the WisunInterface on the authentication process I get "no own certificate", after some debuging I've found that the problem lies on the fact that after the certificates load stored certificates from
wisun_tasklet_add_stored_certificates
it deletes from the list of certificates.I can see two options to fix this problem:
1- Comment line 498 from wisun_tasklet.c which deletes stored certificates
2- On disconnect delete em free
wisun_tasklet_data_ptr
, which gives me the possibility to reload my certificates.Target(s) affected by this defect ?
K64F
Toolchain(s) (name and version) displaying this defect ?
ARM_GCC
What version of Mbed-os are you using (tag or sha) ?
mbed-os 5.15.1
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10
How is this defect reproduced ?
On mbed-os-example-mesh-minimal add after:
printf("Connected. IP = %s\n", sockAddr.get_ip_address());
The text was updated successfully, but these errors were encountered: