RUTX09 mobile data disconnected (internal modem)

To the attention of Teltonika’s Technical Support Office

Good morning,
I report an issue encountered on a RUTX09 router since from the beginning of its use; the problem Is that it periodically disconnects and reconnects to the network, causing annoying problems to the daily office activities on the web. I’ve seen that this issue has already been encountered by other Users on different Teltonika devices and I’ve already tried your suggestions, unfortunately with no solution.

Hardware setup and desired RUTX09 configuration setup is the following:

  • An omnidirectional 5G/LTE antenna placed on the roof in urban environment; ISP’s nearest cell is at approx. 200 meters. There aren’t obstacles between them;
  • Band lock has been activated (B3+B20), choosing “4G/3G Auto” Network type option, to exclude connections to other far cells giving worse signal quality;
  • In this configuration, signal parameters are stable around these values:
    • B3: RSRP -80; RSRQ -15; SINR 11
    • B20: RSRP -68; RSRQ – 10, SINR 10

The problem is that, exactly every four hours, connection is lost by the router, independently from using or not data traffic. The event is “Mobile data disconnected (internal modem)”.

Connection is often automatically re-established after a few seconds, but sometimes - especially if a VPN is active – reconnection fails and it’s necessary to reconnect the router manually.

This problem has been encountered even if:

  • Band selection is set to “Auto”;
  • “4G only” Network type option is active;
  • a reboot has been done;
  • the device has been restored to the factory settings.

Waiting for your kind support, in order to solve this issue.

Best regards

Alberto

Hello,

Make sure the internal modem is up to date by installing the latest RutOS release, then navigating to System → Firmware, and checking the internal modem firmware version. Currently the latest modem firmware version is EG06ELAR04A20M4G.
If that does not help, could you wait for the issue to replicate, then navigate to System → Maintenance → Troubleshoot and extract the system logs from when the disconnection occurred? They can be pasted in the next comment or uploaded to a third-party hosting service like Google Drive.
Thank you.

Best regards,

Hello,
Modem firmware version has been updated before my support request and I confirm that it’s the EG06ELAR04A20M4G version.
Please find below the requested system log extract:

