The firmware you sent me doesn't help for the continued disconnections, the stuff you ask me to do is to complicated btw.

@Elia  

A quick update.

I received the debug firmware from TP-Link some times back.

Provided required logs to them for debug.

Afterwards they sent me a test firmware.

This test firmware fixed the issue of disconnect.

I confirmed them that issue is fixed, and waiting for official firmware release.

@Kevin_Z  to follow up the official firmware release.

To all readers with an MR600, this is where things stand, I believe:

- Changing the settings to 4G only (instead of 3G & 4G), does not help. It does not help for MR200 or MR400 either.

- Please see below link to a beta firmware.  It is for MR600 only.  So far, only Ardneriv has confirmed it works.  It hasn't worked for everyone apparently

- It the beta firmware does not work for you, please see below further instructions on what to do to help the TP-Link team troubleshoot this.

Best wishes,

Dear Customer,

This is Angel from TP-Link support. We have learnt from the community that the internet connection on your Archer MR600 is not so stable. We have created a beta firmware which may solve the unstable issue on MR600. Please have a try with it and feedback it's performance. Thank you.
https://static.tp-link.com/2020/202001/20200117/2020-01-17-Archer_MR600-FW_for_unstable_issue-Tool.zip

If the router is still unstable with the above firmware, please connect your computer to the router by Ethernet cable and run the LTE Log Tool in 'net monitor' mode to capture the debug log. The tool will stop automatically when the internet drops, please save the debug log into a new folder then. The log directory will be opened when the tool is stopped. And, please go to Advanced-System Tools-System Log page, save the system log and save it in the above new folder. Please note that we need both the debug log and the system log.
When the internet drops, please run the Tool again, select the mode as ' dial once' and start it. Check and tell us the internet status once the tool stops. Then save the debug log and system log into another folder. Please note that we need both the debug log and the system log.
If the router can get internet after step4, now the debug process has been finished. If the router still cannot get internet access after step4, please reboot the router to make it connect to the internet, and run the 'dial once' mode to get the debug log and system log when the router can successfully connect to the internet.
At last, please send us the above two or three folders which contain two/three debug logs and two/three system logs. Thanks.

> Dear Customer,
>
> This is Marcia from TP-Link technical support team, regarding to the issue reported on the community, our engineer focus on it now and we have developed a debug tool to locate the issue. Please follow the steps below to get the debug log and System Log for further analysis:
>
> 1. Below is the download link: https://static.tp-link.com/2019/201912/20191217/2019-11-12-Debug_tool_firmware_for_MR600.zip
> Note: Please copy and paste the whole link into an address bar to get the zip file
> 2. Once the router has the new firmware, please run the 'TP-LINK LTE Log Tool.exe', select the mode as 'net monitor' and start it.
> 3. Just keep the router and the Tool run until the internet drops on your router, save the debug log into a new folder. The log directory will be opened when the tool is stopped. And, please go to Advanced-System Tools-System Log page, save the system log and save it in the above new folder. Please note that we need both the debug log and the system log.
> 4. Please run the Tool again, select the mode as ' dial once' and start it. Check and tell us the internet status once the tool stops. Then save the debug log and system log into another folder. Please note that we need both the debug log and the system log.
> 5. Please send us the above two folders which contain two debug logs and two system logs.
>
> Thanks in advance, and have a nice day.
> Your feedback is very important to us, please feel free to contact me for further help.
> Best Regards
> ----------------------------------------------
> Marcia Zhang

Ardneriv wrote

@Elia  

 

A quick update.

I received the debug firmware from TP-Link some times back.

Provided required logs to them for debug.

 

Afterwards they sent me a test firmware.

This test firmware fixed the issue of disconnect.

 

I confirmed them that issue is fixed, and waiting for official firmware release.

@Kevin_Z  to follow up the official firmware release.

 

 

@Guillaume_1978   Hi, After installation of firmware "Archer_MR600v1_1.1.0_0.9.1_[200117-rel34891]_up_boot_2020-01-17_10.08.32.bin", network performance deteriorated: before installation the signal strenght was 75%/100%, after 25%. Now a speed test after installation reports 14MBit in download and 2MBit in upload; before installation was 98MBit in download and 39Mbit in upload. I'm testing if the disconnection after 4 hours is fixed, so I'm waiting 4 hours to check... But if this fix resolves the issue, we have another issue on network performance!!!

This is the log after new firmware installation. As you can see the issue doen't not fix. 

At 13:48:49 log reports: 

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Connection failure, mostly no svc.

2020-02-01 13:48:49 [6] 4G: USER: The network disconnected, start autoconnect!

Follow the full log:

2020-02-01 13:43:20 [6] 4G: INFO: The signal level is 3.

2020-02-01 13:43:35 [6] 4G: INFO: The signal level is 3.

2020-02-01 13:46:44 [5] DHCPD: Recv REQUEST from 94:A1:A2:90:A3:48
2020-02-01 13:46:44 [5] DHCPD: Send ACK to 192.168.1.117
2020-02-01 13:46:44 [5] DHCPD: Recv REQUEST from AC:83:F3:03:C4:56
2020-02-01 13:46:44 [5] DHCPD: Send ACK to 192.168.1.115
2020-02-01 13:46:46 [5] DHCPD: Recv REQUEST from 28:ED:E0:CE:CE:D3
2020-02-01 13:46:46 [5] DHCPD: Send ACK to 192.168.1.116
2020-02-01 13:46:48 [5] DHCPD: Recv REQUEST from 28:ED:E0:CE:C4:26
2020-02-01 13:46:48 [5] DHCPD: Send ACK to 192.168.1.114
2020-02-01 13:48:06 [5] DHCPD: Recv REQUEST from DC:4F:22:93:C0:6B
2020-02-01 13:48:07 [5] DHCPD: Send ACK to 192.168.1.112
2020-02-01 13:48:22 [5] DHCPD: Recv REQUEST from AC:83:F3:03:BB:76
2020-02-01 13:48:22 [5] DHCPD: Send ACK to 192.168.1.131
2020-02-01 13:48:49 [6] 4G: INFO: Conn-Stat = 1, Re-Config = 0, IP-Ver = 4.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Connection failure, mostly no svc.

2020-02-01 13:48:49 [6] 4G: USER: The network disconnected, start autoconnect!

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Try to auto reconnecting.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Delayed backhaul connecting operaton.

2020-02-01 13:48:49 [6] 4G: USER: Get ISP's profile now.

2020-02-01 13:48:49 [6] 4G: USER: GetCurrProf result is:ipver:0  staticApn:0  authType:2  pkgName:Wind  profname:Wind  apn:internet.wind  usr:  psw:  

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Will connect immediately.

2020-02-01 13:48:49 [6] 4G: INFO: LG enter CMobileManagerQmi GetAttachProfileIPType

2020-02-01 13:48:49 [6] 4G: INFO: LG get profile setting pdp_type 3

2020-02-01 13:48:49 [6] 4G: ERROR: Bind mux port session 0 failed (0).

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Start the backhaul status checking timer.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Will check connection status in 10s later.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: The current state is 2.

2020-02-01 13:48:49 [6] 4G: INFO: Conn-Stat = 1, Re-Config = 0, IP-Ver = 4.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Connecting failed, mostly no svc.

2020-02-01 13:48:49 [6] 4G: USER: Fail to connect to the network, start autoconnect!

2020-02-01 13:48:49 [6] 4G: INFO: FSM: In connecting progress, now connecting.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Delayed backhaul connecting operaton.

2020-02-01 13:48:49 [6] 4G: USER: Get ISP's profile now.

2020-02-01 13:48:49 [6] 4G: USER: GetCurrProf result is:ipver:0  staticApn:0  authType:2  pkgName:Wind  profname:Wind  apn:internet.wind  usr:  psw:  

2020-02-01 13:48:49 [6] 4G: INFO: FSM: Will connect in 4s later.

2020-02-01 13:48:49 [6] 4G: INFO: FSM: The current state is 2.

2020-02-01 13:48:50 [6] 4G: INFO: Conn-Stat = 2, Re-Config = 0, IP-Ver = 4.

2020-02-01 13:48:50 [6] 4G: USER: Connected to the network!

2020-02-01 13:48:50 [6] 4G: INFO: FSM: Backhaul connected.

2020-02-01 13:48:50 [6] 4G: INFO: FSM: The current state is 4.

2020-02-01 13:48:50 [6] 4G: INFO: PCell Information:

2020-02-01 13:48:50 [6] 4G: INFO: Physical cell ID204

2020-02-01 13:48:50 [6] 4G: INFO: Absolute cell's frequency 1650

2020-02-01 13:48:50 [6] 4G: INFO: Pcell downlink bandwith 5 (0-1.4, 1-3, 2-5, 3-10, 4-15, 5-20)

2020-02-01 13:48:50 [6] 4G: INFO: pcell's band = 122

2020-02-01 13:48:50 [6] 4G: INFO: Scell 1 information:

2020-02-01 13:48:50 [6] 4G: INFO: scell's band = 145

2020-02-01 13:48:50 [6] 4G: INFO: Physical cell ID of the Scell 0

2020-02-01 13:48:50 [6] 4G: INFO: Absolute cell's frequency 6200

2020-02-01 13:48:50 [6] 4G: INFO: Scell states 1 (0-Deconfigured, 1-Configuread and Deactived, 2-Configured and Actived)

2020-02-01 13:48:50 [6] 4G: INFO: Scell downlink bandwith 3 (0-1.4, 1-3, 2-5, 3-10, 4-15, 5-20)

2020-02-01 13:48:50 [6] 4G: INFO: Conn-Stat = 2, Re-Config = 0, IP-Ver = 4.

2020-02-01 13:48:50 [6] 4G: INFO: PCell Information:

2020-02-01 13:48:50 [6] 4G: INFO: Physical cell ID204

2020-02-01 13:48:50 [6] 4G: INFO: Absolute cell's frequency 1650

I was doing my taxes from 2019 yesterday, saw I bought this router in July, still not working (stable WiFi). We use our phones when we need  stable connection since, the cable connection (Smart TV's) always have worked just fine.

@Fabieuz 

I had the exact same problem. It is not a problem of the router but of the provider.

@Elia we have various people on this thread (and other threads about MR200 and MR400) who have tested various SIM providers,

@Guillaume_1978 what are these providers? My provider is WIND 3 Italy. However this behaviour seam depends on priveder policy... did you test the same sim on other device vendor to check if disconnection happen?

@Fabieuz I and other users tried various SIMs (in the UK, Three and Vodafone), in competing models and in mobile devices.   Only with the TP-Link router it failed / got repeatedly interruprted.

What policies are you specifically referring to?