Random disconnects after Storm Arwen

[gissbro]

Hi, been getting random disconnects that seems to have started since after Storm Arwen hit, did a factory reset to see if that helps.

Any ideas on what it could be?

Regards

H

1. Product name:	BT Business Hub
2. Serial number:	+076399+NQ64317551
3. Firmware version:	Software version 4.7.5.1.83.8.256 (Type A) Last updated 26/03/18
4. Board version:	BT Hub 5A
5. Broadband connection:	Connected
6. Mobile connection:	Not connected
7. Connection uptime :	0 days, 00:07:52
8. Data rate:	448 / 4608
9. Maximum data rate:	1256 / 4800
10. Noise margin:	24.0 / 6.2
11. Line attenuation:	31.5 / 56.0
12. Signal attenuation:	31.5 / 55.5
13. Data sent/received:	3.8 MB / 110.3 MB
14. Broadband username:	home@btbroadband.com
15. Public Wi-fi:	No
16. Static IP:	Disabled
17. 2.4 GHz Wireless network/SSID:	BTHub5-PT67
18. 2.4 GHz Wireless connections:	Enabled (802.11 b/g/n (up to 144 Mb/s))
19. 2.4 GHz Wireless security:	WPA2
20. 2.4 GHz Wireless channel:	Automatic (Smart Wireless)
21. 5 GHz Wireless network/SSID:	BTHub5-PT67
22. 5 GHz Wireless connections:	Enabled (802.11 a/n/ac (up to 1300 Mb/s))
23. 5 GHz Wireless security:	WPA2
24. 5 GHz Wireless channel:	Automatic (Smart Wireless)
25. Firewall:	Default
26. MAC Address:	24:20:c7:48:e2:66
27. VPI/VCI:	0 / 38
28. Modulation:	G.992.1 Annex A
29. Latency type:	Interleaved
30. Software variant:	AA
31. Boot loader:	1.0.0

[gissbro]

17:16:07, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client disassociated
17:15:57, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client associated
17:15:45, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client disassociated
17:15:35, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client associated
17:15:24, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client disassociated
17:15:14, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client associated
17:13:08, 09 Dec.	IN: BLOCK [16] Remote administration (TCP [128.199.95.181]:49838-​>[109.145.174.92]:443 on ppp0)
17:11:56, 09 Dec.	( 587.640000) Device disconnected: Hostname: WebBox155008091 IP: 192.168.1.64 MAC: 00:15:ad:1e:1f:9b
17:11:45, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client disassociated
17:11:39, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client associated
17:11:36, 09 Dec.	IN: BLOCK [16] Remote administration (TCP [128.199.95.181]:49838-​>[109.145.174.92]:80 on ppp0)
17:11:04, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client disassociated
17:10:58, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client associated
17:10:08, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client disassociated
17:10:03, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client associated
17:09:48, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client disassociated
17:09:38, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client associated
17:09:13, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client disassociated
17:09:07, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client associated
17:08:57, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client disassociated
17:08:47, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client associated
17:08:45, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client disassociated
17:08:35, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client associated
17:08:24, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client disassociated
17:08:21, 09 Dec.	( 372.630000) Host Unknown-​bc-​60-​a7-​c5-​5f-​ff (MAC bc:60:a7:c5:5f:ff) using IP 192.168.1.144 detected on interface eth0, port 0
17:08:18, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client disassociated
17:08:14, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client associated
17:08:12, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client associated
17:08:01, 09 Dec.	IN: BLOCK [16] Remote administration (TCP [66.94.118.70]:45060-​>[109.145.174.92]:8443 on ppp0)
17:07:59, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client disassociated
17:07:49, 09 Dec.	ath00: STA bc:98:df:69:32:c6 IEEE 802.11: Client associated
17:07:47, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client disassociated
17:07:37, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client associated
17:07:23, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client disassociated
17:07:17, 09 Dec.	ath10: STA 04:e5:36:ba:24:74 IEEE 802.11: Client associated
17:06:57, 09 Dec.	IN: BLOCK [15] Default policy (TCP [202.137.216.17]:55328-​>[109.145.174.92]:23 on ppp0)
17:06:45, 09 Dec.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.217.8.52]:443-​>[109.145.174.92]:10036 on ppp0)
17:06:44, 09 Dec.	BLOCKED 2 more packets (because of Default policy)
17:06:43, 09 Dec.	( 274.680000) CWMP: session closed due to error: WGET TLS error
17:06:43, 09 Dec.	( 274.160000) CWMP: Server URL: https://pbthdmw.bt.mo; Connecting as user: Default username
17:06:43, 09 Dec.	( 274.150000) CWMP: Session start now. Event code(s): '0 BOOTSTRAP,4 VALUE CHANGE'
17:06:43, 09 Dec.	IN: BLOCK [15] Default policy (TCP [135.92.6.74]:443-​>[109.145.174.92]:57875 on ppp0)
17:06:43, 09 Dec.	IN: BLOCK [15] Default policy (TCP [34.195.242.133]:443-​>[109.145.174.92]:10055 on ppp0)
17:06:41, 09 Dec.	IN: BLOCK [15] Default policy (TCP [45.146.164.100]:57980-​>[109.145.174.92]:3875 on ppp0)
17:06:41, 09 Dec.	IN: BLOCK [15] Default policy (TCP [143.110.178.67]:49589-​>[109.145.174.92]:50050 on ppp0)
17:06:32, 09 Dec.	IN: BLOCK [15] Default policy (TCP [185.112.83.47]:33311-​>[109.145.174.92]:8545 on ppp0)

