up and running

Ok guys I was first install of day and first of cabinet, engineer said 80meg sync.

speedtest below.

http://www.speedtest.net/result/2352379963.png

Edited by Chrysalis (Wed 05-Dec-12 09:59:13)

Nice result there.

What does the modem say? Or is it not hacked yet?

If you have not hacked it yet, don't touch it for a couple of days! A friend had his installed last week and when the Technician back was turned he swapped the new modem for one I lent him that was already hacked. He watched his attainable speeds drop several times that day as the same technician did several more installs from the same cabinet including three neighbours who share the aerial span with one in the same drop wire.

I'm just waiting for my regrade - with a 25Mbps upstream attainable, how close to 19Mbps will I get.

also pingtest result (no packetloss due to java issue)

http://www.pingtest.net/result/73395456.png

and yes is great to have 0ms jitter again, ssh is good to use again.

good news is its a HG modem, but I wont be touching it for at least a week if at all. I have decided if all looks great and speedtests indicate full sync I will leave well alone on the modem. Although I still plan to use my own router.

I get 1ms Jitter

http://www.pingtest.net/result/73396603.png

OK, the latency is rather high but 1ms is pretty good.

In reply to a post by Chrysalis:

Ok guys I was first install of day and first of cabinet, engineer said 80meg sync.

speedtest below.

http://www.speedtest.net/result/2352379963.png

Hi Mate,

I'm shocked you've got FTTC already? I thought montfort wasn't enabled for FTTC yet.
My cab (Hinckley road next to the BP Petrol station) doesn't appear to be done...

Does the online checker say its now avilable in your area? mine is still stating dec 31st.

Can you post a ping test from your connection and your VM one if possible would love to see the difference

correct the exchange still says "coming soon"

my determination got it up and running now

check on infinity checker your address (not post code the address).

Or try BT wholesale checker https://www.btwholesale.com/includes/adsl/main.html

Dont use openreach exchange checker.

Edited by Chrysalis (Wed 05-Dec-12 12:22:56)

BT

C:\windows\system32>ping -n 20 bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=15ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=14ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=14ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=17ms TTL=241
Reply from 212.58.241.131: bytes=32 time=15ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=17ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241
Reply from 212.58.241.131: bytes=32 time=16ms TTL=241

and below VM rerouted via route command (as both routers connected to lan)

C:\windows\system32>route ADD 212.58.241.131/32 192.168.1.1 METRIC 5
OK!

C:\windows\system32>ping -n 20 bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=19ms TTL=242
Reply from 212.58.241.131: bytes=32 time=15ms TTL=242
Reply from 212.58.241.131: bytes=32 time=13ms TTL=242
Reply from 212.58.241.131: bytes=32 time=10ms TTL=242
Reply from 212.58.241.131: bytes=32 time=11ms TTL=242
Reply from 212.58.241.131: bytes=32 time=14ms TTL=242
Reply from 212.58.241.131: bytes=32 time=11ms TTL=242
Reply from 212.58.241.131: bytes=32 time=12ms TTL=242
Reply from 212.58.241.131: bytes=32 time=14ms TTL=242
Reply from 212.58.241.131: bytes=32 time=14ms TTL=242
Reply from 212.58.241.131: bytes=32 time=13ms TTL=242
Reply from 212.58.241.131: bytes=32 time=11ms TTL=242
Reply from 212.58.241.131: bytes=32 time=9ms TTL=242
Reply from 212.58.241.131: bytes=32 time=9ms TTL=242
Reply from 212.58.241.131: bytes=32 time=11ms TTL=242
Reply from 212.58.241.131: bytes=32 time=12ms TTL=242
Reply from 212.58.241.131: bytes=32 time=12ms TTL=242
Reply from 212.58.241.131: bytes=32 time=13ms TTL=242
Reply from 212.58.241.131: bytes=32 time=11ms TTL=242
Reply from 212.58.241.131: bytes=32 time=20ms TTL=242

VM the last week or so has been good (for VM standards) 18-20 hours of the day but goes chaotic at peak, although youtube poor 24/7 and dodgy routing 24/7.

I can see my routing to EU servers now fixed on BT and youtube buffers quickly, browsing noticebly snappier as well. Obviously I havent tested BT during peak yet tho.

Early signs are tho the previous noise issues I had on adsl at this address during office hours are not currently surfacing.

Edited by Chrysalis (Wed 05-Dec-12 12:18:04)

