Upped to ADSL2+ and still on the dark age

[Rik]

If the speed drops the profile will drop instantly, if you then re-connect at a much higher speed, the profile can adjust within hours. Small changes in speed take longer.

As to James' suggestion, so am I.

[troesma]

OK, if that's the case will shut-down today and every 24 hrs and re-ignite within 30 mins, and see how it goes

I just wanted to keep things stable, un-touched, as it was suggested.

[Rik]

I've just had a word with support. Essentially, both sets of advice are right.

What we need from you is the error count from your router. If there are any then the BT systems will not drop the NM. Being ADSL2+, things are working differently, and although it can take the 15 days that applied to Max, it's also possible the system will react faster. Try re-booting every 24 hours for a few days. If that doesn't work and you have no errors, then go for the 15 day stable connection.

[troesma]

Let me try to check where I can pick that piece of info from the Linksys WAG160... even the stats page is a hidden page inside the router Admin menu (took me a while to pick the way to access it from multiple forums)

[Rik]

Good hunting.

[troesma]

Modem behaves well, but firmware is cr*p.

[Rik]

There's a few like that.

[troesma]

Just did a NEW firmware update (which I did 30 days or so ago from out-of-the-box, factory loaded firmware...)

Some gems...

1.00.14

1.   Fixed wireless dropout issue.

1.00.12
1. DownloadSpeedTest(), DUT web UI(port 80) will be inaccessible if set buffer size to a large number
2. v1.00.11, Wireless, Fail to find wireless SSID after set WPA password with "linksys" (7 chars)
3. GetWLanRadios() cannot return correct WideChannel information
4. GetDeviceSettings2() will return wrong country code for United Kingdom.
5. Fix bug that SIP call can not be initialized from WAN to LAN if the SIP Invite packet of the SIP Server doen't include port information.
6. Atheros driver's changelist from 6.1.1.98 to 6.1.1.111:
   - Add FCC6 for Australia and Canada 5GHz.
   - Fixed problem in broadcast performance.
   - Disabled power constraint element when country IE is enabled on 2.4GHz channels since some stations will misunderstand the Power Constraint element and cause tx power to be set incorrectly.
   - Re-enabled 11n NF periodic Calibration.
   - Fixed a problem where STA cannot reassociate to AP after beacon stuck & HW reset.
   - Enhanced dynamic allocation of TID buffers on ADDBA.
   - Fixed throughput degradation issue during downstream TCP legacy co-existence tests.
   - Addressed multiple BSSID performance issue.

So 2 versions within a month. Nice..! 

[Rik]

Indeed.

[troesma]

OK, re-synced yesterday, did it as per manual   and no improvements. Guess I'm stuck. Think today (or tomorrow) the 5-day period for profile change is due. What the hell...

[Rik]

Try and leave things alone for a few days then and see if things settle. WBC, atm, does seem less stable than ADSL Max for me.

[troesma]

Yup, that was my next port of call. I guess that if the core infrastructure is not up to par (which we know is the case with BT) the roll-out of ADSL2+ is going to be a massive botch-up. Or maybe technology-wise it needs maturity, and we're all paying (sic) the costs learning-by-doing. From a commercial standpoint, I guess the folks at IDNet should think of placing a BIG CAVEAT to anyone thinking of switching-up. I personally don't give a damn about the 12 quid or so for the privilege of checking it out, but maybe others do. So if things don't quite work as expected it smells as a rip-off and I'm certain IDnet is not trying to rip-off anyone. Pure commercial common sense. Just my 2c.

[Rik]

I agree. The testing before launch was relatively small scale, so the real problems didn't begin to show (what the testing did reveal was modem/MSAN incompatibility). ATM, I'd urge caution to anyone thinking of making the move because it looks like there's no way back. From what we can make out, BT do not switch people back to DSLAMs if they regrade to Max, they merely profile the MSAN to behave like Max. That said, the launch of Max was at least as painful.

[troesma]

But that caution SHOULD BE MADE EXPLICIT IN THE SERVICE OFFERING. IDnet has always behaved incredibly well, has always been very reliable, always a friendly advice, a no-bullshit service (hey, I'm one of the earliest users of the service at the time it was starting to pick-up commercially through WOM). In the race for keeping up to pace in terms of offering, which in this industry is equal to speed improvements for most of the potential customer base (ok, no throttling,traffic shaping, contention rates... that's something the more savvy/niche consumer would look into...) I guess a ADSL2+ offering is called for, but if the cost is potentially getting people annoyed... not worth it IMHO.

It takes ages to build a reputation and a second to destroy it. In fact, I would be keen to see on IDNet webpage a message (when someone clicks on the ADSL2+ offer option) a big CAVEAT note explaining, in plan language, the potential issues and saying "you susbcribe knowing there is a risk you will see no speed/service improvement..." particularly if there is no way back, as you say.

No-one cares if the previous experience with MAX was at least as painful. In fact, people would argue "haven't you learnt from it..? you don't burn your fingers twice in the same fire.."

[Rik]

You are preaching to the converted.

[troesma]

Yup, maybe so 

It's just that it would be stupid to see the folks run aground on BT screw-ups.

[Rik]

I preach regularly.

[troesma]

Now Rik, I've seen elsewhere that ISPs now have the option of requesting SNR levels (or "Stability options") on all WBC and IPSC connections, to BT. If that's the case, why not IDnet try to request BT a change to the 9/12db level (which I think is the "Stable" option, dunno if fully determined by the MSAN) and see where it goes. That would get things past-by DLM. Views..?

[Rik]

My margin is set to 9db. That's stable with Max, less so with WBC. Going to 12db would probably reduce my speed below that I can achieve with Max (I was always a 'test case' being at the limits of any potential benefit from ADSL2+).

[troesma]

I could always try to do a DMT tweak at my end, but that's on the risky side... maybe ask IDNet to get BT force things down to 9db and see how it goes..?

[Rik]

BT are generally less inclined to force margins down, but it will do no harm to ask.

[Steve]

ATM, I'd urge caution to anyone thinking of making the move because it looks like there's no way back. From what we can make out, BT do not switch people back to DSLAMs if they regrade to Max, they merely profile the MSAN to behave like Max. That said, the launch of Max was at least as painful.

Doesn't sound like its going to be much fun for those people having problems with adsl2+. I presume eventually there will be no choice as adsl max equipment in the exchange will become redundant?

[Rik]

I think BT are ripping out DSLAMs as fast as they can go, Steve.

[Simon]

So, are we saying that eventually, everyone will have to switch, even if the new service isn't up to the old one?

[Rik]

Yes, afaik.