Understood. 
However I am always of the mind that it is best to convert the (very weak) xDSL signal to a considerably stronger set of Ethernet frames as soon as practicable.
Diagrammatically, this --
NTE5 <---> Modem <---------- relatively long distance ----------> Other networking equipment
^ ^
xDSL Ethernet frames
signal
-- rather than --
NTE5 <---------- relatively long distance ----------> Modem <---> Other networking equipment
^ ^
xDSL Ethernet frames
signal
In the latter case, it would be preferable to glue a rectangle of plastic over the xDSL port on the front of the NTE5 face-plate. Why? If any attempt was made to use the port, the in situ wiring would be an excellent bridge tap.
Yeah I realise that, nothing will be plugged in downstairs however and I'll make sure of that. I've done it after a little hassle with a pair of wires which weren't initially making proper contact (had to be the broadband activated line lol). Oddly although Hlog and QLN appear the same as before... on my initial connection I had hundreds of CRC errors per minute. I've since reconnected at a reduced sync rate temporarily and will let things settle before I increase it again tomorrow. Reminds me of my old address where I had to reduce sync rate a bit because of an odd 'stream' of downstream CRC errors. A slight loss in attainable rate but understandable given I've extended the wiring for the DSL/phone slightly.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 19834 Kbps, Downstream rate = 77392 Kbps
Bearer: 0, Upstream rate = 19794 Kbps, Downstream rate = 59995 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): 10.6 6.0
Attn(dB): 17.3 0.0
Pwr(dBm): 12.7 6.9
VDSL2 framing
Bearer 0
MSGc: 17 13
B: 239 238
M: 1 1
T: 64 64
R: 0 16
S: 0.1273 0.3844
L: 15080 5307
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 610729 203236
OHFErr: 5 194
RS: 0 117030
RSCorr: 0 10721
RSUnCorr: 0 0
Bearer 0
HEC: 27 0
OCD: 0 0
LCD: 0 0
Total Cells: 144104018 0
Data Cells: 4535233 0
Drop Cells: 0
Bit Errors: 0 0
ES: 170 322
SES: 11 0
UAS: 1588 61586
AS: 1250
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 2.04 6.17
OR: 89.97 24.61
AgR: 60085.29 19818.63
Bitswap: 433/434 0/0
Total time = 55 min 22 sec
FEC: 0 21442
CRC: 5599 194
ES: 170 322
SES: 11 0
UAS: 1588 61586
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 10 min 22 sec
FEC: 0 0
CRC: 2 0
ES: 1 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 10721
CRC: 2963 194
ES: 86 161
SES: 6 0
UAS: 36 30051
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 55 min 22 sec
FEC: 0 21442
CRC: 5599 194
ES: 170 322
SES: 11 0
UAS: 1588 61586
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 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
Since Link time = 20 min 49 sec
FEC: 0 10721
CRC: 5 194
ES: 3 161
SES: 0 0
UAS: 0 30015
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0Ignore upstream error counters as the modem initially gets the all-time error counters on sync.
I'll increase the downstream sync rate to 67Mbps tomorrow assuming DLM doesn't intervene. If it still appears normal then I'll try 74Mbps after another day or two.
QLN and Hlog: https://imgur.com/a/DgYMIThe point I was making was, that whilst above may have been your immediate requirement, there might evolve later some other requirement for fast data movement around your home, quite apart from (or in addition to) access to the Internet.
I had nothing specific in mind as I have no functioning crystal ball, merely a general suggestion that data cabling is future-proofing.
I see, yeah no worries
, thanks for the suggestion.
EDIT: Switched over to DrayTek, seems to be handling the line much better as previously experienced at the old address. Very mysterious but oh well.
Synced at 70.8Mbps / 19.4Mbps, downstream target SNRM is default at 6dB (offset set on DrayTek to 0). Once the line has settled I'll try reducing it to see if I can squeeze more speed out of the line.
