Hello,
I installed an RUTX50 a few days ago. It has good signal strength but the internet continually drops out. I have tried updating the firmware and changing settings (such as 5g only etc) but the problem does not change. During gaming it drops out constantly and is unusable. I have downloaded a troubleshoot file but I don’t know where to send it.
Thanks in advance for any help.
Hello,
Troubleshoot files cannot be shared here, as this is a public forum.
A few things to check:
Make sure you are running the latest internal modem firmware. It can be updated in the same page as the device firmware;
Make sure you are using the included 18W PSU;
Try disabling 5G and check if the issue reappears;
One thing to note, is that most carriers are using 5G NSA setups, which require the device to be connected to 4G LTE network before it can connect to 5G. So in order to have 5G connection, the network type selector needs to be left on Auto or 4G + 5G.
Could you also share a screenshot of the signal parameters of the device? They can be found by navigating to Status → Network → Mobile. Make sure to blur IMEI, IMSI, and ICCID.
Finally, if the solutions mentioned above do not help, please wait for the issue to replicate, then navigate to System → Administration → Troubleshoot, open the system log window, and paste the last few minutes of logs in the next comment (make sure to remove any sensitive information!)
Best regards,
Hello,
I updated both the device and modem firmware. They are both now current. That made no difference as the problem occurred before and after the updates.
I am using the supplied PSU plugged in to 240v.
I was using the Auto all the time. When I changed to other settings I couldn’t get any connection. The connection shows as NSA when connected.
The signal parameters are:
CONNECTION
| Operator | YES OPTUS YES OPTUS |
|---|---|
| Operator state | Registered, home |
| Cell ID | 20340491 |
| Data connection state | Connected |
| Network type | 5G (NSA) |
DATA TRANSMISSION
| Carrier aggregation | Triple |
|---|---|
| Connected band | LTE B7 / LTE B1 / LTE B3 |
| Signal strength | -64 (Excellent) |
| RSRP | -97 (Fair to poor) / -100 (No signal) / -96 (Fair to poor) |
| RSRQ | -13 (Good) / -12 (Good) / -14 (Good) |
| SINR |
The logs for the time when I connected after the firmware updates and then had the failures are as follows:
Sun Sep 3 15:51:15 2023 daemon.info hostapd: wlan0: STA 7e:91:a9:0e:12:3b WPA: group key handshake completed (RSN)
Sun Sep 3 15:52:07 2023 kern.notice Port link state of port LAN1 changed to DOWN
Sun Sep 3 15:52:09 2023 kern.notice Port link state of port LAN1 changed to UP
Sun Sep 3 15:52:09 2023 kern.notice Port speed for port LAN1 changed to 1000 baseT
Sun Sep 3 15:52:10 2023 daemon.info dnsmasq-dhcp[3351]: DHCPREQUEST(br-lan) 192.168.1.216 04:92:26:bf:e4:7d
Sun Sep 3 15:52:10 2023 daemon.info dnsmasq-dhcp[3351]: DHCPACK(br-lan) 192.168.1.216 04:92:26:bf:e4:7d Brendan
Sun Sep 3 15:52:18 2023 kern.notice Port link state of port LAN1 changed to DOWN
Sun Sep 3 15:53:04 2023 kern.notice Port link state of port LAN1 changed to UP
Sun Sep 3 15:53:04 2023 kern.notice Port speed for port LAN1 changed to 1000 baseT
Sun Sep 3 15:53:05 2023 kern.notice Port link state of port LAN1 changed to DOWN
Sun Sep 3 15:53:07 2023 kern.notice Port link state of port LAN1 changed to UP
Sun Sep 3 15:53:07 2023 kern.notice Port speed for port LAN1 changed to 1000 baseT
Sun Sep 3 15:53:13 2023 kern.notice Port link state of port LAN1 changed to DOWN
Sun Sep 3 15:53:15 2023 kern.notice Port link state of port LAN1 changed to UP
Sun Sep 3 15:53:15 2023 kern.notice Port speed for port LAN1 changed to 1000 baseT
Sun Sep 3 15:54:11 2023 daemon.info dnsmasq-dhcp[3351]: DHCPDISCOVER(br-lan) 192.168.8.160 24:4b:fe:e1:10:57
Sun Sep 3 15:54:11 2023 daemon.info dnsmasq-dhcp[3351]: DHCPOFFER(br-lan) 192.168.1.209 24:4b:fe:e1:10:57
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPDISCOVER(br-lan) 74:83:c2:4d:a7:81
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPOFFER(br-lan) 192.168.1.228 74:83:c2:4d:a7:81
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPREQUEST(br-lan) 192.168.1.209 24:4b:fe:e1:10:57
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPACK(br-lan) 192.168.1.209 24:4b:fe:e1:10:57 DESKTOP-L6O3A3A
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPREQUEST(br-lan) 192.168.1.209 24:4b:fe:e1:10:57
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPACK(br-lan) 192.168.1.209 24:4b:fe:e1:10:57 DESKTOP-L6O3A3A
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPREQUEST(br-lan) 192.168.1.228 74:83:c2:4d:a7:81
Sun Sep 3 15:54:15 2023 daemon.info dnsmasq-dhcp[3351]: DHCPACK(br-lan) 192.168.1.228 74:83:c2:4d:a7:81 SWbas
Sun Sep 3 15:54:15 2023 kern.info Leased 192.168.1.209 IP address for client 24:4b:fe:e1:10:57 - DESKTOP-L6O3A3A in LAN
Sun Sep 3 15:54:15 2023 kern.info Leased 192.168.1.228 IP address for client 74:83:c2:4d:a7:81 - SWbas in LAN
Sun Sep 3 16:01:14 2023 daemon.info hostapd: wlan0: STA 7e:91:a9:0e:12:3b WPA: group key handshake completed (RSN)
Sun Sep 3 16:09:56 2023 kern.notice Port link state of port LAN1 changed to DOWN
Thanks.
Hello,
If the logs are truly from the time when the issue occured, then this is not related to the mobile connection, but rather to the connection between LAN1 port and the device connected to it. Could you check if the issue occurs with a different cable? A different port could also be tested.
When the issue occurs again, please check the status LEDs on the device, in particular - the LAN1 port status LEDs, and the mobile connection status LEDs.
Best regards,
This topic was automatically closed after 15 days. New replies are no longer allowed.