Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: adslmax on May 14, 2019, 12:09:04 AM

Title: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 12:09:04 AM
The line has suddenly resync by DLM caused my FTTC drop from 80/20 to 59/20 after nasty SNR drop to -0.5dB at 17:43. Probably down to crosstalk. But it went back to 80/20 after a short second. Probably installed a new line port due to my cabinet are in the waiting list this morning changed by follow that page.



Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 12:13:18 AM
Old FTTC modem stats 6th May
Title: Re: Badly hit by crosstalk
Post by: re0 on May 14, 2019, 12:20:47 AM
That is certainly a nasty drop there. I don't think I've had a personal experience with the SNR dropping into negative figures on FTTC - except for when I had a Lantiq device in use. :D

Just keep an eye on it but it might just be a one-off. The DLM will play since it's not impacting your stats now. :)
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 12:52:15 AM
There been one single of 85 errored secs at 17:43 in one go!

Scary!

Title: Re: Badly hit by crosstalk
Post by: burakkucat on May 14, 2019, 12:58:57 AM
That really does look like a disturbance to the circuit, caused by work in the cabinet. I suspect the DLM will quite happily ignore that one event. And if you were not monitoring the statistics, you might not have even noticed the temporary degradation of the circuit's performance.
Title: Re: Badly hit by crosstalk
Post by: re0 on May 14, 2019, 01:02:07 AM
It may be scary, but nothing too worrying right now. I remember an old ADSL fault there once was, and ES would be quadruple figures on the downstream for quite a few hours during the day. Seeing massive red bars from DSLstats was scary! The connection seldom dropped since the SNR was around the target, but it was just unusable due to the sheer amount of CRCs.
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 01:02:53 AM
Yes as the line was stable for 68 days until big bang with massive drop in SNR below 0.0dB never seen that in any FTTC. I guess you are correct burakkucat as DLM will ignore that one!
Title: Re: Badly hit by crosstalk
Post by: kitz on May 14, 2019, 01:11:41 AM
That really does look like a disturbance to the circuit, caused by work in the cabinet. I suspect the DLM will quite happily ignore that one event. And if you were not monitoring the statistics, you might not have even noticed the temporary degradation of the circuit's performance.

I would tend to agree with everything said above.   
It's back to normal now - thankfully :)
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 01:16:08 AM
Just been checked roadwork. There is work ongoing at my cabinet pcp 8