Lucky! I work for BT now so I will see what I can do to get myself connected

I updated my reply, use the Btw checker not openreach. Dont tell friends etc. tho so we dont get crosstalk also I am on leics central not demontfort exchange although as I understand it they both been done together at same time.

Edited by Chrysalis (Wed 05-Dec-12 12:25:04)

Thanks results from the ping test look good Thanks for the checker detail, speaking to some people in the NGA team now to see what can be done to get me connected!

whats BTw checker say for you?

also please let us know if you get connected also thanks.

BTw checker says Dec 31st. On the openreach site it shows montfort is accepting orders

yeah I see demontfort updated now but my exchange still "CS".

so your cabinet isnt on yet then.

Just spoke to OpenReach Cab 50 (the one I'm on) is expected to enabled January 2013 , should be a good move over, fed up with the constant VM loss of service, seems to be every month now.

Lucky! I had an AM appointment today - Engineer was a complete no-show!

Zen are getting it re-booked for me..

"Not enough resource" apparently according to BT, funny, at 1PM the engineer was just running a bit late...

Not impressed.

both exchanges now show as available now.

good luck for january.

I unlocked it now.

I am worried I will get DLM's wrath soon tho because after unlocking it seemed to take many attempts to resync and so far DLM has left me alone, I unlocked it to disable QOS as I found out it loses 2mbit of upload performance.

So now I get 18mbit on upload tests instead of 16mbit and also lost 3ms of ping as well.

The stats are better than expected it seems I have a lot of buffer over the max 80mbit sync.

Its was around 110meg attainable down and about 37meg attainable up with a decent 15snr margin. Although the attianable now shows 106meg I think because getting darker.

Interesting about loss of sync when unlocking!

I have a locked and an unlocked modem here and when I did speed tests before both had almost identical results and syc speeds (from BT tester). As to why you are loosing upstream ... strange.

well there would be an obvious loss of sync when turning off, I unplugged the dsl cable when doing this so it was seen as 1 longer loss of sync rather than 2 or more for reboots etc.

When I put the cable back in it flashed and stopped about 4-5 times before staying on. I dont know if the sync process is just much longer on vdsl or it had issues connecting.

Hopefully this wont trigger anything on DLM as I have not had a single disconnection so far, so this will be the first it has seen.

Unlocking itself doesnt affect upstream but disabling QoS (on by default) gains upstream throughput.

Edited by Chrysalis (Thu 13-Dec-12 16:15:59)

Have just re-read your original ... my mind was wandering on another issue at the time.

It still does not make sense though - why would QoS cause a slow down?

I'll try it on mine and see.


Edit:

Interesting ... before I was running at 1.65 Mbps on a 2Mbps service. Remove QoS and it jumps to 1.80 Mbps ...

I shall have to see what happens on Monday when I finally get to the 20Mbps upstream ... I'll talk to one of the tame Tech Support team in Scotland.

Edited by MHC (Thu 13-Dec-12 16:29:55)

I've just disabled it because of what Chrysalis says. Doesn't seem to have affected ping, but these forums seem immediately snappier.

Does that seem logical?

I got the information of here.

http://forums.digitalspy.co.uk/showthread.php?t=1680...

when you toggled it did you lose sync? if not I dont mind turning it on again.

No, I didn't lose sync.

Edited by RobertoS (Thu 13-Dec-12 16:34:55)

ok confirmed no affect on ping, I think the ping changes are because I am on a different routing after a new ip on BT, since I have seen some ping changes from ppp reconnections. But its defenitly affecting upstream throughput.

Edited by Chrysalis (Thu 13-Dec-12 16:40:45)

Yes, I seem to have gained 1Mbps or so upstream. But this snappiness on the forums is new as well. The "post" still takes time, but the preview and things in general is/are flying.

I seem to be getting a fair few HEC errors tho.

But 0 CRC errors which is good.

I'll be better placed to try it out next week ...

I don't have too much experience on QoS - someone must have an understanding of how the queuing and packet analysis works. Maybe it is because it puts everything into various queues before removing them to send whereas without QoS everything goes straight through?

probably yeah, for QoS to work it has to setup some sort of queue system even if there is no QoS rules.

so you going to 80/20 next week? whats your attainable stats.

Edited by Chrysalis (Thu 13-Dec-12 17:03:48)

Finally ... the boss (her consultancy pays the comms bill) has let me move from te 40/2 which we have had for 2 years or so to the 80/20 for an extra £2/month!

Attainable stats are 65/25 at around 450m from the cabinet. Downstream is a little lower than I would expect but the upstream with benefit me as I often max that out running 2x800k feeds to a remote satellite uplink, to the satellite and then down to another location before routing back here.

In reply to a post by Chrysalis:

I seem to be getting a fair few HEC errors tho.

But 0 CRC errors which is good.

Just be mindful that the FEC & CRC error stats as reported in the modem's GUI are incorrect.

The correct ones are obtained via "xdslcmd info --stats" in a Telnet session.

In reply to a post by MHC:

Attainable stats are 65/25 at around 450m from the cabinet.

And there's me with an attainable of 51/12 at about 450m

Anyway, my QOS was already disabled, after two speed tests I enabled it and lost about 0.75Mbps on two consecutive speed tests, disabling increased upload rates to what they were before, so certainly seems to make a difference, but not a lot in my case.

In reply to a post by Chrysalis:

I got the information of here.

http://forums.digitalspy.co.uk/showthread.php?t=1680...

I thought the information about turning off QoS was around the same places that talk about flashing the unlocked firmware. I certainly did mine at the same time back in December last year.

At the time, my SamKnows graphs changed from upstream throughput of 8.7Mbps to 9.8Mbps (pre-80/20 days). Nowadays they're always >19Mbps.

Perhaps this change should be highlighted more, if it isn't well-known.

yeah I think it gives around 10% of whatever the max rate is.

10% would tie in with my result.

About 8.75% here - so not too far away.

Thanks for the heads-up on using the BTWholesale checker - my exchange (Folkestone, Kent) is listed as ready December 2012 but not yet, the wholesale checker says it is available now and Sky have booked me in for a 3rd Jan install!!

In reply to a post by Chrysalis:

also pingtest result (no packetloss due to java issue)

http://www.pingtest.net/result/73395456.png

and yes is great to have 0ms jitter again, ssh is good to use again.

Try using Firefox for the pingtest. My Chrome doesn't do packet loss tests.

attainable rate this morning plummeted some 20mbit/sec down to 90. I dont know when exactly as it isnt been graphe.

also 5 SES and a few thousand crc. The impact on my connection doesnt seem visible tho and right now error count is pretty much 0 again.

So I think this isnt crosstalk but that noise issue I had on adsl is still here, but since I had so much headroom on this connection I hadnt noticed. So I think I got a potential problem when I start getting crosstalk, although I could be wrong and this is simply crosstalk from an install today. But a 20meg drop from crosstalk this quick seems quite bad.

I have already fixed it.

In reply to a post by Chrysalis:

attainable rate this morning plummeted some 20mbit/sec down to 90. I dont know when exactly as it isnt been graphe.

Aren't you running Bald_Eagle1's graphing scripts? They are very good. A big plus is the 1-minute interval logging file.

I am now but wasnt earlier, although I had some trouble getting them to work.

The snapshot graphs dont work just the ongoing graphs.

I am assuming now its crosstalk from a new install but 20meg seems a heavy hit.

For the snapshot graphs run TestStats2.bat

And, it's fine to open the modem_stats.log file in Notepad or similar, as long as you don't do it during the update process and don't Save it back. Just close the text editor. The updating will have kept running while you read.

I know, it wasnt working but now I fixed it.

Upgraded to 20 Mbps upstream and all speedtests are coming in at around 9.4 Mbps. Modem says capped at 20000 kbps and attainable at 24xxx Mbps with 16dB SNR. Turned QoS OFF and no change!

Something odd about my connection - need to find some time to reboot modem, router, switch &c and also try unlocked modem. Then start to investigate.

I've seen this reported once or twice - but I can't recall if it was on here, or on Plusnet's own forum.

IIRC it is a confusing issue, and needs persistence from the ISP towards BT to fix.

What does the BT Speedtester say for the upstream profile? It is almost certainly 20Mbps, but is worth checking first.

Fortunately I am a BT Business customer ... will try the BT tester when I have a wired connection again as it was busy when I tried earlier but modem shows a 20000kbps cap - previously 1999.


Great test! 56 down - I would have expected 60 but is reasonable. Upstream at 3.97 Mbps with a 20Mbps profile. I am going to have some interesting discussions with support later this week. I'll check everything here and try with a locked modem (just in case!) ...

Edited by MHC (Tue 18-Dec-12 11:57:14)

In reply to a post by MHC:

Upgraded to 20 Mbps upstream and all speedtests are coming in at around 9.4 Mbps. Modem says capped at 20000 kbps and attainable at 24xxx Mbps with 16dB SNR. Turned QoS OFF and no change!

Something odd about my connection - need to find some time to reboot modem, router, switch &c and also try unlocked modem. Then start to investigate.

so you havent unlocked your modem instead you swap out with an unlocked? is there a reason you do this?

I have wondered since unlocking if the shipped firmware is a newer version with any bug fixes than the unlocked firmware, we dont know as its locked.

The throughput been stuck at under 10mbit wont be down to QoS either, that looks like a mismatched profile somewhere throttling throughput. Since the SIN's tell isp's to run their own profiles and your openreach profile is at 20mbit its logical to assume the BT retail profile is stuck.

Edited by Chrysalis (Tue 18-Dec-12 12:33:49)

Spell checker changed it! I originally typed un-unlocked and thought I changed it to locked ... balancing the laptop on my arm and typing is not ideal!

I'm running unlocked and have tried with QoS enabled and disabled. Plan to try a locked modem - just in case and to prove it is not modem related.

I think unlocking the Huawei only changes the firewall setting from "BT" to Standard.

Just want to test with a second to make sure that all at my end is "clean".

Have just hit the "10 day training period" wall! Even though te CS adviser acknowledged that 3.5 Mbps was rather low for a 20 Mbps service where attainable rate is ~24Mbps

They will probably have to update the BRAS profile by hand for you.

Probably - but I need to demolish the "10-day wall" first!

The fault is certainly *behaving* like there's a mismatch of profile somewhere, but most ISPs don't employ one in the upstream direction. There aren't any compelling reasons for having one.

4Mbps is a strange number too.

Have you checked with a different computer, or tried altering the RWIN or other TCP settings?

Didn't somebody discover that there antivirus was causing a similar problem, not sure if it was affecting upload or download though.

So far just one PC ... I don't believe I can change RWIN on Win7.


AV is currently MSE on this one ...


I will get a chance on another PC later one.


The graph in Task Manager is nice and flat acosss the top - just the normal ripple with no large spikes or troughs so it suggests it is coming through at a constant rate.

Have tried a couple of other PCs and get the same results. BT Speedtester is around 3.5 Mbps and various recent tests on speedtest.net, tbb (Java and Flash), & visualware give 9.3 to 9.5 Mbps.

Even running two concurrent tests give a combined result of about the same figure.

Something is STUCK!

Agreed. That's an ISP issue then...

yeah that was based on just the 10mbit.

now he needs to test wired on something like a parted magic boot media.

Have just been through check with different modems, different routers, different local IP ranges (mine is non-standard and not one of the normal defaults). Connected direct to router with no switch in the network and just a short cable ... Different PSUs to the modem and anything else that came to mind!

9.3/9.4/9.5 for every test ... Modem still shows attainable as 24141 with 15.2 SNR margin and 20000 line rate!

I have proved it is nothing here so it must be back in the BT systems somewhere! As I said before - I need to demolish the "ten-day wall". A CS tech I spoke to earlier obviously recognised it as a problem and has scheduled a call back for next Thursday - and with their reputation it will happen.

So, twiddle my thumbs and wait.

16Mbps would make some work a lot easier !

Ridiculous making you wait, when DLM has pretty much sorted itself out by 2 days.

Pointless bureaucracy.

I know and I feel the CS Tech knew too ... I'll let them use their rules but have just filled out a satisfaction survey. It detected I was unhappy and asked for my contact number so they could call me!

Plusnet have often reported "an anomaly" in the IP Profile system when users have has similar problems to this. Sometimes they refer to the system being out of balance.

From what I gather, the BTW system holds the IP Profile at two places, not just one. (This is nothing to do with the Plusnet copy IP Profile system though that is relevant to Plusnet users).

The BT Speed test reports one of these, but the other seems to be the controlling one. The two can occasionally fail to be the same. When PN detect this from some diagnostic they can run, they request a rebalancing (of the IP Profile?). That fixes it.

Just a case of wait and see ...

http://forums.thinkbroadband.com/fibre/t/4190470-re-...

In reply to a post by RobertoS:

Plusnet have often reported "an anomaly" in the IP Profile system when users have has similar problems to this. Sometimes they refer to the system being out of balance.

From what I gather, the BTW system holds the IP Profile at two places, not just one. (This is nothing to do with the Plusnet copy IP Profile system though that is relevant to Plusnet users).

The BT Speed test reports one of these, but the other seems to be the controlling one. The two can occasionally fail to be the same. When PN detect this from some diagnostic they can run, they request a rebalancing (of the IP Profile?). That fixes it.

Hi MHC,

I'll be happy to have a look over your connection and see where the problem lies.

Could you drop me in an email please so I can have a closer look?

http://bt.custhelp.com/app/contact_email/c/4950

Cheers

Craig
BTCare

He's a BT Business user Craig.

A nice offer but as BatBoy has already said, it is a business account and I believe you cannot access those. I'll get it sorted in the next few days ...

Hi Badboy,

Yup so I seen we can forward this to our BT Business colleagues..

ta

Craig

Hi Craic,

Always happy to put you straight..

LOL, I just knew when he spelled your name wrong something would be coming.

Edited by R0NSKI (Wed 19-Dec-12 22:53:51)

In reply to a post by BT_Care:

Hi Badboy,

Yup so I seen we can forward this to our BT Business colleagues..

ta

Craig

I see you understand BatBoy's real personality! Just don't call him BattyBoy.


I have a call back scheduled for next week - and don't have too much time this week to deal with it, and I can suffer a few more days!

attainable rate took another dive, this time large again and on the upstream.

now attainable is lower than 80 meg is 73408 and upstream dropped to 23718

so in less than a month I have gone from 110meg down to 73meg down and 36meg up to 23meg up.

The change I think happened at 10am this morning, Obviously since the attainable went below my previous sync it now means I have a new sync as well.

In reply to a post by Chrysalis:

Obviously since the attainable went below my previous sync it now means I have a new sync as well.

Not necessarily. My attainable on downstream sometimes went below sync when I was on Fast Path, no chance at all of course on interleaved. Upstream sync currently 14933, attainable 14613.

More likely whatever noise has hit you caused a low resync and also a low attainable.

You have the logging going now don't you? It can be interesting to watch the attainable varying all the time, and relate that to what the noise margin is doing. You could page back to whatever happened and check the figures just before and after.

You do seem to have a messy d-side .

I meant a resync.

If my long term sync drops to the estimated I can deal with that as thats what was estimated and still a good speed, my concern however is how fast this has dropped in a 2 week period and DLM, I spoke to the engineer today and he said has been 6 installs including mine and one this morning, and the cabinet can hold another 120 or so.

I havent been logging 24/7 and over the course of the day whenever checking the attainable has been only slight variance of a few hundred kbit. The 2 drops have been sudden large drops and confirmed as installs by my engineer and yes I have his number as he asked me to report back to him how my speeds are and ip profile.

If it was temporary noise my snrm would go back up after the noise has gone away. My new graphs from the modem show increased quiet line noise across the board, and less available snr (not snrm) on the higher frequencies from about 1/3 onwards.

So I am now waiting for vectoring

Edited by Chrysalis (Sat 22-Dec-12 20:49:38)

In reply to a post by Chrysalis:

The 2 drops have been sudden large drops and confirmed as installs by my engineer and yes I have his number as he asked me to report back to him how my speeds are and ip profile.

That's grim. Still points towards a d-side issue to do with the other d-sides, giving abnormally high signal distortions. Wouldn't that tie in with your ADSLx troubles?

If it was temporary noise my snrm would go back up after the noise has gone away. My new graphs from the modem show increased quiet line noise across the board, and less available snr (not snrm) on the higher frequencies from about 1/3 onwards.

Agreed.

I get the impression you are only running the snapshot script by Bald_Eagle1. I strongly recommend the 24/7 logging one instead. That doesn't stop you running a snapshot if you like at any time. The instructions are on page 5 of the setup pdf.

I was running just the snapshot, I am not going to run the 24/7 forever.

Also I need to set it up on anothe rmachine really rather than this one if I am for long periods. I have had it running the last several hours tho to see how stable things are after the recent change.

The guy who wrote the hg612 firmware page suggested that the QLN graph can be used to diagnose crosstalk and that does seem to suggest its crosstalk as well, it has almost across the board quiet line noise increase, approx doubled noise.

I do agree with you tho there may well be an issue d-side thats making crosstalk more severe than average. But its not like I will be able to report it as a fault, as I am not even supposed to be aware of my attianable so as far asBT are concerned my sync has dropped 10% and is still above the estimated speed. Is there a MSR figure on FTTC that protects me against extreme drops in future tho?

Also of interest is that to protect adsl2+ lines the frequency that clashes with adsl2+ has massively reduced power output so vdsl2 to protect adsl2+ sacrifices a chunk of the strongest part of its signal. This I have no isse with tho but its interesting because if the day comes adsl is removed as a product then I would assume they would increase this power again.

The adsl troubles I had were e-side noise bursts during office hours, no signs of those on this service.

Edited by Chrysalis (Sun 23-Dec-12 01:28:47)

In reply to a post by Chrysalis:

Is there a MSR figure on FTTC that protects me against extreme drops in future tho?

No. There is a blanket minimum of 15Mbps, provided you got more than 15Mbps in the first place.

It is strange that there is nothing related to either the initial speed, or the estimate.

Also of interest is that to protect adsl2+ lines the frequency that clashes with adsl2+ has massively reduced power output so vdsl2 to protect adsl2+ sacrifices a chunk of the strongest part of its signal.

Yes. When the cabinet is closer to the exchange, the "power mask" limits the power less but over a wider frequency range. If the cabinet is further away, the mask causes a higher power reduction (of VDSL2) but over narrower frequencies.

It is one aspect where the distance from the exchange *does* play a part in the speed you can get

This I have no isse with tho but its interesting because if the day comes adsl is removed as a product then I would assume they would increase this power again.

It would have to be removed as a product from all LLU's, and then dismissed as a possibility by NICC too. I think we'll get FTTP first...

you think the closer to exchange masking is more generous?

TBH, I don't know. I've never been good at reading log graphs.

I *suspect* that the different masks make it better for those cabinets that are further away, as I think those lines can make more use of the frequencies that are no longer usable by exchange-based ADSL. But it is no more than a gut feel, and I could easily be wrong.

I found a really good thread here with people posting stats and some with openreach screenshots that show line length, it would appear every 2db or so of attenuation on D1 equates to around 100m line length, which would suggest my copper length is not 200m but more like 500m as my D1 attenuation is 9.6db.

this guy has attenuation slightly higher than me and the openreach device shows 0.5km.

http://forums.overclockers.co.uk/showpost.php?p=2137...

his attainable is much higher but more reading also shows people with much lower attenuation at similiar distance also, there is huge variations which I am guessing is down to crosstalk in localities excluding the people with ali d-sides.

I wonder where the line routing goes with it been over double the direct distance. The cabinet is on the same road as me so maybe it goes up the couple of side streets first that are en route.

I've estimated my distance as 450 meters, never got any engineers to measure it though. I was getting about 50 meg when first connected but then interleaving kicked in and I dropped to 40, which has slowly increased to 45 with an attainable of about 51, I was the first on the cabinet and don't seem to be affected by cross talk, unless the intial drop was due to it. Either way my speeds have always been less than the average for my distance, which is about 60, my estimate is 57. And my neighbour tells me he gets about 55 on speed tests, but I've never managed to get his line stats.

In reply to a post by Chrysalis:

I found a really good thread here with people posting stats and some with openreach screenshots that show line length, it would appear every 2db or so of attenuation on D1 equates to around 100m line length, which would suggest my copper length is not 200m but more like 500m as my D1 attenuation is 9.6db.

That'll be interesting, but I'll have to look later. I think the numbers are off though...

To compare, my current line has D1 attenuation of 11.4 dB, but is only 400 metres. That's my measurements, rather than anything produced by an engineer. Unknown age or condition.

My previous line had D1 attenuation of 14.1dB, and was 550m (measured by me), and was reported to be 550-600m (as reported by the installer's test equipment). The D-side of that line was definitely only 16 years old.

Perhaps you're closer to 300m, rather than 500m.

spanner thrown in the works.

one thing is I am fairly sure its much longer than 200m, or its ali or something affecting attenuation.

So my current sync is probably normal after crosstalk is in affect.

andruec has posted a graph with what you described, his early blocks have less power reduction in fact the first blocks seem to have none, so I counted the missing spaces on his bit graph which I think were lost due to the power masking and then counted mine and in my opinion I lose more so it seems if closer to the exchange there is less of a penalty for adsl crosstalk protection.