No join accept after join request

These need to be fairly small for the backend to consider your gateway to be alive. Try with 45 seconds or there abouts. Also keep in mind session tracking firewall timeouts, the connection should not expire.

Why use values that large? With the default values a gateway consumes less than 100MB traffic a month, with these settings things break as you noticed.

@kersing Yes with the default configuration it consumes less than 100 MB. But the use-case is to get the connectivity on the open sea. So we are using Satellite connection and if a single gateway consumes around 100 MB it is going to be super expensive.

Moreover we are using single satellite modem for two gateways. When both the gateways are pinging continuous, communication window of the satellite is opened for a longer time and when it is open for more than 200 seconds. We are getting penalty on the actual data usage.

This is reason why we choose to have a high ping interval.

Those values will not work for an UDP based packet forwarder, you could try BasicStation which is TCP based and check if that fits your use case better. Or look into satellite based LoRaWAN nodes.