Information for Operational Teams
Highway Authority:    Telford and Wrekin Borough Council
Location:    S/O 74 WILLOWFIELD TELFORD TF7 5NT (cabinet 8)
Description:    Excavation to expose and repair buried telecoms plant in the footway.
Permit status:    Permit Granted
Works ref:    BC005DL1W00000IBZ2HHPJ01
Title: Re: Badly hit by crosstalk
Post by: aesmith on May 14, 2019, 11:47:44 AM
There been one single of 85 errored secs at 17:43 in one go!
Scary!
85 in an hour isn't really much in terms of actual impact, other than what it might cause DLM to do.  I found no detectable slow down even with 70 CRC per minute (around 2800 ES per hour).
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 11:49:39 AM
There seem five openreach engineers are working at the cabinet footpath at the moment (don't know what they are doing?)
Title: Re: Badly hit by crosstalk
Post by: CarlT on May 14, 2019, 03:06:25 PM
Switch the monitoring off, leave the engineers alone and enjoy the Internet - they're fixing a fault as your Roadworks copy/paste says  :P

Quote
Description:    Excavation to expose and repair buried telecoms plant in the footway.

Digging to get to ducting, breaking ducting open, finding broken cable, splicing in new cable / moving services to unbroken and unused pairs in the existing cable.
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 04:02:20 PM
The engineer told me off to stay away and no camera photo taken please by the BT footpath and cabinet!  ??? >:( It's a free country anyway.

Line been resync this lunchtime drop 80 to 62  :( :(

Thank alots DLM :( now been banded capped at 62Meg

Code: [Select]
Stats recorded 14 May 2019 16:03:49

DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:  AnnexA version - A2pv6F039g1.d24m
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  2 hours 19 min 59 sec
Resyncs:                1 (since 14 May 2019 13:23:45)

Downstream Upstream
Line attenuation (dB):  12.7 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 62999 19999
SNR margin (dB):        5.3 9.3
Power (dBm):            12.5 0.7
Interleave depth:        16 1
INP:                    48.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 26875 Kbps, Downstream rate = 62778 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 62999 Kbps

I checked my DSL Checker as handback now at 62.6 matched my sync rate 62Meg :(
Title: Re: Badly hit by crosstalk
Post by: re0 on May 14, 2019, 04:26:29 PM
The engineer told me off to stay away and no camera photo taken please by the BT footpath and cabinet!  ??? >:( It's a free country anyway.
Bit unfair of them, if you were on public property. It's easier to just honour their request, however.

Line been resync this lunchtime drop 80 to 62  :( :(

Thank alots DLM :( now been banded capped at 62Meg
SNRM looks a bit too low to be only banded? Anyway, just wait for them to finish their works before acting upon this.
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 04:37:41 PM
SNRM looks a bit too low to be only banded? Anyway, just wait for them to finish their works before acting upon this.

SNR went crazy today all over the place from 2dB to 7dB
Title: Re: Badly hit by crosstalk
Post by: johnson on May 14, 2019, 05:01:48 PM
adslmax what do you use your connection for?

Some streaming? General web browsing?

Any real impact from the change in speed to what you do with it?

I have a 25/1 connection and its enough for 2 people to stream, game, do what they like. Do I want a faster connection? Yes. But would it really make any difference to day to day life? Nope.

Enjoy your 60-80 down and 20 up! Go watch some TV or play some games!  ;D
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 05:07:57 PM
 ;D I am off on holiday this thursday to Spain for two weeks. So, my broadband will stay active cos my daughter will use it for watching netflix.

Can't wait for my holiday break  :sun: :rain: :comp:
Title: Re: Badly hit by crosstalk
Post by: burakkucat on May 14, 2019, 10:39:32 PM
If you currently don't need to use your connection to the Internet, then power down the modem whilst the repair work is ongoing. That way the DLM process will not take any action on your circuit.
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 14, 2019, 10:51:31 PM
The line went back to 80/20 shortly after 6pm so must be the work by openreach today.
Title: Re: Badly hit by crosstalk
Post by: Chrysalis on May 15, 2019, 08:14:55 AM
dont thin its crosstalk, looks like interference and probably caused by the ongoing work.
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 15, 2019, 09:56:07 AM
Everything went back to normal now.

SNR steady solid at 6.9dB for 15 hours now. But why is line attenuation increase to 12.7? Before used to be 11.5?

Code: [Select]
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:  AnnexA version - A2pv6F039g1.d24m
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  15 hours 36 min 9 sec
Resyncs:                0 (since 15 May 2019 09:49:15)

Downstream Upstream
Line attenuation (dB):  12.7 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79999 19999
SNR margin (dB):        6.9 12.5
Power (dBm):            12.5 0.6
Interleave depth:        16 1
INP:                    48.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)
Title: Re: Badly hit by crosstalk
Post by: PhilipD on May 15, 2019, 02:11:27 PM
Hi

Everything went back to normal now.

SNR steady solid at 6.9dB for 15 hours now. But why is line attenuation increase to 12.7? Before used to be 11.5?

Code: [Select]
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:  AnnexA version - A2pv6F039g1.d24m
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  15 hours 36 min 9 sec
Resyncs:                0 (since 15 May 2019 09:49:15)

Downstream Upstream
Line attenuation (dB):  12.7 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79999 19999
SNR margin (dB):        6.9 12.5
Power (dBm):            12.5 0.6
Interleave depth:        16 1
INP:                    48.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

Attenuation reported by modems is not the same attenuation as your physical line that BT might use to judge distance or speeds your line might get, with the modems attenuation more an average based on all frequencies received which varies meaning this attenuation figure can vary also.  Your true physical line attenuation which is measured at a fixed frequency of 300KHz is very likely completely unchanged.

The trouble is with modem stats is you can't really take any single figure and draw any conclusion from it changing, as its a balancing act you need to consider other values alongside it. 

I suspect your modem is receiving higher frequencies than it did before so your average attenuation has gone up, because these higher frequencies have a higher attenuation.  This actually shows an improvement in your line, the opposite of what we might expect seeing that attenuation figure go upwards.

Regards

Phil
Title: Re: Badly hit by crosstalk
Post by: adslmax on May 15, 2019, 07:30:53 PM
Can see cable damaged on the ground by the fibre cabinet
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 17, 2019, 01:48:18 AM
My line has changed 13 hours ago. I just got back from my holiday went to Greece for my break. Was surprise to see large increase in max sync rate at 101151K with SNR at 10dB.  :o Has the cabinet got new line card?

Code: [Select]
Downstream Upstream
Line attenuation (dB):  11.1 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 80000 20000
SNR margin (dB):        10.1 13.0
Power (dBm):            12.4 0.3
Interleave depth:        16 8
INP:                    46.00 47.00
G.INP:                  Enabled Enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 32325 Kbps, Downstream rate = 101151 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 80000 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):        10.1             13.0
Attn(dB):        11.1            0.0
Pwr(dBm):        12.4            0.3

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              130             97
M:              1               1
T:              0               0
R:              8               8
S:              0.0518          0.1554
L:              21468           5457
D:              16              8
I:              139             106
N:              139             106
Q:              16              8
V:              14              2
RxQueue:                57              39
TxQueue:                19              13
G.INP Framing:          18              18
G.INP lookback:         19              13
RRC bits:               24              24
                        Bearer 1
MSGc:           186             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              5.3333          16.0000
L:              48              16
D:              3               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             3838896416              566479
RSCorr:         1665            1546
RSUnCorr:       0               0
                        Bearer 1
OHF:            3106988         1022413
OHFErr:         0               0
RS:             37283860                3888325
RSCorr:         23              97
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9252097         132
rtx_c:          202             1633884
rtx_uc:         0               323600

                        G.INP Counters
LEFTRS:         0               4451
minEFTR:        79999           20003
errFreeBits:    60892608                528201173

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    3382818780              0
Data Cells:     385076385               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               0
SES:            0               0
UAS:            0               0
AS:             49914

                        Bearer 0
INP:            46.00           47.00
INPRein:        0.00            0.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            80614.82        20102.08

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

Bitswap:        0/0             0/0

Total time = 13 hours 51 min 54 sec
FEC:            1665            1546
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 6 min 54 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:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 13 hours 51 min 54 sec
FEC:            1665            1546
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
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 = 13 hours 51 min 53 sec
FEC:            1665            1546
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >

Title: Re: Badly hit by crosstalk
Post by: kitz on June 17, 2019, 09:30:31 AM
Nice, that is quite some jump. 
It's possible that a couple of your disturbers may have their modems switched off if they are away on holiday.  When my immediate neighbours got FTTC I suddenly lost circa 10Mbps which is what took me down to ~65Mbps.    There are also another few cross talkers that I've noticed over the years who have taken a good chunk of my sync speed.   However ~30Mbps seems to be rather a lot for just 1 or 2 cross talkers.


Interestingly, I notice that you appear to have g.inp on your upstream, so I am assuming you may be on the new trial.
Title: Re: Badly hit by crosstalk
Post by: dee.jay on June 18, 2019, 08:35:59 AM
Maybe now it'll stay at 80/20 and you can forget about it.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 12:12:50 PM
Something isn't right on my line. Since G.INP enabled on both as I only getting 20/18 in throughput speed. The thinkbroadband monitor is suffering packet loss. What was caused this? Any idea?

https://www.thinkbroadband.com/speedtest/1560855886821950155
https://www.speedtest.net/result/8346589409

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d3e60413fe4ce714d2eff50230f56fe7210244e6

Microsoft Windows [Version 10.0.18362.175]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\W7>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.26] with 32 bytes of data:
Reply from 212.58.244.26: bytes=32 time=13ms TTL=54
Reply from 212.58.244.26: bytes=32 time=12ms TTL=54
Reply from 212.58.244.26: bytes=32 time=13ms TTL=54
Reply from 212.58.244.26: bytes=32 time=12ms TTL=54

Ping statistics for 212.58.244.26:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 13ms, Average = 12ms

C:\Users\W7>


Title: Re: Badly hit by crosstalk
Post by: kitz on June 18, 2019, 12:32:12 PM
Oh dear :(
How long has it been like that?    If I were you I'd raise a ticket as it looks like something is limiting your throughput.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 12:40:51 PM
It's been like this since I come back from Greece but I only find out when I ran the speedtest and never knew this so low throughput speed. I have to raise this with PN now.
Title: Re: Badly hit by crosstalk
Post by: kitz on June 18, 2019, 12:43:52 PM
Quote
but I only find out when I ran the speedtest and never knew this so low throughput speed.

and when was that you noticed the low speedtest.
You can't say for sure if it is since you returned from Greece if you only just noticed it 30 mins ago.


btw..  which modem are you using right now?
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 12:46:47 PM
Billion 8800NL connected with TP LInk VR2600 for Wireless Router but this throughput speed is tested via ethernet to my pc ethernet as I have asked PN for GEA Test to see if the line was banded?
Title: Re: Badly hit by crosstalk
Post by: kitz on June 18, 2019, 12:51:25 PM
GEA test run by the ISP could be pretty useless as the DLM profile is often a few weeks out of date :/
It would be interesting to see it though if you do get one as it might show something.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 12:58:07 PM
Just checked Broadband Quality Monitor as it start to get packet loss around 5pm yesterday and it kept continue.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d3e60413fe4ce714d2eff50230f56fe7210244e6

Stats recorded 18 Jun 2019 12:55:18

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    2 days 1 hour 11 min 49 sec
Resyncs:                   0 (since 18 Jun 2019 10:55:45)
         
            Downstream   Upstream
Line attenuation (dB):     11.1      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   80000      20000
SNR margin (dB):           10.1      12.9
Power (dBm):               12.4      0.3
Interleave depth:          16      8
INP:                       46.00      47.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             15.7154      4298.3486
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0.0      0.0
Title: Re: Badly hit by crosstalk
Post by: kitz on June 18, 2019, 01:09:10 PM
Cheers.    Yes I can see on there, that is when it likely started.    Keep us updated on what PN say.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 01:21:29 PM
Updated: PN Profile are incorrect than BT one. They have corrected it now. As for GEA Test they say it outdated. As it was old one.

https://www.thinkbroadband.com/speedtest/1560860162575921055

https://www.speedtest.net/result/8346748578

I was bit annoyed by PN no longer gave high speed profile check on the member account as it making much harder for us to think what has gone wrong with the line speed etc very annoying to chase it up with PN.

This one no longer in use: https://portal.plus.net/my.html?action=data_transfer_speed
Title: Re: Badly hit by crosstalk
Post by: kitz on June 18, 2019, 06:11:36 PM
Totally agree that its annoying how we can no longer check it ourselves.   Glad you got it sorted although I wonder what would have triggered such a change :-\
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 07:20:41 PM
Kitz I won't be with PN much longer as I am leaving them in October when my contract has expiry for Fibre 80/20 with LRS line only. I am thinking to move both the line and fibre 80/20 to Zen Internet.

Reason of leaving PN:

lack of support via ticket
ongoing billing issues (not fixed yet since September 2018)
removed PN profile rate from the member account

Such a shame really because PN used to be good but not anymore.

PN send me GEA TEST but it outdated (nearly two weeks ago)

Code: [Select]
Circuit ID NA Service ID ***************
Test Outcome Pass
Test Outcome Code GTC_FTTC_SERVICE_0000
Description GEA service test completed and no fault found .
Main Fault Location OK
Sync Status In Sync
Downstream Speed 79.9 Mbps
Upstream Speed 20.0 Mbps
Appointment Required N
Fault Report Advised N
NTE Power Status PowerOn
Voice Line Test Result Pass
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
Repetitive Electrical Impulse Noise Not Detected
Cross Talk Not Detected
Estimated Line Length In Metres 262.7
Upstream Rate Assessment Very Good
Downstream Rate Assessment Very Good
Interference Pattern Regular Interference Observed Daily
Service Impact No Impact Observed
Interference Duration Longest Occurrence From 17:30 to 20:45
Interference Location Unknown
Interference Observed In Days 2
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
Profile Name 0.128M-80M Downstream, Retransmission Low - 0.128M-20M Upstream, Error Protection Off
Time Stamp 2019-06-05T15:00:00
Parameters MIN MAX AVG
Down Stream Line Rate 79.2 Mbps 79.9 Mbps 79.6 Mbps
Up Stream Line Rate 19.9 Mbps 20.0 Mbps 19.9 Mbps
Up Time 0.0 Sec 900.0 Sec 897.4 Sec
Retrains 0.0 4.0 0.0
Current and Last 15 Minute Bin Performance
Parameters Last Traffic Count(Upto 15 mins) Current Traffic Count(Upto 15 mins)
Start Time Stamp 2019-06-18T13:37:02Z 2019-06-18T13:52:02Z
Ingress Code Violation 0 27
Egress Code Violation 0 0
Errored Seconds 0 0
Severely Errored Seconds 0 0
Unavailable Seconds 0 0


Title: Re: Badly hit by crosstalk
Post by: CarlT on June 18, 2019, 10:24:11 PM
Your GEA test was done earlier today. The date from 2 weeks ago isn't the timing of the test it's possibly last resync.
Title: Re: Badly hit by crosstalk
Post by: kitz on June 18, 2019, 11:04:58 PM
For some obscure reason the GEA test never returns the current DLM profile and is usually (always!) 13/14 days out of date.

I first noticed this when g.inp was introduced ~4yrs ago and I had a battle on my hands trying to convince PN that the GEA tests they were giving out on their forums contained out of date info.  I certainly recall trying to convince Matty several times that a line definitely had g.inp enabled and PN denying it because the profile from GEA saying it didn't.  It was Bob Pullen who eventually acknowledged I was correct and that DLM profile data should never be taken as current.  It doesnt even tie up with the last sync :(

Anyhow I digress, the crux is the DLM profile data lags by 2 weeks and this is not specific to Plusnet - it also affects other ISPs. 
That's why I said several posts above after Max said he'd requested one: "GEA test run by the ISP could be pretty useless as the DLM profile is often a few weeks out of date :/"   :'(
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 18, 2019, 11:23:38 PM
I was not surprise many ISP's never reported outdated GEA Test to either BTWholesale or Openreach. They should updated at the same time when the profile changed via BTw speedtester after last resync from the modem. Over 2 weeks is a joke. The same with PN Profile as it pretty quick to downgrade speed profile on the line but take ages to recover to increase the profile speed but sometimes it doesn't pick it up until request PN to check the profile speed to matched BT profile rate are rather annoyed in these case.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 19, 2019, 11:03:13 AM
The line has been resync after 3am this morning. Very strange to put high rtx on upstream as bearer 0 INPRein 1.00

Stats recorded 19 Jun 2019 11:00:19

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     7 hours 43 min 3 sec
Resyncs:                   1 (since 19 Jun 2019 11:00:15)
         
            Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      20000
SNR margin (dB):           7.0      7.3
Power (dBm):               12.4      0.6
Interleave depth:          16      4
INP:                       46.00      55.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             2.0525      981.7606
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 27830 Kbps, Downstream rate = 86481 Kbps
Bearer: 0, Upstream rate = 20000 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.0             7.3
Attn(dB):        11.8            0.0
Pwr(dBm):        12.4            0.6

Downstream      Upstream
General
   rtx_tx             9654798            2833029         
   rtx_c              60744              6094234         
   rtx_uc             25                 1316850         
   LEFTRS             716                17263           
   minEFTR            79999              19995           
   errFreeBits        34071588           590752791       
Bearer 0
   RxQueue            57                 135             
   TxQueue            19                 27             
   G.INP Framing      18                 18             
   G.INP Lookback     19                 27             
   RRC Bits           24                 24             
   Interleave depth   16                 4               
   INP                46.00              55.00           
   INPRein            0.00               1.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  1               
   INP                4.00               4.00           
   INPRein            4.00               4.00           
   Delay              3                  0     

Since Link time = 7 hours 48 min 43 sec
FEC:            44529437                33723917
CRC:            21              658
ES:             15              480
SES:            0               377
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0     

Still getting packet loss even before and after resync according to thinkbroadband monitor below



Title: Re: Badly hit by crosstalk
Post by: kitz on June 19, 2019, 11:17:17 AM
Code: [Select]
INP:                       46.00      55.00
G.INP:                     Enabled      Enabled

Not sure sorry.   All I know is they are trialling higher levels of re-tx.   I guess you are on that trial.

What is your throughput speed like?
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 19, 2019, 11:57:41 AM
What is your throughput speed like?

https://www.thinkbroadband.com/speedtest/1560941784851254255
Title: Re: Badly hit by crosstalk
Post by: meritez on June 19, 2019, 05:33:12 PM
Profile changes look like this:

Code: [Select]
Profile Summary
Profile name Profile change time stamp
0.128M-80M Downstream, Interleaving Low - 0.128M-20M Upstream, Error Protection Off 2019-06-06T10:00:00
0.128M-80M Downstream 5dB, Retransmission High - 0.128M-20M Upstream, Error Protection Off 2019-06-18T00:45:00
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 19, 2019, 07:24:28 PM
Kitz - I kept asked myself 'Why do Openreach want to trial G.INP and Interleaved with Low/Medium/High rtx on upstream for?' Because upstream isn't important roleplay by DLM? Or maybe something to do with G.Fast highest upstream with 50Meg on the cabinet to keep FTTC upstream more stable?
Title: Re: Badly hit by crosstalk
Post by: CarlT on June 19, 2019, 10:50:50 PM
FTTC and G.fast do not impact each other. Any FTTC DLM settings are not related.

The error correction on your upstream is appropriate and is an attempt to protect your service. I imagine further changes will be coming, too.

Since Link time = 7 hours 48 min 43 sec
FEC:            44529437                33723917
CRC:            21              658
ES:             15              480
SES:            0               377
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 19, 2019, 10:57:52 PM
@CarIT

This is latest errors as of now:

Since Link time = 1 days 11 sec
FEC:            119270905               92923313
CRC:            63              1727
ES:             35              1145
SES:            0               886
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: Chrysalis on June 20, 2019, 07:44:56 AM
886 SES in a day and half is very high.  Especially if that is whilst g.inp is also enabled.
Title: Re: Badly hit by crosstalk
Post by: tubaman on June 20, 2019, 08:34:40 AM
886 SES in a day and half is very high.  Especially if that is whilst g.inp is also enabled.

Agree, that is a lot of SES.
My line runs at about 900 - 1000 ES each day on the DS side (with G.INP and 3dB) but only has five or six SES events in the same period.
I've only ever had G.INP on the US side for very short periods so I'm not sure how much of an advantage it would be for me. It would be interesting to see though.
 :)
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 20, 2019, 10:22:09 AM
Oh well well. DLM taken action this morning after 5am. Guess what, silly to reduced upstream from 20000Kbps to 19000Kbps and decided to change interleave depth from 4 to 2 and INP from 55.00 to 56.00. Before the new trial on upstream kicked in the upstream error was clean as a spot with zero but the last 48 hours went very badly with too many SES in the last 48 hours.

Why would Openreach trial on upstream making it lots worsen? Are they trying to reduced upload speed for many of us? Not happy with this trial. Really rubbish. :(

Since Link time = 5 hours 21 min 21 sec
FEC:            25789818                5838599
CRC:            2               44
ES:             2               56
SES:            0               26
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

Title: Re: Badly hit by crosstalk
Post by: tubaman on June 20, 2019, 01:22:14 PM
....
Why would Openreach trial on upstream making it lots worsen? Are they trying to reduced upload speed for many of us? Not happy with this trial. Really rubbish. :(
....

I very much doubt it's the trial making things worse for you - adding G.INP to the US side where necessary should help increase the available speed, not reduce it.
Clearly something is going on with the US side of your connection right now and DLM is doing its best to deal with that.  The fact that it now has G.INP in its tool set should be making things less bad than it would be without it.
 :)
Title: Re: Badly hit by crosstalk
Post by: ejs on June 20, 2019, 06:41:18 PM
If you had the historical data that clearly showed all those upstream errors started the moment G.INP was enabled on the upstream, that might suggest that these upstream errors are due to the upstream G.INP somehow not functioning properly.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 20, 2019, 11:43:24 PM
Off to bed now I expecting another DLM change on upstream overnight

Since Link time = 18 hours 33 min 29 sec
FEC:            64773398                17052392
CRC:            2               138
ES:             2               160
SES:            0               78
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: burakkucat on June 20, 2019, 11:45:37 PM
Hmm . . . I don't like that SES count.  :-\
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 20, 2019, 11:47:52 PM
 :o :-[

It's clearly something wrong with G.INP on upstream with high rtx-tc with interleaved depth at 2. SES - 80 now
Title: Re: Badly hit by crosstalk
Post by: burakkucat on June 20, 2019, 11:56:35 PM
I can't see how the DLM activation of US G.Inp can be responsible for the climbing SES count.

I would be more inclined to accept that recent work in the cabinet has disturbed the tie-pairs for your circuit and it is now malfunctioning in a non-linear sense. Whatever the malfunction, it is probably manifesting itself at the low-frequency end of the band. 
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 20, 2019, 11:59:17 PM
Was told by PN earlier today that my upstream are likely to be banded at 19Mbps by DLM.  :(
Title: Re: Badly hit by crosstalk
Post by: burakkucat on June 21, 2019, 12:10:49 AM
That "oscillation" visible in the SNRM plot looks very much like that which sometimes appears on Kitz' circuit after a remote circuit re-train has been instigated. The solution is to close down the circuit from the CPE end.

If you've finished for the day, the simplest thing would be to power off your modem overnight. As I've described it in the past, give the line-card port some time to "relax".
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 12:12:30 AM
I can't do this - modem power down or my daughter will moaned at me she want to watch Netflix in bed.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 07:53:22 AM
The line has resync after 7:30am this morning but SNR are very bad -5dB on downstream. Never see anything like this on my line since FTTC first installed in 2014.

Stats recorded 21 Jun 2019 07:52:18

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 18 min 5 sec
Resyncs:                   1 (since 21 Jun 2019 07:36:15)
         
            Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19000
SNR margin (dB):           -4.7      11.7
Power (dBm):               12.4      0.6
Interleave depth:          16      2
INP:                       46.00      56.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)   

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 28035 Kbps, Downstream rate = 44914 Kbps
Bearer: 0, Upstream rate = 19000 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):        -4.7             11.7
Attn(dB):        11.8            0.0
Pwr(dBm):        12.4            0.6   

Since Link time = 18 min 5 sec
FEC:            1308234         216063
CRC:            15               0
ES:             12               0
SES:            35               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >

Downstream      Upstream
General
   rtx_tx             9901884            40282           
   rtx_c              1552               10511504       
   rtx_uc             1                  1559889         
   LEFTRS             30                 20399           
   minEFTR            79982              18996           
   errFreeBits        1713887            638051878       
Bearer 0
   RxQueue            57                 130             
   TxQueue            19                 26             
   G.INP Framing      18                 18             
   G.INP Lookback     19                 26             
   RRC Bits           24                 24             
   Interleave depth   16                 2               
   INP                46.00              56.00           
   INPRein            1.00               1.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  1               
   INP                4.00               4.00           
   INPRein            4.00               4.00           
   Delay              3                  0   

     
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 08:04:59 AM
I have decided to power down the modem and leave it off for today. Something are not right as downstream ES and SES has gone shoot up pretty fast!
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 11:55:32 AM
Got modem back on after three hours powered down.

The ES and SES has suddenly stopped now and downstream SNR are spot on now.

Ran throughput speed only getting 70Meg (BTw speedtester say IP Profile on your line is 73.59Mbps? Use to be 77.35Mbps.

Stats recorded 21 Jun 2019 11:54:28

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 22 min 40 sec
Resyncs:                   0 (since 21 Jun 2019 11:41:45)
         
            Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19000
SNR margin (dB):           7.8      10.0
Power (dBm):               12.5      0.6
Interleave depth:          16      2
INP:                       46.00      56.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             1.9017      2.0661
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 22964 Kbps, Downstream rate = 89996 Kbps
Bearer: 0, Upstream rate = 19000 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.8             10.0
Attn(dB):        11.8            0.0
Pwr(dBm):        12.5            0.6

Downstream      Upstream
General
   rtx_tx             9918538            33             
   rtx_c              1077               10517073       
   rtx_uc             0                  1591862         
   LEFTRS             26                 20408           
   minEFTR            79982              18996           
   errFreeBits        1706699            638601467       
Bearer 0
   RxQueue            57                 130             
   TxQueue            19                 26             
   G.INP Framing      18                 18             
   G.INP Lookback     19                 26             
   RRC Bits           24                 24             
   Interleave depth   16                 2               
   INP                46.00              56.00           
   INPRein            1.00               1.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  1               
   INP                4.00               4.00           
   INPRein            4.00               4.00           
   Delay              3                  0               

Since Link time = 22 min 59 sec
FEC:            2008882         58407
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 12:33:46 PM
Updated: Still ES and SES zero after 7 hours stable connected ;D When I was powered down the modem I can see red light at the end right side that probably caused lots of ES SES few days ago might caused this. The red light has gone off when I powered it back on this morning. Maybe Billion Modem is getting wearing out? Maybe time to buy new Broadcom chipset modem that work with dslstats and hg612 modem stats?

Since Link time = 7 hours 42 min 43 sec
FEC:            14320112                544075
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: pooclah on June 21, 2019, 06:45:27 PM
Max have you swapped modems?

I'm just wondering why this

         
            Downstream   Upstream
Line attenuation (dB):     11.1      0.0

Went to this

         
            Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 06:54:41 PM
No still the same modem billion 8800nl as I don't have other modem as plusnet hub one sold last year
Title: Re: Badly hit by crosstalk
Post by: pooclah on June 21, 2019, 07:16:27 PM
Strange then. Out of my field so perhaps somebody else can explain it.

Kevin

Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 07:18:55 PM
Beat me, I don't understand of why line attenuation do change time to time?
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 07:32:09 PM
Just noticed both SNR and speed connection has steady now after 6pm.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 07:39:58 PM
Strange then. Out of my field so perhaps somebody else can explain it.

Kevin

Worse case feared me the most are SNR down to -4.7dB with max data rate down to 44914K but stay at 79999K sync rate before I forced it powered it down as things isn't right. This part I don't understand at all why it went below -5dB SNR for FTTC. Wish I showed this to Openreach engineer if I raised this fault with PN but I didn't because I saw modem was steady on red light on warning on the end right side.

Title: Re: Badly hit by crosstalk
Post by: kitz on June 21, 2019, 08:24:22 PM
Quote
Got modem back on after three hours powered down.
The ES and SES has suddenly stopped now and downstream SNR are spot on now.

As mentioned earlier by b*cat when the SNRM starts oscillating like the way it was, then powering down for a while can often resolve this.
I know this isn't the first time and I have definitely told you at least once in the past, possibly more when I've seen your line do similar.  Powering down for a short while resolved it in previously for you.

It usually occurs after an enforced remote power down OR power cut/power surge.    When the modem comes back up the SNR starts spiking in the behaviour displayed on your graphs.
 
It's not unique to your line - I've seen it happen on many other lines.  It's not unique to the modem or FTTC either.   
Mine has been doing so way back to the days of maxdsl.    The first time I saw it happen was using a Voyager 2100 after a workman turned power off at the mains.   I was monitoring using MRTG (there was no Routerstats back then nevermind DSLstas).   
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 08:50:32 PM
Yeah ok but I remember PN and Openreach engineer told me try to leave Modem on at all times! Maybe they talked about not too much rebooted modem etc.

The modem seem lots better now

Bitswap:        6375/6375               4006/4006

Total time = 9 hours 18 min 12 sec
FEC:            14320628                544547
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            27              27
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 3 min 12 sec
FEC:            17              7
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:            45              55
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 = 9 hours 18 min 12 sec
FEC:            14320628                544547
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            27              27
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 = 9 hours 17 min 45 sec
FEC:            14320628                544547
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >
Title: Re: Badly hit by crosstalk
Post by: kitz on June 21, 2019, 09:42:47 PM
Quote
I remember PN and Openreach engineer told me try to leave Modem on at all times! Maybe they talked about not too much rebooted modem etc

It's all about moderation.   Once in a while does no harm especially if the line is doing silly things like oscillating all over the place :)
Some people power down their modems every night - I agree that is total overkill, but DLM is designed to make an allowance for that and because it uses what I believe to be a rather unique way of detecting unforced retrains it shouldn't even pay any attention to one power down per day of >30mins.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 09:57:56 PM
I do believe Billion 8800NL was good modem for a long while since 2015. But, I think if it was too much resync by DLM then the Billion are badly affected by spike SNR all over the place. I do remember Openreach engineer did not approved of this modem and told to use Openreach HG612 modem instead.

Maybe I was going to upgraded a new modem soon FRITZ!Box 7590 with great features and better wireless than Billion. But does the Huawei fibre cabinet like those modem? Like broadcom chipset?
Title: Re: Badly hit by crosstalk
Post by: kitz on June 21, 2019, 10:17:17 PM
Quote
the Billion are badly affected by spike SNR all over the place

As mentioned above the SNR spiking after a remote power down is not unique to the Billion.   It can occur on any modem.   It's just that you are more likely to notice it happening because you can record with DSLstats.

Quote
I do remember Openreach engineer did not approved of this modem and told to use Openreach HG612 modem instead.

He was probably correct to say so, because at one time that and the ECI modem were the only modems approved by Openreach.  Some engineers wouldn't even entertain the hacked versions which gave line stats because they ran on custom firmware. 

Quote
Maybe I was going to upgraded a new modem soon FRITZ!Box 7590 with great features and better wireless than Billion.
Better wireless yes.   But not sure if you need the other features such as 4G backup.  They come with a hefty price tag.    I can't recall off the top of my head which model FRITZ!box my daughter was supplied by Zen, but she hates it because it's fugly and they can't get any decent stats out of it.   The wireless is no better than the TPlink I gave her last year to replace an ECI modem supplied by Openreach when they had a new line installed after they moved.

 



Title: Re: Badly hit by crosstalk
Post by: adslmax on June 21, 2019, 10:21:33 PM
I got TP LINK VR2600 wireless router, the wifi are superb all round but I don't like the modem on it own because there is no connection uptime on it and will not work with dslstats and hg612 modem stats. This is why I have to use Billion modem as stand alone and disabled wireless on it and use TP LINK router as a wireless from the Billion.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 22, 2019, 12:04:13 AM
That's it for today happy with zero ES & SES all day today should be happy for DLM to get back to 20Meg upstream and low retransmission on both downstream and upstream tomorrow I hope so

Since Link time = 12 hours 28 min 25 sec
FEC:            14321133                544718
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: tubaman on June 22, 2019, 08:22:14 AM
That all looks good again.
Time to leave it alone and DLM will doubtless give you the full 20Mbps back before too long.
 :)
Title: Re: Badly hit by crosstalk
Post by: kitz on June 22, 2019, 09:45:25 AM
Quote
because there is no connection uptime on it and will not work with dslstats and hg612 modem stats.

So why are you even thinking out shelling out a few hundred pounds for a Fritz!box which wont either ...  nor will the wifi be any better than your TPlink  :-\

The reason I queried what you said about the Fritz!box is because you would most likely be wasting your money for what you need/want.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 22, 2019, 10:12:32 AM
Updated: No DLM action yet but remain stable with zero ES / SES but still on High Retransmission on both downstream and upstream. @Kitz - ok I stay with both Billion with TP Link for now until Full Fibre come along (FTTP) 

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 26012 Kbps, Downstream rate = 91442 Kbps
Bearer: 0, Upstream rate = 19000 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):        8.4             11.1
Attn(dB):        11.8            0.0
Pwr(dBm):        12.5            0.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              130             163
M:              1               1
T:              0               0
R:              8               10
S:              0.0518          0.2726
L:              21468           5106
D:              16              2
I:              139             174
N:              139             174
Q:              16              2
V:              14              1
RxQueue:                57              130
TxQueue:                19              26
G.INP Framing:          18              18
G.INP lookback:         19              26
RRC bits:               24              24
                        Bearer 1
MSGc:           186             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              5.3333          16.0000
L:              48              16
D:              3               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             1957143152              2995801
RSCorr:         14323109                544796
RSUnCorr:       0               0
                        Bearer 1
OHF:            5060171         886384
OHFErr:         0               0
RS:             60721307                3142884
RSCorr:         187             0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9932109         565
rtx_c:          13027           10517559
rtx_uc:         0               1591862

                        G.INP Counters
LEFTRS:         169             20408
minEFTR:        79999           19002
errFreeBits:    99168671                661686785

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    3913968187              0
Data Cells:     100521017               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               0
SES:            0               0
UAS:            27              27
AS:             81291

                        Bearer 0
INP:            46.00           56.00
INPRein:        1.00            1.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            80614.82        19175.30

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

Bitswap:        6380/6380               4047/4047

Total time = 22 hours 35 min 18 sec
FEC:            14323109                544796
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            27              27
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 5 min 18 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:            13              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 = 22 hours 35 min 18 sec
FEC:            14323109                544796
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            27              27
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 = 22 hours 34 min 51 sec
FEC:            14323109                544796
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >

Downstream      Upstream
General
   rtx_tx             9932112            565             
   rtx_c              13030              10517559       
   rtx_uc             0                  1591862         
   LEFTRS             169                20408           
   minEFTR            79982              18994           
   errFreeBits        99485907           661761925       
Bearer 0
   RxQueue            57                 130             
   TxQueue            19                 26             
   G.INP Framing      18                 18             
   G.INP Lookback     19                 26             
   RRC Bits           24                 24             
   Interleave depth   16                 2               
   INP                46.00              56.00           
   INPRein            1.00               1.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  1               
   INP                4.00               4.00           
   INPRein            4.00               4.00           
   Delay              3                  0 

Title: Re: Badly hit by crosstalk
Post by: michty_me on June 22, 2019, 10:36:22 AM
I would be delighted to get G.inp back on my upstream. I remember many moons ago I had it for a while and gave me nearly full upstream speed. Now I'm sitting about 14mbps.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 22, 2019, 12:00:28 PM
Gone pass 24 hours with no errors

Since Link time = 1 days 28 min 33 sec
FEC:            14323613                544808
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: Chrysalis on June 22, 2019, 03:11:07 PM
I can't see how the DLM activation of US G.Inp can be responsible for the climbing SES count.

I would be more inclined to accept that recent work in the cabinet has disturbed the tie-pairs for your circuit and it is now malfunctioning in a non-linear sense. Whatever the malfunction, it is probably manifesting itself at the low-frequency end of the band. 

If I remember right he reported his DS attainable also shot up, suggesting that work perhaps rearranged a lot of pairs, so these errors could be a improperly connected pair or perhaps some nasty crosstalk affect on the US.  I am inclined to agree with you its related to this work.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 23, 2019, 11:43:15 AM
Still no action on DLM yet. I do believe now that upstream are banded at 19Meg for a long while now because the downstream stay at 80Meg with DLM will take no action.

Since Link time = 2 days 10 min 47 sec
FEC:            14326604                545867
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: CarlT on June 23, 2019, 03:37:22 PM
I would contact Plusnet support. This is serous business.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 24, 2019, 11:54:36 AM
DLM take action this morning just after 6am

The change are:

Downstream   Upstream
Line attenuation (dB):     11.9   (before was 11.8)   0.0
Signal attenuation (dB):   Not available on VDSL2   
Max (kbps):                       91788      32553
Connection speed (kbps):   79999      19000 (no change)
SNR margin (dB):           8.6      12.5
Power (dBm):               12.5      0.6
Interleave depth:          16      4 (before was 2)
INP:                       46.00      49.00 (before was 56.00)
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

Interleave depth   16                 4 (before was 2)             
   INP                46.00              49.00 (before was 56.00)           
   INPRein            0.00 (before was 1.00)               0.00 (before was 1.00)           
   Delay              0                  0     

Look like upstream are banded at 19000Kbps instead of 19999Kbps.  :(
Title: Re: Badly hit by crosstalk
Post by: CarlT on June 24, 2019, 12:22:24 PM
DLM continues to do what it's supposed to. It was implemented and tuned by professionals, not people contemplating how best to irritate a random customer in Telford.

It responded to a severe error condition fairly promptly, it will monitor and only adjust the parameters back once the algorithm is confident it's safe to do so. The worst possible response would be to put you back into conditions where you've packet loss.

Is the loss of 999 kbps of upstream capacity really impacting you so profoundly that you feel it necessary to watch every parameter change as DLM adjusts? Far more impacting was the packet loss that DLM resolved for you.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 24, 2019, 04:24:12 PM
https://www.speedtest.net/result/8362885859

Still throughput speed of 70Meg out of BTw Bras IP Profile 77.35Mbps. I guess PN profile are incorrect one (again) but for upload I lose 1Mbps from it. Normally I get 74/19
Title: Re: Badly hit by crosstalk
Post by: ejs on June 24, 2019, 06:26:25 PM
Do the people who thought that there must have been something physically wrong with adslmax's line think that it's now been fixed?
Title: Re: Badly hit by crosstalk
Post by: Alex Atkin UK on June 24, 2019, 10:01:08 PM
So why are you even thinking out shelling out a few hundred pounds for a Fritz!box which wont either ...  nor will the wifi be any better than your TPlink  :-\

The reason I queried what you said about the Fritz!box is because you would most likely be wasting your money for what you need/want.

Probably getting it free when moving to Zen?
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 26, 2019, 09:22:27 AM
Finally at last DLM has restored everything back to normal now  as upstream are now back at 20000Kbps ;D :)

Stats recorded 26 Jun 2019 09:20:48

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 5 min 21 sec
Resyncs:                   0 (since 26 Jun 2019 09:15:52)
         
            Downstream   Upstream
Line attenuation (dB):     11.9      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      20000
SNR margin (dB):           8.4      11.4
Power (dBm):               12.4      0.7
Interleave depth:          16      8
INP:                       46.00      47.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0000      0.0000
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0

Interleave depth   16                 8               
   INP                46.00              47.00           
   INPRein            0.00               0.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  1               
   INP                4.00               4.00           
   INPRein            4.00               4.00           
   Delay              3                  0   

Title: Re: Badly hit by crosstalk
Post by: burakkucat on June 26, 2019, 06:56:17 PM
That's good to know.  :)
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 26, 2019, 07:54:38 PM
Pretty very good at the moment with no errors and bitswap still on zero.

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 28618 Kbps, Downstream rate = 91116 Kbps
Bearer: 0, Upstream rate = 20000 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):        8.4             11.4
Attn(dB):        11.9            0.0
Pwr(dBm):        12.4            0.7

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              130             97
M:              1               1
T:              0               0
R:              8               8
S:              0.0518          0.1554
L:              21468           5457
D:              16              8
I:              139             106
N:              139             106
Q:              16              8
V:              14              2
RxQueue:                57              39
TxQueue:                19              13
G.INP Framing:          18              18
G.INP lookback:         19              13
RRC bits:               24              24
                        Bearer 1
MSGc:           186             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              5.3333          16.0000
L:              48              16
D:              3               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             2942441104              1191942
RSCorr:         645             386
RSUnCorr:       0               0
                        Bearer 1
OHF:            2381447         293920
OHFErr:         0               0
RS:             28577369                974356
RSCorr:         49              10
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9935592         61
rtx_c:          277             10518098
rtx_uc:         0               1591862

                        G.INP Counters
LEFTRS:         1               20410
minEFTR:        79999           19997
errFreeBits:    46673017                772644367

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1589905760              0
Data Cells:     18288941                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               0
SES:            0               0
UAS:            0               0
AS:             38258

                        Bearer 0
INP:            46.00           47.00
INPRein:        0.00            0.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            80614.82        20102.08

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

Bitswap:        0/0             0/0

Total time = 10 hours 37 min 38 sec
FEC:            645             386
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 7 min 38 sec
FEC:            0               12
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:            2               6
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 = 10 hours 37 min 38 sec
FEC:            645             386
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
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 = 10 hours 37 min 37 sec
FEC:            645             386
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 27, 2019, 10:51:21 AM
DLM has turned off G.INP on upstream.

Stats recorded 27 Jun 2019 10:46:58

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 6 min 56 sec
Resyncs:                   0 (since 27 Jun 2019 10:43:15)
         
            Downstream   Upstream
Line attenuation (dB):     11.9      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19999
SNR margin (dB):           8.6      15.0
Power (dBm):               12.5      0.7
Interleave depth:          16      1
INP:                       48.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0000      0.0010
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0

Interleave depth   16                 1               
   INP                48.00              0.00           
   INPRein            0.00               0.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  0               
   INP                4.00               0.00           
   INPRein            4.00               0.00           
   Delay              3                  0               

This time I have to kept an eyes out on upstream for ES, SES but I thought DLM want to stay G.INP for both to stable the line?
Title: Re: Badly hit by crosstalk
Post by: tubaman on June 27, 2019, 11:34:17 AM
Max, is this DLM instigating the changes or are you manually rebooting the modem?
I ask as all of my DLM resyncs have been in the dead of night, and also your modem is showing no previous resyncs which would indicate a reboot to me.
 :)
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 27, 2019, 11:37:18 AM
Cos I reset all resync on the modem to reset all errors count so I want to see what the errors are like next 24 hours! It's been resync this morning after 3am say thinkbroadband monitor

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d3e60413fe4ce714d2eff50230f56fe7210244e6

Since Link time = 56 min 55 sec
FEC:            18              22
CRC:            0               5 (+27 since 3am) total 32
ES:             0                5 (+11 since 3am) total 16
SES:            0               0 (+3 since 3am) total 3
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 27, 2019, 12:00:12 PM
I have decided enough of these errors so I have powered down modem and switch it back on at around 1pm to stop these crazy errors.
Title: Re: Badly hit by crosstalk
Post by: michty_me on June 27, 2019, 12:13:47 PM
I would just leave it and let DLM do its thing.
Title: Re: Badly hit by crosstalk
Post by: tubaman on June 27, 2019, 12:15:51 PM
Your modem has a 24hr ('Previous 1 Day time') error log built in, so there is no need to reboot it after each DLM intervention.
That low level of ES you are seeing is nothing to worry about at all. Remember that you can have up to 2880 ES per day (assuming Speed profile) before DLM will take action.
 :)
Title: Re: Badly hit by crosstalk
Post by: j0hn on June 27, 2019, 12:59:40 PM
Rebooting and initiating a resync every time DLM makes a change is generally not a good idea.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 27, 2019, 01:16:39 PM
I haven't rebooted it. It was resync itself by DLM at overnight. Anyway, been powered down the modem for an hour. Back online now and will leave it alone to avoid any spike in SNR with these current stats:

Stats recorded 27 Jun 2019 13:15:20

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 14 min 23 sec
Resyncs:                   0 (since 27 Jun 2019 13:15:15)
         
            Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19999
SNR margin (dB):           8.5      15.1
Power (dBm):               12.6      0.6
Interleave depth:          16      1
INP:                       48.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0000      0.0000
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 25858 Kbps, Downstream rate = 91481 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):        8.6             15.1
Attn(dB):        11.8            0.0
Pwr(dBm):        12.6            0.6

                        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               222538
OHFErr:         0               1
RS:             67845680                752555
RSCorr:         7               0
RSUnCorr:       0               0
                        Bearer 1
OHF:            54972           0
OHFErr:         0               0
RS:             658926          0
RSCorr:         1               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9936013         0
rtx_c:          10              0
rtx_uc:         0               0

                        G.INP Counters
LEFTRS:         0               0
minEFTR:        79982           0
errFreeBits:    1077390         0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    135844765               0
Data Cells:     90390           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               1
SES:            0               0
UAS:            28              28
AS:             883

                        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:        3/3             1/1

Total time = 15 min 11 sec
FEC:            7               0
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 11 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:            7               0
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 15 min 11 sec
FEC:            7               0
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            28              28
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 = 14 min 43 sec
FEC:            7               0
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 27, 2019, 01:34:50 PM
So after 30 minutes uptime, the Errors seem lots better now after powered down the modem. I do believe everytimes the DLM resync overnight cause a spike in SNR all over the place with red light on the modem when G.INP was removed off (upstream). Maybe Billion modem issues with resync itself with spike. I dunno. Not sure why. I better go outside now and don't need to check dslstats until tomorrow to see what the errors are. I wish DLM leave both upstream and downstream G.INP enabled on and leave it alone but surprise DLM decided to turn off G.INP (Upstream for no reason)

Since Link time = 33 min 23 sec
FEC:            63              0
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: CarlT on June 27, 2019, 02:14:48 PM
Better idea: turn DSL Stats off. If you don't notice anything wrong it's fine.

Monitoring every twitch of your broadband is neither healthy or normal, it's pretty obsessive.
Title: Re: Badly hit by crosstalk
Post by: grahamb on June 27, 2019, 03:12:18 PM
Better idea: turn DSL Stats off. If you don't notice anything wrong it's fine.

Actually, that's sound advice for everybody!  ;)
Title: Re: Badly hit by crosstalk
Post by: re0 on June 27, 2019, 03:31:38 PM
Actually, that's sound advice for everybody!  ;)
Me, three. I would reserve it for diagnostics, but I cannot personally resist having a Raspberry Pi connected for 24/7 logging and graphing. :-X I do not think the logging and graphing is a problem in itself, since it could prove useful if a fault comes along. But the checking I do multiple times a day is... excessive. :-[
Title: Re: Badly hit by crosstalk
Post by: CarlT on June 27, 2019, 05:25:55 PM
Everyone should be forced to work in IT for a while. Will soon reduce the appetite to 'take work home' with you.
Title: Re: Badly hit by crosstalk
Post by: re0 on June 27, 2019, 06:37:08 PM
Everyone should be forced to work in IT for a while. Will soon reduce the appetite to 'take work home' with you.
That'll work, at least until you quit. Though, if you ever work on "helldesk", then you'd probably never want to work again. :P
Title: Re: Badly hit by crosstalk
Post by: tubaman on June 27, 2019, 06:40:23 PM
Better idea: turn DSL Stats off. If you don't notice anything wrong it's fine.
....
Oh so true.....but It's very tempting to have a little peek every now and again. ::)
Title: Re: Badly hit by crosstalk
Post by: flilot on June 27, 2019, 06:54:10 PM
Though, if you ever work on "helldesk", then you'd probably never want to work again. :P

I recommend everyone work on a "helldesk" at least once in their life.  It toughens you up (aside from crying in the car on the way home every night).   :lol:
Title: Re: Badly hit by crosstalk
Post by: re0 on June 27, 2019, 07:06:35 PM
I recommend everyone work on a "helldesk" at least once in their life.  It toughens you up (aside from crying in the car on the way home every night).   :lol:
And remember, if you want to keep your job, the director of a company who needs support is always right and shouldn't need to follow your instructions. The bigger the support package, the more right they are.

Sorry for off topic!
Title: Re: Badly hit by crosstalk
Post by: flilot on June 27, 2019, 08:36:32 PM
And remember, if you want to keep your job, the director of a company who needs support is always right and shouldn't need to follow your instructions. The bigger the support package, the more right they are.

Sorry for off topic!
Spot on!  ;D
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 27, 2019, 09:05:19 PM
Just got back home from a day out. Not surprise the Errors are start to pick up again. DLM should have left G.INP enabled to get errors free. But the errors are not that bad then 6/7 days ago.

Don't understand DLM sometimes.  ???

Since Link time = 7 hours 59 min 57 sec
FEC:            966             78
CRC:            0               26
ES:             0               22
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Title: Re: Badly hit by crosstalk
Post by: tubaman on June 28, 2019, 08:00:33 AM
No problem with that level of errors - just ignore them.
Clearly you are used to a line with virtually no errors, but that is a very unusual thing. DLM is not there to give you an error free line, but the best balance between speed and an acceptable error level.
Below are the stats from my line - look at how many errors there are, but also look at the 49 days of uptime. You can have a lot of errors before DLM worries about it, and you are barely scratching the surface with the number you have.
 :)

(Ignore my 'since link time' counter showing under 3 minutes - it's a bug in my Zyzel unit that the days and hours drop off after a certain amount of uptime)
Code: [Select]
====================================================================================
    VDSL Training Status:   Showtime
                    Mode:   VDSL2 Annex B
            VDSL Profile:   Profile 17a
                G.Vector:   Disable
            Traffic Type:   PTM Mode
             Link Uptime:   49 days: 17 hours: 2 minutes
====================================================================================
       VDSL Port Details       Upstream         Downstream
               Line Rate:      7.056 Mbps       45.516 Mbps
    Actual Net Data Rate:      7.030 Mbps       45.517 Mbps
          Trellis Coding:         ON                ON
              SNR Margin:        4.9 dB            3.1 dB
            Actual Delay:          0 ms              0 ms
          Transmit Power:        6.5 dBm          11.9 dBm
           Receive Power:      -15.5 dBm         -23.4 dBm
              Actual INP:        0.0 symbols      50.0 symbols
       Total Attenuation:        0.0 dB          26.6 dB
Attainable Net Data Rate:      6.882 Mbps       46.087 Mbps
====================================================================================
  VDSL Band Status        U0      U1      U2      U3      U4      D1      D2      D3
  Line Attenuation(dB): 11.7 51.0   N/A   N/A   N/A 21.4 60.7 90.3
Signal Attenuation(dB): 11.7 51.3   N/A   N/A   N/A 33.3 60.3   N/A
        SNR Margin(dB): 5.1 4.9   N/A   N/A   N/A 3.1 3.1   N/A
         TX Power(dBm): -3.9 6.1   N/A   N/A   N/A 9.8 7.8   N/A
====================================================================================

            VDSL Counters

           Downstream        Upstream
Since Link time = 2 min 47 sec
FEC: 1369264475 6101
CRC: 175418 2410
ES: 46710 2232
SES: 747 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 55 sec
FEC: 184730 1
CRC: 20 0
ES: 6 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: 143395 3
CRC: 11 1
ES: 6 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 42 min 55 sec
FEC: 524877 4
CRC: 45 1
ES: 20 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: 28067001 116
CRC: 4519 56
ES: 1020 50
SES: 19 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Total time = 1 days 42 min 55 sec
FEC: 3975250867 7877
CRC: 351380 6026
ES: 107888 5711
SES: 1105 3
UAS: 172 140
LOS: 3 0
LOF: 19 0
LOM: 0 0
====================================================================================
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 28, 2019, 10:11:25 AM
My errors count latest stats:

Since Link time = 21 hours 8 min 5 sec
FEC:            3026            202
CRC:            0               76
ES:             0               68
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 25739 Kbps, Downstream rate = 91337 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):        8.5             15.0
Attn(dB):        11.8            0.0
Pwr(dBm):        12.6            0.6

Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19999
SNR margin (dB):           8.5      15.0
Power (dBm):               12.6      0.6
Interleave depth:          16      1
INP:                       48.00      0
G.INP:                     Enabled      Not enabled

Still low errors on upstream but more important the downstream are errors free which it good.
Title: Re: Badly hit by crosstalk
Post by: adslmax on June 29, 2019, 08:42:27 AM
Latest stats below: so far everything looking good.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 03, 2019, 07:07:25 PM
Updated after 6 days and 6 hours: All seem fine without any DLM action.

Title: Re: Badly hit by crosstalk
Post by: adslmax on July 07, 2019, 01:14:08 PM
Updated after 10 days and all seem fine without any DLM action.  ;D


Title: Re: Badly hit by crosstalk
Post by: adslmax on July 09, 2019, 07:28:05 PM
Tomorrow I might order G.fast with Zen Internet as Zen say the total cost below:

New line installation £70.80
New G.fast activated fee £55.00
New G.fast service 160/30 £49.99

Total cost one off payment £175.79 then 11 monthly payments of £49.99 on a 12 months contract.

Openreach email communicate with me below:

1st email:
Iíve had one of our technical experts take a look at why the 2 premises below are being quoted different speeds, heís confirmed that this is due to discrepancies being identified on one of the lines that would need to be resolved to enhance the speed.  In this instance (mine) would be offered a managed install (engineering visit) to optimise the line and fix any wiring issues, whereas (next 2 doors) could opt for a self-install.  The estimated speeds are based on physical measurements taken from our line test systems.

2nd email:
An engineer managed install will certainly help you achieve the best possible speed, however Iím unable to provide a guarantee as to what that would be.  Given the estimated speeds from the line tests, you would hope something very close to 300mb would be achievable.

3rd email:
Unfortunately an engineer visit can only be arranged once we have received an order.  Thereís a number of ISPís who can offer the GFAST service, however they would all be in the same position.

4th email:
The ISPís can and do set different minimum thresholds, you would therefore need to discuss this point directly with them.

Anyway I spoken to Zen Internet as they asked the provisioning team of everything what openreach and I was communicate about G.fast and Zen say that Engineer is only come to my property to installed new line socket as per of my request and put in the same hallway where the feed are coming in from outside as it will be in your master socket (where your current FTTC on it) and added a second master socket for G.fast and switched the line on. Zen say engineer are not responsible for any optimise the line and fix any wiring issues such as very close to 300mb would be achievable nor set different minimum thresholds. U will order 160/30 as our test system say your line will support 198Meg down and 29Meg up but these could anything from 114Meg to 152Meg for your line. We held no responsible for not getting 300Meg or more as your line length are much further away from the exchange to the cabinet.

But, Zen Internet warned me 10 days cooling period is only start from the day of your order not the day of your G.fast activated so u can't cancelled the order once it was activated as it will be more than 10 working days for the new line and G.fast possible within 2 weeks.

here is layout of where the g.fast cable route (sorry for my poor layout drawing) go to: https://ibb.co/wCdXVHM
 



 

 

Title: Re: Badly hit by crosstalk
Post by: j0hn on July 10, 2019, 01:18:57 AM
Do you know what houses are on the same DP as you?
Is the house in your drawing that had the 330/50 estimate on the same DP?

Do you need G.Fast? That's a lot of money for something you likely don't need.

I would guess you would get the full 160/30 as your estimates look off compared to the neighbours.
You could always get 114/9 though.

I'm not sure how Zen come up with their estimates.
The upstream estimate is your clean/high estimate.
The downstream estimate range is between slightly under clean/high and slightly above impacted/low.
I also though 120Mb was the minimum now so how can they estimate as low as 114Mb?

Zen give you a Huawei MT992 which gives zero stats.
The Zen portal will tell you the current sync speed.

You would need to kindly ask the OpenReach engineer to show you on his/her handheld device what the line is capable of like in the attached image.
They have no obligation to show you this though so be nice and offer tea/coffee and biscuits.

It looks like an Exfo MaxTester 630G
https://www.exfo.com/en/products/field-network-testing/copper-dsl-testing/maxtester-630g/

I think if you don't need it, don't order it.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 10, 2019, 02:06:42 AM
Do you know what houses are on the same DP as you? Yes
Is the house in your drawing that had the 330/50 estimate on the same DP? Yes

If that house get 330/50 then why should mine get it as well as all houses are are the same connected to cabinet 8? See screenshot below

Title: Re: Badly hit by crosstalk
Post by: tubaman on July 10, 2019, 08:10:47 AM
What would this much more expensive service allow you to do that you can't do on your current 80/20 service?
As j0hn has eluded to you could end up with 114/9 - ie faster download but less than half of your current upload speed, although this would appear unlikely. Are you prepared to take that risk?
One other thing - how do you manage to communicate directly with Openreach, as I thought consumers could only go via an ISP?
 :)
Title: Re: Badly hit by crosstalk
Post by: PhilipD on July 10, 2019, 08:12:59 AM
Hi

If that house get 330/50 then why should mine get it as well as all houses are are the same connected to cabinet 8? See screenshot below

The only way to know is order it and find out.  No one here can possibly answer your question as to why or what speed you will get as we don't have the information.  BT are the holders of more information than any of us, but yes they can have mistakes in that data, again you'll only know for sure when you have a working G.Fast connection.  G.Fast frequencies can fall off a cliff over just a few metres, and we don't know how your telephone line route compares to next door or next door but one.  Another 10 or 15 metres can easily see G.Fast drop from top speed to something less impressive. 

There is likely to be more than one distribution point on your street, so somewhere along it you will get a split, where one house goes to one distribution point, and next door goes to another.  Say that DP is further up the street away from the PCP, then the telephone line travels away from the PCP, joins the distribution point before travelling back to the PCP, easily adding many metres of distance.

It doesn't matter how many posts you make on the subject, or who you email, you will not get any confirmation of being able to get anything more than the Low estimates. 

Either decide not to order G.Fast and let the subject drop, or order it and find out what you can achieve in reality.

Regards

Phil





Title: Re: Badly hit by crosstalk
Post by: adslmax on July 10, 2019, 09:24:44 AM
It's pretty stupid for Zen Internet to limit 10 days cooling off period from the first day of your order not the first day of installation? Because if the engineer switched on G.fast and bingo I got full 330/50 then it will be worth it and Zen will charged me for another order to upgraded from 160/30 to 330/50 if Zen got the proof from my line stats, if was disappointed low at 114/9 then can cancelled it with cooling off period within 10 days of activated.

Is there any other ISP's can do that like cooling off period on day of activation not the day of order?

Title: Re: Badly hit by crosstalk
Post by: PhilipD on July 10, 2019, 09:37:24 AM
Hi

You will just have to do a search on ISPs and see what their terms and conditions are.  Think Vodafone do 30 days.

Zen are just doing the legal minimum required, it's not stupid for them. :)

Hopefully the next post from you will be that you've upgraded and post your G.Fast line stats, or we don't hear from you again on this topic :)  No one can make the decision for you.

Regards

Phil


Title: Re: Badly hit by crosstalk
Post by: adslmax on July 10, 2019, 09:40:13 AM
How to access G.fast modem stats like openreach engineer to provided one? Unlocked hack to get these full stats?

But, if Zen think my line will be 114/9 but Openreach are now minimum for G.fast to order is at 120Mbps (use to be 100Mbps) and more likely the order will get rejected by BTw?
Title: Re: Badly hit by crosstalk
Post by: tubaman on July 10, 2019, 10:09:49 AM
I doubt any of the ISP supplied kit will provide much, if anything, in the way of stats - you'll need to buy your own for that, and it won't be cheap as G.fast is quite new and not that widely used so the choice is pretty limited.
I'm not aware that anyone has unlocked the MT992 yet, but others may know more about that.
 :)
