@ne1gold I buy an other modem and it's the same. For everbody it's about the situation of covid-19 and many people on 4G antenna, so i will wait the end of this situation and see if something change.

Good Luck everybody

@Kevin_Z 

Kevin_Z wrote

@tommylux 

 

Please provide some needed information first.

 

What is the current hardware and firmware version of your product? 

 

And how often it loses connection? How did you make it work? 

 

Have you ever tried any troubleshooting methods? What about the corresponding results. 

 

Thanks a lot. 

I have Frequent 4G disconnections and its not stable. I have V1 hardware and 1.1.0 0.9.1 v0001.0 Build 190412 Rel.66770n firmware. Please find the logs collected at the time of disconnections.

2020-05-10 13:46:29 [6] 4G: USER: Network type is LTE.

2020-05-10 13:46:29 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:46:33 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:46:49 [6] 4G: USER: Network type is LTE.

2020-05-10 13:46:50 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:46:52 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:47:29 [6] 4G: USER: Network type is LTE.

2020-05-10 13:47:29 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:47:34 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:47:57 [6] 4G: USER: Network type is LTE.

2020-05-10 13:47:57 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:48:01 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:48:08 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 13:48:09 [6] 4G: USER: Network type is LTE.

2020-05-10 13:48:09 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:48:13 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:48:39 [6] 4G: USER: Network type is LTE.

2020-05-10 13:48:40 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:48:41 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:48:48 [6] 4G: USER: Network type is LTE.

2020-05-10 13:48:49 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:48:50 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:49:14 [6] 4G: USER: Network type is LTE.

2020-05-10 13:49:14 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:49:18 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:49:49 [6] 4G: USER: Network type is LTE.

2020-05-10 13:49:49 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:49:52 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:50:09 [6] 4G: USER: Network type is LTE.

2020-05-10 13:50:09 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:50:13 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 13:50:24 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:50:58 [6] 4G: USER: Network type is LTE.

2020-05-10 13:50:58 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:51:01 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:51:09 [6] 4G: USER: Network type is LTE.

2020-05-10 13:51:09 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:51:24 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:52:18 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 13:54:23 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 13:56:28 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 13:56:34 [6] 4G: USER: Network type is LTE.

2020-05-10 13:56:34 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 13:56:35 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 13:58:33 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:00:31 [6] 4G: USER: Network type is LTE.

2020-05-10 14:00:31 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 14:00:37 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 14:00:39 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:01:13 [6] 4G: USER: Network type is LTE.

2020-05-10 14:01:13 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 14:01:17 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 14:02:43 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:04:49 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:04:58 [6] 4G: USER: Network type is LTE.

2020-05-10 14:04:58 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 14:04:58 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 14:05:52 [6] System: Device(0C:DD:24:E5:A2:4A) joins in 5G Wlan
2020-05-10 14:05:52 [5] DHCPD: Recv REQUEST from 0C:DD:24:E5:A2:4A
2020-05-10 14:05:52 [5] DHCPD: Send ACK to 192.168.8.101
2020-05-10 14:06:17 [6] System: User(0C:DD:24:E5:A2:4A) logs in.
2020-05-10 14:06:23 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:23 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:06:23 [6] Httpd: NCSI response check succeed.
2020-05-10 14:06:25 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:25 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:06:25 [6] Httpd: NCSI response check succeed.
2020-05-10 14:06:53 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:53 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:06:53 [6] Httpd: NCSI response check succeed.
2020-05-10 14:06:54 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:06:54 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:54 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:06:54 [6] Httpd: NCSI response check succeed.
2020-05-10 14:06:55 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:55 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:06:55 [6] Httpd: NCSI response check succeed.
2020-05-10 14:06:57 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:57 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:06:57 [6] Httpd: NCSI response check succeed.
2020-05-10 14:06:58 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:06:58 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:00 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:01 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:01 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:01 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:03 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:03 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:03 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:15 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:16 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:16 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:17 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:17 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:17 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:18 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:18 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:19 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:20 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:20 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:20 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:21 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:21 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:22 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:23 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:23 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:24 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:40 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:07:40 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:07:41 [6] Httpd: NCSI response check succeed.
2020-05-10 14:07:46 [6] Httpd: DNS 185.23.125.70 resolve timeout for dns.msftncsi.com
2020-05-10 14:07:48 [6] Httpd: DNS 8.8.8.8 resolve timeout for dns.msftncsi.com
2020-05-10 14:07:51 [6] 4G: USER: Network type is LTE.

