-
Notifications
You must be signed in to change notification settings - Fork 408
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
LWM2M Bootstrap towards Leshan Server fails. ( leshan.eclipseprojects.io/ ) #819
Comments
What do you call "the Leshan Server" ? Which kind of handshake failures did you face ? |
Now you change the issue title, I get that you are using the sandbox. So if you want more information about the handshake failure, I need a more data. Like a tcpdump/wireshark capture. (You maybe found a bug?) |
By the way the sandbox is automatically restarted to update it (system updates or leshan updates) and so there is no guaranty it is always up. If you need a stable environment you should consider to host it yourself. |
Hi, |
Does your device use X509 to authenticate itself ? |
No, just the configured Key. |
You mean you are using PreSharedKey ? |
I looked at all the sandbox logs of this month and so only handshake issue I see is about certificate So If you can provide a wireshark/tcpdump capture :) |
Ok, I just looked at it and your device uses only deprecated CBC block ciphers. As this ciphers are not consider as safe enough we deactivate it by default. But If you run the sandbox by yourself you can activate old cipher option with :
|
(I fixed the x509 issue : commit 25413f2) Could we close this issue ? |
Thanks for Support. |
Hello,
I am facing frequent issues with bootstrapping from a remote LWM2M Server towards the Leshan server.
I can see handshake failures reported from the Leshan server, even if the direct connect with the same credentials works.
Have you faced any issues last 2 weeks ?
Thanks!
Cheers,
MP
The text was updated successfully, but these errors were encountered: