Am I on my way to 3db

Had a resync today at 10am and now margin is 5db with a sync of 68. Last resync was on 20th which was when my new cable was put in. So 5 days and my target seems to have dropped to 5db. Am I on my way to 3db? No ES down and about 40 up per day.

New sync: 73353/19070. Margin: 3.9db

Nice . Good to see the sync values as things progress.

dB made up from deci and Bel with a capital B when written out in full it is usually decibel but when abbreviated dB.

Edited by MHC (Thu 27-Apr-17 09:15:07)

Question is will it now go from 4dB to 3dB as ES is beginning to creep up as can be seen on MWDS. I suspect not.

i hope i get put on 3dB it would mean my sync of 80/20 will be once again. currently at 71/20.

Seen a few with 3db and a decent amount of ES. You never know

If they become extremely high, it could have the reverse effect and go back up also.

What was your sync before all the work was carried out by openreach? (I have forgot now).

Sync was 46m on my modem and 40 on BT tester before new cable. MWDS is showing a red light for standard which I believe Talk Talk use so it may as you say put my target back up. Seeing 1000 ES today and the odd drop in snr to 2.8db but I think target still at 4db sync 73.

Seems to take DLM a couple of days to act.

Looks like a re-sync just occurred at 13.31 taking my target margin back to 5dB and 68 sync. Still that's better than 46 when I started this FTTC journey.

Named after Alexander Graham Bell, originally from Edinburgh.

https://en.wikipedia.org/wiki/Decibel

I also am accustomed to using "dB".

Looks like DLM is trying again after 8 days uptime, target seems to be now 4dB after a re-sync at 11.30. Seeing some errors but not as many as before, sync is 70986.

May be checking to see if what it didn't like at 4dB was a temporary or solid problem.

Well it is definitely trying again. Tenacious little algorithm it is.

It has Dalton-teeth.

Interesting seeing how the noise margin has made an impact on the sync speed per 1db decrement.

Your line looks very similar to mine, apart from mine has been trashed by the dodgy HG612 rebooting and locking up.

How do you access the line stats on the 9970 when it's bridged? Lan cable directly into?

See reply in other thread, either lan cable or wireless.

Am now on 3db with sync of 73923 but errors have shot up and MWDS is showing amber for DLM.

That was short lived, DLM put me back on a 4dB target early this morning after a grand total of 1800 ES/24.

DLM is trying 3dB again just had a resync at 4 pm and sync went up to 73598 but suspect it will be short lived as errors are increasing as well.

Dumb Line Management.

MWDS DLM indicator already amber and errors up to 250 in the space of 2 hours.

One thing I have noticed is that my router doesn't pick up the drop and PPPoE session stays active so the profile or whatever TTB are using doesn't adjust. I have to manually drop the PPPoE session on the router to get a new profile to see new speeds when DLM resyncs.

So that was short lived back to 4dB and sync of 70126. Wonder if DLM will keep trying 3dB ad infinitum?

I think I may be at last.

MDWS HappyBunny 13:37

Yes seems to be rolling out widely now, have seen a few on Kitz getting lowered. I notice you have 1 ES @ 5dB.

Using telnet I'm seeing some on upstream. None on downstream since it reconnected. (Since Link time).

Edited by RobertoS (Sat 10-Jun-17 16:13:51)

I saw one on DS on MWDS after re-sync using the 24 hour option on the graph (yellow line) also check DLM monitor on MWDS says 1 ES on DS.

Seeing as all DSLStats does is read the telnet figures for errors, and pbParams for other info, plus perhaps a few other commands for background data, I don't see how the "Since link time" in my recent telnet xdslctl can have removed it .

The one you see, (in red on my display as I have Blue theme) is before the re-sync. I now have 4 on the upstream, zero downstream. See the bottom section or errors "Since Link time = 3 hours 53 min 59 sec".

> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 12878 Kbps, Downstream rate = 66691 Kbps
Bearer: 0, Upstream rate = 12878 Kbps, Downstream rate = 65740 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.0 6.0
Attn(dB): 19.3 0.0
Pwr(dBm): 13.5 7.4

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 54
R: 10 16
S: 0.1182 0.5876
L: 17193 3458
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 72 0
TxQueue: 18 0
G.INP Framing: 18 0
G.INP lookback: 18 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0

Counters
Bearer 0
OHF: 0 1770438
OHFErr: 0 4
RS: 473260256 95563656
RSCorr: 23222 7
RSUnCorr: 0 0
Bearer 1
OHF: 874023 0
OHFErr: 0 0
RS: 8739611 0
RSCorr: 15 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 153 0
rtx_c: 149 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 65749 0
errFreeBits: 1285380766 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1774847457 0
Data Cells: 1760150 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 27 335
SES: 10 0
UAS: 142 132
AS: 14040

Bearer 0
INP: 50.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 7.96
OR: 0.01 32.14
AgR: 65807.38 12910.26

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 10627/11020 6/6

Total time = 15 days 8 hours 31 min 44 sec
FEC: 8819413 548
CRC: 585 344
ES: 27 335
SES: 10 0
UAS: 142 132
LOS: 1 0
LOF: 9 0
LOM: 0 0
Retr: 4
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 1 min 44 sec
FEC: 17 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 159 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 8 hours 31 min 44 sec
FEC: 28311 8
CRC: 562 11
ES: 10 10
SES: 10 0
UAS: 33 23
LOS: 1 0
LOF: 9 0
LOM: 0 0
Retr: 1
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 735742 19
CRC: 0 17
ES: 0 18
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 3 hours 53 min 59 sec
FEC: 23222 7
CRC: 0 4
ES: 0 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

Well there is definitely 1 ES at 22:00 today. Not that that's a lot.

Yep.

The graph and DSLStats are upstairs on my old machine next to the router. The graph I think only records hourly totals? I haven't been to look at this one. Stats

SNR (dB): 5.0 5.9
Attn(dB): 19.3 0.0
Pwr(dBm): 13.5 7.5

Since Link time = 10 hours 24 min 29 sec
FEC: 744729 14
CRC: 1 5
ES: 1 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0

Edited by RobertoS (Sun 11-Jun-17 00:04:46)

Be interesting to see if the ES stay as low on 4 and 3dB. Mine is fine on 4dB but struggles on 3dB with ES into thousands and DLM takes action.

How long does it take between steps, once it has started? IIRC yours was 1-2 days?

Yes 1 or 2 days but then I got a gap of 14 days when DLM reversed the 3dB to 4dB and then tried 3dB again after a couple of days.

Just dropped to 4dB, at about 15:31.

Your sync nearly on par with mine.

Something badly wrong though . I'm getting around 60MBps repeatedly on BTW test and thinkbroadband. With a dreadful graph.

The BT Performance test will not retrieve my IP Profile, and my AA Radius log is showing BTW reporting linerate=65127000/12747000 to them. Which AA then cut to 98.167% to give their max throughput.

That linerate misreporting is exactly what happened when the line was capped. Far below the sync my modems were showing. (2 x HG612, 1 x Zyxel, 1 x Vigor 130, and this Billion).

Looks like contacting AA time . But they can't see my modem of course. Only the BT Wholesale figure.

Now tbb now
and
Sunday 14 May when the sync was 64513. (I think that was when I had a high sync from being first to reconnect after a cabinet power cycle).

Edited by RobertoS (Mon 12-Jun-17 17:00:14)

Could this be the reason for the line rate being misreported?

https://community.plus.net/t5/Fibre-Broadband/Massiv...

That TBB now speed test looks rough I would let the experts at AA know as that is why you are paying a premium.

It could be Ian, but a quick flip through that looks as if it's to do with banding? Which does cause it. How or why I never found out when it happened to me.

However my line isn't banded, else the syncs would not be normal type and DLM would not be taking me down the lower noise margin path.

I have emailed AAISP support with the details.

Thanks for the link.

I sent them an email at 17:18 Tim . We shall see.

I was wondering if you were on the "Retransmission high" profile which would back up ejs's thoughts.

Be interesting to see what AAISP come back with.

Any idea how to tell please?

A GEA test will show the profile, this was mine not so long back

0.128M-80M Downstream, Retransmission Low - 0.128M-20M Upstream, Error Protection Off

Had this issue when I was on Plusnet recently - only 91% of sync shown by ip profile and throughput a bit lower than that. No banding, was on G.inp retransmission high according to Plusnet GEA test.

On sky ATM but still in initial period waiting for g.inp reactivation. Hopefully problem won't reoccur.

Ta. I'll see what they have to say, and ask them about that.

I can't see it being high though. It wouldn't make sense on G.INP and lowering my noise margin to add over 3Mbps each step. Which could only increase error/retransmission rates and is counter-productive when the loss of speed caused is 68952 - 65127 = 3825Kpps. Insane even .

No huge retransmissions below. I'll have a look what MDWS has later, see if I can find history. (HappyBunny if you want to have a look).

xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 12714 Kbps, Downstream rate = 70047 Kbps
Bearer: 0, Upstream rate = 12747 Kbps, Downstream rate = 68952 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 4.1 6.0
Attn(dB): 19.3 0.0
Pwr(dBm): 13.7 7.4

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 53
R: 10 16
S: 0.1127 0.5936
L: 18033 3423
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 76 0
TxQueue: 19 0
G.INP Framing: 18 0
G.INP lookback: 19 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0

Counters
Bearer 0
OHF: 0 2957672
OHFErr: 0 0
RS: 822329992 156705746
RSCorr: 591396 1
RSUnCorr: 0 0
Bearer 1
OHF: 1447906 0
OHFErr: 0 0
RS: 14478443 0
RSCorr: 10 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 1477 0
rtx_c: 1195 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 1 0
minEFTR: 68947 0
errFreeBits: 1475878493 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3083825067 0
Data Cells: 14467982 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 38 362
SES: 20 0
UAS: 175 155
AS: 23259

Bearer 0
INP: 50.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 7.89
OR: 0.01 32.42
AgR: 69022.53 12779.59

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 18287/19730 391/394

Total time = 17 days 12 hours 59 min 34 sec
FEC: 11327246 600
CRC: 1125 374
ES: 38 362
SES: 20 0
UAS: 175 155
LOS: 2 0
LOF: 15 0
LOM: 0 0
Retr: 5
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 14 min 34 sec
FEC: 83634 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 89662 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 12 hours 59 min 34 sec
FEC: 615289 7
CRC: 539 3
ES: 10 3
SES: 10 0
UAS: 33 23
LOS: 1 0
LOF: 6 0
LOM: 0 0
Retr: 1
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 896353 30
CRC: 0 20
ES: 0 17
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 6 hours 27 min 37 sec
FEC: 591396 1
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

Edited by RobertoS (Mon 12-Jun-17 22:00:17)

No response from AA? I went on to IRC web chat and one or two engineers were there when I had my problem with single thread speeds to ask for advice and see if it was related to their problem but it turned out to be networking on Windows 10.

I don't like their IRC. I looked at it a few times long before i migrated to them.

I'll rely on email .

Got a reply this morning.

Interestingly there was another re-sync still at 4dB at 02:15 today. I think DLM is also tuning the upstream to eliminate the error seconds on that.

Don't know if you're aware but your MWDS has been down since 10:27.

Damn!

Thanks Tim . I paused DSLStats and RouterStatsLite to run some speed tests, as I feel they can cause wobbles. Then forget to restart them .

Running now.

No useful response yet from AAISP . I pointed them to my post in this thread about it and I have stats, along with an extract from their own Radius log for my line.

They did give this - Down:65.9 (63.6/64.2/69.5) Up:12.8 (12.7/13.0/13.0)
2017-05-31T09:15:00 0.128M-80M Downstream, Retransmission Low - 0.128M-20M Upstream, Error Protection Off

which simply shows the problem but with the useful confirmation the line is on an open profile. Which rules out the "Retransmission High" theory from the Plusnet thread.

They seem to have ignored my earlier evidence asked for a screen shot of the Billion stats, and asked if I was sure I was looking at the sync, not the attainable. Bah !

That's just a summary. I don't think the full emails should be published. I replied with the full stats and why trying any of the other modems I have was either not wise, or pointless.

Thought it might be something like that.

I have found with my WD9970 that with the stats hack or accessing it via wifi that the router goes to sleep around every hour. Still not sure if it is the router or windows networking again as I am running a separate dongle for stats over wifi.

Been looking for a cheap second hand Billion on eBay but none come up yet.

Thanks for posting what you got back but did you notice the profile was dated 31/5? Have you not resynced since then?

Hmmmm . Thanks Ian. You're right, I didn't spot that.

I see the time is 09:15:00 as well. I have this post holding my sync at 09:29, 63679/13080Kbps in my sig. My previous one was 30/05 at 23:34:55 with the same figure.

I shall be making a less than happy comment to them tomorrow later today.

The person dealing with the case was similarly hopeless last time I had an issue. I shall check back before emailing them, as I think it was the same trouble when I had banding.

Edited by RobertoS (Wed 14-Jun-17 00:31:37)

Hows the speed test now and have you tried any other testers?

I use BT Wholesale and tbb. Both looked a lot better in terms of evenness, but not good, and around 61Mbps which was much slower.

Are you on a BT Wholesale circuit? If so, what are your sync and IP Profile? Have you ever checked they match?

I am on TTB -> Daisy -> Uno. I would have to ask Matt but TTB must have a similar profiling system as my router doesn't notice sync drops and I have to manually drop PPPoE session in the router to get new speeds when DLM resyncs my line.

There are some parameters in the router called Internet Detection set to PPP Echo, Echo Interval set to 6 and Max Echo set to 10. Maybe playing with those will get the Asus router to detect sync drops.

Thanks Tim.

I might ask more when I wake up.

Any further forward Bob, how are speeds now?

I haven't checked Tim. Pointless really until I get some action from AAISP, which I have doubts about.

The sync is still as per that surprising re-sync still on 4dB margin, and which I'm now sure was aimed at some minor DLM tweak to eliminate the upstream errors. Which until this last quarter of an hour it had succeeded in doing.

I'm too busy with "life" to spend time tracking back to my previous similar problem which they did not solve. But I did by getting a DLM reset by other means.

I'll probably come back ti it, but it may be in three weeks, as I'm away fro a fortnight from Friday morning. I usually turn the modem/router off, but I shall leave it on with DSLStats running, so MWDS should update and I can watch that aspect.

Unless as happened last night, Microsoft decide to do a forced reboot of that computer. That's what caused the breakdown of DSLStats. I'll have a look later to see if it has a "Start on boot" option.

Oh ok, well AA have gone down in my estimation after your experience. Uno is similar get the wrong person and nothing happens, get Matt and you get things moving.

Anyway, enjoy your hols. and no thinking about broadband matters while you are away.

I do think it is one person. It's the same one as before.

Thanks for the good wishes .

My sync and target are now on par with yours. I had an unexpected re-sync today and my sync dropped to 69587 with a 4.1dB target. It was relatively unexplained how I was getting 71½ sync at 4.3dB the last few days. Ho hum such is FTTC.

hey guys,

I've had fibre since June 5, and I am getting these stats. Out of curiosity is the noise margin acceptable?

Data rate:
20.00 kbps / 79.99 kbps

Maximum data rate:
20000 / 119965

Noise margin:
16 / 16.5

Line attenuation:
14.1

is the noise margin acceptable?

Yep

Maximum data rate:
20000 / 119965

You'r quite close to the CAB with an attainable of nearly 120 Mbps

That margin over the default of 6 dB is "spare" and your line could pick up 10 dB of extra noise before you are down to the default.

Ian

Whereabouts are you located? Interested to see if the xDb rollout has extended over the area it initially covered.

In reply to a post by ian007jen:

is the noise margin acceptable?

Yep

Maximum data rate:
20000 / 119965

You'r quite close to the CAB with an attainable of nearly 120 Mbps

That margin over the default of 6 dB is "spare" and your line could pick up 10 dB of extra noise before you are down to the default.

Ian

Ohhh that sounds good, I was rather worried over thinking everything. But thanks for clearing that up. It's good to know I could nearly get 120 Mbps, especially with the gfast roll out next year

@fishpan I am based in London, Westminster

Edited by deleted (Sat 17-Jun-17 11:53:58)

So DLM is toying with me and just put my margin back up to 5dB for no apparent reason, sync dropped a couple of meg too.

Hazel Grove on Stepping Hill exchange.

Checking remotely via MDWS mine seems to have stabilised now on 4dB. It hasn't attempted 3dB.

And maybe not many people on your cab yet. I used to get over 140mbs attainable but it soon went down.

In reply to a post by Banger:

My sync and target are now on par with yours. I had an unexpected re-sync today and my sync dropped to 69587 with a 4.1dB target. It was relatively unexplained how I was getting 71½ sync at 4.3dB the last few days. Ho hum such is FTTC.

Email from MyDslWebStats

This is to let you know that a resync/restart occurred on your line at 17:21 on Sunday, 18th June 2017 local time (+/- 1 minute).

Reason: 1 Remote Defect Indicator/DLM

Current Downstream Sync Rate is now 71288kbps @ 2.7db SNRM
Current Upstream Sync Rate is now 12440kbps @ 6.0db SNRM

Currently Attainable 71940 @ 2.9dB.

Nice. Mine is going the other way for some unexplainable reason now back to 5dB but no ES on the DS unless it's the US ES.

The up/down colourings are in the top left of the ES graph area. Below the main headings.

Down, Up, Down Tot, Down Avg/24hr, Up Tot/24hr.

Yes I know I regularly monitor the ES Graph on MWDS.

Well, I have had Zero US and DS ES today and my US sync has gone up to 19905 with DS target at 5dB and sync at 67296. Wonder if DLM is trying to get me more US sync and lower US ES as well.

Although can't be sure MWDS is seeing all the ES as the router every so often stops responding to DSLStats and can't login to telnet so it is quite possible MWDS is not recording all the ES stats.

My upstream sync drops a fraction with every downstream margin fall. Odd.

I saw that too when my margin was dropping and DS sync was increasing. I suspect as the downstream takes up more bandwidth as sync increases the upstream bandwidth suffers thus a slight drop in sync. I am now seeing the opposite on my line with the target going back up.

So another resync today and sync has dropped to 65992/17629. Still on 5dB but looks like my sync is dropping every day. Wonder if its the heat?

Does your noise margin change when you switch the fan or aircon on and off?

Not really although DSLStats recorded the re-sync at 10:14 MWDS didn't see it that probably because only half the data is being uploaded.

I run RouterStatsLite at the same time as DslStats, with its sampling interval set to 5 seconds. You can tell a lot more from that than from DslStats at one minute and a huge amount more than MDWS picks up with its the DslStats upload.