[gissbro]

( 238.320000) CWMP: Server URL: https://pbthdmw.bt.mo; Connecting as user: Default username
17:06:06, 09 Dec.	( 238.320000) CWMP: Session start now. Event code(s): '0 BOOTSTRAP,4 VALUE CHANGE'
17:06:05, 09 Dec.	( 237.670000) NTP synchronization start
17:06:04, 09 Dec.	( 236.620000) WAN operating mode is ADSL
17:06:03, 09 Dec.	( 235.330000) PPP IPCP Receive Configuration ACK
17:06:03, 09 Dec.	( 235.310000) PPP IPCP Send Configuration Request
17:06:03, 09 Dec.	( 235.290000) PPP IPCP Receive Configuration NAK
17:06:03, 09 Dec.	( 235.290000) PPP IPCP Send Configuration ACK
17:06:03, 09 Dec.	( 235.280000) PPP IPCP Receive Configuration Request
17:06:03, 09 Dec.	( 235.270000) PPP IPCP Send Configuration Request
17:06:01, 09 Dec.	( 233.670000) PPPoA is up -​ VPI: 0, VCI: 38 Down Rate=4608Kbps, Up Rate=448Kbps; SNR Margin Down=6.3dB, Up=24.0dB
17:06:01, 09 Dec.	( 233.660000) CHAP authentication successful
17:06:01, 09 Dec.	( 233.570000) CHAP Receive Challenge
17:06:01, 09 Dec.	( 233.570000) Starting CHAP authentication with peer
17:06:01, 09 Dec.	( 233.570000) PPP LCP Receive Configuration ACK
17:06:01, 09 Dec.	( 233.550000) PPP LCP Send Configuration Request
17:06:01, 09 Dec.	( 233.550000) PPP LCP Receive Configuration Reject
17:06:01, 09 Dec.	( 233.540000) PPP LCP Send Configuration ACK
17:06:01, 09 Dec.	( 233.540000) PPP LCP Receive Configuration Request
17:06:01, 09 Dec.	( 233.460000) PPP LCP Send Configuration Request
17:05:58, 09 Dec.	( 230.460000) PPP LCP Send Configuration Request
17:05:55, 09 Dec.	( 227.460000) PPP LCP Send Configuration Request
17:05:52, 09 Dec.	( 224.460000) PPP LCP Send Configuration Request
17:05:49, 09 Dec.	( 221.460000) PPP LCP Send Configuration Request
17:05:46, 09 Dec.	( 218.460000) PPP LCP Send Configuration Request
17:05:45, 09 Dec.	ath00: STA bc:98:df:f3:67:c8 IEEE 802.11: Client disassociated
17:05:42, 09 Dec.	( 214.320000) ETHoA is up -​ VPI: 0, VCI: 35 Down Rate=4608Kbps, Up Rate=448Kbps; SNR Margin Down=6.1dB, Up=24.0dB
17:05:42, 09 Dec.	( 214.320000) ATM over DSL is up

[Keith_Beddoe]

@gissbro 

Are you a BT Business customer?

[gissbro]

Yes, I just did a quiet line test and there was a quite a bit of noise so thats probably it

[Keith_Beddoe]

@gissbro 

This is the BT Residential Customer Forum, so if you want more specific help from a moderator (BT Employee), then you would need to post on the BT Business forum.

https://business.forums.bt.com/

A noisy line would cause broadband problems.

[gissbro]

Oops so sorry I misread your previous question, I am NOT a business user

[gissbro]

I also made sure to do another quiet line test on the test socket just to make sure and its definitely noisy

[PaddyB]

Hi @gissbro,

Thank you for posting. I'm sorry if you're having problems with the stability of your connection. If you can hear noise on the line when doing the quiet line test, it would indicate there is a fault, and more than likely an engineer will be needed to repair the line.

If you send me your details, I'll be able to take a look at the connection and run a few tests. 

I have sent you a private message with instructions on how to contact the team.  You can access your messages via the envelope icon at the top right of the screen, or click on this link, Private messages

Thanks,

Paddy

[imjolly]

Any reason to use a BT business hub on a residential line?

You are on adslmax and could upgrade to adsl2 which may not improve down connection speed. But would Inc rese up speed by about 100%