Server timesout

[sridevgit]

When Client connects to Leshan server behind NAT, After 2 mints, server is no longer in position to issue any requests to client until next registration update. We are going live very soon and lot of our devices are LTE, So it would be practically impossible to send registration update every 2 minutes since the devices will be in motion most of the time, it would be hard to have network everywhere. Any help for workaround for this issue would be much appreciated. Thank you

[boaks]

I'm not sure, what you mean.

When Client connects to Leshan server behind NAT, After 2 mints, server is no longer in position to issue any requests to client until next registration update although the client is connected to the server.

Do you mean "the leshan demo server shows the device as connected in the web ui"?
If that's true, then I would just truncate your issue description to

When Client connects to Leshan server behind NAT, After 2 mints, server is no longer in position to issue any requests to client until next registration update

And yes, that behavior is simply the nature of a NAT! If the address translation times out, there is no back-translation and so the destination gets unreachable.
So, why do you use a NAT? Can you configure it to keep the address translation for more than those 2 minutes?

So it would be practically impossible to send registration update every 2 minutes since the devices will be in motion most of the time, it would be hard to have network everywhere.

Hm, so what do you really plan? If the device can't send the update registration, because it has no network, how should then the request reach the device?

Anyway, eclipse-leshan/leshan#542 contains also a idea, how to solve the "NAT nature issue" (sending frequently 1 byte UDP messages). Maybe that helps you as well.

[boaks]

Just to add:
If you can't change the address translation timeout, but your NAT is on a router, some router have also a "port forwarding", which may be used to by pass the NAT.