2020-05-10 14:07:51 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 14:07:51 [6] 4G: USER: Not registered, searching!

2020-05-10 14:07:51 [6] 4G: USER: Registered with a network!

2020-05-10 14:07:52 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 14:07:52 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 14:08:01 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:02 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:03 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:04 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:04 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:05 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:06 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:07 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:07 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:12 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:13 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:14 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:15 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:15 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:16 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:18 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:18 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:19 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:20 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 14:08:20 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 14:08:20 [6] Httpd: NCSI response check succeed.
2020-05-10 14:08:30 [6] System: Device(0C:DD:24:E5:A2:4A) leaves 5G Wlan
2020-05-10 14:08:58 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:09:31 [6] System: Device(F0:6E:0B:13:53:7A) leaves 5G Wlan
2020-05-10 14:09:35 [6] System: Device(F0:6E:0B:13:53:7A) joins in 5G Wlan
2020-05-10 14:09:36 [5] DHCPD: Recv REQUEST from F0:6E:0B:13:53:7A
2020-05-10 14:09:36 [5] DHCPD: Send ACK to 192.168.8.105
2020-05-10 14:11:04 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:13:08 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:15:14 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:17:19 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:19:24 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:21:28 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:23:34 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:25:39 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:27:44 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:29:49 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:31:54 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:33:59 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:36:04 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:38:09 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:40:13 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:42:18 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:44:23 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:46:28 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:48:33 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:50:38 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:52:44 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:54:48 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:56:54 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 14:58:59 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:01:04 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:03:09 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:05:14 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:07:19 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:09:23 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:11:29 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:13:34 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:15:39 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:17:44 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:19:49 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:21:54 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:22:23 [6] System: Device(C0:BD:C8:9E:E1:3F) joins in 2.4G Wlan
2020-05-10 15:22:23 [5] DHCPD: Recv REQUEST from C0:BD:C8:9E:E1:3F
2020-05-10 15:22:23 [5] DHCPD: Send ACK to 192.168.8.100
2020-05-10 15:23:58 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:26:04 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:28:09 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:30:14 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:32:19 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:34:24 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:36:29 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:36:46 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 15:36:46 [5] DHCPD: Recv DISCOVER from 4E:14:2D:46:A1:76
2020-05-10 15:36:46 [5] DHCPD: Send OFFER with ip 192.168.8.103
2020-05-10 15:36:47 [5] DHCPD: Recv REQUEST from 4E:14:2D:46:A1:76
2020-05-10 15:36:47 [5] DHCPD: Send ACK to 192.168.8.103
2020-05-10 15:37:14 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 15:37:14 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 15:38:34 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:38:41 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 15:38:41 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 15:40:38 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:42:43 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:44:49 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:46:54 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:47:47 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 15:48:59 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:51:04 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:53:09 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:55:14 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:57:19 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 15:59:23 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:01:29 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:03:34 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:05:39 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:07:44 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:09:16 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 16:09:17 [5] DHCPD: Recv DISCOVER from 4E:14:2D:46:A1:76
2020-05-10 16:09:17 [5] DHCPD: Send OFFER with ip 192.168.8.103
2020-05-10 16:09:18 [5] DHCPD: Recv REQUEST from 4E:14:2D:46:A1:76
2020-05-10 16:09:19 [5] DHCPD: Send ACK to 192.168.8.103
2020-05-10 16:09:48 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:11:53 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:11:55 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 16:11:55 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 16:12:36 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 16:12:36 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 16:12:38 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 16:12:42 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 16:12:47 [5] DHCPD: Recv DISCOVER from 4E:14:2D:46:A1:76
2020-05-10 16:12:47 [5] DHCPD: Send OFFER with ip 192.168.8.103
2020-05-10 16:12:47 [5] DHCPD: Recv REQUEST from 4E:14:2D:46:A1:76
2020-05-10 16:12:48 [5] DHCPD: Send ACK to 192.168.8.103
2020-05-10 16:13:09 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 16:13:09 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 16:13:58 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:16:03 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:18:08 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:20:13 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:22:19 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:24:23 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:26:28 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:28:34 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:30:39 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:32:43 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:34:49 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:36:53 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:38:58 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:41:03 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:43:08 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:45:13 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:47:18 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:47:30 [6] System: User(22:EF:F4:41:2C:1E) logs in on Tether App
2020-05-10 16:48:18 [6] 4G: LTE connection down
2020-05-10 16:48:20 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:20 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:20 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:20 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:21 [6] 4G: LTE connection up
2020-05-10 16:48:21 [5] 4G: LTE internet connected.
2020-05-10 16:48:26 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:26 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:26 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:26 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:26 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:26 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:26 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:26 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:31 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:31 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:31 [6] 4G: ERROR: Post event to MOBILE server failed, errno = 146 (Connection refused).