Title: Re: Badly hit by crosstalk
Post by: PhilipD on July 10, 2019, 10:15:13 AM
How to access G.fast modem stats like openreach engineer to provided one? Unlocked hack to get these full stats?

But, if Zen think my line will be 114/9 but Openreach are now minimum for G.fast to order is at 120Mbps (use to be 100Mbps) and more likely the order will get rejected by BTw?

Stop going around in circles, we don't really know. Yes now the rules have changed, again no one knows how an ISP will interpret those rules when the estimated speed range goes above and below 120.  You had chance to order G.Fast ages ago, you've been talking about it for long enough, so give it enough time and the goal posts will move, that's life.

Try placing an order and find out and tell us.

You will have some idea of sync speed by a simple speed test, no need for hacked modems.

This is completely off topic now.  There is nothing anyone can say that hasn't been said already to you.  Order it, or leave it, your decision.





Title: Re: Badly hit by crosstalk
Post by: adslmax on July 10, 2019, 10:19:44 AM
Running speed test will be pointless as it will be capped at 160/30 how would I know if it will go to max data rate like 330/50? I have to be polite ask the engineer to show me the stats rate for G.fast from his kit tool and should be able to tell me what are the max data rate are?

Think I have to bite the bullet and get this order with Zen today!

Line one will be PN FTTC 80/20 (until October then cease on the line)
Line two will be Zen G.fast 160/30

