Hello,
The troubleshooting steps depend on what WAN source you are using. However, since you are using RUTX14, I assume the issues you are facing are mobile connection-related. It is best to troubleshoot after the issue reoccurs. Download the troubleshoot file, open it using 7zip or a similar archiving tool, and in the troubleshoot folder you will see a few .log files. For mobile connection, the main ones you should be looking at are system.log and gsm.log.
The system.log file contains all of the event logs. So for example one thing I noticed on the first look in the system.log file, is that the router is trying to set different APNs in the hope of receiving an IP address from one of them, but it is timing out:
Thu May 18 14:34:34 2023 daemon.info mobifd: [gsm.modem0] APN '' isn't prepared for PDP 1, preparing it
Thu May 18 14:34:35 2023 daemon.info mobifd: [gsm.modem0] Initializing modem. Please wait.
Thu May 18 14:34:38 2023 daemon.info mobifd: [gsm.modem0] APN '' was successfully prepared for PDP 1
Thu May 18 14:34:38 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 10 seconds of timeout
Thu May 18 14:34:58 2023 daemon.info mobifd: [gsm.modem0] APN 'Internet' isn't prepared for PDP 1, preparing it
Thu May 18 14:34:58 2023 daemon.info mobifd: [gsm.modem0] Initializing modem. Please wait.
Thu May 18 14:35:01 2023 daemon.info mobifd: [gsm.modem0] APN 'Internet' was successfully prepared for PDP 1
Thu May 18 14:35:01 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 15 seconds of timeout
The exact reason why this is happening could be explored in the gsm.log file.
In the get_net_reg_stat (get network registration status) query, we can see that the modem is searching for an operator:
get_net_reg_stat:
{
"mode_id": 3,
"mode": "Enabled (with location information)",
"status_id": 2,
"status": "Searching"
}
This could indicate a few things, such as:
- The operator is denying registration to the device;
- There are no cell towers from your operator nearby;
- Operator whitelist is configured incorrectly;
Of course, there could be many more reasons, and most of the things I mentioned are mostly speculation. It should be kept in mind, that troubleshoot file is mostly a tool for an internal investigation of what could be wrong, and is not oriented toward customers, so some information might not be as easy to understand, and no learning resources are available.
If you do not manage to figure out what could be wrong with the device, please provide more information on this case and I will be able to help with further troubleshooting the issue.
Hope this helps!
Best regards,
DaumantasG