2020-05-10 16:48:31 [6] 4G: ERROR: Client communication with server failed.

2020-05-10 16:48:35 [6] 4G: ERROR: New sms count is 0

2020-05-10 16:48:36 [6] 4G: USER: Mobile device manager (qmi) initialized OK.
Init QMI services......

2020-05-10 16:48:36 [6] System: Device(C0:BD:C8:9E:E1:3F) leaves 2.4G Wlan
2020-05-10 16:48:38 [6] 4G: USER: Start get voice service object.

2020-05-10 16:48:38 [6] 4G: USER: VOICE Service Object got.

2020-05-10 16:48:38 [6] 4G: USER: VOICE QMI Client Init successfully, handle is 0x00C7BDE0.

2020-05-10 16:48:38 [6] 4G: ERROR: 0x00000046 QMI_ERR_INVALID_OPERATION

2020-05-10 16:48:38 [6] 4G: ERROR: [zc] ParseCmdRet(set_resp.resp) != MP_ERR_SUCCESS, continue

2020-05-10 16:48:38 [6] 4G: USER: Mobile device manager (qmi) initialized OK.

2020-05-10 16:48:38 [6] 4G: WARN: Sim card is inserted.

2020-05-10 16:48:38 [6] 4G: ERROR: 0x00000010 QMI_ERR_NOT_PROVISIONED

2020-05-10 16:48:38 [6] 4G: ERROR: Get sim card number failed (0).

2020-05-10 16:48:38 [6] 4G: WARN: Event (0x10000001) not found its logic thread.

2020-05-10 16:48:41 [6] 4G: ERROR: 0x0000004A QMI_ERR_INFO_UNAVAILABLE

2020-05-10 16:48:41 [6] 4G: ERROR: result=1, error=74

2020-05-10 16:48:41 [6] 4G: ERROR: QMI NAS Get PHY CA Info failed, ret = 0.

2020-05-10 16:48:41 [6] 4G: USER: The service status is limited.

2020-05-10 16:48:41 [6] 4G: USER: Not registered, searching!

2020-05-10 16:48:41 [6] 4G: USER: Network type is LTE.

2020-05-10 16:48:41 [6] 4G: ERROR: 0x0000004A QMI_ERR_INFO_UNAVAILABLE

2020-05-10 16:48:41 [6] 4G: ERROR: result=1, error=74

2020-05-10 16:48:41 [6] 4G: ERROR: QMI NAS Get PHY CA Info failed, ret = 0.

2020-05-10 16:48:41 [6] 4G: USER: The service is available.

2020-05-10 16:48:41 [6] 4G: USER: Registered with a network!

2020-05-10 16:48:41 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 16:48:41 [6] 4G: USER: Get ISP's profile now.

2020-05-10 16:48:41 [6] 4G: USER: GetCurrProf result is:ipver:0  staticApn:0  authType:2  pkgName:Zain  profname:Zain  apn:zain  usr:  psw:  

2020-05-10 16:48:41 [6] 4G: USER: Start connecting to the network!

2020-05-10 16:48:42 [6] 4G: ERROR: Bind mux port session 0 failed (0).

2020-05-10 16:48:42 [5] DHCPD: Recv DISCOVER from C0:BD:C8:9E:E1:3F
2020-05-10 16:48:42 [5] DHCPD: Send OFFER with ip 192.168.8.100
2020-05-10 16:48:42 [5] DHCPD: Recv REQUEST from C0:BD:C8:9E:E1:3F
2020-05-10 16:48:42 [6] 4G: ERROR: 0x0000004A QMI_ERR_INFO_UNAVAILABLE

2020-05-10 16:48:42 [6] 4G: ERROR: result=1, error=74

2020-05-10 16:48:42 [6] 4G: ERROR: QMI NAS Get PHY CA Info failed, ret = 0.

2020-05-10 16:48:42 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 16:48:42 [6] 4G: ERROR: 0x0000004A QMI_ERR_INFO_UNAVAILABLE

2020-05-10 16:48:42 [6] 4G: ERROR: result=1, error=74

2020-05-10 16:48:42 [6] 4G: ERROR: QMI NAS Get PHY CA Info failed, ret = 0.

2020-05-10 16:48:42 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 16:48:42 [5] DHCPD: Send ACK to 192.168.8.100
2020-05-10 16:48:42 [5] DHCPD: Recv REQUEST from C0:BD:C8:9E:E1:3F
2020-05-10 16:48:43 [6] 4G: USER: GET_SMSC_ADDRESS response, value = +966590100880

2020-05-10 16:48:43 [5] DHCPD: Send ACK to 192.168.8.100
2020-05-10 16:48:43 [6] System: Device(C0:BD:C8:9E:E1:3F) joins in 5G Wlan
2020-05-10 16:48:43 [6] 4G: USER: The service status is limited.

2020-05-10 16:48:43 [6] 4G: USER: Not registered, searching!

2020-05-10 16:48:43 [6] 4G: USER: The service is available.

2020-05-10 16:48:43 [6] 4G: USER: Registered with a network!

2020-05-10 16:48:43 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 16:48:43 [6] 4G: USER: Now registrat on network 420 4, long_eons Zain KSA short_eons Zain KSA.

2020-05-10 16:48:43 [6] 4G: USER: Connected to the network!

2020-05-10 16:48:43 [6] 4G: ERROR: 0x0000004A QMI_ERR_INFO_UNAVAILABLE

2020-05-10 16:48:43 [6] 4G: ERROR: result=1, error=74

2020-05-10 16:48:43 [6] 4G: ERROR: QMI NAS Get PHY CA Info failed, ret = 0.

2020-05-10 16:48:43 [6] 4G: ERROR: 0x0000004A QMI_ERR_INFO_UNAVAILABLE

2020-05-10 16:48:43 [6] 4G: ERROR: result=1, error=74

2020-05-10 16:48:43 [6] 4G: ERROR: QMI NAS Get PHY CA Info failed, ret = 0.

2020-05-10 16:48:46 [6] 4G: LTE connection up
2020-05-10 16:48:47 [5] 4G: LTE internet connected.
2020-05-10 16:48:47 [6] 4G: USER: Network type is LTE PLUS.

2020-05-10 16:49:16 [6] System: Device(22:EF:F4:41:2C:1E) joins in 5G Wlan
2020-05-10 16:49:17 [5] DHCPD: Recv DISCOVER from 22:EF:F4:41:2C:1E
2020-05-10 16:49:17 [5] DHCPD: Send OFFER with ip 192.168.8.102
2020-05-10 16:49:17 [5] DHCPD: Recv REQUEST from 22:EF:F4:41:2C:1E
2020-05-10 16:49:18 [5] DHCPD: Send ACK to 192.168.8.102
2020-05-10 16:49:49 [6] System: User(22:EF:F4:41:2C:1E) logs in on Tether App
2020-05-10 16:50:08 [6] System: Device(22:EF:F4:41:2C:1E) joins in 2.4G Wlan
2020-05-10 16:50:08 [6] System: Device(22:EF:F4:41:2C:1E) leaves 5G Wlan
2020-05-10 16:50:18 [6] System: Device(22:EF:F4:41:2C:1E) leaves 2.4G Wlan
2020-05-10 16:50:21 [6] System: Device(22:EF:F4:41:2C:1E) joins in 2.4G Wlan
2020-05-10 16:50:22 [5] DHCPD: Recv DISCOVER from 22:EF:F4:41:2C:1E
2020-05-10 16:50:22 [5] DHCPD: Send OFFER with ip 192.168.8.102
2020-05-10 16:50:22 [5] DHCPD: Recv REQUEST from 22:EF:F4:41:2C:1E
2020-05-10 16:50:23 [5] DHCPD: Send ACK to 192.168.8.102
2020-05-10 16:50:25 [6] System: User(22:EF:F4:41:2C:1E) logs in on Tether App
2020-05-10 16:51:47 [6] System: User(22:EF:F4:41:2C:1E) logs in.
2020-05-10 16:51:50 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 16:51:50 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 16:51:50 [6] Httpd: NCSI response check succeed.
2020-05-10 16:51:55 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 16:51:55 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 16:51:56 [6] Httpd: NCSI response check succeed.
2020-05-10 16:53:46 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 16:53:47 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 16:53:47 [6] Httpd: NCSI response check succeed.
2020-05-10 16:53:55 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:53:58 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 16:53:58 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 16:53:58 [6] Httpd: NCSI response check succeed.
2020-05-10 16:54:26 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:54:57 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:56:43 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 16:56:43 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 16:56:53 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 16:56:53 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 16:57:02 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:58:12 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 16:58:12 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 16:59:06 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 16:59:53 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 16:59:53 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 17:01:12 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:02:11 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 17:02:12 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 17:02:45 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 17:02:50 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 17:03:16 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:04:02 [6] System: Device(0C:DD:24:E5:A2:4A) joins in 5G Wlan
2020-05-10 17:04:02 [5] DHCPD: Recv REQUEST from 0C:DD:24:E5:A2:4A
2020-05-10 17:04:02 [5] DHCPD: Send ACK to 192.168.8.101
2020-05-10 17:04:21 [6] System: User(0C:DD:24:E5:A2:4A) logs in.
2020-05-10 17:04:31 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 17:04:31 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 17:04:34 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 17:04:34 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 17:04:34 [6] Httpd: NCSI response check succeed.
2020-05-10 17:04:39 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 17:04:39 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 17:04:39 [6] Httpd: NCSI response check succeed.
2020-05-10 17:05:21 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:07:08 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 17:07:08 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 17:07:13 [5] DHCPD: Recv DISCOVER from 4E:14:2D:46:A1:76
2020-05-10 17:07:13 [5] DHCPD: Send OFFER with ip 192.168.8.103
2020-05-10 17:07:13 [5] DHCPD: Recv REQUEST from 4E:14:2D:46:A1:76
2020-05-10 17:07:13 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 17:07:13 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 17:07:13 [5] DHCPD: Send ACK to 192.168.8.103
2020-05-10 17:07:14 [5] DHCPD: Recv DISCOVER from 4E:14:2D:46:A1:76
2020-05-10 17:07:14 [5] DHCPD: Send OFFER with ip 192.168.8.103
2020-05-10 17:07:14 [5] DHCPD: Recv REQUEST from 4E:14:2D:46:A1:76
2020-05-10 17:07:14 [5] DHCPD: Send ACK to 192.168.8.103
2020-05-10 17:07:26 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:08:21 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:09:10 [6] System: Device(4E:14:2D:46:A1:76) joins in 2.4G Wlan
2020-05-10 17:09:10 [6] System: Device(4E:14:2D:46:A1:76) leaves 5G Wlan
2020-05-10 17:09:19 [6] System: Device(4E:14:2D:46:A1:76) joins in 5G Wlan
2020-05-10 17:09:19 [6] System: Device(4E:14:2D:46:A1:76) leaves 2.4G Wlan
2020-05-10 17:09:32 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:09:52 [6] System: Device(0C:DD:24:E5:A2:4A) joins in 2.4G Wlan
2020-05-10 17:09:52 [6] System: Device(0C:DD:24:E5:A2:4A) leaves 5G Wlan
2020-05-10 17:09:52 [5] DHCPD: Recv REQUEST from 0C:DD:24:E5:A2:4A
2020-05-10 17:09:52 [5] DHCPD: Send ACK to 192.168.8.101
2020-05-10 17:11:36 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:13:42 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:13:55 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 17:13:55 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 17:13:55 [6] Httpd: NCSI response check succeed.
2020-05-10 17:15:15 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 17:15:15 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 17:15:15 [6] Httpd: NCSI response check succeed.
2020-05-10 17:15:16 [6] Httpd: DNS 185.23.125.70 resolve succeed for dns.msftncsi.com
2020-05-10 17:15:16 [6] Httpd: DNS 185.23.125.70 resolve succeed for www.msftncsi.com
2020-05-10 17:15:16 [6] Httpd: NCSI response check succeed.
2020-05-10 17:15:47 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:17:52 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:19:57 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2020-05-10 17:21:05 [6] System: Device(4C:DD:31:C4:49:7B) joins in 2.4G Wlan
2020-05-10 17:21:13 [6] System: Device(4C:DD:31:C4:49:7B) leaves 2.4G Wlan
2020-05-10 17:22:01 [4] IGMP: V2 igmp router occured! Not matching ours V3.
 

