@Kevin_Z 

Thank u so much Kevin. Waiting the e-mail.

Just come across this threat, I've also got the VR2100 , Im in the UK and I have exactly the same issue as everyone else, my unit reboots ever 1-2 days for no apparent reason.

Its completely stable and works fine right up until the point it randomly decides to reboot. Ive checked the system logs and it is a reboot as the time resets  to 2016 before it reconnects to the web and re-sync's it time with NTP.

I brought this to replace the default BT Hub 6 router supplied with my internet Line as the BT router has poor wifi quality.

I have put the original BT unit back and it is stable and does not restart, so I assume that rules out the line being at fault. 

Here is a screenshot from the unit an hour after the last reboot

I've also got the first few lines from the system log after the reboot if this helps (I've blanked my id info with xxxxx's)

2016-01-01 00:00:20 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2016-01-01 00:00:30 [5] System: DSL Training
2016-01-01 00:00:41 [6] DHCPD: Recv DISCOVER from 74:75:48:D3:25:B5
2016-01-01 00:00:41 [5] DHCPD: Send OFFER with ip 192.168.0.100
2016-01-01 00:00:41 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:00:41 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:00:41 [5] DHCPD: Send ACK to 192.168.0.104
2016-01-01 00:00:42 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 00:00:43 [6] DHCPD: Recv DISCOVER from FC:A1:83:0E:1C:9C
2016-01-01 00:00:43 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 00:00:44 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 00:00:44 [5] DHCPD: Send ACK to 192.168.0.108
2016-01-01 00:00:44 [6] DHCPD: Recv DISCOVER from 68:9A:87:88:51:82
2016-01-01 00:00:44 [5] DHCPD: Send OFFER with ip 192.168.0.102
2016-01-01 00:00:45 [6] DHCPD: Recv DISCOVER from 34:D2:70:2B:B1:ED
2016-01-01 00:00:45 [5] DHCPD: Send OFFER with ip 192.168.0.103
2016-01-01 00:00:45 [5] DHCPD: Send ACK to 192.168.0.102
2016-01-01 00:00:46 [5] DHCPD: Send ACK to 192.168.0.103
2016-01-01 00:00:48 [5] System: DSL Link Up us/ds 0/79999 kbps Type 64/65B PTM Annex B
2016-01-01 00:00:52 [6] PPP: sent [PADT session is 3181]
2016-01-01 00:00:52 [6] PPP: sent [PADI Host-Uniq(0x0000052c)]
2016-01-01 00:00:53 [3] PPP: Unable to complete PPPoE Discovery
2016-01-01 00:00:53 [4] PPP: Connect script failed
2016-01-01 00:00:57 [6] PPP: sent [PADT session is 3181]
2016-01-01 00:00:57 [6] PPP: sent [PADI Host-Uniq(0x00000601)]
2016-01-01 00:00:58 [6] DHCPD: Recv DISCOVER from xxxxxxxxxxxxxxx
2016-01-01 00:00:58 [5] DHCPD: Send OFFER with ip 192.168.0.105
2016-01-01 00:00:58 [5] DHCPD: Send ACK to 192.168.0.105
2016-01-01 00:01:02 [6] PPP: sent [PADI Host-Uniq(0x00000601)]
2016-01-01 00:01:12 [6] PPP: sent [PADI Host-Uniq(0x00000601)]
2016-01-01 00:01:12 [6] PPP: rcvd  [PADO PeerMac(xxxxxxxxxxxxxx)]
2016-01-01 00:01:12 [6] PPP: sent [PADR Host-Uniq(0x00000601)]
2016-01-01 00:01:12 [6] PPP: rcvd  [PADS SessionID(0x0ca2)]
2016-01-01 00:01:12 [5] PPP: Connected to 20:e0:9c:df:29:c1 via interface nas8.101
2016-01-01 00:01:12 [6] PPP: Using interface ppp1
2016-01-01 00:01:12 [5] PPP: Connect: ppp1 <--> nas8.101
2016-01-01 00:01:12 [6] PPP: CHAP authentication succeeded: CHAP authentication success
2016-01-01 00:01:12 [5] PPP: CHAP authentication succeeded

2016-01-01 00:01:12 [5] PPP: peer from calling number xxxxxxxxxxxx authorized
2016-01-01 00:01:12 [5] PPP: local  IP address xxxxxxxxxxx
2016-01-01 00:01:12 [5] PPP: remote IP address xxxxxxxxxxxxxx
2016-01-01 00:01:12 [5] PPP: primary   DNS address xxxxxxxxx
2016-01-01 00:01:12 [5] PPP: secondary DNS address xxxxxxxxxxx
2020-12-03 08:46:07 [5] DHCPD: Send ACK to 192.168.0.119
2020-12-03 08:46:14 [5] DHCPD: Send ACK to 192.168.0.119

Any comments or suggestions before I arrange for the unit to be returned for a replacement under warranty ?

@plasmahal 

I have been engaged with my ISP after changing over to the plusnet router that they sent me.

I have had similar issues with not the router rebooting but the connection dropping.

They have investigated and said the sent BT openreach to fix a fault at the cabinet.

I am still getting the drop outs.

Once they have resolved these dropouts, I will then return to the TP-link router and see what happens and report back.

@plasmahal 

Thanks for the info, I suspect my Router reboot issue is separate to your issues, Because even if the line was problematic, you would not expect the router to reboot. It should just disconnect the line and then try to retrain. My router is actually rebooting, as per several other people on this thread.  I am hopeing Support might have some comments to make,. I guess we will see..  Thanks again

It's really weird. They have sent me a debug firmware and i have not got a reset issue since 6 days and 22 hrs.

My Firmware Version is 1.1.0 0.9.1 v009e.0 Build 201102 Rel.67451n now.

@naz_eg 

I got a beta version to try earlier, so until I've had it running a few days I won't know if its fixed the issue.. However I'm glad you have noticed an improvment, it bodes well.

F.Y.I  my firmware version now is 1.1.0 0.9.1 v009e.0 Build 201203 Rel.33349n

Not sure how the release number  works but I assume by the build version they must have daily beta builds.. 

I will post to let you know how I get on and hopefully they will release a stable public version soon... 

Cheers

@The-Geek 

Unfortunately it rebooted again :( (after 7 days.)

@Kevin_Z 

Hi again.

I uploaded the new beta fimrware but it rebooted after 3 days again.

Firmware Version:1.1.0 0.9.1 v009e.0 Build 201203 Rel.33349n 

I sent the debug file to Fitz.Peng via e-mail.