I decided to upgrade the firmware this week to F/W 3.8.2.2 - (576D17 / vector3).
Things seem to working, but not really.

I can't quite put my finger on exactly what's going wrong, beyond webpages coming back blank and various streaming media failing to work. With the occasional "connection was reset" thrown in for good measure.
The problem is, I then switched to F/W 3.8.2.2 - (548006 / non vector) and similar things were happening.
Edit: I'm less sure of this. non-vector is currently stable for me.

My ISP is Plusnet.
Vector3 syncs at around 75k/20k.
NoVector syncs at around 63k/20k.


console output:

Code:

> sys ver Router Model: Vigor2860n+ Version: 3.8.2.2_VT3 English Profile version: 3.0.0 Status: 1 (0x49065e4c) Router IP: 192.168.1.1 Netmask: 255.255.255.0 Firmware Build Date/Time: Feb 19 2016 16:53:47 Router Name: DrayTek Revision: 54455 V381_LTE Current VDSL2 Firmware Version: 05-07-06-0D-01-07 ADSL Firmware Version: 05-07-02-08-00-01 Annex A VDSL2 Firmware Version: 05-07-06-0D-01-07 > vdsl status more Near End Far End Note Trellis : 1 1 Bitswap : 1 1 ReTxEnable : 0 1 <--snip--->

As I understand it, the "ReTxEnable : 0 - 1" means G.998.4 is active downstream and inactive upstream.
Yet the online status shows "SHOWTIME" but doesn't show "Vectoring Active" (as described in http://www.draytek.co.uk/support/guides/kb-dsl-ginp)

I left the vector3 firmware active for 24 hours, just in case it was one of those features the network needs to "train" about the connection. It didn't seem to help.


Any thoughts as to which firmware I should be using (The lack of "Vectoring Active" on the status page is leaning me towards the non-vector version. But I've read posts suggesting vector2 in the UK. etc. etc.

Any thoughts as to why any of these different firmwares might be causing my dropout/latency issues? (I'm guessing I might need to leave the line training for longer, but maybe it's just the fact that I keep swapping and changing firmwares quite so often).

Is there anything I should be asking my ISP? (Again, posts elsewhere seem to indicate the vectoring is on by default, but can be switched off when the equipment doesn't use it).

With vector 3 try disabling hardware acceleration. Pages not loading sounds like it's caused by that