Re: [leshan-dev] Problem with keeping communication

[Julien Vermillard <jvermillard@xxxxxxxxx>]

Hi,

I think the best way to debug it is to do a wireshark/tcpdump capture on both ends (client and server) and check if the packets are well received by the client.

Please note on network using NAT, you have a very small route timeout and after ~60 second the route from the server to the client can be closed.

--
Julien Vermillard

On Thu, Jun 23, 2016 at 2:12 PM, Rarsonic Mato Sunyer <pdvr@xxxxxxx> wrote:

I have a program that uses a Leshan client object, running from a Raspberry Pi 1. Said program uses DTLS security.

The issue is that many times, after an indefinite amount of time, the client stops sending or accepting packets, thus failing the LWM2M updates and not receiving any requests from the server.

If I stop the client then start it again the connection works once more, at least until the next failure.

That has happened too on PCs but it's much rarer.

This may be a Californium or even an unrelated issue, but I'm starting here, Leshan being on top of the networking API pile.

Best Regards,

Ramon Mato.

_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev