RUT241 - Mobile connection lost every hour

florian.pirnbacher · April 8, 2024, 7:41am

Hi,
I have a problem with one of my RUT241. I set up the router last week. We have a private APN in our company.
The problem is, that the router looses its mobile connection every hour for about 10 seconds. I have searched many topics in the community, but I didn’t found a resolution.
I have tried many setting: Firmware upgrade, static APN, static network type, firewall settings, and so on.

I also checked the log files, but i didn’t find any issues in there.
Maybe someone can help me?

Here is the log file:
(notice that I have changed some ip addresses because of private APN!)

root@sa-pwrhive-rt01:~# logread -f
Mon Apr  8 06:58:24 2024 daemon.notice netifd: mob1s1a1 (30841): Mobile connection lost!
Mon Apr  8 06:58:24 2024 daemon.notice netifd: Interface 'mob1s1a1' has lost the connection
Mon Apr  8 06:58:24 2024 daemon.notice netifd: Network device 'wwan0' link is down
Mon Apr  8 06:58:25 2024 daemon.notice netifd: mob1s1a1 (4772): Stopping network mob1s1a1
Mon Apr  8 06:58:26 2024 daemon.notice netifd: mob1s1a1 (4772): Stopping network on /dev/cdc-wdm0!
Mon Apr  8 06:58:26 2024 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,18 --stop-network 0xFFFFFFFF --autoconnect
Mon Apr  8 06:58:26 2024 daemon.notice netifd: mob1s1a1 (4772): "No effect"
Mon Apr  8 06:58:26 2024 daemon.notice netifd: mob1s1a1 (4772): Releasing client-id 18 on /dev/cdc-wdm0
Mon Apr  8 06:58:26 2024 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,18 --release-client-id wds
Mon Apr  8 06:58:27 2024 daemon.notice netifd: mob1s1a1 (4772): Command failed: Not found
Mon Apr  8 06:58:27 2024 daemon.notice netifd: Network device 'qmimux0' link is down
Mon Apr  8 06:58:27 2024 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity loss
Mon Apr  8 06:58:29 2024 daemon.notice netifd: Interface 'mob1s1a1_4' is disabled
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): udhcpc: SIOCGIFINDEX: No such device
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): udhcpc: unicasting a release of XXX.XXX.XXX.XX to XXX.XXX.XXX.XX
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): udhcpc: sending release
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): udhcpc: can't bind to interface qmimux0: No such device
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): udhcpc: bindtodevice: No such device
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): udhcpc: entering released state
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1_4 (30870): Command failed: Permission denied
Mon Apr  8 06:58:29 2024 daemon.notice netifd: Interface 'mob1s1a1_4' is now down
Mon Apr  8 06:58:29 2024 daemon.warn dnsmasq[5253]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Apr  8 06:58:29 2024 daemon.notice netifd: mob1s1a1 (4772): Command failed: Permission denied
Mon Apr  8 06:58:29 2024 daemon.notice netifd: Interface 'mob1s1a1' is now down
Mon Apr  8 06:58:29 2024 daemon.notice netifd: Interface 'mob1s1a1' is setting up now
Mon Apr  8 06:58:30 2024 daemon.info dnsmasq[5253]: read /etc/hosts - 4 addresses
Mon Apr  8 06:58:30 2024 daemon.info dnsmasq[5253]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Mon Apr  8 06:58:30 2024 daemon.notice netifd: mob1s1a1 (5038): wwan[5038] Using wwan usb device on bus 1-1
Mon Apr  8 06:58:31 2024 daemon.notice netifd: mob1s1a1 (5038): wwan[5038] Using proto:qmux device:/dev/cdc-wdm0 iface:wwan0 desc:MeigLink SLM750
Mon Apr  8 06:58:32 2024 kern.info Mobile data disconnected (internal modem)
Mon Apr  8 06:58:34 2024 daemon.notice netifd: mob1s1a1 (5038): Calculated qmimux ifname: qmimux0
Mon Apr  8 06:58:35 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 16 --dl-datagram-max-size 4096 --ul-max-datagrams 11 --ul-datagram-max-size 4096 --dl-min-padding 0
Mon Apr  8 06:58:35 2024 daemon.notice netifd: mob1s1a1 (5038): Starting network mob1s1a1 using APN: private.sbgag.m2m
Mon Apr  8 06:58:36 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,18 --release-client-id wds --modify-profile --profile-identifier 3gpp,1 --profile-name profile1 --roaming-disallowed-flag no    --auth-type none  --apn private.sbgag.m2m  --pdp-type ip
Mon Apr  8 06:58:36 2024 daemon.info dnsmasq[5253]: read /etc/hosts - 4 addresses
Mon Apr  8 06:58:36 2024 daemon.info dnsmasq[5253]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Mon Apr  8 06:58:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --get-client-id wds
Mon Apr  8 06:58:37 2024 daemon.notice netifd: mob1s1a1 (5038): 18
Mon Apr  8 06:58:37 2024 daemon.notice netifd: mob1s1a1 (5038): cid4: 18
Mon Apr  8 06:58: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,18
Mon Apr  8 06:58:37 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-ip-family ipv4 --set-client-id wds,18
Mon Apr  8 06:58:38 2024 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,18 --start-network --apn private.sbgag.m2m --profile 1  --auth-type none --username  --password
Mon Apr  8 06:58:38 2024 daemon.notice netifd: mob1s1a1 (5038): pdh4: -511197280
Mon Apr  8 06:58:38 2024 daemon.notice netifd: mob1s1a1 (5038): -511197280
Mon Apr  8 06:58:38 2024 daemon.notice netifd: mob1s1a1 (5038): Setting up qmimux0
Mon Apr  8 06:58:38 2024 daemon.notice netifd: mob1s1a1 (5038): Setting dynamic MTU: 1500 on qmimux0
Mon Apr  8 06:58:38 2024 daemon.notice netifd: Interface 'mob1s1a1' is now up
Mon Apr  8 06:58:38 2024 daemon.notice netifd: Network device 'wwan0' link is up
Mon Apr  8 06:58:38 2024 daemon.notice netifd: mob1s1a1 (5038): Setting up qmimux0 V4 DCHP
Mon Apr  8 06:58:38 2024 daemon.notice netifd: Interface 'mob1s1a1_4' is enabled
Mon Apr  8 06:58:38 2024 daemon.notice netifd: Network device 'qmimux0' link is up
Mon Apr  8 06:58:38 2024 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity
Mon Apr  8 06:58:38 2024 daemon.notice netifd: Interface 'mob1s1a1_4' is setting up now
Mon Apr  8 06:58:39 2024 daemon.notice netifd: mob1s1a1_4 (5602): udhcpc: started, v1.34.1
Mon Apr  8 06:58:39 2024 daemon.notice netifd: mob1s1a1_4 (5602): udhcpc: broadcasting discover
Mon Apr  8 06:58:39 2024 daemon.notice netifd: mob1s1a1_4 (5602): udhcpc: broadcasting select for XXX.XXX.XXX.XX, server XXX.XXX.XXX.XX
Mon Apr  8 06:58:39 2024 daemon.notice netifd: mob1s1a1_4 (5602): udhcpc: lease of XXX.XXX.XXX.XX obtained from XXX.XXX.XXX.XX, lease time 7200
Mon Apr  8 06:58:39 2024 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (wwan0)
Mon Apr  8 06:58:40 2024 daemon.notice netifd: Interface 'mob1s1a1_4' is now up
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain test
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain onion
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain localhost
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain local
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain invalid
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain bind
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using only locally-known addresses for domain lan
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using nameserver 10.XXX.XXX.XXX#53
Mon Apr  8 06:58:40 2024 daemon.info dnsmasq[5253]: using nameserver 10.XXX.XXX.XXX#53
Mon Apr  8 06:58:45 2024 daemon.info dnsmasq[5253]: read /etc/hosts - 4 addresses
Mon Apr  8 06:58:45 2024 daemon.info dnsmasq[5253]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Mon Apr  8 06:58:46 2024 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (qmimux0)
Mon Apr  8 06:58:50 2024 daemon.info dnsmasq[5253]: read /etc/hosts - 4 addresses
Mon Apr  8 06:58:50 2024 daemon.info dnsmasq[5253]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Mon Apr  8 06:58:51 2024 kern.info Mobile data connected (internal modem)
Mon Apr  8 06:58:51 2024 kern.info Joined LTE network (internal modem)
Mon Apr  8 06:58:51 2024 kern.info Connected to Magenta-T- Telekom.de operator (internal modem)

I also downloaded a troubleshoot file from router, but I can’t upload because I’m a new user here.

Kind regards,
Florian

Marijus · April 9, 2024, 6:30am

Hello,

I’ve reviewed the logread and everything seems normal except for the loss of mobile connection. To better understand the issue, could you let me know if this happens regularly, like at the same time every day, or if it’s random?

I also noticed that you captured the exact moment of disconnection with logread -f. Does a specific event trigger this? How’s the signal? Could it be due to signal fluctuations?

Best regards,

Marijus

florian.pirnbacher · April 9, 2024, 8:24am

Hi Marijus,
thanks for your answer.

It happens every hour. See the screenshot from network event log:

No, there is no trigger from my side.
Signal is very good, you can see in this screenshot:

Kind regards,
Florian

Marijus · April 9, 2024, 8:32am

Hello,

Have you contacted your carrier about this issue? It might be a carrier-related problem, especially when using a private APN. Network configurations can be changed, and the carrier might not even be aware of the issue.

Regarding the router, do you have any crontab jobs running on it, especially on an hourly basis, that might influence mobile connection maybe even indirectly, like some service restart?

Kind regards,

Marijus

florian.pirnbacher · April 9, 2024, 11:21am

Hello Marijus,
carrier Magenta has been contacted last week. But they are unfortunately not very helpful in this case…

The config of the router is not very high-complex. The most complex setting is a NAT rule, that a device on LAN port of the router can communicate with port 502 to a centralized station. To check, I also have unplugged this device from router. But issue is still alive.

