GL-E5800 (Mudi 7) - Multiple cellular issues

GL-E5800 (Mudi 7) — cellular session issues, raw log captures

Device: GL-E5800, firmware 4.8.5, Quectel RG650V-EU
QRM650VEU00ADR02A04G8G_OCPU_RGH_01.005.01.005
Package: gl-sdk4-cellular git-2026.156.24582-f1aa5a0-1
(gl-sdk4-cellular_git-V4.9_disconnect_test.ipk installed)
SIM: Free Mobile FR (208 15), roaming Austria, +COPS: 0,0,"3 AT",7 (232 05)
APN free. Current config: ip_type=IP (IPv4-only), default MTU, no band mask.
All excerpts are verbatim from /etc/sys_log.


Issue 1 — Network periodically deactivates the data session (ESM cause 36)

What we face: the internet connection drops every ~10–30 minutes (bursts down
to 2–4 minutes apart), whether idle or mid-download. Each event assigns a new WAN
IP, so all TCP/VPN sessions die. VoLTE/IMS stays up. With the test IPK the router
recovers in ~40–55 s; the network refuses the first re-activation attempts for
~35 s of that.

Observations:

Deactivation with re-activation retries (session ~20 min old, light traffic):

Wed Aug  5 23:32:26 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=0 CallendCode=0) cb_msg.wwan_status:0x0
Wed Aug  5 23:32:26 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=6 CallendCode=36) cb_msg.wwan_status:0x6
Wed Aug  5 23:32:42 2026 user.info Diag_Lib[12932]: (cm.c:8743) Executing dial disconnection, initiated by PREPARE_DIAL (bus: cpu, slot: 1 interface:modem_cpu update_status:0 dial_status_flag:0)
Wed Aug  5 23:32:43 2026 user.info Diag_Lib[12932]: (cm.c:8619) Executing dial connect, initiated by INTERFACE OFFLINE (bus: cpu, slot: 1 interface: modem_cpu)
Wed Aug  5 23:32:52 2026 user.info Diag_Lib[12932]: (network.c:2900) get_network_info failed, bus=cpu slot=1
Wed Aug  5 23:33:00 2026 user.info Diag_Lib[12932]: (cm.c:3590) Failed to activate pdp state to module (retry 1/3)
Wed Aug  5 23:33:12 2026 user.info Diag_Lib[12932]: (network.c:2900) get_network_info failed, bus=cpu slot=1
Wed Aug  5 23:33:17 2026 user.info Diag_Lib[12932]: (cm.c:3590) Failed to activate pdp state to module (retry 2/3)
Wed Aug  5 23:33:19 2026 user.info Diag_Lib[12932]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.158.231.97 ctx_ipv6:

AT+CEER queried after this event:

+CEER: Network failure

Deactivation during an active multi-GB download (session age 12 min):

Wed Aug  5 23:12:06 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=0 CallendCode=0) cb_msg.wwan_status:0x0
Wed Aug  5 23:12:06 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=6 CallendCode=36) cb_msg.wwan_status:0x6
Wed Aug  5 23:12:06 2026 daemon.info gl-repeater[10581]: (repeater.lua:2177) interface modem_cpu down
Wed Aug  5 23:12:06 2026 daemon.info gl-repeater[10581]: (repeater.lua:1849) switch in 3 seconds...
Wed Aug  5 23:12:22 2026 user.info Diag_Lib[12932]: (cm.c:8743) Executing dial disconnection, initiated by PREPARE_DIAL (bus: cpu, slot: 1 interface:modem_cpu update_status:0 dial_status_flag:0)
Wed Aug  5 23:12:22 2026 user.info Diag_Lib[5258]: (cm.c:5753) disconnect by qmap start
Wed Aug  5 23:12:22 2026 user.info Diag_Lib[5258]: (cm.c:5787) disconnected by qmap end

Burst — three events in five minutes:

Thu Aug  6 00:00:38 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=6 CallendCode=36) cb_msg.wwan_status:0x6
Thu Aug  6 00:00:55 2026 user.info Diag_Lib[12932]: (cm.c:8619) Executing dial connect, initiated by INTERFACE OFFLINE (bus: cpu, slot: 1 interface: modem_cpu)
Thu Aug  6 00:01:12 2026 user.info Diag_Lib[12932]: (cm.c:3590) Failed to activate pdp state to module (retry 1/3)
Thu Aug  6 00:01:29 2026 user.info Diag_Lib[12932]: (cm.c:3590) Failed to activate pdp state to module (retry 2/3)
Thu Aug  6 00:01:31 2026 user.info Diag_Lib[12932]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.29.41.121 ctx_ipv6:
Thu Aug  6 00:03:26 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=3 CallendCode=1026) cb_msg.wwan_status:0x6
Thu Aug  6 00:03:44 2026 user.info Diag_Lib[12932]: (cm.c:8619) Executing dial connect, initiated by INTERFACE OFFLINE (bus: cpu, slot: 1 interface: modem_cpu)
Thu Aug  6 00:03:53 2026 user.info Diag_Lib[12932]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.158.231.208 ctx_ipv6:
Thu Aug  6 00:04:37 2026 user.info Diag_Lib[12932]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=6 CallendCode=36) cb_msg.wwan_status:0x6
Thu Aug  6 00:04:54 2026 user.info Diag_Lib[12932]: (cm.c:8619) Executing dial connect, initiated by INTERFACE OFFLINE (bus: cpu, slot: 1 interface: modem_cpu)
Thu Aug  6 00:05:19 2026 user.info Diag_Lib[12932]: (cm.c:3590) Failed to activate pdp state to module (retry 1/3)
Thu Aug  6 00:05:37 2026 user.info Diag_Lib[12932]: (cm.c:3590) Failed to activate pdp state to module (retry 2/3)
Thu Aug  6 00:05:39 2026 user.info Diag_Lib[12932]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.29.106.226 ctx_ipv6:

PDN state across events (AT queries, before → after — same values except cid 1):

+CGPADDR: 1,"10.61.215.211"        <- changes at every event
+CGPADDR: 2,"253.222.0.0.1.31.108.242.0.0.0.0.181.22.201.105"   <- unchanged across events
+CGPADDR: 3,"0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"
+CEREG: 0,5                        <- unchanged across events
+CGCONTRDP: 1,5,"free","10.95.154.208",,"212.27.40.190","212.27.40.191"
+CGACT: 1,1
+CGACT: 2,1
+CGACT: 3,0

Radio at event time (15 s sampler):

+QENG: "servingcell","NOCONN","LTE","FDD",232,05,1DDDD64,418,500,1,5,5,27AE,-84,-13,-51,16,6,60,-
+QCAINFO: "PCC",500,100,"LTE BAND 1",5,418,-84,-10,-54,12
+QCAINFO: "SCC",1525,75,"LTE BAND 3",1,388,-93,-7,-76,14,1,75,19525
+QTEMP: "mdmss-0","37"  (all sensors 27–40 °C at all events)

CallendType=6 CallendCode=36 lines per day (v4/v6 pairs counted twice):

Jun 3: 5   Jul 28: 24   Jul 29: 10   Jul 30: 35   Jul 31: 24
Aug 1: 23  Aug 2: 22    Aug 3: 75    Aug 4: 11    Aug 5: 64

Jun 3 events occurred on home network 208 15 (France). Hourly distribution peaks
14:00–23:00 every day; near zero 01:00–09:00.


Issue 2 — IPV4V6 dial while roaming: IPv6 never granted, cm re-dials in a loop

What we face: with APN IP type IPV4V6, every dial while roaming succeeds
for IPv4 but gets no IPv6 context; the connection manager then tears the working
IPv4 session down and re-dials on an ~80 s cycle, escalating to forced radio
re-registration. Switching the APN to IPv4-only stops the loop entirely.

Observations:

Roaming — all sampled dual-stack dials return empty ctx_ipv6::

Wed Aug  5 17:46:40 2026 user.info Diag_Lib[14285]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.47.25.57 ctx_ipv6:
Wed Aug  5 17:57:33 2026 user.info Diag_Lib[14285]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.29.118.192 ctx_ipv6:
Wed Aug  5 18:14:06 2026 user.info Diag_Lib[14285]: (cm.c:8012) Dial success with  APN: free ctx_ipv4:10.31.141.17 ctx_ipv6:

Home network (208 15, France, June 3) — the same dual-stack dial DID receive an
IPv6 context:

