topic Re: SLow adsl in Broadband

SLow adsl

Georg — Sat, 02 Mar 2024 09:01:39 GMT

I have just changed broadband from one provider to plus net , old provider I was 20mb-22mb on adsl2+ as I am approx 950m

from exchange now my speed is 4mb-7mb. https://librespeed.org/results/?id=10kccdm. I know that it takes up to 10 days to level out but not a slow speed as is. Plugged into main nte no extns.

any help please

Re: SLow adsl

willcutforth — Sat, 02 Mar 2024 12:02:17 GMT

@Georg Sorry to hear that. Are you able to describe how you are set up? THe best way to do it would be through sending us pictures if possible.

Re: SLow adsl

Townman — Sat, 02 Mar 2024 13:16:15 GMT

It would help if you first post your router stats please.

Connection modulation, U/L and D/L speed, attenuation and SNRM.

Is there any noise on the telephone line?

Re: SLow adsl

Georg — Sat, 02 Mar 2024 16:25:55 GMT

1. Product name:	Plusnet Hub
2. Serial number:	+081441+NQ81820617
3. Firmware version:	Software version 4.7.5.1.83.8.289.1.3 Last updated Unknown
4. Board version:	Plusnet Hub One
5. DSL uptime:	0 days, 10:19:57
6. Data rate:	448 / 8096
7. Maximum data rate:	1296 / 11584
8. Noise margin:	26.0 / 20.2
9. Line attenuation:	10.0 / 14.1
10. Signal attenuation:	10.0 / 14.9
11. Data sent/received:	292.1 MB / 8.7 GB
12. Broadband username:	xxxxxxx@plusdsl.net
13. 2.4 GHz Wireless network/SSID:	PLUSNET-5X2N
14. 2.4 GHz Wireless connections:	Enabled (802.11 b/g/n (up to 144 Mb/s))
15. 2.4 GHz Wireless security:	WPA2
16. 2.4 GHz Wireless channel:	Automatic (Smart Wireless)
17. 5 GHz Wireless network/SSID:	PLUSNET-5X2N
18. 5 GHz Wireless connections:	Enabled (802.11 a/n/ac (up to 1300 Mb/s))
19. 5 GHz Wireless security:	WPA2
20. 5 GHz Wireless channel:	Automatic (Smart Wireless)
21. Firewall:	Default
22. MAC Address:	08:d5:9d:93:f2:d8
23. VPI/VCI:	0 / 38
24. Modulation:	G.992.1 Annex A
25. Latency type:	Interleaved
26. Software variant:	AA
27. Boot loader:	1.0.0

Moderator's note:
Personal information removed from a public forum (to an area that staff can see).

Re: SLow adsl

HPsauce — Sat, 02 Mar 2024 14:18:21 GMT

Downstream attenuation of 14 (implies line length about 1km) would give maximum speeds around 22mbps as you have had.

Noise margin downstream of 20 implies a fault or restriction, it's normally about 6. Cause or effect?

Re: SLow adsl

jab1 — Sat, 02 Mar 2024 14:23:00 GMT

Noise margin and DSL uptime point to a major fault somewhere - unless the Hub has been rebooted/switched off.

Re: SLow adsl

Georg — Sat, 02 Mar 2024 14:23:21 GMT

Router is setup as per instructions using all Plusnet cables into a filter as I took the main plate offf nte as it was a problem in the past . No extensions just 1 cordless phone. Adsl is adsl_G.dmt. was Adsl2+ with last provider same routing from exchange as beginning of the week when old provider ceased getting 20-22mb.

Re: SLow adsl

RealAleMadrid — Sat, 02 Mar 2024 14:29:59 GMT

@Georg For some unknown reason you have been provisioned on the wrong service G.992.1 modulation is plain ADSL, you should be on ADSL2+ which is G.992.5 which has the higher speed you should be getting.

Need to call support and hope they understand the error of their ways and fix it.

@jab1 It's not a line fault, just on the wrong service.

Re: SLow adsl

jab1 — Sat, 02 Mar 2024 14:33:06 GMT

@RealAleMadrid OK - although the DSL uptime looks strange for the amount of data transferred. Would be interesting to see the router error log.

Re: SLow adsl

HPsauce — Sat, 02 Mar 2024 14:37:06 GMT

Data rate 448/8096 looks like the line has been configured at an "old school" fixed speed!

