I think we can deduce now:-
There are very few errors on the line
g.inp is enabled ( I don’t know if this is high or low )
The line is on fastpath
With that high SNRM and the attainable much higher than the sync the line is banded.
Others might be able to deduce even more. I would certainly leave this a few days, please avoid anything that might cause a resync ( router rebooting etc)
If those stats remain stable a DLM reset would remove banding, but no point trying to get that until your sure the line / router doesn’t resync ( reset as you have mentioned) or the banding will just be reapplied.
I know John said banding is caused by drop outs / successive resyncs but it's never been the case. The HUB never reset hourly or daily. In post 26 when I linked the latest HUB resets / resyncs it went from 48941, 14 days later 46901, 14 days later 42051. If all of this is banding but my HUB only reset once every 14 days why does the sync rate continue to drop, then band me again? This has been the pattern all along from 70+ Mbps to 40 ish Mbps. I can understand the crosstalk but how can somebody be on fast path but with 10+ noise margin and a way lower sync rate?
Yes, I will leave it for a few days, if it does restart it won't have been by me. Could all of this have been caused by faulty HUB's? I'll post up the stats again in a few days providing the router stays on. An issue may present itself the longer the router is on which should be easily identifiable with all of you observing.
By the way I forgot to do one thing with this router. I applied the firmware update but never disabled the TR-069 John Lewis supervisor thing. I only found this out by reading threads after I had already applied it
. Is this something I really ought to do or should I be fine?