I got very high confident and believe my line will gain around 250/30 or greater not 114/9 from Zen. I have to trust my line can get around 250-300 / 30-40 on the line.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 10, 2019, 11:27:02 AM
Oh dear me, if I want to see G.fast full stats the BT Smart 2 Hub are expensive £200 but it warned there: Please note: The BT Smart Hub will only work with BT broadband (don't think it won't work with other ISP like Zen :( :o https://shop.bt.com/products/bt-smart-hub-2-097683-DYNK.html

Cos the MT992 will be very difficult to get it unlocked. I guess I have to leave G.fast out for now. Stay with FTTC for now and have to accepted to stay with 80/20 for few more years until IF they ever bring FTTP to my area one day. Who know.

Title: Re: Badly hit by crosstalk
Post by: tubaman on July 10, 2019, 11:56:27 AM
Yes, BT's routers are all locked to the BT/Plusnet service as they won't allow you to change the PPP credentials (amongst other things).
Even if they weren't they only give you pretty basic stats anyway.
If you need the extra speed of G.fast then you have little option but to live without detailed connection stats at present.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 10, 2019, 04:16:52 PM
Just got email back from Openreach as BTw database will updated soon for two next doors as it was wrong speed estimated at 330/50 as it should be 231/35 not 330/50. And also good news they say my house should be 227/35 not 198/29. Openreach has apology for this incorrect wrong data.

They say the correct data for my property are below:

Title: Re: Badly hit by crosstalk
Post by: g3uiss on July 10, 2019, 10:23:26 PM
Oh this seems a long thread. Iím not sure being pragmatic what can be achieved here. I have 22 down 2 up and there is nothing I canít stream / download. And thatís all I can get.

In reality the products are cheap, what exactly does a user need in the really world. I challenge anyone to note a few mpbs difference in their connection.
Title: Re: Badly hit by crosstalk
Post by: carringj on July 10, 2019, 11:36:22 PM
I totally agree. At my previous house I had a 25/5 connection. I used to stream HD content, download large files, teach classes over Webex etc etc. Never had a problem. I now live in a VM area and have a 100/6 connection - its more than enough capacity. What is this obsession to get more speed - if you have 5+ people living with you who are constantly downloading large files or streaming 4K at the same time, then it could be justified.
Title: Re: Badly hit by crosstalk
Post by: re0 on July 10, 2019, 11:37:21 PM
Max, you may have the option of the ZyXEL XMG3927-B50A from A&A which should be priced a smidge under £150. Still expensive but no issues with it thus far. You would have to email them to find out the current price and availability.

Are you going to try your luck with the 160/30 package after all this, or we looking forward to another 9 pages? :P I have confidence the sync rate will be satisfactory enough for the package, but the age old question is: is it worth it?
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 11, 2019, 12:21:30 AM
Not going to order G.fast 160/30 because it not worth the money. Stayed with FTTC.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 11, 2019, 02:37:42 PM
I have finally ordered G.fast 160/30 and see how it goes from there. Not Zen Internet but different ISP. Openreach engineer come to my property to install new line and G.fast 29th July am slot.

I just want to get on with it and can cancel PN FTTC in October when my contract has expired.
Title: Re: Badly hit by crosstalk
Post by: tubaman on July 11, 2019, 05:31:36 PM
Which ISP did you go with?
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 11, 2019, 06:33:48 PM
My new ISP will be CIX in here: https://www.cix.uk/broadband/gfast as they say it will be openreach managed install with Huawei MT992 Openreach modem as I have to use my own TP Link VR2600 Wireless Router.

How long do I need to wait for new telephone number data to come up? There is no data available for this number. This could be either because it is not a BT line or it is a new BT number that has just been provided. Most new numbers will appear on the checker 24 hours after BT has installed the line
Title: Re: Badly hit by crosstalk
Post by: tubaman on July 12, 2019, 08:13:09 AM
I've not seen them before.
How much is that costing, as the £39 per month quoted by CIX appears to require line rental on top?
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 12, 2019, 08:56:46 AM
No line rental are £13 per month on top of G.fast £39 totally £52 a month inc VAT and they do have excellent control panel https://www.cix.uk/broadband/control-panel
Title: Re: Badly hit by crosstalk
Post by: j0hn on July 12, 2019, 09:30:02 AM

How long do I need to wait for new telephone number data to come up? There is no data available for this number. This could be either because it is not a BT line or it is a new BT number that has just been provided. Most new numbers will appear on the checker 24 hours after BT has installed the line

The answer is in your question.
24 hours after they enable your line.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 12, 2019, 09:36:05 AM
Thanks. CIX did told me my G.fast can get full max 160/30 no problem but for 330/50 they suggest me to try 160/30 first and CIX will ask engineer in report of what the max data rate for G.fast once it activated. But CIX say I could possible get 227/35 but try 160/30 first see how it go.
Title: Re: Badly hit by crosstalk
Post by: j0hn on July 12, 2019, 09:52:45 AM
Shouldn't you try 160/30 and see if it is enough for YOU.

You don't need to order the fastest speed available just to take part in an internet willy waving competition.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 12, 2019, 10:07:53 AM
The reason I want G.fast 330/50 not because of download but a much better upload speed.
Title: Re: Badly hit by crosstalk
Post by: tubaman on July 12, 2019, 10:34:17 AM
The reason I want G.fast 330/50 not because of download but a much better upload speed.

What are you uploading that needs that sort of speed? I ask as I am stuck with about 6Mbps upload and that is more than adequate for my needs.
 :)
Title: Re: Badly hit by crosstalk
Post by: j0hn on July 12, 2019, 11:09:47 AM
The reason I want G.fast 330/50 not because of download but a much better upload speed.

With your estimates G.Fast risks providing a lower upstream rate than VDSL2.

If it's only for the increased upstream you might be very disappointed.
Title: Re: Badly hit by crosstalk
Post by: adslmax on July 12, 2019, 11:37:37 AM
I have cancel the order with CIX cos they reply with my email as BTwholesale with the order of G.fast was below minimum 120Mbps on G.fast and here is the line estimated from BTw from CIX. Overall disappointed with that poor estimated look like Zen Internet are right from the start as they did warned me of those low speed of 114/9 on G.fast.

Hi **********,

Estimates for the property are:

Down:     101 - 114.2
Up:       9.1 - 12.1

Regards,

***********
CIX
Title: Re: Badly hit by crosstalk
Post by: burakkucat on July 12, 2019, 06:17:04 PM
The Subject line of this topic is "Badly hit by crosstalk".

As its contents have now meandered off into the realms of what Max may or may not order, has or has not ordered, etc, I have decided that "time" should be called on this topic.

Hence my announcement: This topic is now locked.