As its a temporary thing have you thought about using a rj45 splitter, you will lose lan performance as you will be limited to 100 MBit, but as its temporary thought it may save some effort.

As solchain suggests use an RJ45 splitter - 100Mb only needs two pairs and as the modem only has 100Mb ports and your line speed is under 100Mb you should not see any issues.


Or split the cable yourself to two sockets at each end: 1, 2, 3 & 6 Green and Orange for the main data connection and 4, 5, 7 & 8 Blue and Brown for the monitoring connection.

https://en.wikipedia.org/wiki/TIA/EIA-568 has details

In reply to a post by RobertoS:

It's hard to tell whether the jump in latency is DLM raising it or a different gateway on IDNet.

Those stats show a DLM setting identical to mine, and identical FEC and interleaving settings as a consequence.

These seem to be fairly standard DLM settings for G.INP, pretty much equivalent to "no intervention needed", and I've maintained zero ESs for the last 100 days.

I've calculated that the minimal FEC and interleaving that goes alongside retransmission amounts to 0.2ms of latency and about 6% of bandwidth reduction.

It doesn't look like the latency increase (which seemed abnormally high anyway) is due to DLM.

For comparison:
My Broadband Ping

Yes, but he has had two or three disconnections since then. Following a latency drop, the latest ones increased it again. Which is why I've asked for (non-urgent) new stats to see if anything has changed .

Yes. The stats were gathered after the disconnection at 1800 ... which highlights the downside of live BQM's, because that disconnection has now fallen off the graph we can see.

But the 1930 disconnections were reported as PPP disconnections only ... suggesting the change in latency is as part of the PPP establishment process, not a resync.

As you say, though, an update to the stats will help clarify.

Just home and connected up longer cable to lan2 so I can sit in lounge and not on stairs

Latest stats are below.

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27969 Kbps, Downstream rate = 84568 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 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): 7.1 15.3
Attn(dB): 10.1 0.0
Pwr(dBm): 13.9 -5.7
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 130 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0518 0.3781
L: 21468 5374
D: 16 1
I: 139 127
N: 139 254
Q: 16 0
V: 14 0
RxQueue: 60 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 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 849366
OHFErr: 0 75
RS: 2416909200 3881597
RSCorr: 522 566
RSUnCorr: 0 0
Bearer 1
OHF: 5432279 0
OHFErr: 0 0
RS: 65186615 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 129754 0
rtx_c: 12 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 80015 0
errFreeBits: 106472054 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 538951293 0
Data Cells: 14673254 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: 0 44
SES: 0 0
UAS: 28 28
AS: 87257

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80614.82 20063.54

Bearer 1
INP: 4.00 0.00
INPRein: 4.00 0.00
delay: 3 0
PER: 16.06 0.01
OR: 95.62 0.01
AgR: 95.62 0.01

Bitswap: 24801/24801 48/48

Total time = 1 days 14 min 45 sec
FEC: 522 566
CRC: 0 75
ES: 0 44
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 14 min 45 sec
FEC: 0 27
CRC: 0 2
ES: 0 2
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: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 14 min 45 sec
FEC: 0 27
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 522 539
CRC: 0 73
ES: 0 42
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 14 min 17 sec
FEC: 522 566
CRC: 0 75
ES: 0 44
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

Those stats show the link has been up since 6pm yesterday, so the changes in latency at 730pm are something for the ISP, not caused by DLM.

Your line looks fine, stable, few errors, and minimal extra latency (0.2ms)

Cheers WWWombat, so get onto IDnet then?
Latency has jumped from 8ms on Saturday (after almost 5 years of stability on FTTC) and is now up at 25ms...just a bit confused as to why.

The connectivity could be taking a different route over their network if a piece of kit has failed or if they've taken it offline for maintenance/upgrade.

Yes, I'd get them involved.

The extra latency is likely to come from alternative routing of your PPP session, but the difference is extreme.