I put it on sale today, received a new modem/router 2 days ago, just plugged out the mr600 and put the new one in (diffent brand) using the exact same cables, worked flawlessley with in 10 minutes zero hicups (yet) . So thank you for nothing TP-link and 10 months for doing nothing for us!

@Elia ,

i have had from too many years the Archer Mr400 version firmware v.1 (1350) and i can say that it was very good 4G network and dual band wifi good.....

unfortunately what I'm going to do ? i will buy new Archer Mr600 in 21/05/2020....... immediatly I found too many problems!!!!

Disconnection from the internet connection.....wifi that grow up and down! exspecially the 2,5 GHZ...TERRIBLE!

I have found this forum surfing internet to understand which problems have this modem!!!

So After too many days to undestand i have arrived to these considerations:

This modem is terrible and according me is not possible to put in the market one modem that not run correctly!!

1) The 4G+ make problems with the mobile connection and must be lock in only 4G mode.

2) The 2,5Ghz network is growing up and down and are instable if you have a extender this will be crazy because the power of the network growing up and down make unstable the extender and it will be crazy.

3) I have discovered also a strange ghost network that is not possible to delete and is connected to the 2,4Ghz network...

...after too many days to study this modem i think this ghost network... is a new function that have these new modems from tp-link and it is connected to "Mesh" Devices and probaly follow the 2,4 ghz network to connect the others Mesh devices.....

But this ghost network is not possible to delete or to disable with some flag in the modem's settings .

http://www.imagebam.com/image/e365e91344909904

https://thumbs2.imagebam.com/a6/a5/f2/e365e91344909904.jpg

http://www.imagebam.com/image/e365e91344909904

https://thumbs2.imagebam.com/a6/a5/f2/e365e91344909904.jpg

So actually there isn't new firmware that make stable this modem?

Why?

Actually, according me, this modem is unusable correctly!

Tp-Link where are you?

Where are you doing for this modem?

Please Make in settings details one flag to disable the ghost network if someone not want to use the Mash function, probaly the 2,4Ghz will be more usable than before.

Actually for trying to use the modem i have disabled the 4G+ network ....but i have bought this modem ONLY for this 4G+ version...to use the power of these new mobile networks.

Actually i have disabled the 2,4Ghz network and leave the 5Ghz network only....now my netgear extender ex6200 is more stable than before and i can use the extender 2,4 Ghz and double 5Ghz networks one from the router one from the extender.....

@ technical from Tp-Link is possible to receive one answer to these questions and to receive how is possible to make usable this modem?

thanks

Happened just now, this is what I get.

When I restart, it connects.. Would be good if it could just automatically restart when the internet status = Disconnected.

Firmware Version:1.1.0 0.9.1 v0001.0 Build 190412 Rel.66770n Hardware Version:Archer MR600 v1 00000001 IMEI:865371040209842

@tommylux I notice that while your MR600 firmware version is the same as mine (I am also running beta), my build is 200417 Rel 75138n. 

I wonder why they are different?

@Kevin_Z I am experiencing this exact same problem. Can you please forward on the beta firmware to me too please? 

All the best,

James

Kevin_Z wrote

@Elia 

 

Thanks for your requesting. Sorry to respond late. 

 

We have released a beta firmware which you can install and verify whether it can solve this problem. 

 

Please check your inbox to get the download link and other information we need to narrow down the issue. 

 

Good day. 

@Elia Easily share a 3G/4G connection with up to 64 wireless devices, such as phones, tablets, and laptops, at the same time. 4 LAN ports stand ready to provide internet for wired devices like desktop computers. 

TP-Link has released its first-ever 4G+ Cat6 AC1200 Wireless Dual Band Gigabit Router, the Archer MR600. It supports higher LTE-level networks along with a warp downlink speed of about 300 Mbps. The company claims that it has combined a Qualcomm X12 LTE Modem, 802.11 ac Wi-Fi, and Gigabit Ethernet ports together to provide high-speed internet access in any place that has 4G/3G access already. 

