Iot sdk thesis

Figure 3.3.2.1 Registering Credentials for ‘SODAQWakaamaDTLS’ client on Eclipse Leshan Server 
(NOTE: ‘Client Endpoint’ and ‘Identity’ have the same name. It is not necessary that both these 
variables have the same name. The only requirement is that both of them should be exactly 
identical to how they have been set in their relevant variables in source code.) 
3.3.5
 
Results 
The results that imply successful integration of DTLS in Wakaama are: successful 
deployment of Wakaama LWM2M client on SODAQ SARA and successful registration of the 
deployed client on a LWM2M server. 
Successful Deployment 
The successful deployment of the client on SODAQ SARA is evident from the terminal 
output. For convenient reading, the total output has been displayed in two parts. 
Figure 3.3.3.1 Wakaama Client Successful deployment on SODAQ SARA 
 

---

66 
Successful Registration of The Deployed Client on a LWM2M Server 
The successful registration of client is indicated by the appearance of the given client 
name ‘SODAQWakaamaDTLS’ in Eclipse’s Leshan URL Client List. Also notice that the 
‘lock’ symbol signifies that the communication between the client on SODAQ SARA and the 
Leshan server is secured with DTLS. This is the testimony of successful tinydtls integration in 
existing Wakaama implementation. 
Figure 3.3.2.2 ‘SODAQWakaamaDTLS’ Registered with ‘Communication over DTLS’ on Eclipse Leshan 
Server 
To observe the registration process of the LWM2M client deployed on SODAQ SARA 
secured with DTLS, a Leshan server is set-up on a private Linux server using the open-source 
downloadable java implementation of LWM2M is available here [37]. The private Linux server 
was accessed via Secure Shell facility in PuTTY software.
The server was available on a public URL and the server IP is updated accordingly in 
source code (
const char * serverIP =
) before deploying. The DTLS 
credentials are also added to this local Leshan server, the process of which is exactly identical 
as shown in Figure 3.3.2.1.