Re: SLow adsl

RealAleMadrid — Sat, 02 Mar 2024 14:38:39 GMT

@willcutforth You don't need to see any pictures. The OP is on the wrong ADSL service, standard ADSL which explains the low speeds.

Plusnet needs to modify the service to ADSL2+

Re: SLow adsl

willcutforth — Sat, 02 Mar 2024 15:20:59 GMT

@RealAleMadrid Done

Re: SLow adsl

Georg — Sat, 02 Mar 2024 21:01:44 GMT

20:41:09, 02 Mar.	BLOCKED 14 more packets (because of Packet invalid in connection)
20:41:08, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59646 on ppp0)
20:41:07, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client associated
20:41:05, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [213.123.252.186]:443->[51.6.202.121]:59732 on ppp0)
20:41:03, 02 Mar.	BLOCKED 1 more packets (because of Packet invalid in connection)
20:41:02, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59694 on ppp0)
20:41:01, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client disassociated
20:40:56, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [204.79.197.200]:443->[51.6.202.121]:59714 on ppp0)
20:40:55, 02 Mar.	BLOCKED 8 more packets (because of Packet invalid in connection)
20:40:54, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [81.134.117.171]:443->[51.6.202.121]:59708 on ppp0)
20:40:54, 02 Mar.	BLOCKED 7 more packets (because of Packet invalid in connection)
20:40:52, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [81.134.117.171]:443->[51.6.202.121]:59705 on ppp0)
20:40:52, 02 Mar.	BLOCKED 8 more packets (because of Packet invalid in connection)
20:40:52, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [184.28.176.67]:443->[51.6.202.121]:59653 on ppp0)
20:40:52, 02 Mar.	BLOCKED 9 more packets (because of Packet invalid in connection)
20:40:51, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59646 on ppp0)
20:40:50, 02 Mar.	BLOCKED 1 more packets (because of Packet invalid in connection)
20:40:50, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client associated
20:40:49, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59695 on ppp0)
20:40:48, 02 Mar.	BLOCKED 1 more packets (because of Packet invalid in connection)
20:40:47, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59694 on ppp0)
20:40:45, 02 Mar.	BLOCKED 1 more packets (because of Packet invalid in connection)
20:40:44, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [213.123.252.186]:443->[51.6.202.121]:59659 on ppp0)
20:40:44, 02 Mar.	BLOCKED 12 more packets (because of Packet invalid in connection)
20:40:44, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client disassociated
20:40:43, 02 Mar.	IN: BLOCK [5] Fragmented packet (IP 192.168.1.232->192.168.1.66 fragment_offset=1504)
20:40:43, 02 Mar.	IN: BLOCK [5] Fragmented packet (IP 192.168.1.232->192.168.1.66 fragment_offset=32)
20:40:43, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59646 on ppp0)
20:40:41, 02 Mar.	BLOCKED 1 more packets (because of Packet invalid in connection)
20:40:40, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [213.123.252.186]:443->[51.6.202.121]:59659 on ppp0)
20:40:40, 02 Mar.	BLOCKED 12 more packets (because of Packet invalid in connection)
20:40:39, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59646 on ppp0)
20:40:39, 02 Mar.	BLOCKED 2 more packets (because of Packet invalid in connection)
20:40:37, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [13.107.246.64]:443->[51.6.202.121]:59620 on ppp0)
20:40:37, 02 Mar.	BLOCKED 18 more packets (because of Packet invalid in connection)
20:40:37, 02 Mar.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [92.123.128.151]:443->[51.6.202.121]:59646 on ppp0)
20:40:33, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client associated
20:40:28, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client disassociated
20:40:17, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client associated
20:40:11, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client disassociated
20:40:00, 02 Mar.	ath00: STA c0:4a:00:cb:51:5f IEEE 802.11: Client associated
20:39:58, 02 Mar.	(108213.750000) Lease for IP 192.168.1.66 renewed by host Unknown-f2-29-8a-29-6c-84 (MAC f2:29:8a:29:6c:84). Lease duration: 1440 min
20:39:58, 02 Mar.	(108213.750000) Device connected to ath10: Hostname: Unknown-f2-29-8a-29-6c-84 IP: 192.168.1.66 MAC: f2:29:8a:29:6c:84 via f2:29:8a:29:6c:84 Lease time: 1440 min. Link rate: 866.7 Mbps
20:39:58, 02 Mar.	(108213.680000) Lease requested
20:39:56, 02 Mar.	(108211.050000) Lease for IP 192.168.1.66 renewed by host Unknown-f2-29-8a-29-6c-84 (MAC f2:29:8a:29:6c:84). Lease duration: 1440 min
20:39:56, 02 Mar.	(108211.050000) Device connected to ath10: Hostname: Unknown-f2-29-8a-29-6c-84 IP: 192.168.1.66 MAC: f2:29:8a:29:6c:84 via f2:29:8a:29:6c:84 Lease time: 1440 min. Link rate: 351.0 Mbps
20:39:56, 02 Mar.	(108210.980000) Lease requested
20:39:54, 02 Mar.	(108209.070000) Lease for IP 192.168.1.66 renewed by host Unknown-f2-29-8a-29-6c-84 (MAC f2:29:8a:29:6c:84). Lease duration: 1440 min
20:39:54, 02 Mar.	(108209.070000) Device connected to ath10: Hostname: Unknown-f2-29-8a-29-6c-84 IP: 192.168.1.66 MAC: f2:29:8a:29:6c:84 via f2:29:8a:29:6c:84 Lease time: 1440 min. Link rate: 866.6 Mbps