Wed Jan 24 18:57:37 2024 kern.info Mobile data connected (internal modem)
Wed Jan 24 18:57:38 2024 kern.info Joined LTE network (internal modem)
Wed Jan 24 18:57:38 2024 kern.info Connected to xxxxxxxxxxxx operator (internal modem)
Wed Jan 24 19:57:32 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: broadcasting renew
Wed Jan 24 19:57:33 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: lease of xxxxxxxxxxxxxx obtained from xxxxxxxxxxxxxx, lease time 7200
Wed Jan 24 19:59:22 2024 kern.notice Password auth succeeded for admin on HTTP from xxxxxxxxxxxxx
Wed Jan 24 19:59:22 2024 daemon.err uhttpd[1942]: vuci: accepted login for admin from xxxxxxxxxxxxx
Wed Jan 24 20:57:33 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: broadcasting renew
Wed Jan 24 20:57:33 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: lease of xxxxxxxxxxxxxxx obtained from xxxxxxxxxxxxxx, lease time 7200
Wed Jan 24 21:57:33 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: broadcasting renew
Wed Jan 24 21:57:33 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: lease of xxxxxxxxxxxxxxxxx obtained from xxxxxxxxxxxxxxx, lease time 7200
Wed Jan 24 22:36:39 2024 kern.notice Password auth succeeded for admin on HTTP from xxxxxxxxxxxxx
Wed Jan 24 22:36:39 2024 daemon.err uhttpd[1942]: vuci: accepted login for admin from xxxxxxxxxxxxx
Wed Jan 24 22:57:33 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: broadcasting renew
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (4435): Mobile connection lost!
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Interface ‘mob1s1a1’ has lost the connection
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Network device ‘wwan0’ link is down
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Stopping network mob1s1a1
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Network device ‘qmimux0’ link is down
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ has link connectivity loss
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Interface ‘mob1s1a1_6’ has link connectivity loss
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Interface ‘mob1s1a1_6’ is now down
Wed Jan 24 22:57:34 2024 daemon.warn dnsmasq[21779]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Stopping network on /dev/cdc-wdm0!
Wed Jan 24 22:57:34 2024 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,21 --stop-network 0xFFFFFFFF --autoconnect
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): “No effect”
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: SIOCGIFINDEX: No such device
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1_4 (4419): udhcpc: received SIGTERM
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ is now down
Wed Jan 24 22:57:34 2024 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,21 --release-client-id wds
Wed Jan 24 22:57:34 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ is disabled
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Releasing client-id 21 on /dev/cdc-wdm0
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Command failed: Not found
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Stopping network on /dev/cdc-wdm0!
Wed Jan 24 22:57:34 2024 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,22 --stop-network 0xFFFFFFFF --autoconnect
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): “No effect”
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Releasing client-id 22 on /dev/cdc-wdm0
Wed Jan 24 22:57:34 2024 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,22 --release-client-id wds
Wed Jan 24 22:57:34 2024 daemon.notice netifd: mob1s1a1 (32152): Command failed: Not found
Wed Jan 24 22:57:35 2024 daemon.notice netifd: mob1s1a1 (32152): Command failed: Permission denied
Wed Jan 24 22:57:35 2024 daemon.notice netifd: Interface ‘mob1s1a1’ is now down
Wed Jan 24 22:57:35 2024 daemon.notice netifd: Interface ‘mob1s1a1’ is setting up now
Wed Jan 24 22:57:35 2024 daemon.info dnsmasq[21779]: read /etc/hosts - 4 addresses
Wed Jan 24 22:57:35 2024 daemon.info dnsmasq[21779]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Jan 24 22:57:35 2024 daemon.info dnsmasq-dhcp[21779]: read /etc/ethers - 0 addresses
Wed Jan 24 22:57:35 2024 daemon.notice netifd: mob1s1a1 (32400): wwan[32400] Using wwan usb device on bus 3-1
Wed Jan 24 22:57:35 2024 daemon.notice netifd: mob1s1a1 (32400): wwan[32400] Using proto:qmux device:/dev/cdc-wdm0 iface:wwan0 desc:Quectel EG06
Wed Jan 24 22:57:35 2024 kern.info Mobile data disconnected (internal modem)
Wed Jan 24 22:57:35 2024 daemon.notice netifd: mob1s1a1 (32400): Quering active sim position
Wed Jan 24 22:57:35 2024 daemon.notice netifd: mob1s1a1 (32400): Calculated qmimux ifname: qmimux0
Wed Jan 24 22:57:36 2024 user.notice root: uqmi -d /dev/cdc-wdm0 --timeout 6000 --wda-set-data-format --link-layer-protocol raw-ip --ul-protocol qmap --dl-protocol qmap --dl-max-datagrams 32 --dl-datagram-max-size 16384 --ul-max-datagrams 11 --ul-datagram-max-size 8192 --dl-min-padding 0
Wed Jan 24 22:57:36 2024 daemon.notice netifd: mob1s1a1 (32400): Starting network mob1s1a1 using APN: xxxxxxxxxxxxx
Wed Jan 24 22:57:36 2024 daemon.info dnsmasq[21779]: read /etc/hosts - 4 addresses
Wed Jan 24 22:57:36 2024 daemon.info dnsmasq[21779]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Jan 24 22:57:36 2024 daemon.info dnsmasq-dhcp[21779]: read /etc/ethers - 0 addresses
Wed Jan 24 22:57:36 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,21 --release-client-id wds --modify-profile --profile-identifier 3gpp,1 --profile-name profile1 --roaming-disallowed-flag yes --auth-type none --apn xxxxxxxxxxxxx --pdp-type ipv4v6
Wed Jan 24 22:57:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --get-client-id wds
Wed Jan 24 22:57:37 2024 daemon.notice netifd: mob1s1a1 (32400): 21
Wed Jan 24 22:57:37 2024 daemon.notice netifd: mob1s1a1 (32400): cid4: 21
Wed Jan 24 22:57:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --wds-bind-mux-data-port --mux-id 1 --ep-iface-number 4 --set-client-id wds,21
Wed Jan 24 22:57:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-ip-family ipv4 --set-client-id wds,21
Wed Jan 24 22:57:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,21 --start-network --apn xxxxxxxxxxxxxxxxxxx --profile 1 --auth-type none --username --password
Wed Jan 24 22:57:37 2024 daemon.notice netifd: mob1s1a1 (32400): pdh4: -667754992
Wed Jan 24 22:57:37 2024 daemon.notice netifd: mob1s1a1 (32400): -667754992
Wed Jan 24 22:57:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --get-client-id wds
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): 22
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): cid6: 22
Wed Jan 24 22:57:38 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --wds-bind-mux-data-port --mux-id 1 --ep-iface-number 4 --set-client-id wds,22
Wed Jan 24 22:57:38 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-ip-family ipv6 --set-client-id wds,22
Wed Jan 24 22:57:38 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,22 --start-network --apn xxxxxxxxxxxxxxxxx --profile 1 --auth-type none --username --password
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): pdh6: -1028198320
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): -1028198320
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): Setting up qmimux0
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): Setting configured MTU: 1500 on qmimux0
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1’ is now up
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Network device ‘wwan0’ link is up
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): Setting up qmimux0 V4 DCHP
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ is enabled
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Network device ‘qmimux0’ link is up
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ has link connectivity
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ is setting up now
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): Setting up qmimux0 V6 static
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): {
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “pdp-type”: “ipv4-or-ipv6”,
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “ip-family”: “ipv6”,
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “mtu”: 1500,
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “ipv4”: {
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400):
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): },
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “ipv6”: {
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “ip”: “xxxxxxxxxxxxxxxx”,
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “ip-prefix-length”: 64,
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “gateway”: “xxxxxxxxxxxxxx”,
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “gw-prefix-length”: 64
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): },
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): “domain-names”: {
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400):
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): }
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): }
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1 (32400): uci: Entry not found
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_6’ is enabled
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_6’ is setting up now
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_6’ is now up
Wed Jan 24 22:57:38 2024 daemon.notice netifd: Interface ‘mob1s1a1_6’ has link connectivity
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1_4 (722): udhcpc: started, v1.34.1
Wed Jan 24 22:57:38 2024 daemon.notice netifd: mob1s1a1_4 (722): udhcpc: broadcasting discover
Wed Jan 24 22:57:39 2024 daemon.notice netifd: mob1s1a1_4 (722): udhcpc: broadcasting select for xxxxxxxxxxxx, server xxxxxxxxxxxxx
Wed Jan 24 22:57:39 2024 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (wwan0)
Wed Jan 24 22:57:39 2024 daemon.notice netifd: mob1s1a1_4 (722): udhcpc: lease of xxxxxxxxxxxxx obtained from xxxxxxxxxxxxx, lease time 7200
Wed Jan 24 22:57:39 2024 daemon.notice netifd: Interface ‘mob1s1a1_4’ is now up
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain test
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain onion
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain localhost
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain local
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain invalid
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain bind
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using only locally-known addresses for domain lan
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using nameserver xxxxxxxxxxxxx#53
Wed Jan 24 22:57:39 2024 daemon.info dnsmasq[21779]: using nameserver xxxxxxxxxxxxx#53
Wed Jan 24 22:57:40 2024 daemon.info dnsmasq[21779]: read /etc/hosts - 4 addresses
Wed Jan 24 22:57:40 2024 daemon.info dnsmasq[21779]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Jan 24 22:57:40 2024 daemon.info dnsmasq-dhcp[21779]: read /etc/ethers - 0 addresses
Wed Jan 24 22:57:41 2024 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_6 (qmimux0)
Wed Jan 24 22:57:42 2024 kern.info Mobile data connected (internal modem)
Wed Jan 24 22:57:42 2024 kern.info Joined LTE network (internal modem)
Wed Jan 24 22:57:42 2024 kern.info Connected to xxxxxxxxxxxxxxxxxx operator (internal modem)
Wed Jan 24 22:57:42 2024 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (qmimux0)
Wed Jan 24 22:57:42 2024 user.info : Starting database size optimization…
Wed Jan 24 22:57:44 2024 daemon.info dnsmasq[21779]: read /etc/hosts - 4 addresses
Wed Jan 24 22:57:44 2024 daemon.info dnsmasq[21779]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Wed Jan 24 22:57:44 2024 daemon.info dnsmasq-dhcp[21779]: read /etc/ethers - 0 addresses
Wed Jan 24 22:57:44 2024 kern.info Mobile data connected (internal modem)
Wed Jan 24 22:57:44 2024 kern.info Joined LTE network (internal modem)
Wed Jan 24 22:57:44 2024 kern.info Connected to xxxxxxxxxxxxxxxx operator (internal modem)
Wed Jan 24 22:57:46 2024 user.info : Finished database optimization
Wed Jan 24 22:57:55 2024 daemon.warn dnsmasq[21779]: nameserver xxxxxxxxxxxx refused to do a recursive query
Wed Jan 24 22:58:40 2024 daemon.warn dnsmasq[21779]: nameserver xxxxxxxxxxxx refused to do a recursive query

Looking for your kind answer, in order to solve the problem.
Thank you for your cooperation
Kind regards
Alberto

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 neither of them is an option, please fill out the Contact Us form here: Teltonika Networks - LTE Routers, Gateways & Modems for IoT

Best regards,

Hello,
thank you; I’ll contact you as indicated.
Best regards
Alberto

This topic was automatically closed after 15 days. New replies are no longer allowed.