[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [wakaama-dev] Leshan and Wakaama over DTLS
|
Hi Frank,
> Has anybody got this setup working ?
Long ago (10 Months), I used tinyDTLS and Scandium to do so.
(But it was a other wakaama client dtls implementation.)
> How do I turn on logging/tracing on the Leshan side to see what is going on on the CoAP and DTLS layers ?
You may use "Californium-logging.properties" or "Scandium-logging.properties" and enable the chosen one with
"-Djava.util.logging.config.file=". Or enable it programmatically with
ScandiumLogger.initialize();
CaliforniumLogger.initialize();
And then set the wanted level.
To see the CoapMessages, you may add a MessageTracer Interceptor:
MessageTracer tracer = new MessageTracer();
for (Endpoint endpoint : lwServer.getCoapServer().getEndpoints()) {
endpoint.addInterceptor(tracer);
}
(But this will only show something, if the DTLS Handshake was successful).
My experience is, using WireShark on 5683 and 5684 (coap or dtls) gives also good hints
About problems.
> Any tips and tricks ? Pitfalls to avoid ?
Chose the right port (5684 for DTLS) :-).
Mit freundlichen Grüßen / Best regards
Achim Kraus
Bosch Software Innovations GmbH
Communications (INST/ESY1)
Stuttgarter Straße 130
71332 Waiblingen
GERMANY
www.bosch-si.de
www.blog.bosch-si.com
achim.kraus@xxxxxxxxxxxx
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn
-----Ursprüngliche Nachricht-----
Von: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] Im Auftrag von Frank Gerlach
Gesendet: Dienstag, 26. April 2016 12:08
An: leshan-dev@xxxxxxxxxxx; wakaama-dev@xxxxxxxxxxx
Betreff: [wakaama-dev] Leshan and Wakaama over DTLS
Hello all,
I am posting this to the Leshan and Wakaama list, because I want to get these two to talk to each other.
So, I want the wakaama client(with tinyDTLS) to communicate with Leshan, using DTLS and a pre-shared key.
I added the PSK, endpoint name and key identity in the Leshan GUI.
Then I changed the code in lwm2mclient in order to match this.
Apparently the server does not respond.
Now maybe somebody can help with the following questions:
Has anybody got this setup working ?
How do I turn on logging/tracing on the Leshan side to see what is going on on the CoAP and DTLS layers ?
Any tips and tricks ? Pitfalls to avoid ?
Thanks for your help !
Kind regards
_______________________________________________
wakaama-dev mailing list
wakaama-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wakaama-dev