Communication issues
If your problem appears after some time with a known working configuration, you can jump directly to the System known to be working section.
Otherwise, you can consult the following Fresh installation or reconfiguration section.
Fresh installation or reconfiguration
Network configuration
The first thing to verify is that your gateway is able to communicate with the server, from an IP point of view.
You can find more information regarding the network configuring in the legacy documentation.
The ping command can be used to verify you have access.
The most simple is to try first to reach the router on which the LORIX One is connected. In case of success and if you need to access the outside world, try with an external server.
For example, the command ping 8.8.8.8 can be used to verify you can reach the DNS servers of Google.
Another point to check is that your firewall is accepting output connections. Otherwise, the gateway will obviously not be able to communicate with external servers.
Server configuration
Once you've validated that your network configuration is fine in the previous section, you need to ensure the forwarder is correctly configured to reach the network server, being hosted in the cloud or in your own network.
You can find more information regarding the server configuration for a given forwarder in the legacy documentation.
System known to be working
You successfully configured your gateway including the network aspect as well as the connection to your server.
After some time of running however, you can't to reach your gateway, it's not detected by the server or simply you don't receive packets from nodes.
No more access using SSH
When you have the trouble, is the gateway not accessible anymore through the SSH and you need to switch power off and on to get it back ?
In this case, the page regarding a bug in the Linux's ethernet driver can probably helps you.
The gateway is not connected to the server
You can still reach the gateway using SSH but it's not detected anymore by the server.
In this case, the first thing to test is that the configured packet-forwarder is still running.
To validate that, you can use the command:
It returns the actual status of the chosen forwarder and lets you know if it died.
If the forwarder is still running, you have maybe a temporary network issue or the server is down.
You can try to restart the forwarder using the command:
If the problem persists after the restart, contact us for more support.
Known issue with the packet-forwarders
The UDP Semtech packet-forwarder and its derived (ttn, poly-pkt-forwarder) are known to die quite easily in case of some errors.
A badly formatted LoRa packet for example is considered as a fatal error and the packet-forwarder will stop.
For this reason, it is now monitored in LORIX OS but if you can't move forward with it, you can find more information here on how to configure the legacy firmware for this issue.