Skip to content
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 Server #139

Closed
Hezouwe opened this issue Jun 5, 2016 · 0 comments
Closed

LWM2M Server #139

Hezouwe opened this issue Jun 5, 2016 · 0 comments

Comments

@Hezouwe
Copy link

Hezouwe commented Jun 5, 2016

Hello,

i would like to use LWM2M Server on a Raspberry pi 2.
Do i need additional configuration if i want to use it ?
What is implemented in this code ?
If i need to add something (features, functionalities, ...), is it possible?
Is it well documented?

Thanks,

Hezouwe

mike-scott pushed a commit to mike-scott/leshan that referenced this issue Jan 31, 2018
The server_name extension is meant to help selecting keys or
certificates at the (D)TLS level during the handshake. Once the security
association is established the (virtual) host name that a CoAP message
is supposed to be sent to is indicated by the CoAP message's Uri-Host
option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants