Update.... solved the Syslog problem, albeit the exported log doesn't (probably) show information as the system reboots or restarts...

All the rest of the problems remain and I have a reboot from minutes to hours. Probably 10 a day...

@Kevin_Z I played with the Bridge mode, but need routing, and I couldn't get the VR2100 to pass through internet traffic. It does allow me to connect to my modem (BT SmartHub 2) and local devices but no further...and not the internet. The BT device sees the internet....

Yes this new firmware I installed 6 days ago (Firmware Version:1.5.0 0.9.1 v009e.0 Build 210619 Rel.63114n) helped, router does not reboot randomly anymore.

That was a great and comprehensive article…all the tips enumerated and explained will be helpful for those who are wise enough to tap from it. Any business nowadays without social media signals and presence may not make it to the outermost, and investment too is part of the key to success in business. Keep up the good work.<a href="https://greenteaneko.com/">greenteaneko</a>

Update

Spent a few hours with TP-Link support person from the UK on (Thursday and) Friday. We've now managed to get a (sort of) temporary fudge which uses my BT SmartHub 2  as a dsl modem, and the VR2100 as my network router. Currently all internal addresses have moved from 192.168.1.x to 192.168.0.x which is a pain. This was a learning experience for both TP-Link and me......

The mechanism is to set the VR2100 to wireless router only mode. Plug VR2100 LAN port 4 into one/any of the BT hub's LAN ports. Take your (internal) network traffic from any (or all) of ports 1,2,3 of the VR2100.

Leave the rest of the BT SmartHub 2's LAN ports empty.

Leave the DHCP server running on the BT SmartHub 2 AND the VR2100.

Switch off the BT SmartHub 2's WiFi on both channels and use the VR2100 as your WIFI device.

At this point the only device seen from the BT SmartHub 2 should be the VR2100 router. It's address will look something like 192.168.1.XX.

Open a browser to the BT SmartHub 2 via the normal 192.168.1.254, and to the VR2100 now via 192.168.0.1

I suspect that one needs to set up (and I am verifying this at the moment) a DMZ from the BT Hub, on/to the VR2100 router. That's to get correct routing through (for things like NAS, or RDP) as if the VR2100 was connected directly to DSL. A setup option for this can be found on the BT SmartHub 2.

Although this setup doesn't solve my problems with the VR2100 but I am working to a fashion. Still by no means acceptable as I want to remove the BT SmartHub 2 from my network.

I'm not sure how stable the modem/router is. The best way to confirm reboot is that VR2100 log outputs change from an initial date sometime in 2016, to current (accurate) time synced from the web. I intend to leave my remote Syslog server running to see if we can catch the same behavior in wireless router mode, but I'm not sure we can count on similar log output in the this mode.

BTW, does anyone else use tpPLC app on Android? Mine doesn't seem to find many/all of the PowerLine devices on my network. tpPLC app seems to work better on a windows PC connected to the PowerLine LAN via Ethernet . FYI If you update the tpPLC app on the PC, I've found it doesn't seem to scan correctly without a PC reboot.

Situation update

My VR2100 as a router seems to be stable thus far and as I can tell. BUT only as a router and NOT a modem/router. That's not what I purchased. It seems possible that TP-Link's DSL drivers are at fault; certainly for my implementation (Openreach and BT DSL), which just so happens to be the most prevalent in the UK.

I've been in discussion with TP-Link about a swap-out of the VR2100 for (just) a router but, in true tradition, their customer service has failed again. Now it's their RMA team.

Honestly, has this company never heard of customer satisfaction?

@Kevin_Z I have a VR2100 modem/router and a VR900 Modem/router, both are connected separately to 2 VDSL2 Plusnet services.

The VR900 v3 is rock solid and has been up for over 90 days with no problem at all.

The VR2100 v1 is unfortunately having problems with this reboot situation and even though the beta firmware has been applied it does not work as it should.

I would very much like to swap the VR2100 for another VR900 v3. Can you please facilitate this?

@Dogzdinner unfortunately I need the Mesh facility on the VR2100 so the VR900 isn't an option for me.