RUT50x - modem keeps disconnecting - Implicitly detached

Hi, I have a problem with RUT50X. Cellular connection disconnects every 15-16 minutes (and then reconnects within 8 seconds)

I see in the log that there is always an event that is called “daemon.info mobifd: [gsm.modem0] Network notification received “Implicitly detached”” before each disconnect.

Sun Jul 7 16:29:13 2024 daemon.info mobifd: [gsm.modem0] Network notification received “Implicitly detached”
Sun Jul 7 16:29:28 2024 daemon.notice netifd: mob1s1a1 (14930): Mobile connection lost!
Sun Jul 7 16:29:28 2024 daemon.notice netifd: Interface ‘mob1s1a1’ has lost the connection
Sun Jul 7 16:29:28 2024 daemon.notice netifd: Network device ‘wwan0’ link is down
Sun Jul 7 16:29:28 2024 daemon.notice netifd: mob1s1a1 (17219): Stopping network mob1s1a1
Sun Jul 7 16:29:28 2024 daemon.notice netifd: mob1s1a1 (17219): Stopping network on /dev/cdc-wdm0!

SIM card is working well / without any issue in Huawei LTE modem / delivered originally by T-Mobile.

How can i resolve it? Could you give me further details?

Additional info:

  • mobile provider is T-Mobile CZ
  • Firmware version RUTX_R_00.07.07.3
  • Internal modem firmware version RG501QEUAAR12A08M4G_04.200.04.200
  • Kernel version 5.10.210

Best Regards, Karel

Someone far more knowledgeable will reply i’m sure, my initial thoughts are that t-Mobile may not be happy about the SIM being used in another device other than the one they supplied you with, possibly maybe!

I do know that some fibre / landline internet service providers restrict service specifically to the provided router. I’d start by contacting t-mobile and to see if they can offer any help.

Hello,

Experiencing an 8-second disconnection every 15-16 minutes is quite specific. According to the log:

Sun Jul 7 16:29:13 2024 daemon.info mobifd: [gsm.modem0] Network notification received “Implicitly detached”

This indicates that the disconnection was not initiated by the device itself but rather by the carrier or more precisely the MME. Please contact your mobile carrier regarding this issue. The scenario described by @akwe-xavante, or something similar, is quite plausible, especially with large carriers like T-Mobile.

Best regards,