TP-Link has launched its first 4G+ Router – Archer MR600, which supports higher LTE level networks with a warp downlink speed of up to 300 Mbps. With the popularisation of LTE-Advanced networks, 3G/4G routers have become a more convenient and cost-effective choice, freeing network access from the traditional Ethernet cable layout. To meet the needs for higher bandwidth and stability, Archer MR600 combines a Qualcomm X12 LTE Modem, 802.11 ac Wi-Fi, and fully gigabit Ethernet ports together to offering a consummate solution for high-speed internet access everywhere with 4G/3G access. 

Qualcomm Snapdragon X12 LTE Modem
Archer MR600 adopts a Qualcomm Snapdragon X12 Modem to boost transfer speeds. Compared to previous 3G/4G routers, Archer MR600 additionally supports Band5 (850 MHz) and Band28 (700 MHz) for greater compatibility, allowing it to work with all leading telcos like Jio, Vodafone, Airtel, etc. TP-Link also integrates AC1200 dual-band Wi-Fi into the router. Lag-free connections are ensured for up to 64 devices at once, making it one of the best choices for a data-abundant lifestyle.

4G+ Cat6 Data Speeds
According to the Global Mobile Suppliers Association, Category 6 has taken part 44% of all subscribed commercial networks and is already the most pervading UE Category in use. Archer MR600 takes advantage of its 4G+ Category 6 network to deliver download speeds of up to 300 Mbps. “Considering the growth in 4G deployments and to empower our partners to be on the forefront, TP-Link has launched Archer MR600, an ideal WiFi solution to be used at ATM, retail fuel pump, automation, surveillance, remote branch office connectivity, etc ” said Mr. Sanjay Sehgal, Senior Vice President, SMB & Telco.

Gigabit Ethernet Ports
With the increased downlink rate, the traditional 100 Mbps Ethernet ports would cause greater bandwidth waste, limiting the applications with heavy transferring traffic.

In contrast, Archer MR600 – with its full gigabit Ethernet ports – provides remarkable speed and reliable connections for high-intensive wired devices; such as your smart TV, game consoles, NAS, and more.

Key Features and Technologies:

• LTE-Advanced Cat6: Up to 300 Mbps downlink/50 Mbps uplink. ‡
• Fully Gigabit Ports: 3 × gigabit LAN ports + 1 × gigabit WAN/LAN port.
• 64 Concurrent Devices: 32 devices on 2.4 GHz and 32 devices on 5 GHz.
• Support TP-Link OneMeshTM: Able to work with TP-Link OneMesh products, to provide a more flexible and cost-effective Mesh network.
• SIM Card Plug and Play: With an integrated 4G+ modem and a built-in SIM card slot, all you need to do is insert a micro SIM card and turn on the router. 
• Detachable LTE Antennas: Better signal strength with the option to change external antennas.
• WAN Connection Backup: Supports Wi-Fi Router Mode which is compatible with cable, fiber, and DSL modems with a WAN/LAN port.
• Easy Management with the Tether App: Set up the 4G+ router in minutes.

TP-Link offers a wide range of LTE routers as below:
 
Archer MR400 AC1200 Wireless Dual Band 4G LTE Router.
Archer MR200 AC750 Wireless Dual Band 4G LTE Router.
Archer MR6400 300Mbps Wireless N 4G LTE Router.

Little update to this group.

I had the MR200 under intense investigation but we failed to make it work properly and returned it under the product warranty, which, I need to say, worked very well via Amazon (even after 9 months - of pain admittedly-).

Kevin and the team having tried to help throughout, we wanted to give it a second go with the MR600 instead of switching manufacturer. 

So far, unfortunately, it is not great.  

The product itself is an upgrade to the MR200 but

- we have similar interruptions which is a bugger

- while the top speeds achieved are quite higher, they are more erratic and our average speed is actually about the same due to long sequences of low speed.   This is unexplained. 

- The strength of the signal <from> the MR600 is stronger than the MR200, but its ability to better pick the 4G/+/LTE signal is not demonstrated, so no improvement here.

We'll go through the motions of the beta firmware, etc. again and will report to this group.