Wed Jun  3 00:01:26 2026 ... (cm.c:3827) Dial success with MCC:208 MNC:15 APN: free.re CID:1 IP_type :IPV4V6 ctx_ipv4:10.111.40.205 ctx_ipv6:42.13.228.135.23.127.60.164.0.0.0.0.55.179.245.21
Wed Jun  3 06:02:26 2026 ... (cm.c:3827) Dial success with MCC:208 MNC:15 APN: free CID:1 IP_type :IPV4V6 ctx_ipv4:10.63.95.106 ctx_ipv6:42.13.228.135.35.79.63.103.0.0.0.0.55.192.64.64

Post-dial failure codes in the roaming + IPV4V6 configuration (Aug 5 pre-reboot
counts: 27 × code 210, 32 × type 3/2000):

Tue Jul 28 12:18:24 2026 user.info Diag_Lib[12785]: (cm.c:4069) wwan handle:1 sub_id:0 (CallendType=2 CallendCode=210) cb_msg.wwan_status:0x8
Wed Jul 29 03:26:00 2026 user.info Diag_Lib[14431]: (cm.c:5493) wwan handle:1 sub_id:0 (CallendType=6 CallendCode=50) cb_msg.wwan_status:0x8

(ESM cause 50 = "PDN type IPv4 only allowed".) Escalation:

Wed Aug  5 21:30:51 2026 user.info Diag_Lib[14285]: (cm.c:7458) Start force re-register network(CFUN=4 -> CFUN=1)...

After switching to ip_type=IP + reboot at 21:51: code 210 count 27 → 0,
type 3/2000 count 32 → 1, forced CFUN re-registrations 2 → 0. The Issue 1
deactivations continued unchanged.


Issue 3 — Manual Cellular MTU (1360) kills the session under sustained transfer

What we face: with a manual MTU of 1360 set in the Cellular settings, every
sustained download died within 30–105 s. With MTU on default, multi-GB transfers
run with only the Issue 1 periodic deactivations.

Observations:

With network.modem_cpu.mtu='1360' — download tests run ON the router
(curl -o /dev/null, single stream, ipv4.download.thinkbroadband.com):

run 1: full rate,    died t=73 s,  390,572,443 bytes   (event 22:36:08)
run 2: full rate,    died t=30 s,  101,402,419 bytes   (event 22:40:38)
run 3: 500 KB/s cap, died t=105 s,  55,354,279 bytes   (event 22:44:59)

A client game update through the router died at ~100 MB under the same config.

After removing the override (default MTU, reboot at ~23:00): the same game
update transferred ~3 GB; the only deactivations in that period were the Issue 1
periodic ones (23:12:06, 23:32:26), not correlated with transfer start. Reboots
alone (21:50, 22:19) had not changed the under-load behaviour.


Issue 4 — After rapid deactivation/redial churn, the modem stops responding

What we face: during a phase of rapid session deaths (Issue 3 config, client
download retrying), the router could not reconnect for 6 minutes and finally the
modem stopped answering; only a power cycle recovered it.

Observations:

After the 22:54:11 deactivation, seven dial attempts over six minutes produced
no Dial success and no call-end codes, then:

Wed Aug  5 22:59:58 2026 user.info Diag_Lib[12932]: (cm.c:3497) Failed to get cell info form module (retry 1/30) ret[-1]
Wed Aug  5 22:59:59 2026 user.info Diag_Lib[12932]: (cm.c:3497) Failed to get cell info form module (retry 2/30) ret[-1]

Device was power-cycled at ~23:00 to recover.

@Cathy Any of them fixed in 4.10 beta 2? Is it worth testing ?

1 Like

I’ve updated 4.10 beta2 at least IPv6 loop seems gone.

The disconnection seems also gone but need more time to be sure.

Hello fab, thanks for your feedback.

The v4.10 beta2 contains fixes for issue 1 and issue4.

As for issue 2, may I ask if you tested with two SIM cards—one roaming card (plmn: 203 05) and one local sim card(plmn:208 15 )? IP address is assigned by the operator. If you are testing two sim cards, the operator may allocate different IP addresses for different types of cards, which may be normal behavior. If log entry "force re-register network" appears frequently, could you please send the full sys_log with us for further analysis?

Iseue 3: as far as I know, improper MTU setting may affect the file download. In general, we recommend using the default values.

@Cathy

Hello,

Issue 2: no same SIM card. The issue is that with V4V6 when the provider do not return v6 mudi must keep the v4 and stop. In my case it was causing loop.

Mtu issue : its an issue as there is no reason that settings an MTU on the interface lower than carrier disconnect the session on download.