Do the stats shed any light on the disconnections? If I can get a handle on that I can then look at what the DLM is doing.

Well, maybe.

AS is the number of seconds the router has been powered up and unless I've pressed a wrong key on the calculator on my phone calculator that's about 70 days.

That means over 2.3 million RSCorr (Corrected errors) per day, plus another 22,000 RSUnCorr. That's pretty high. If a lot of them are occurring in a short burst they would cause a disconnection. Spread evenly over the day I would expect (on FTTC) that they would be unnoticeable.

This is where the monitoring programs come in, as the idea is to have them running 24/7. They would show when the errors are occurring. When I was running them for several months I put an old laptop next to the router, which is next to the modem. In your case, if you have a spare computer and there is room by the modem you could just connect that into LAN2. If not, I think your best bet is HomePlugs as mentioned before, to get the monitoring data up to the router.

Depending what cable you are using to get the VDSL2 signal up there may be a pair in that you could use instead.

I was hoping to be able to run dslstats headless on my raspberry pi but it doesn't seem that that's possible. I have started it running and it's recording now. Should I reboot the modem and start a new recording or just leave it running now?

Just leave it running. Unless you'd find it easier looking at smaller numbers.

I don't know the dslstats one really, it didn't exist when I started using Bald_Eagle's.

Edited by RobertoS (Sat 17-Jan-15 00:57:16)

I have had dslstats running since last night. Here are some graphs for FEC, CRC, and ES errors:

http://imgur.com/a/wQSWU