I created a post here with the same question, as I cannot find any other places to get support?
The LTE/5G connection on my RUTX50 is lost every few days, and restored as soon as I restart the connection (it says the modem was rebooted). So it must be some kind of problem in the RUTX50.
I hope someone here can help fix this problem?
Troubleshooting file: troubleshoot-Teltonika-RUTX50.com-2023-08-16.tar.gz - pCloud
Problem occurred last at approx. 16/08 21.34
Hello, I have the same problem. When I loss the connection, I can’t access the open ports in the mobile interface but the wan interface yes. I have configured the load balancing mode for both interface.
I don’t know if it’s a firmware bug. I have the firmware version 7.03
Hello,
Firstly, I’d recommend installing the latest RutOS version to check if the behavior reoccurs.
Secondly, please post the internal modem firmware version that the device is using. It can be found by navigating to System → Firmware. A similar issue has been addressed with a modem update, so if there is an update available for the internal modem, please apply it.
Finally, if none of the recommendations help, please wait for the issue to replicate, then log into the WebUI, navigate to System → Administration → Troubleshoot, and copy the last few minutes of the system log. It can be pasted in the next comment. Make sure to remove any sensitive information!
Best regards,
Sorry, I should have mentioned that. This occurs on the latest versions of firmware and modem firmware:
RUTX_R_00.07.04.5 and RG501QEUAAR12A08M4G_04.200.04.200. The system tells me there are no newer versions.
There does not seem to be anything of interest in the system log before I log in to restart the modem:
Wed Aug 16 18:37:33 2023 daemon.info dnsmasq-dhcp[3938]: DHCPACK(br-lan) 192.168.8.2 10:56:ca:09:eb:86 peplink
Wed Aug 16 19:08:18 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: broadcasting renew
Wed Aug 16 19:08:19 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: lease of 109.56.139.146 obtained from 109.56.139.145, lease time 7200
Wed Aug 16 20:08:19 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: broadcasting renew
Wed Aug 16 20:08:19 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: lease of 109.56.139.146 obtained from 109.56.139.145, lease time 7200
Wed Aug 16 21:08:19 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: broadcasting renew
Wed Aug 16 21:08:19 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: lease of 109.56.139.146 obtained from 109.56.139.145, lease time 7200
Wed Aug 16 21:33:47 2023 kern.notice Authentication was successful from HTTP 192.168.8.2
Wed Aug 16 21:33:47 2023 daemon.err uhttpd[1920]: vuci: accepted login for admin from 192.168.8.2
Wed Aug 16 21:34:21 2023 daemon.err uhttpd[1920]: Command failed: Not found
Wed Aug 16 21:34:22 2023 daemon.err uhttpd[1920]: Failed to parse message data
Wed Aug 16 21:34:23 2023 daemon.err uhttpd[1920]: Command failed: Method not found
Wed Aug 16 21:35:05 2023 daemon.info mobifd: [gsm.modem0] Config reload initiated
Wed Aug 16 21:35:05 2023 daemon.notice netifd: mob1s1a1 (9065): Stopping network mob1s1a1
Wed Aug 16 21:35:05 2023 daemon.notice netifd: Network device 'qmimux0' link is down
Wed Aug 16 21:35:05 2023 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity loss
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: SIOCGIFINDEX: No such device
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1_4 (25282): udhcpc: received SIGTERM
Wed Aug 16 21:35:06 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is now down
Wed Aug 16 21:35:06 2023 user.warn mwan3-hotplug[9064]: hotplug called on mob1s1a1 before mwan3 has been set up
Wed Aug 16 21:35:06 2023 daemon.notice netifd: Interface 'mob1s1a1_4' is disabled
Wed Aug 16 21:35:06 2023 daemon.warn dnsmasq[3938]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1 (9065): Stopping network on /dev/cdc-wdm0!
Wed Aug 16 21:35:06 2023 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,14 --stop-network 0xFFFFFFFF --autoconnect
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1 (9065): Releasing client-id 14 on /dev/cdc-wdm0
Wed Aug 16 21:35:06 2023 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,14 --release-client-id wds
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1 (9065): Command failed: Not found
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1 (9065): Command failed: Not found
Wed Aug 16 21:35:06 2023 daemon.notice netifd: mob1s1a1 (9065): Command failed: Permission denied
Wed Aug 16 21:35:06 2023 daemon.notice netifd: Interface 'mob1s1a1' is now down
Wed Aug 16 21:35:07 2023 daemon.info dnsmasq[3938]: read /etc/hosts - 4 addresses
Wed Aug 16 21:35:07 2023 daemon.info dnsmasq[3938]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Aug 16 21:35:07 2023 daemon.info dnsmasq-dhcp[3938]: read /etc/ethers - 0 addresses
Wed Aug 16 21:35:08 2023 kern.info Mobile data disconnected (internal modem)
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] SMS storage: sm
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 15 seconds of timeout
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] Connected to operator '3 3'
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] -CFUN- Functionality: "Full"
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] -COPS- Mode: "Auto", operator: "3 3"
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] -CREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "50202", cell ID: "58122556", technology: "E-UTRAN-NR"
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] -CGREG- Mode: "Enabled (with location information)", status: "Not registered", LAC: "", cell ID: "", technology: "Unknown"
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] -CEREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "50202", cell ID: "58122556", technology: "E-UTRAN-NR"
Wed Aug 16 21:35:08 2023 daemon.info mobifd: [gsm.modem0] IP address on PDP context "1": "109.56.139.146"
Wed Aug 16 21:35:08 2023 daemon.notice netifd: Interface 'mob1s1a1' is setting up now
Wed Aug 16 21:35:08 2023 daemon.notice netifd: mob1s1a1 (9735): wwan[9735] Using wwan usb device on bus 2-1
Wed Aug 16 21:35:09 2023 daemon.notice netifd: mob1s1a1 (9735): wwan[9735] Using proto:qmapv5 device:/dev/cdc-wdm0 iface:wwan0 desc:Quectel RG50X
Wed Aug 16 21:35:09 2023 daemon.notice netifd: mob1s1a1 (9735): Failed to parse message data
Wed Aug 16 21:35:09 2023 daemon.notice netifd: mob1s1a1 (9735): Command failed: Not found
Wed Aug 16 21:35:09 2023 daemon.notice netifd: mob1s1a1 (9735): Failed to parse message data
Wed Aug 16 21:35:09 2023 daemon.notice netifd: mob1s1a1 (9735): WARNING: Variable 'list' does not exist or is not an array/object
Wed Aug 16 21:35:09 2023 daemon.notice netifd: mob1s1a1 (9735): Creating context with PDP: 1
Wed Aug 16 21:35:11 2023 daemon.notice netifd: mob1s1a1 (9735): Quering active sim position
Wed Aug 16 21:35:11 2023 daemon.notice netifd: mob1s1a1 (9735): Calculated qmimux ifname: qmimux0
This message is why the modem restart occurs. This message usually indicates a setting change by the user. For example, if you were to change the APN, this message would be generated, and the modem would be restarted. I presume in this case no settings were changed manually?
Best regards,
Correct: No manual interaction at all, at any of the times this has occurred.
Only after the problem occurs, I log in and restart the modem. In this case everything around 21:35:05 is me restarting the modem.
It just happened again now, noticed at 17/08 21.04.
Nothing that looks interesting or suspicious in the log.
Please help with this, urgently. It is a huge problem that this hardware just stops the connection at random times…
Hello,
In order to resolve the issue that you are currently experiencing, additional provision of further confidential details is required. Hence, it is recommended that you reach out to your designated sales manager or the reseller from whom you acquired the device in question. They will be able to assist you in addressing this matter more effectively. If you don’t have a designated sales manager, and the reseller is not willing to cooperate, please fill out the Contact Us form here: Teltonika Networks - LTE Routers, Gateways & Modems for IoT
Additional troubleshooting steps that may help here would be:
Let me know if you experience any issues.
Best regards,
This topic was automatically closed after 15 days. New replies are no longer allowed.