@Marvin_S 

hi, my nx600 is working in 3G/4G mode for 2 weeks without any crash. In the logs, I can see some exceptions :

2025-05-10 02:41:47 [3] LTE: Exception:item length too long(1026)

2025-05-10 02:41:52 [3] LTE: Exception:item length too long(1028)

However, these exceptions are without impact, the nx600 don't reboot and thé issue is not visible from a user point of view.

I will go back in 3G/4G/5G mode in order to catch thé logs and thé status page.

Have a Nice day

@Marvin_S 

Hi,

I have the log of the recurring issue of my nx600 when configured 3G/4G/5G.

12/05 11H57 : nx600 is configured from 3G/4G mode to 3G/4G/5G mode

2025-05-12 07:41:11 [5] LTE: Connected to the network!

2025-05-12 07:41:47 [3] LTE: Exception:item length too long(1026)

2025-05-12 07:41:52 [3] LTE: Exception:item length too long(1028)

2025-05-12 09:27:06 [5] LTE: Network type is LTE.

2025-05-12 09:27:16 [5] LTE: Network type is LTE PLUS.

2025-05-12 09:31:06 [5] LTE: Network type is LTE.

2025-05-12 09:31:16 [5] LTE: Network type is LTE PLUS.

2025-05-12 11:55:52 [5] Mesh: Success Add Client : MAC : F6:78:FA:A6:99:60

2025-05-12 11:55:52 [5] DHCPD: Recv DISCOVER from F6:78:FA:A6:99:60
2025-05-12 11:55:52 [5] DHCPD: Send OFFER with ip 192.168.0.8
2025-05-12 11:57:20 [5] LTE: Not registered, not currently searching!

2025-05-12 11:57:20 [5] LTE: Network type is NONE.

2025-05-12 11:57:20 [5] LTE: 4G/5G register state change: disconnect

2025-05-12 11:57:20 [5] LTE: network changed: 208,1->0,0

2025-05-12 11:57:26 [3] LTE: Exception:item length too long(1026)

2025-05-12 11:57:33 [5] LTE: Registered with a network!

2025-05-12 11:57:33 [5] LTE: Network type is NR.

2025-05-12 11:57:33 [5] LTE: network changed: 0,0->208,1

2025-05-12 11:57:36 [5] LTE: Start connecting to the network!

2025-05-12 11:57:38 [5] LTE: Fail to connect to the network, start autoconnect!

2025-05-12 11:57:40 [5] LTE: Connected to the network!

2025-05-12 11:58:40 [3] LTE: Exception:item length too long(1026)

2025-05-12 11:58:45 [3] LTE: Exception:item length too long(1030)

2025-05-12 11:58:55 [3] LTE: Exception:item length too long(1032)

15/05 03H12 : nx600 issue is occurring after 3 days in 3G/4G/5G mode (WIFi is OK, LAN is OK, GUI is OK, 3G/4G/5G is KO)

2025-05-15 03:12:22 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:12:27 [3] LTE: Exception:item length too long(1034)

2025-05-15 03:12:57 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:13:52 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:13:57 [3] LTE: Exception:item length too long(1034)

2025-05-15 03:14:27 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:15:30 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:15:35 [3] LTE: Exception:item length too long(1034)

2025-05-15 03:16:06 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:16:23 [5] LTE: Not registered, not currently searching!

2025-05-15 03:16:23 [5] LTE: Network type is NONE.

2025-05-15 03:16:23 [5] LTE: network changed: 208,1->0,0

2025-05-15 03:17:08 [3] LTE: Exception:GetMobileStatus fail

2025-05-15 03:17:13 [3] LTE: Exception:item length too long(1034)

15/05 05H52 : nx600 is rebooted from the GUI and is working correctly again 

2016-01-01 19:26:27 [6] LTE: p_str(p_len=30)=150,600,3600,21600,43200,86400, p_size=16

2016-01-01 19:26:27 [6] LTE: table[0]=150

2016-01-01 19:26:27 [6] LTE: table[1]=600

2016-01-01 19:26:27 [6] LTE: table[2]=3600

2016-01-01 19:26:27 [6] LTE: table[3]=21600

2016-01-01 19:26:27 [6] LTE: table[4]=43200

2016-01-01 19:26:27 [6] LTE: table[5]=86400

2016-01-01 19:26:27 [6] LTE: table_number=6, lte_disconn_reboot_threshold=150

2016-01-01 19:26:28 [5] Mesh: Success Add Client : MAC : 70:EE:50:XX:XX:XX

2016-01-01 19:26:28 [5] Mesh: Success Add Client : MAC : 54:EF:44:XX:XX:XX

2016-01-01 19:26:28 [5] Mesh: Success Add Client : MAC : 50:1E:2D:XX:XX:XX

2016-01-01 19:26:28 [5] Mesh: Success Add Client : MAC : 58:D3:49:XX:XX:XX

2016-01-01 19:26:28 [5] Mesh: Success Add Client : MAC : A4:11:62:XX:XX:XX

2016-01-01 19:26:28 [5] Mesh: Success Add Client : MAC : EC:B5:FA:XX:XX:XX

2016-01-01 19:26:29 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from 86:F1:7E:XX:XX:XX to FF:FF:FF:FF:FF:FF)
2016-01-01 19:26:29 [5] DHCPC: Recv OFFER from server 192.168.1.1 with ip 192.168.1.235 (from 60:35:C0:XX:XX:XX  to 86:F1:7E:XX:XX:XX)
2016-01-01 19:26:29 [5] DHCPC: Send REQUEST to server 192.168.1.1 with request ip 192.168.1.235 (from 86:F1:7E:XX:XX:XX to FF:FF:FF:FF:FF:FF)
2016-01-01 19:26:30 [5] DHCPC: Recv ACK from server 192.168.1.1 with ip 192.168.1.235 lease time 86400 (from 60:35:C0:XX:XX:XX to 86:F1:7E:XX:XX:XX)
2016-01-01 19:26:30 [5] DHCPC: Recv DNS server address 192.168.1.1,0,0,0,0
2025-05-15 05:52:08 [5] DHCPD: Recv REQUEST from A4:11:62:XX:XX:XX
2025-05-15 05:52:18 [5] DHCPD: Recv DISCOVER from EC:B5:FA:XX:XX:XX
2025-05-15 05:52:18 [5] DHCPD: Send OFFER with ip 192.168.0.7
2025-05-15 05:52:24 [5] DHCPD: Recv REQUEST from A4:11:62:XX:XX:XX
2025-05-15 05:52:26 [5] Mesh: Success Add Client : MAC : F6:78:FA:XX:XX:XX

2025-05-15 05:52:26 [5] DHCPD: Recv DISCOVER from F6:78:FA:XX:XX:XX
2025-05-15 05:52:26 [5] DHCPD: Send OFFER with ip 192.168.0.8
2025-05-15 05:52:33 [6] LTE: first_valid_uptime=64

2025-05-15 05:52:33 [5] LTE: SIM plugged.

2025-05-15 05:52:33 [5] LTE: Registered with a network!

2025-05-15 05:52:33 [5] LTE: Network type is NR.

2025-05-15 05:52:33 [5] LTE: network changed: 0,0->208,1

2025-05-15 05:52:33 [5] LTE: Start connecting to the network!

2025-05-15 05:52:36 [5] LTE: Fail to connect to the network, start autoconnect!

2025-05-15 05:52:42 [5] LTE: Fail to connect to the network, start autoconnect!

2025-05-15 05:52:44 [5] LTE: Connected to the network!

to summarize :

- my nx600 is stable in 3G/4G mode

- my nx600 is presenting one of the following issue every few days when configured in 3G/4G/5G mode

   issue #1: nx600 is crashing and rebooting autonomously 

   issue #2 : nx600 3G/4G/5G is not working (LAN is working, GUI is working, WIFI is working) until it is manually rebooted

If needed, I can share the status page before the issue, during the issue, and after rebooting.

  @FredericS 

Hi,

I am sure TP-Link support has fix for "2025-05-15 03:12:22 [3] LTE: Exception:GetMobileStatus fail" , subsequent reboot may also get fixed once patches out for your devices.

You can also activate external syslog server to get much more details while NX600 triggers reboot like below.

