Allow them to be migrated, then ask that they be given an up to 8 profile.

Openreach run no hardware for ADSL2+ on 21CN, the MSAN is ran by BT Wholesale, openreach just provide a copper line

In reply to a post by MrSaffron:

Openreach run no hardware for ADSL2+ on 21CN, the MSAN is ran by BT Wholesale, openreach just provide a copper line

openreach do the home visits and probably provide stats from those visits on what they think are home wiring faults.

It is still the case, as long as your router allows you to do it.

I force ADSL2 instead of 2+, simply for stabillity.

In reply to a post by Chrysalis:

openreach do the home visits and probably provide stats from those visits on what they think are home wiring faults.

And your evidence that the stats are wrong is?

In reply to a post by BatBoy:

In reply to a post by Andrue:

Perhaps it is but I keep an eye on the graphs as part of my job

Er, nice job.

Lol, it's not a major part. Mostly I develop software however someone in our office has to be responsible for the connection and I volunteered.

In reply to a post by WWWombat:

Hmm. Is this a problem whose nature is being masked by the bonding?

What is the likelihood that, when one line resyncs, the other does so at the same moment?

If one line resyncs alone, then what happens to the ICMP packets? Are 50% routed to the wrong modem, and lost forever? Or is the routing smart enough so it appears like (just) a loss of 50% capacity?

Either way, a sync on one of the lines is not going to look the same, on the TBB graphs, as "standard" broadband.

That's my theory as well - it explains why the graph goes 'mostly red and blue' rather than entirely red.

@Andrue: What happens when you deliberately turn one modem off, and leave things running on the other one? Has this been tried before?

It's being tested now. So far the results are intriguing. I unplugged just one line and didn't bother to reboot the modem (it's a single modem with dual cards). Throughput has dropped (well duh) but that's all. No errors, no horrible ping.

Edited by Andrue (Thu 11-Oct-12 09:05:45)

In reply to a post by Andrue:

It's being tested now. So far the results are intriguing. I unplugged just one line and didn't bother to reboot the modem (it's a single modem with dual cards). Throughput has dropped (well duh) but that's all. No errors, no horrible ping.

I plugged the line back in, waited a minute then unplugged the other one. That caused a reaction. Killed the connection in fact. I've rebooted the modem now and it's back (on just the other line).

In reply to a post by Andrue:

In reply to a post by Andrue:

It's being tested now. So far the results are intriguing. I unplugged just one line and didn't bother to reboot the modem (it's a single modem with dual cards). Throughput has dropped (well duh) but that's all. No errors, no horrible ping.

I plugged the line back in, waited a minute then unplugged the other one. That caused a reaction. Killed the connection in fact. I've rebooted the modem now and it's back (on just the other line).

By "Killed", I guess you mean that the TBB graph went totally red? Rather than the red/blue combination?

I presume it was done just before your post, and I can see the top to bottom red that I normally associate with loss of connection.

There was a 1 hour segment of mixed red and blue 6:40 to 7:15am today and what looks to be fairly standard busy office until the early evening.

When you unplugged the connection initially did the connection continue to operate? If not then other than more capacity the service does not seem to provide redundancy.

Reconnecting the line should not normally need you to reboot the modem. I do this a lot when swapping around review hardware, and a reboot is very rare, unless I have been tinkering with settings and getting things wrong