In reply to a post by pcoventry76:

::edit:: and now he's left.. with the cover for the box on the pole dangling so it's exposed which means we get some rain....

Idiot.

From the BT website:

Damage to outdoor equipment like junction boxes, telephone poles and overhead wires

This equipment is looked after by Openreach, and you can report the fault directly to them.

You can report the problem through their website or over the phone on 0800 023 2023

The Plusnet profile just set itself down on my line again... only a tiny bit to 71.8 Mb.

I've been collecting stats from my HG612 and it doesn't show any line re-syncs during the 4 day and 11 hour period, though there have been connection resets, and is still synced at 74444 kbps

I don't understand why it's below the BT IP profile of 72.06 as I thought they were meant to be identical.

@timl if BTW profile is 72.06Mb and your PN profile should be 72.0Mb

In reply to a post by adslmax:

@timl if BTW profile is 72.06Mb and your PN profile should be 72.0Mb

Indeed, and it isn't, so the question is, "why not?"

I would want to see the current IP Profile before passing judgement. Not a statement of unchanged sync.

timl did say the IP profile was 72.06Mb, which matches the sync, so unless it briefly sync'd lower and the IP profile followed it down, then it all went back up again, the Plusnet profile doesn't make sense.

Exactly, it doesn't make sense. So I don't trust figures that are not supported by a test taken and copied at the time, and also in this case a view of the full HG612 xdslcmd info --stats figures.

Hi Roberto,

Here's the results from the xdslcmd. I think there's a clue to the Plusnet sync... it seems to be taking the attainable or sync rate whichever is lower.

When it was first put in the attainable was in the high 90's. Now, whatever it syncs at the attainable is either exactly the sync or slightly below it... it varies throughout the day (as my sync log shows)

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27009 Kbps, Downstream rate = 73972 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 74444 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): 6.1 9.4
Attn(dB): 13.0 0.0
Pwr(dBm): 13.5 1.0
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 22 5
R: 0 16
S: 0.1026 0.3771
L: 18712 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 326488840 208142
OHFErr: 3946 52
RS: 0 1963065
RSCorr: 0 922
RSUnCorr: 0 0

Bearer 0
HEC: 1391 0
OCD: 18 0
LCD: 18 0
Total Cells: 2099222810 0
Data Cells: 1569657475 0
Drop Cells: 0
Bit Errors: 0 0

ES: 394 47
SES: 4 0
UAS: 26 26
AS: 554924

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.69 6.15
OR: 112.96 202.87
AgR: 74556.76 20203.27

Bitswap: 114209/114209 26/26

Total time = 1 days 10 hours 9 min 10 sec
FEC: 0 922
CRC: 3946 52
ES: 394 47
SES: 4 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 9 min 10 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 5 0
ES: 5 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 10 hours 9 min 10 sec
FEC: 0 14
CRC: 21 1
ES: 19 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 177
CRC: 105 17
ES: 84 14
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 6 days 10 hours 8 min 43 sec
FEC: 0 922
CRC: 3946 52
ES: 394 47
SES: 4 0
UAS: 0 0
LOS: 0 0
OF: 0 0
OM: 0 0

In reply to a post by timl:

Here's the results from the xdslcmd. I think there's a clue to the Plusnet sync... it seems to be taking the attainable or sync rate whichever is lower.

If it were (which it isn't), that would give 71.5 or 71.6, not 71.8. You will probably find that the attainable figure varies from one minute to the next in any case.