Line 'stuck' at 55 down 9 up.

ClixRapidix — Wed, 14 Sep 2022 16:14:39 GMT

Hello everyone,

I moved to a new property and the only connection I can get is a VDSL2, coming from a previous FTTH connection I'm a bit disappointed but it is what it is, and since my exchange is not an FTTH priority exchange its safe to assume its going to take a couple of years. I've been using VDSL2 before so its okay as long as its stable.

I'm using a Netgear DM200 acting purely as a modem only, and for the main router I'm using an ASUS RT-AC86U.

The Netgear line stats tell me that I can get at least 70 down and 19 up. I'm currently synced at 55 down and 9 up. I know it can take 10 days for the DSLAM to find a stable rate.

I don't mind the download speed since its good enough for my needs, but the upload makes a bit of difference since I work from home and I tend to upload large files to the cloud.

I called BT and they said that the best my line can do is down 40 (I'm synced at 55 so good), but they cannot assume me a solid upload speed. Can anyone shine a light on this or what I can do?

Here are my line stats:

BusyBox v1.28.4 () built-in shell (ash) BusyBox v1.28.4 (2018-05-22 15:53:59 EDT) built-in shell (ash) Enter 'help' for a list of built-in commands. +---------------------------------------------+ | Lantiq UGW Software UGW-6.1.1 on XRX200 CPE | root@DM200:~# ./line_stats.sh local dsl={} dsl.atuc_vendor_id="Infineon 178.6" dsl.atuc_system_vendor_id="45,43,49,20,74,65,6C,65" dsl.chipset="Lantiq-VRX200" dsl.firmware_version="5.7.11.5.0.7" dsl.api_version="4.17.18.6" dsl.xtse1=0x0 dsl.xtse2=0x0 dsl.xtse3=0x0 dsl.xtse4=0x0 dsl.xtse5=0x0 dsl.xtse6=0x0 dsl.xtse7=0x0 dsl.xtse8=0x2 dsl.xtse_s="0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2" dsl.annex_s="B" dsl.line_mode_s="G.993.2 (VDSL2)" dsl.profile=6 dsl.profile_s="17a" dsl.line_state_num=0x801 dsl.line_state_detail="showtime_tc_sync" dsl.line_state="UP" dsl.errors_fec_near=2817 dsl.errors_fec_far=672451769 dsl.errors_es_near=0 dsl.errors_es_far=92665 dsl.errors_ses_near=0 dsl.errors_ses_far=1456 dsl.errors_loss_near=0 dsl.errors_loss_far=452 dsl.errors_uas_near=35 dsl.errors_uas_far=35 dsl.errors_hec_near=0 dsl.errors_hec_far=0 dsl.errors_crc_p_near=0 dsl.errors_crc_p_far=0 dsl.errors_crcp_p_near=0 dsl.errors_crcp_p_far=0 dsl.power_mode_num=0 dsl.power_mode_s="L0 - Synchronized" dsl.latency_num_down="8.0 ms" dsl.latency_num_up="0.0 ms" dsl.latency_s_down="Interleave" dsl.latency_s_up="Fast" dsl.data_rate_down=55000000 dsl.data_rate_up=9995000 dsl.data_rate_down_s="55.000 Mb" dsl.data_rate_up_s="9.995 Mb" dsl.line_attenuation_down="11.8" dsl.line_attenuation_up="10.6" dsl.noise_margin_down="7.6" dsl.noise_margin_up="12.5" dsl.signal_attenuation_down="12.1" dsl.signal_attenuation_up="10.7" dsl.actatp_down="-1.5" dsl.actatp_up="-1.7" dsl.max_data_rate_down=71224872 dsl.max_data_rate_up=19389375 dsl.max_data_rate_down_s="71.224 Mb" dsl.max_data_rate_up_s="19.389 Mb" dsl.line_uptime=347 dsl.line_uptime_s="5m 47s"

Thank you 🙂

Re: Line 'stuck' at 55 down 9 up.

licquorice — Wed, 14 Sep 2022 16:35:11 GMT

Your line has been provisioned as Fibre1 rather than Fibre2. Call customer services and point out their error.

This topic

Line 'stuck' at 55 down 9 up.

Re: Line 'stuck' at 55 down 9 up.