@Kevin_Z 

The problems STILL CONTINUE but TP-Link say or do very little.

They.re quite happy taking our money but refuse to recall this garbage router.

The last contact from technical support was 03/03/21.

@JGMTB 

Agreed - this type of product should just work, especially when so many of us are dependent on it for work and school from home.

The beta I tried was https://static.tp-link.com/beta/2021/202102/20210222/Archer_VR2100V1_210219.zip but it rebooted 5 times in a couple of hours.

The official firmware has 1-2 reboots per day.

@Kevin_Z 

What is happening next?

Firmware Version: 1.3.0 0.9.1 v009e.0 Build 201122 Rel.66972n

Hardware Version: Archer VR600 v3 00000000

Mine lasted about 2 hours after plugging it back in before restarting. Log reset to 2016 again with the following:

2016-01-01 00:00:41 [5] System: DSL Training
2016-01-01 00:00:50 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:00:50 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:00:51 [6] DHCPD: Recv DISCOVER from 32:3D:E5:A1:B2:03
2016-01-01 00:00:51 [5] DHCPD: Send OFFER with ip 192.168.1.100
2016-01-01 00:00:51 [5] DHCPD: Send ACK to 192.168.1.100
2016-01-01 00:00:51 [6] DHCPD: Recv DISCOVER from 34:03:DE:41:2A:1B
2016-01-01 00:00:51 [5] DHCPD: Send OFFER with ip 192.168.1.101
2016-01-01 00:00:52 [5] DHCPD: Send ACK to 192.168.1.101
2016-01-01 00:00:52 [6] DHCPD: Recv DISCOVER from A4:08:01:58:19:E7
2016-01-01 00:00:52 [5] DHCPD: Send OFFER with ip 192.168.1.102
2016-01-01 00:00:53 [5] DHCPD: Send ACK to 192.168.1.102
2016-01-01 00:00:54 [6] DHCPD: Recv DISCOVER from BC:E9:2F:02:C7:70
2016-01-01 00:00:54 [5] DHCPD: Send OFFER with ip 192.168.1.103
2016-01-01 00:00:55 [5] DHCPD: Send ACK to 192.168.1.103
2016-01-01 00:00:56 [6] DHCPD: Recv DISCOVER from F4:03:2A:5E:3B:10
2016-01-01 00:00:56 [5] DHCPD: Send OFFER with ip 192.168.1.104
2016-01-01 00:00:56 [5] DHCPD: Send ACK to 192.168.1.104
2016-01-01 00:01:07 [5] System: DSL Link Up us/ds 0/0 kbps Type 64/65B PTM Annex B
2016-01-01 00:01:11 [6] PPP: sent [PADT session is 4128]
2016-01-01 00:01:11 [6] PPP: sent [PADI Host-Uniq(0x00000596)]
2016-01-01 00:01:11 [6] PPP: rcvd  [PADO PeerMac(24-21-24-7d-b7-9d)]
2016-01-01 00:01:11 [6] PPP: sent [PADR Host-Uniq(0x00000596)]
2016-01-01 00:01:11 [6] PPP: rcvd  [PADS SessionID(0x1028)]
2016-01-01 00:01:11 [5] PPP: Connected to 24:21:24:7d:b7:9d via interface nas8.101
2016-01-01 00:01:11 [6] PPP: Using interface ppp1
2016-01-01 00:01:11 [5] PPP: Connect: ppp1 <--> nas8.101
2016-01-01 00:01:11 [6] PPP: CHAP authentication succeeded: CHAP authentication success
2016-01-01 00:01:11 [5] PPP: CHAP authentication succeeded
2016-01-01 00:01:11 [5] PPP: peer from calling number 24:21:24:7D:B7:9D authorized
2016-01-01 00:01:11 [6] PPP: Terminating on signal 15
2016-01-01 00:01:11 [5] PPP: Connection terminated.
2016-01-01 00:01:11 [5] PPP: Release PPP unit success
2016-01-01 00:01:11 [5] DHCPD: Send ACK to 192.168.1.105
2016-01-01 00:01:15 [6] PPP: sent [PADT session is 4128]
2016-01-01 00:01:15 [6] PPP: sent [PADI Host-Uniq(0x000005df)]
2016-01-01 00:01:15 [6] PPP: rcvd  [PADO PeerMac(24-21-24-7d-b7-9d)]
2016-01-01 00:01:15 [6] PPP: sent [PADR Host-Uniq(0x000005df)]
2016-01-01 00:01:16 [6] PPP: rcvd  [PADS SessionID(0x1029)]
2016-01-01 00:01:16 [5] PPP: Connected to 24:21:24:7d:b7:9d via interface nas8.101
2016-01-01 00:01:16 [6] PPP: Using interface ppp1
2016-01-01 00:01:16 [5] PPP: Connect: ppp1 <--> nas8.101
2016-01-01 00:01:16 [6] PPP: CHAP authentication succeeded: CHAP authentication success
2016-01-01 00:01:16 [5] PPP: CHAP authentication succeeded
2016-01-01 00:01:16 [5] PPP: peer from calling number 24:21:24:7D:B7:9D authorized
2016-01-01 00:01:16 [5] PPP: local  IP address ###.###.###.###
2016-01-01 00:01:16 [5] PPP: remote IP address 172.16.18.113
2016-01-01 00:01:16 [5] PPP: primary   DNS address 212.159.6.10
2016-01-01 00:01:16 [5] PPP: secondary DNS address 212.159.6.9

What next @Kevin_Z  ?

VR2100 switched back to MODEM.

Welcome back CRC and dropping speed... Welcome back... (from 50/5)

@Zajic That's truly awful - which firmware?

At least my router is maintaining a good speed when not rebooting

Zajic wrote

VR2100 switched back to MODEM.

 

Welcome back CRC and dropping speed... Welcome back... (from 50/5)

@david-m I got special firmware for our country but absolute no help. Now i rollbacked to official firmware. I'm starting to lose patience. I'm starting to regarded as cheating on customers.

(i tested another modem device, information above, VR2100 have big problem)

@TP-Link 

Why can,t you just admit you,ve messed up big time rushing out a router to consumers that was clearly not ready to be released.

Did you actually test this router before release?

Did you not see the problems Asus had with the AC68U router using a Mediatek chipset and they failed to fix them?

TP--Link clearly cannot fix these problems on this router. It has been over a year since release with the same problems it has now so do the decent thing and recall the router?

After going back to the official FW release 1.4.0 0.9.1 v009e.0 Build 201122 Rel.72659n it rebooted after 10 hours. Now it has been stable for 1 day 15 hours but I am constantly waiting for it to reboot during a work video call.