In reply to a post by WWWombat:

For your line, we need to be checking basic stability - that resyncs don't happen, and errors stay manageable...

Unfortunately the firmware I'm using on the modem at the moment doesn't seem to report errors correctly (or at least in the web gui anyway)

I say this as straight away I noticed errors on "Path 1" which don't seem to be in use (What is path 1 and what "could" it bring in the future)

I think the 2ms could be explained in the variance between Plusnet gateways, as you connect to different ones after a resyncs. We'll see from the graphs..

The 10GB file is questionable. The synced modems are constantly transferring blocks of data, even when you aren't downloading. Errors happen anyway, and become part of the stats. A download should make no difference.

Well, that was true before g.INP, and probably remains true ... but we need to observe more to be sure.

Path 1 might be bearer 1, as I described earlier.

But I don't trust the data in the GUI, and would need to compare it with the telnet output to say for sure

But what is path 1 for as currently I only see path 0 in use?

As requested!

http://tinypic.com/r/14iftll/8

If you scroll down your command line telnet print well below the VDSL2 framing section you see lots of settings for Bearer 1. As in this post from an older thread.

Path 0 in the GUI is Bearer 0 in the xdslcmd stats. Path 1 is Bearer 1 but doesn't have a sync. But it is definitely in use when G.INP is activated. Most of us don't see anything to do with Bearer 1 in our xdslcmd output. You didn't in earlier posts.

WWWombat explained what Bearer 1 does in this post .

OK, Thanks for pointing out the information and the post I missed

Easily missed .

I've just realised why doesn't have a sync! There's only one connection. (/me slaps head).

So it just bungs a few packets down the same sync'ed connection, with presumably some identifying field in the packet header. Effective loss of Bearer 0 throughput negligible in most cases, and no doubt DLM would get more excited if it felt there were too many packets on Bearer 1.

That's perhaps why they are only rolling it out slowly, to fine tune the DLM from real-world use.

Edited by RobertoS (Sat 21-Mar-15 23:55:50)

In reply to a post by RobertoS:

That's perhaps why they are only rolling it out slowly, to fine tune the DLM from real-world use.

Well I've become an unexpected trialist for G.INP by the looks of things, could have some local network guys on the phone this week asking questions about my modem!

Specially as my firmware version has had the BT Agent killed so they most likely won't be able to talk to it or even push the firmware back.

do you think g.inp is been made the new default profile? as seeing it been enabled on good lines.