RUTX50 problems with mobile connection

I have a problem with mobile connection. As soon as I start a speed test via the laptop connected to the LAN port, the mobile radio connection is disconnected. Below are the last entries from the logfile:

1132 Tue Apr 22 17:51:50 2025 daemon.notice netifd: Interface 'mob1s1a1' is now down
1133 Tue Apr 22 17:51:50 2025 daemon.notice netifd: Interface 'mob1s1a1' is setting up now
1134 Tue Apr 22 17:51:50 2025 daemon.notice netifd: mob1s1a1 (18604): wwan[18604] Using wwan usb device on bus 2-1
1135 Tue Apr 22 17:51:50 2025 daemon.notice netifd: mob1s1a1 (18604): wwan[18604] Using proto:qmapv5 device:/dev/cdc-wdm0 iface:wwan0 desc:Quectel RG50X
1136 Tue Apr 22 17:51:51 2025 daemon.info dnsmasq[3143]: read /etc/hosts - 12 names
1137 Tue Apr 22 17:51:51 2025 daemon.info dnsmasq[3143]: read /tmp/hosts/dhcp.cfg01411c - 4 names
1138 Tue Apr 22 17:51:51 2025 daemon.info dnsmasq-dhcp[3143]: read /etc/ethers - 0 addresses
1139 Tue Apr 22 17:51:56 2025 user.notice qmux: mob1s1a1 teardown successful
1140 Tue Apr 22 17:51:57 2025 daemon.notice netifd: mob1s1a1 (18604): Calculated qmimux ifname: qmimux0
1141 Tue Apr 22 17:51:57 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 10000 --set-autoconnect disabled
1142 Tue Apr 22 17:51:57 2025 daemon.notice netifd: mob1s1a1 (18604): Informing driver of raw-ip for wwan0 ..
1143 Tue Apr 22 17:51:57 2025 user.notice root: uqmi -d /dev/cdc-wdm0 --timeout 6000 --wda-set-data-format --qos-format 0 --link-layer-protocol raw-ip --endpoint-type hsusb --endpoint-iface-number 4 --ul-protocol qmapv5 --dl-protocol qmapv5 --ul-max-datagrams 11 --ul-datagram-max-size 8192 --dl-max-datagrams 62 --dl-datagram-max-size 31744 --dl-min-padding 0
1144 Tue Apr 22 17:51:58 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,14 --release-client-id wds --modify-profile 3gpp,1 --profile-name 1 --roaming-disallowed-flag no
1145 Tue Apr 22 17:52:29 2025 daemon.notice netifd: mob1s1a1 (18604): Network registration failed
1146 Tue Apr 22 17:52:29 2025 daemon.notice netifd: mob1s1a1 (18604): 2-1 mob1s1a1 reloading mobifd
1147 Tue Apr 22 17:52:29 2025 daemon.info mobifd: [gsm.modem0] Config reload initiated
1148 Tue Apr 22 17:52:29 2025 daemon.notice netifd: mob1s1a1 (19442): Stopping network mob1s1a1
1149 Tue Apr 22 17:52:29 2025 daemon.info mobifd: [gsm.modem0] SIM is ready
1150 Tue Apr 22 17:52:29 2025 daemon.notice netifd: mob1s1a1 (19442): Command failed: Not found
1151 Tue Apr 22 17:52:29 2025 daemon.notice netifd: mob1s1a1 (19442): Command failed: Not found
1152 Tue Apr 22 17:52:30 2025 daemon.err mobifd: [gsm.modem0] GSM error in "mb_check_sms_storage:564" (Failed to parse response), gsmd_method_id: "63"
1153 Tue Apr 22 17:52:30 2025 daemon.err mobifd: [gsm.modem0] Failed to get SMS storage
1154 Tue Apr 22 17:52:30 2025 daemon.notice netifd: mob1s1a1 (19442): Command failed: Permission denied
1155 Tue Apr 22 17:52:30 2025 daemon.notice netifd: Interface 'mob1s1a1' is now down
1156 Tue Apr 22 17:52:31 2025 daemon.info dnsmasq[3143]: read /etc/hosts - 12 names
1157 Tue Apr 22 17:52:31 2025 daemon.info dnsmasq[3143]: read /tmp/hosts/dhcp.cfg01411c - 4 names
1158 Tue Apr 22 17:52:31 2025 daemon.info dnsmasq-dhcp[3143]: read /etc/ethers - 0 addresses
1159 Tue Apr 22 17:52:31 2025 kern.info Mobile data disconnected (internal modem)
1160 Tue Apr 22 17:52:33 2025 daemon.err mobifd: [gsm.modem0] Init 'sms_storage_check' failed. Retrying
1161 Tue Apr 22 17:52:34 2025 daemon.info mobifd: [gsm.modem0] Modem settings init completed
1162 Tue Apr 22 17:52:34 2025 daemon.info mobifd: [gsm.modem0] Starting connection setup
1163 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with "15s" of timeout
1164 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] Connected to operator "26202"
1165 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] -CFUN- Functionality: "Full"
1166 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] -COPS- Mode: "Auto", operator: "26202"
1167 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] -CREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "43554", cell ID: "7846421", technology: "E-UTRAN-NR"
1168 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] -CGREG- Mode: "Enabled (with location information)", status: "Not registered", LAC: "", cell ID: "", technology: "Unknown"
1169 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] -CEREG- Mode: "Enabled (with location information)", status: "Registered, home", LAC: "", cell ID: "7846421", technology: "E-UTRAN-NR"
1170 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] -C5GREG- Mode: "Enabled (with location information)", status: "Not registered", LAC: "", cell ID: "", technology: "Unknown"
1171 Tue Apr 22 17:52:35 2025 daemon.info mobifd: [gsm.modem0] IP address on PDP context "1": "100.77.77.32"
1172 Tue Apr 22 17:52:35 2025 daemon.notice netifd: Interface 'mob1s1a1' is setting up now
1173 Tue Apr 22 17:52:35 2025 daemon.notice netifd: mob1s1a1 (19855): wwan[19855] Using wwan usb device on bus 2-1
1174 Tue Apr 22 17:52:35 2025 daemon.notice netifd: mob1s1a1 (19855): wwan[19855] Using proto:qmapv5 device:/dev/cdc-wdm0 iface:wwan0 desc:Quectel RG50X
1175 Tue Apr 22 17:52:36 2025 user.notice qmux: mob1s1a1 teardown successful
1176 Tue Apr 22 17:52:38 2025 daemon.notice netifd: mob1s1a1 (19855): Calculated qmimux ifname: qmimux0
1177 Tue Apr 22 17:52:38 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 10000 --set-autoconnect disabled
1178 Tue Apr 22 17:52:38 2025 daemon.notice netifd: mob1s1a1 (19855): Informing driver of raw-ip for wwan0 ..
1179 Tue Apr 22 17:52:39 2025 user.notice root: uqmi -d /dev/cdc-wdm0 --timeout 6000 --wda-set-data-format --qos-format 0 --link-layer-protocol raw-ip --endpoint-type hsusb --endpoint-iface-number 4 --ul-protocol qmapv5 --dl-protocol qmapv5 --ul-max-datagrams 11 --ul-datagram-max-size 8192 --dl-max-datagrams 62 --dl-datagram-max-size 31744 --dl-min-padding 0
1180 Tue Apr 22 17:52:39 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,14 --release-client-id wds --modify-profile 3gpp,1 --profile-name 1 --roaming-disallowed-flag no
1181 Tue Apr 22 17:52:39 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --get-client-id wds
1182 Tue Apr 22 17:52:39 2025 daemon.notice netifd: mob1s1a1 (19855): 14
1183 Tue Apr 22 17:52:39 2025 daemon.notice netifd: mob1s1a1 (19855): cid4: 14
1184 Tue Apr 22 17:52:39 2025 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,14
1185 Tue Apr 22 17:52:39 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-ip-family ipv4 --set-client-id wds,14
1186 Tue Apr 22 17:52:39 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,14 --start-network --profile 1 --ip-family ipv4
1187 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): pdh4: 1381204992
1188 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 1381204992
1189 Tue Apr 22 17:52:40 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --get-client-id wds
1190 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 15
1191 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): cid6: 15
1192 Tue Apr 22 17:52:40 2025 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,15
1193 Tue Apr 22 17:52:40 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-ip-family ipv6 --set-client-id wds,15
1194 Tue Apr 22 17:52:40 2025 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 6000 --set-client-id wds,15 --start-network --ip-family ipv6 --profile 1
1195 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): pdh6: 1380917456
1196 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 1380917456
1197 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): Setting up qmimux0
1198 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): Setting configured MTU: 1500 on qmimux0
1199 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1' is now up
1200 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Network device 'wwan0' link is up
1201 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): Setting up qmimux0 V4 DCHP
1202 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_4' is enabled
1203 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Network device 'qmimux0' link is up
1204 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_4' has link connectivity
1205 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_4' is setting up now
1206 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): Setting up qmimux0 V6 static
1207 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): {
1208 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	"pdp-type": "ipv4v6",
1209 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	"ip-family": "ipv6",
1210 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	"mtu": 1500,
1211 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	"ipv4": {
1212 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855):
1213 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	},
1214 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	"ipv6": {
1215 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 		"ip": "2a00:20:b2d7:97a3:bce3:c0f0:35d5:ecd",
1216 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 		"ip-prefix-length": 64,
1217 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 		"gateway": "2a00:20:b2d7:97a3:2c95:e55a:7659:ace4",
1218 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 		"gw-prefix-length": 64,
1219 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 		"dns1": "2a01:860:0:300::53",
1220 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 		"dns2": "2a01:860:0:300::153"
1221 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	},
1222 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	"domain-names": {
1223 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855):
1224 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): 	}
1225 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): }
1226 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1 (19855): uci: Entry not found
1227 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_6' is enabled
1228 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_6' is setting up now
1229 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_6' is now up
1230 Tue Apr 22 17:52:40 2025 daemon.notice netifd: Interface 'mob1s1a1_6' has link connectivity
1231 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: reading /tmp/resolv.conf.d/resolv.conf.auto
1232 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using nameserver 2a01:860:0:300::53#53
1233 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using nameserver 2a01:860:0:300::153#53
1234 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for test
1235 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for onion
1236 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for localhost
1237 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for local
1238 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for invalid
1239 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for bind
1240 Tue Apr 22 17:52:40 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for lan
1241 Tue Apr 22 17:52:40 2025 daemon.notice netifd: mob1s1a1_4 (20342): udhcpc: started, v1.34.1
1242 Tue Apr 22 17:52:41 2025 daemon.notice netifd: mob1s1a1_4 (20342): udhcpc: broadcasting discover
1243 Tue Apr 22 17:52:41 2025 daemon.notice netifd: mob1s1a1_4 (20342): udhcpc: broadcasting select for 100.77.77.32, server 100.77.77.33
1244 Tue Apr 22 17:52:41 2025 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (wwan0)
1245 Tue Apr 22 17:52:41 2025 daemon.notice netifd: mob1s1a1_4 (20342): udhcpc: lease of 100.77.77.32 obtained from 100.77.77.33, lease time 7200
1246 Tue Apr 22 17:52:41 2025 daemon.notice netifd: Interface 'mob1s1a1_4' is now up
1247 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: reading /tmp/resolv.conf.d/resolv.conf.auto
1248 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using nameserver 139.7.30.125#53
1249 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using nameserver 139.7.30.126#53
1250 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using nameserver 2a01:860:0:300::53#53
1251 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using nameserver 2a01:860:0:300::153#53
1252 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for test
1253 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for onion
1254 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for localhost
1255 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for local
1256 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for invalid
1257 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for bind
1258 Tue Apr 22 17:52:41 2025 daemon.info dnsmasq[3143]: using only locally-known addresses for lan
1259 Tue Apr 22 17:52:43 2025 daemon.info dnsmasq[3143]: read /etc/hosts - 12 names
1260 Tue Apr 22 17:52:43 2025 daemon.info dnsmasq[3143]: read /tmp/hosts/dhcp.cfg01411c - 4 names
1261 Tue Apr 22 17:52:43 2025 daemon.info dnsmasq-dhcp[3143]: read /etc/ethers - 0 addresses
1262 Tue Apr 22 17:52:43 2025 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_6 (qmimux0)
1263 Tue Apr 22 17:52:44 2025 kern.info Mobile data connected (internal modem)
1264 Tue Apr 22 17:52:44 2025 kern.info Joined 5G-NSA network (internal modem)
1265 Tue Apr 22 17:52:44 2025 kern.info Connected to 26202 operator (internal modem)
1266 Tue Apr 22 17:52:45 2025 kern.notice DNS resolution restored
1267 Tue Apr 22 17:52:45 2025 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (qmimux0)
1268 Tue Apr 22 17:52:46 2025 daemon.info mobifd: Connection setup completed for 'mob1s1a1'
1269 Tue Apr 22 17:52:46 2025 daemon.info mobifd: Connection setup completed for modem: 'gsm.modem0'
1270 Tue Apr 22 17:52:46 2025 daemon.info mobifd: Connection setup completed for 'mob1s1a1'
1271 Tue Apr 22 17:52:46 2025 daemon.info mobifd: Connection setup completed for modem: 'gsm.modem0'
1272 Tue Apr 22 17:52:47 2025 daemon.info dnsmasq[3143]: read /etc/hosts - 12 names
1273 Tue Apr 22 17:52:47 2025 daemon.info dnsmasq[3143]: read /tmp/hosts/dhcp.cfg01411c - 4 names
1274 Tue Apr 22 17:52:47 2025 daemon.info dnsmasq-dhcp[3143]: read /etc/ethers - 0 addresses
1275 Tue Apr 22 17:52:48 2025 daemon.err rms_mqtt[6997]: Connected to remote host
1276 Tue Apr 22 17:52:49 2025 daemon.err rms_mqtt[6997]: Failed to connect with authentication keys
1277 Tue Apr 22 17:53:45 2025 kern.notice IPv4 connectivity restored
1278 Tue Apr 22 17:53:45 2025 kern.notice IPv6 connectivity restored

What is striking, the SIM PIN is saved and yet the SIM is displayed as locked.

Good afternoon,

Seems like the device is either not registering the Pin code, or it is incorrect.

Please reset the device via bootloader method : https://wiki.teltonika-networks.com/view/RUTX50_Device_Recovery_Options#Bootloader_menu

Firmware : https://wiki.teltonika-networks.com/view/RUTX50_Firmware_Downloads

After that, please in WEBUI Network → Mobile → General input the Pin code, and don’t forget to press save and apply.

Lastly, try a different Sim in this device, and this Sim in another device and see if it operates differently.

Regards,
Arturas

After a while unlock is no longer displayed and it has automatically unlocked again. So he can’t forget the PIN.