[BUG][LTE][Chateau 5G R17 ax] Slow LTE unless Torch is enabled

RouterOS General
1

Hi,

I’m having some LTE issues with my new Chateau 5G R17 ax (modem RG650E-EU). I have great reception, but I’m getting terribly slow speeds (<100kbps) unless I start a WinBox torch session on the LTE interface.

I’m running routeros and wifi-qcom version 7.21rc4from Dec/29/2025 13:47:22. My LTE/5G modem is on the latest firmware.

Without torch running

[admin@MikroTik] > /interface/lte/monitor lte1 once
            status: running                               
      manufacturer: Quectel                               
             model: RG650E-EU                             
          revision: RG650EEU00AAR01A04G8G                 
  current-operator: [REDACTED]                                 
    current-cellid: [REDACTED]                                
            enb-id: [REDACTED]                                  
         sector-id: [REDACTED]                                      
        phy-cellid: [REDACTED]                                     
        data-class: LTE                                   
    session-uptime: 7m48s                                 
              imei: [REDACTED]                       
              imsi: [REDACTED]                         
             iccid: [REDACTED]                    
      primary-band: B7@20Mhz earfcn: [REDACTED]  
           ca-band: B1@20Mhz earfcn: [REDACTED]  
                    B7@20Mhz earfcn: [REDACTED]  
                    B20@10Mhz earfcn: [REDACTED]  
        ul-ca-band: B7@20Mhz earfcn: [REDACTED]  
     dl-modulation: qpsk                                  
               cqi: 13                                    
                ri: 2                                     
               mcs: 0

With torch running

[admin@MikroTik] > /interface/lte/monitor lte1 once
            status: running                              
      manufacturer: Quectel                              
             model: RG650E-EU                            
          revision: RG650EEU00AAR01A04G8G                
  current-operator: [REDACTED]                                 
    current-cellid: [REDACTED]                             
            enb-id: [REDACTED]                                  
         sector-id: [REDACTED]                                    
        phy-cellid: [REDACTED]                                     
        data-class: LTE                                  
    session-uptime: 1m12s                                
              imei: [REDACTED]                         
              imsi: [REDACTED]                         
             iccid: [REDACTED]                    
      primary-band: B1@20Mhz earfcn: [REDACTED]   
           ca-band: B7@20Mhz earfcn: [REDACTED]   
                    B7@20Mhz earfcn: [REDACTED]   
        ul-ca-band: B7@20Mhz earfcn: [REDACTED]   
     dl-modulation: 64qam                                
               cqi: 12                                   
                ri: 2                                    
               mcs: 11                                   
              rssi: -64dBm                               
              rsrp: -92dBm                               
              rsrq: -9dB                                 
              sinr: 19dB