There are no crontab jobs configured.

Kind regards,
Florian

Marijus · April 9, 2024, 11:35am

Hello,

To determine if this specific SIM card or private network is causing the constant reconnection issue, you can try switching to another SIM card for at least 1-2 hours or during the timeframe when disconnections occur as it seems to be very consistent. This will help us understand which component is responsible: the router or the provider.

Kind regards,

Marijus

florian.pirnbacher · April 10, 2024, 6:37am

Hello,
ok. Good input.I will try this the next time, when I’m on site of the router.

Thanks!

Kind regards,
Florian

florian.pirnbacher · April 10, 2024, 7:45am

Hello Marijus,
I have new insights. I checked some other routers with similar configurations.

→ The router with my connection problem has firmware RUT2M_R_00.07.06.10

→ One another router has firmware RUT2M_R_00.07.06.3 - this router has the same connection problem!

→ And again one another router has also firmware RUT2M_R_00.07.06.3 and also same problem. On this router I downgraded the firmware to RUT2_R_00.07.04.5. Now there are no connection problems anymore!

By the way: All routers have the same SIM carrier with same private APN.

It seems that this is a problem with firmware?

Kind regards,
Florian

Marijus · April 10, 2024, 7:56am

Hello,

Yes, firmware changes might interfere, but it will be very hard to pinpoint what is the issue here. We still need to know if private APN is not a culprit here. As some specific settings on that network may be used. Test with another SIM card would still help rule out a lot of possibilities.

Kind regards,
Marijus

florian.pirnbacher · April 10, 2024, 8:31am

Hi,
I will test it with other SIM card when I’m on site.

In the meantime I was able to find out that apparently only one modem model and modem firmware is affectet, but on different router models with different router firmware:

RUT951
RUT2M_R_00.07.06.10
RUT9M_R_00.07.04.5

Modem SLM750-VE
SLM750-V_4.0.12_EQ101

RUT241
RUT2M_R_00.07.06.3
RUT2M_R_00.07.04.3

Modem SLM750-VE
SLM750-V_4.0.12_EQ101

I have not seen the problem on routers with other modem model or modem firmware. I have checked about 10-15 devices.

Kind regards,
Florian

Marijus · April 10, 2024, 8:55am

Hello,

I’ve noticed that the modem firmware you are using is quite outdated. Could you please try updating the modem firmware and checking again if disconnection issues still persist?

Best regards,
Marijus

florian.pirnbacher · April 10, 2024, 9:04am

Hi,
how can I upgrade only the modem firmware? And where do I get the modem firmware? I didn’t found it on teltonika website.

Kind regards,
Florian

Marijus · April 10, 2024, 9:21am

Hello,

To check for newer modem firmware, follow these steps:

Navigate to System → Firmware → Update firmware page.
Look for the location marked in the image below.

If a new firmware version is available, proceed to upgrade it using the provided firmware/modem upgrade section below.

Kind regards,
Marijus

florian.pirnbacher · April 10, 2024, 9:32am

Hi,
sorry, I forget to inform you that in our private APN is no internet connection allowed. So I don’t have access to direct Teltonika firmware upgrades.
I have to do it with firmware files.

Is this also possible, just with modem firmware?

Kind regards,
Florian

Marijus · April 10, 2024, 11:08am

Hello,

I highly recommend updating the modem via an internet connection. The alternative option is reserved for rare cases where a specific modem firmware is required. This alternative method involves downloading and installing multiple packages, which can complicate matters when internet access is unavailable. Moreover, there’s a risk of bricking the device if power is lost during the update process.

Therefore, I strongly advise disconnecting devices from your private network and updating them via an internet connection.

Kind regards,
Marijus

florian.pirnbacher · April 10, 2024, 12:12pm

Hello Maijus,
ok. I will be on site next monday and will try to update the firmware with direct internet connection.

Kind regards,
Florian

PS: The traffic of our routers with private APN is routed through a firewall. Do you know the URL’s and ports, where the routers will connect by firmware upgrades?

Marijus · April 10, 2024, 12:19pm

Hello,

Communication should be working with host rut.teltonika.lt on port 5000. This information can be found in /etc/config/rut_fota

2024-04-09-10-45-01-192.168.1.1

Best regards,
Marijus

florian.pirnbacher · April 10, 2024, 12:36pm

Hi Marijus,
thanks for information.
In the meantime I built up a test-system. I have upgraded a router RUT241 with modem model SLM750-VE to modem firmware SLM750-V_4.57.20_EQ101 (must be the newest?) → same connection failure every hour.

Kind regards,
Florian

florian.pirnbacher · April 16, 2024, 7:11am

Hello Marijus,
now I have tested the router with SIM card from another carrier, with public APN. The connection problem is still present!
Firmware version: RUT2M_R_00.07.06.3
Internal modem firmware version: SLM750-V_4.0.12_EQ101

I will do another test with newest available firmware (RUT2M_R_00.07.06.10).

Kind regards,
Florian

system · April 23, 2024, 7:41am

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