192.168.1.1    Apr 24 21:57:28        local0    err    LTE    Exception:GetMobileStatus fail 
192.168.1.1    Apr 24 21:58:03        local0    err    LTE    Exception:GetMobileStatus fail 
192.168.1.1    Apr 24 21:58:38        local0    err    LTE    Exception:GetMobileStatus fail 
192.168.1.1    Apr 24 21:59:13        local0    err    LTE    Exception:GetMobileStatus fail 
192.168.1.1    Apr 24 21:59:48        local0    err    LTE    Exception:GetMobileStatus fail 
192.168.1.1    Apr 24 21:59:48        local0    info    LTE    execute save 
192.168.1.1    Apr 24 21:59:48        local0    err    LTE    Exception:archive length too long(1096) 
192.168.1.1    Apr 24 21:59:48        local0    info    LTE    new config flag=00000009, new status flag=00000009, index=0, token=2, archive(len=391)={"ver":300,"stast":7,"num":1,"tbl":[{"idx":0,"up":"92028","rule":"0,N,P;1,N,P;2,N,P;3,N,F;4,E,F;5,U,U;6,U,U;7,U,U;8,U,U;9,U,U;10,U,U;11,U,U;12,U,U;","m":{"st
192.168.1.1    Apr 24 21:59:48        local0    info    LTE    execute reboot 
192.168.1.1    Apr 24 22:01:42        local0    info    LTE    first_valid_uptime=50 
192.168.1.1    Apr 24 22:01:42        local0    info    LTE    mobile_invalid_reboot_token=3 
192.168.1.1    Apr 24 22:01:42        local0    notice    DHCPD    Recv RELEASE from B0:4A:39:96:90:E4
192.168.1.1    Apr 24 22:01:42        local0    notice    DHCPD    Recv REQUEST from 00:93:37:8C:F1:81
192.168.1.1    Apr 24 22:01:42        local0    notice    DHCPD    Send ACK to 192.168.1.3
192.168.1.1    Apr 24 22:01:44        local0    notice    DHCPD    Recv DISCOVER from B0:4A:39:96:90:E4
192.168.1.1    Apr 24 22:01:44        local0    notice    DHCPD    Send OFFER with ip 192.168.1.4
192.168.1.1    Apr 24 22:01:56        local0    info    LTE    first_conn_uptime=66 
192.168.1.1    Apr 24 22:01:56        local0    info    LTE    health_conn_uptime=66 
 

Do reach to support for enabling trace or getting customized firmware with fix for your device. 

Yasin

  @myag 

hi, thank you for your reply.

If a fix is already identified, a new firmware containing the fix should be available soo :)

fred

  @FredericS 

Yes, support shared fix for my device and random network (lan/wifi) issue still being worked. 

  @myag Hi , i have the same problem here. In italy with "ho mobile" as provider, the router says "Exception:GetMobileStatus fail" and then reboot .Please let me know when a solution will be provided.

@dariox3084 

The error due to too many neighboring cell being discovered by CPE, In my case 35 neighboring cells identified and errors starts coming once CPE reaches 29 cells.  Support enabled trace for my device and also released customized firmware to fix neighboring cell issues.  This firmware cannot be shared as it is locked to MAC address. 

I also discovered new Ethernet/WiFi bug reproducible in beta firmware and support still working on it. 

You can check with support for enabling trace for your device, you may see entries like below to confirm issue on neighboring cell.

[D][ATC][atchannel.c:readline:561]AT< +ECELL: 35,13,"00137B102","2357",420,1,347,43,16,-392,-48,7,13,,1,1450,13,"00FFFFFFF","FFFF",,,346,61,22,-320,-36,,21,,,9260,13,"00FFFFFFF","FFFF",,,346,43,13,-392,-54,,14,,,1450,13,"00FFFFFFF","FFFF",,,78,41,8,-400,-64,,14,,,1450,13,"00FFFFFFF","FFFF",

Yasin

  @myag Thank you for the info!

i can't understand why this fix is not provided to all devices, but maybe it's my fault.

@Kevin_Z  can you help me? The custom firmware can give me problems if i move to another location with other 5g cells?

Thanks