Debug logs

 2026-01-06 19:13:08 system,info device changed by winbox-3.43/tcp-msg(winbox):admin@192.168.88.254 (/interface set lte1 disabled=no mtu=1500 name=lte1; /interfac
e lte set [ find ] allow-roaming=yes apn-profiles=[REDACTED] band="" disabled=no mtu=1500 name=lte1 network-mode=lte,5g nr-band=""; /queue interface set lte1)
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDS - STOP_NETWORK_IFACE
 2026-01-06 19:13:08 lte,error lte1 qmi: dropped reply
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDS - [notify] PKT_SRVC_STATUS
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> DMS - SET_OPERATING_MODE
 2026-01-06 19:13:08 lte,debug lte1 qmi: state: radio off => idle
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< UIM - ATTR_REQ
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDS - [notify] LTE_ATTACH_PARAMS
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> UIM - ATTR_REQ
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< UIM - SLOTS_STATUS
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> NAS - [notify] SYS_INFO_IND
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> UIM - SLOTS_STATUS
 2026-01-06 19:13:08 lte,debug lte1 qmi: slot #0 state: empty
 2026-01-06 19:13:08 lte,debug lte1 qmi: slot #1 state: esim without profile
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< UIM - GET_CARD_STATUS
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> UIM - GET_CARD_STATUS
 2026-01-06 19:13:08 lte,debug lte1 qmi: UIM state: 1 APP state: 7, type: 2
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< UIM - READ_TRANSPARENT
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> UIM - READ_TRANSPARENT
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< UIM - READ_TRANSPARENT
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> UIM - READ_TRANSPARENT
 2026-01-06 19:13:08 lte,debug lte1 qmi: state: idle => SIM ready
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< WDA - SET_DATA_FORMAT
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDA - SET_DATA_FORMAT
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< WDA - SET_LOOPBACK_STATE
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDA - SET_LOOPBACK_STATE
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< WDS - MODIFY_PROFILE_SETTINGS
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDS - MODIFY_PROFILE_SETTINGS
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< WDS - SET_LTE_ATTACH_PDN_LIST
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> WDS - SET_LTE_ATTACH_PDN_LIST
 2026-01-06 19:13:08 lte,debug lte1 qmi: set system preference, operator: [auto]
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< NAS - SET_SYSTEM_SELECTION_PREF
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> NAS - SET_SYSTEM_SELECTION_PREF
 2026-01-06 19:13:08 lte,debug lte1 qmi: set radio state: online
 2026-01-06 19:13:08 lte,debug lte1 qmi: <<< DMS - SET_OPERATING_MODE
 2026-01-06 19:13:08 lte,debug lte1 qmi: >>> DMS - SET_OPERATING_MODE
 2026-01-06 19:13:08 lte,debug lte1 qmi: state: SIM ready => online
 2026-01-06 19:13:13 system,info,account user admin logged in from 192.168.88.254 via winbox
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:19 lte,debug lte1 qmi: state: online => searching
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> NAS - [notify] SYS_INFO_IND
 2026-01-06 19:13:19 lte,debug lte1 qmi: state: searching => deregistered
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:19 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:20 lte,debug lte1 qmi: state: deregistered => registered
 2026-01-06 19:13:20 lte,debug lte1 qmi: state: registered => packet service attached
 2026-01-06 19:13:20 lte,debug lte1 qmi: state: packet service attached => connecting
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] SYS_INFO_IND
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] CURRENT_PLMN_NAME
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] SYS_INFO_IND
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> WDS - [notify] LTE_ATTACH_PARAMS
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] OPERATOR_NAME_DATA
 2026-01-06 19:13:20 lte,debug lte1 qmi: >>> NAS - [notify] CURRENT_PLMN_NAME
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> DSD - [notify] SYSTEM_STATUS
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> NAS - [notify] SERVING_SYSTEM
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> NAS - [notify] SYS_INFO_IND
 2026-01-06 19:13:21 lte,debug lte1 qmi: <<< WDS - START_NETWORK_IFACE
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> WDS - START_NETWORK_IFACE
 2026-01-06 19:13:21 lte,debug lte1 qmi: state: connecting => connected
 2026-01-06 19:13:21 lte,debug lte1 qmi: state: connected => connecting
 2026-01-06 19:13:21 lte,debug lte1 qmi: >>> WDS - [notify] PKT_SRVC_STATUS
 2026-01-06 19:13:22 lte,debug lte1 qmi: <<< WDS - GET_RUNTIME_SETTINGS
 2026-01-06 19:13:22 lte,debug lte1 qmi: >>> WDS - GET_RUNTIME_SETTINGS
 2026-01-06 19:13:22 lte,info lte1 IPv4: 10.16.47.128, DNS: [REDACTED], MTU: 1500
 2026-01-06 19:13:22 lte,debug lte1 qmi: current apn: [REDACTED]
 2026-01-06 19:13:22 lte,debug lte1 qmi: state: connecting => connected
 2026-01-06 19:13:22 lte,debug lte1 qmi: state: connected => running
 2026-01-06 19:13:22 interface,info lte1 link up
 2026-01-06 19:23:03 system,info,account user admin logged in from 192.168.88.254 via winbox

I’m super happy about my unit except for this issue. Mikrotik is a great company and you folks make great sustainable products for a fair price. Thank you.

2

Hi,

showing the full configuration would help a lot.

3

Is there something specific you’d like to see? This smells like a firmware bug to me, but I’m not a hardware engineer. Here are some relevant config parameters. I removed all the boilerplate stuff as to not divulge too much about my internal network topology :slight_smile:

/interface ethernet switch set 0 cpu-flow-control=yes
/interface list add comment=defconf name=WAN
/interface list add comment=defconf name=LAN
/interface lte apn set [ find default=yes ] apn=[REDACTED] ip-type=ipv4 use-network-apn=no use-peer-dns=no
/interface lte apn add add-default-route=no apn=[REDACTED] ip-type=ipv4 name=[REDACTED] use-peer-dns=no
/interface lte set [ find default-name=lte1 ] allow-roaming=yes apn-profiles=[REDACTED] band="" network-mode=lte,5g nr-band=""
/queue type add fq-codel-ecn=no kind=fq-codel name=fq-codel-ethernet-default
/queue interface set ether1 queue=fq-codel-ethernet-default
/queue interface set ether2 queue=fq-codel-ethernet-default
/queue interface set ether3 queue=fq-codel-ethernet-default
/queue interface set ether4 queue=fq-codel-ethernet-default
/queue interface set ether5 queue=fq-codel-ethernet-default
/routing table add disabled=no fib name=rtab-1
/disk settings set auto-media-interface=bridge auto-media-sharing=yes auto-smb-sharing=yes
/ipv6 settings set disable-ipv6=yes
/interface list member add comment=defconf interface=bridge list=LAN
/interface list member add comment=defconf interface=lte1 list=WAN
/interface list member add interface=ether1 list=WAN
/interface list member add interface=bridge-foo list=LAN
/interface lte settings set sim-slot=esim
/ip route add disabled=no dst-address=0.0.0.0/0 gateway=lte1 routing-table=rtab-1

4

One of notable things which happen when torch gets started is that fast track gets disabled. So in vast majority of cases where "running torch solves performance problems" this means that firewall rules (which affect fasttrack) are not set correct (for a particular use case).

Therefore we are asking for (full) configuration ... because it's hard to tell where that error might be without seeing full config. By all means do anonymize configuration export (mask passwords, public IP address, serial number ... but don't mask private IP addresses or MAC addresses, these are not sensitive outside your own LAN).