Re: SLow adsl

jab1 — Sat, 02 Mar 2024 21:09:18 GMT

Thanks for that, @Georg . Unfortunately, because of the number of blocked access attempts and your devices requesting leases, it doesn't really tell me much.

Any chance you could post your current router statistics again please? Don't forget to obscure your username,

Re: SLow adsl

HPsauce — Sat, 02 Mar 2024 21:19:45 GMT

I guess it all depends what exactly @willcutforth did, whether it took effect immediately and also if a router reboot is needed?

Re: SLow adsl

jab1 — Sat, 02 Mar 2024 21:21:12 GMT

Hopefully, a new stats report may help.

Re: SLow adsl

Townman — Sun, 03 Mar 2024 00:05:07 GMT

That’s the router’s activity log shown it doing what it should do. It would be helpful to see the stats page again … but remember to redact personal information.

Re: SLow adsl

Georg — Sun, 03 Mar 2024 08:39:25 GMT

1. Product name: Plusnet Hub
2. Serial number: +081441+NQ81820617
3. Firmware version: Software version 4.7.5.1.83.8.289.1.3 Last updated Unknown
4. Board version: Plusnet Hub One
5. DSL uptime: 1 days, 04:44:25
6. Data rate: 448 / 8096
7. Maximum data rate: 1296 / 11584
8. Noise margin: 26.0 / 20.2
9. Line attenuation: 10.0 / 14.1
10. Signal attenuation: 10.0 / 14.9
11. Data sent/received: 426.6 MB / 12.1 GB
12. Broadband username:
13. 2.4 GHz Wireless network/SSID: PLUSNET-5X2N
14. 2.4 GHz Wireless connections: Enabled (802.11 b/g/n (up to 144 Mb/s))
15. 2.4 GHz Wireless security: WPA2
16. 2.4 GHz Wireless channel: Automatic (Smart Wireless)
17. 5 GHz Wireless network/SSID: PLUSNET-5X2N
18. 5 GHz Wireless connections: Enabled (802.11 a/n/ac (up to 1300 Mb/s))
19. 5 GHz Wireless security: WPA2
20. 5 GHz Wireless channel: Automatic (Smart Wireless)
21. Firewall: Default
22. MAC Address: 08:d5:9d:93:f2:d8
23. VPI/VCI: 0 / 38
24. Modulation: G.992.1 Annex A
25. Latency type: Interleaved
26. Software variant: AA
27. Boot loader: 1.0.0
This is the latest of what is going on with the router.

Re: SLow adsl

jab1 — Sun, 03 Mar 2024 08:41:43 GMT

Try rebooting the router, and then rechecking that data.

Re: SLow adsl

Georg — Sun, 03 Mar 2024 08:58:05 GMT

Looking at the stats the max from exchange is 8mb on Adsl_G.dmt. I should be on Adsl2+ and not Adsl_G.dmt. So it looks like I will have to contact Plusnet to alter this. I was getting up to 22mb with old provider on Adsl2+ then changed to Plusnet and now down to 7.4mb on same line and routing ect.