(Only DslStats is running at the moment while I'm away).

Yes I tried Routerstats but couldnt get either version to work with the WD9970. Also I dont know if its the hack or the router but it will stop responding on the LAN for quite a while I am currently trying to access it to reboot it but it is not responding!

Looks like the computer may have rebooted at 10:40 this morning. Possibly a Windows update, maybe even the Creators edition. I forgot to make DslStats load with Windows, but even that might not have been sufficient.


Further information will be supplied when possible ....

Yes, I see that on your SNRM graph, I rebooted my router last night and it is still supplying data to MWDS pity there isn't a reboot scheduler like there is on the Asus.

So I am using powerline to get stats now and DSLStats sprang into life when I plugged the powerline into my Asus router. I wonder if I have duff wifi on the WD9970, will soon tell as I plan to run Powerline and ping the router for a while.

you getting a lot of resyncs, either a line issue or the DLM been way over active.

I suspect DLM and my DS ES has started to register since I started using the powerline so DLM may again intervene and band me.

Well, the powerline seems to be doing its job, no packet loss after a few hours connection time so looks like a wifi problem somewhere. Will swap dongle with an Asus N53 when it arrives and see if that is any more reliable.

the powerline plugs can cause problems for dsl, as they can cause interference.

Yes, I am aware but the wifi on the router or my dongle doesn't seem reliable thus not providing stable stats, been running the powerline since last night and stats are now stable on MWDS. I am getting a Billion 8800NL R2 soon so maybe the wireless on that plus I think there is a way to see the Billion on the WAN cable.

there is a way to see the Billion on the WAN cable

If you "see" the billion on the WAN cable you can do the same with the TP-Link...the router is the device that must be able to add an additional network via the WAN link.

What router do you use....and its LAN IP address?

Using an Asus DSL-N55U and its IP is 192.168.1.1 and the TP-Link is 192.168.1.250.

Copied from Kitz

Sorted I need to enter the following with IP for modem at 192.168.2.10

ifconfig eth2.4 192.168.2.9 netmask 255.255.255.0

I can now ping and access the modem from my desktop with just the above command.

How do you make this permanent as saveall doesnt seem to work and the config is lost after a reboot?

Got rid of those horrible powerline devices and gained a couple of meg on sync.

So I have yet to discover how to make the change permanent but in the mean time an ugly script to do the job after a router reboot. Written in vbs

set oShell = CreateObject("WScript.Shell")
oShell.run("Telnet")
WScript.Sleep 1000
oShell.SendKeys("Open 192.168.1.1 ")
WScript.Sleep 1000
oShell.SendKeys("{Enter}")
WScript.Sleep 1000
oShell.SendKeys"admin"
WScript.Sleep 1000
oShell.SendKeys("{Enter}")
WScript.Sleep 1000
oShell.SendKeys("PASSWORD")
WScript.Sleep 1000
oShell.SendKeys("{Enter}")
WScript.Sleep 1000
oShell.SendKeys("ifconfig eth2.4 192.168.2.9 netmask 255.255.255.0 ")
WScript.Sleep 1000
oShell.SendKeys("{Enter}")
WScript.Sleep 1000

Reminiscent of tst10.exe

Interesting thanks for that link BatBoy.

My sync seems to be slowly dropping, down to 65 DS but 17 US and still at 5dB DS target. Wonder if its the cold weather. No more reboots of the router for me for a while I think.

I'm going home tomorrow, so will see what is going on with mine.

Can't see your username on MWDS. Is it me or because you haven't uploaded for a while your name disappears?

Remember? I was on holiday?

I got back 9pm today Thursday. DSLStats has gone wonky, which is why it wasn't uploading after the reboot I guessed had happened. I need to delete it and re-download.

My connection hasn't changed since before I went away. Stats Thursday night:

> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 12440 Kbps, Downstream rate = 73691 Kbps
Bearer: 0, Upstream rate = 12440 Kbps, Downstream rate = 71288 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 3.4 6.4
Attn(dB): 19.4 0.0
Pwr(dBm): 13.7 7.5

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 51
R: 10 16
S: 0.1090 0.6082
L: 18644 3341
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 80 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0

Counters
Bearer 0
OHF: 0 125870624
OHFErr: 17 88
RS: 1319829200 2123136525
RSCorr: 252732783 389
RSUnCorr: 0 0
Bearer 1
OHF: 60760964 0
OHFErr: 1 0
RS: 607609027 0
RSCorr: 437929 0
RSUnCorr: 1 0

Retransmit Counters
rtx_tx: 1326011 0
rtx_c: 1307041 0
rtx_uc: 62 0

G.INP Counters
LEFTRS: 30 0
minEFTR: 71271 0
errFreeBits: 1576522904 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 614736131 0
Data Cells: 23711412 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 24 92
SES: 11 0
UAS: 66 55
AS: 975989

Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 7.78
OR: 0.01 32.88
AgR: 71361.18 12473.44

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 660019/703665 9315/9353

Total time = 16 days 22 hours 9 min 8 sec
FEC: 297419007 496
CRC: 565 100
ES: 24 92
SES: 11 0
UAS: 66 55
LOS: 1 0
LOF: 3 0
LOM: 0 0
Retr: 1
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 9 min 8 sec
FEC: 88832 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 149081 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 22 hours 9 min 8 sec
FEC: 15311306 14
CRC: 2 10
ES: 2 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 17809081 53
CRC: 0 18
ES: 0 18
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 11 days 7 hours 6 min 29 sec
FEC: 252732783 389
CRC: 17 88
ES: 12 81
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

There is a new version of DSLStats V6.0.2.

Ah, OK. I got my 5.9.n working this morning. See MDWS. The 20-day option shows where it breaks.

I can only see 5 days as I haven't paid. Your MWDS name has re-appeared in the list now it had disappeared before.

So DLM tried 3db months ago and found that errors were to high on my line and settled for 5db for quite a while. Today I had a resync at around 9.32am and it seems like I am on 4db target as sync has gone from 71 to 75 meg. Didn't realise DLM would try again my MWDS is banger if you want to take a look.

In reply to a post by Banger:

So DLM tried 3db months ago and found that errors were to high on my line and settled for 5db for quite a while. Today I had a resync at around 9.32am and it seems like I am on 4db target as sync has gone from 71 to 75 meg. Didn't realise DLM would try again my MWDS is banger if you want to take a look.

As we all know by now, DLM is a constant and not something that just switches off. Therefore if the DLM sees that your line has been stable with 5dB for a while it will try 4dB again to see what happens

Your new modem handling the line better it seems .

@RobertCrowther thanks for the explanation.

@Bob yes seems pretty low on ES so stable apart from me messing about swapping modems.

So I have hit the heady heights of 78 sync @ 3.5db, attainable 80. Wonder if it will stay that way as last time it was only for a day or so but this time the modem seems to be keeping the errors down.

I have also found the best way to cause an errorless resync. A reboot causes about 50 DS ES but going into the router power management and switching DSL power to off then on again causes an errorless resync. Handy to know it also gets just that little bit extra out of sync retrain.

I'd imagine powering the router up without the DSL cable in and then connecting the cable say 30 seconds later would have the same result?

Tried that swapping the DSL cable to my spare to test it but was left with 50 DS ES on my MWDS graph as it seems to cause errors.