cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
djalki
Newbie
1,572 Views
Message 1 of 12

Homehub 5 keeps dropping clients and then rebooting - Log enclosed

The hub keeps, every 5 minutes to once every few hours, dropping wireless clients.

All devices lose connectivity, laptops, phones, tablet etc, the blue light then flashes green, then the hub restarts and flashes red. Generally get connection back within about 5 minutes.

BT are as ever going through the script, and that is fair enough, but they want me to agree to an engineer visit which can incure a £129 cost if they go no fault found.

No other devices are on the line and we are plugged into the test socket (which has made no difference)

If anyone has a spare few minutes to check out the log below, I would really appreciate it.

 

16:10:35, 17 Feb.ath00: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client associated
16:09:48, 17 Feb.ath00: STA 30:75:12:bc:32:f2 IEEE 802.11: Client associated
16:09:09, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client associated
16:09:06, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client disassociated
16:09:06, 17 Feb.ath00: STA 00:91:f9:4b:a0:16 IEEE 802.11: WiFi registration failed
16:08:59, 17 Feb.ath00: STA 38:94:96:a7:17:75 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath00: STA 30:75:12:bc:32:f2 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath00: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath00: STA 30:75:12:bc:32:f2 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath10: STA 30:75:12:bc:32:f2 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath10: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath10: STA 38:94:96:a7:17:75 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath10: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath00: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath10: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath10: STA 30:75:12:bc:32:f2 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath10: STA c0:f8:da:7c:40:d8 IEEE 802.11: Client associated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client disassociated
16:08:47, 17 Feb.ath00: STA d4:ca:6d:2a:14:07 IEEE 802.11: Client associated
17:08:28, 17 Feb.ath10: STA 38:94:96:a7:17:75 IEEE 802.11: Client associated
17:08:28, 17 Feb.( 158.110000) NTP synchronization success!
16:10:39, 17 Feb.( 272.950000) Device disconnected: Hostname: MikroTik IP: 192.168.1.92 MAC: d4:ca:6d:2a:14:03
16:10:39, 17 Feb.( 272.950000) Device disconnected: Hostname: MSFT-​5-​0-​00-​26-​2d-​36-​36-​ab-​2 IP: 192.168.1.89 MAC: 00:26:2d:36:36:ab
16:10:39, 17 Feb.( 272.950000) Device disconnected: Hostname: android-​6c0273d2c2cbf2a0 IP: 192.168.1.73 MAC: 44:d4:e0:b7:ec:64
16:10:39, 17 Feb.( 272.950000) Device disconnected: Hostname: HomeUser-​PC IP: 192.168.1.71 MAC: 00:1f:3c:99:f8:ff
16:10:35, 17 Feb.( 268.830000) Lease for IP 192.168.1.70 renewed by host DELL-​PC (MAC c0:f8:da:7c:40:d8). Lease duration: 1440 min
16:10:35, 17 Feb.( 268.830000) Device connected: Hostname: DELL-​PC IP: 192.168.1.70 MAC: c0:f8:da:7c:40:d8 Lease time: 1440 min. Link rate: 108.7 Mbps
16:10:35, 17 Feb.( 268.720000) Lease requested
16:10:00, 17 Feb.( 233.700000) Lease for IP 192.168.1.69 renewed by host android-​9227342dbd8d35be (MAC 30:75:12:bc:32:f2). Lease duration: 1440 min
16:10:00, 17 Feb.( 233.700000) Device connected: Hostname: android-​9227342dbd8d35be IP: 192.168.1.69 MAC: 30:75:12:bc:32:f2 Lease time: 1440 min. Link rate: 52.8 Mbps
16:10:00, 17 Feb.( 233.590000) Lease requested
16:09:58, 17 Feb.( 231.920000) Device disconnected: Hostname: MikroTik IP: 192.168.1.92 MAC: d4:ca:6d:2a:14:03
16:09:58, 17 Feb.( 231.920000) Device disconnected: Hostname: MSFT-​5-​0-​00-​26-​2d-​36-​36-​ab-​2 IP: 192.168.1.89 MAC: 00:26:2d:36:36:ab
16:09:58, 17 Feb.( 231.920000) Device disconnected: Hostname: android-​6c0273d2c2cbf2a0 IP: 192.168.1.73 MAC: 44:d4:e0:b7:ec:64
16:09:58, 17 Feb.( 231.920000) Device disconnected: Hostname: HomeUser-​PC IP: 192.168.1.71 MAC: 00:1f:3c:99:f8:ff
16:09:58, 17 Feb.( 231.910000) Device disconnected: Hostname: DELL-​PC IP: 192.168.1.70 MAC: c0:f8:da:7c:40:d8
16:09:57, 17 Feb.( 230.180000) Lease requested
16:09:53, 17 Feb.( 226.160000) Lease requested
16:09:48, 17 Feb.( 221.680000) Device disconnected: Hostname: MikroTik IP: 192.168.1.92 MAC: d4:ca:6d:2a:14:03
16:09:48, 17 Feb.( 221.680000) Device disconnected: Hostname: MSFT-​5-​0-​00-​26-​2d-​36-​36-​ab-​2 IP: 192.168.1.89 MAC: 00:26:2d:36:36:ab
16:09:48, 17 Feb.( 221.680000) Device disconnected: Hostname: android-​6c0273d2c2cbf2a0 IP: 192.168.1.73 MAC: 44:d4:e0:b7:ec:64
16:09:48, 17 Feb.( 221.680000) Device disconnected: Hostname: HomeUser-​PC IP: 192.168.1.71 MAC: 00:1f:3c:99:f8:ff
16:09:48, 17 Feb.( 221.680000) Device disconnected: Hostname: DELL-​PC IP: 192.168.1.70 MAC: c0:f8:da:7c:40:d8
16:09:19, 17 Feb.( 192.310000) Lease for IP 192.168.1.92 renewed by host MikroTik (MAC d4:ca:6d:2a:14:03). Lease duration: 1440 min
16:09:19, 17 Feb.( 192.180000) Lease requested
0 Ratings
Reply
11 REPLIES 11
Distinguished Guru
1,563 Views
Message 2 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

Can you post your line stats from the HH5 please? These are in Troubleshooting/Helpdesk on the web interface at http://192.168.1.254

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
If you found this post helpful, please click on the star on the left
If not, I'll try again 🙂
0 Ratings
Reply
djalki
Newbie
1,558 Views
Message 3 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

Hi,

 

17:07:52, 17 Feb.( 122.510000) WAN operating mode is VDSL
17:07:52, 17 Feb.( 122.510000) Last WAN operating mode was VDSL
17:07:49, 17 Feb.( 119.380000) PPP IPCP Receive Configuration ACK
17:07:49, 17 Feb.( 119.270000) PPP IPCP Send Configuration Request
17:07:49, 17 Feb.( 119.270000) PPP IPCP Receive Configuration NAK
17:07:49, 17 Feb.( 119.260000) PPP IPCP Send Configuration ACK
17:07:49, 17 Feb.( 119.260000) PPP IPCP Receive Configuration Request
17:07:49, 17 Feb.( 119.240000) PPP IPCP Send Configuration Request
17:07:46, 17 Feb.( 116.580000) PPPoE is up -​ Down Rate=39993000Kbps, Up Rate=9995000Kbps; SNR Margin Down=18.4dB, Up=16.2dB
17:07:46, 17 Feb.( 116.470000) CHAP authentication successful
17:07:46, 17 Feb.( 116.200000) CHAP Receive Challenge
17:07:46, 17 Feb.( 116.190000) CHAP Receive Challenge
17:07:46, 17 Feb.( 116.140000) Starting CHAP authentication with peer
17:07:46, 17 Feb.( 116.140000) PPP LCP Receive Configuration ACK
17:07:42, 17 Feb.( 113.050000) PPP LCP Send Configuration Request
17:07:42, 17 Feb.( 113.050000) PPP LCP Receive Configuration Reject
17:07:41, 17 Feb.( 111.850000) PPP LCP Send Configuration ACK
17:07:41, 17 Feb.( 111.850000) PPP LCP Receive Configuration Request
17:07:41, 17 Feb.( 111.830000) PPP LCP Send Configuration Request
17:07:25, 17 Feb.( 95.790000) PTM over DSL is up
17:06:31, 17 Feb.( 41.660000) WAN Auto-​sensing running.
17:01:51, 16 Feb.( 112.640000) WAN operating mode is VDSL
17:01:51, 16 Feb.( 112.640000) Last WAN operating mode was VDSL
17:01:49, 16 Feb.( 110.800000) PPP IPCP Receive Configuration ACK
17:01:49, 16 Feb.( 110.790000) PPP IPCP Send Configuration Request
17:01:49, 16 Feb.( 110.790000) PPP IPCP Receive Configuration NAK
17:01:49, 16 Feb.( 110.780000) PPP IPCP Send Configuration ACK
17:01:49, 16 Feb.( 110.780000) PPP IPCP Receive Configuration Request
17:01:49, 16 Feb.( 110.770000) PPP IPCP Send Configuration Request
17:01:48, 16 Feb.( 109.390000) PPPoE is up -​ Down Rate=39993000Kbps, Up Rate=9995000Kbps; SNR Margin Down=18.4dB, Up=16.1dB
17:01:48, 16 Feb.( 109.370000) CHAP authentication successful
17:01:47, 16 Feb.( 109.070000) CHAP Receive Challenge
17:01:47, 16 Feb.( 109.070000) Starting CHAP authentication with peer
17:01:47, 16 Feb.( 109.070000) PPP LCP Receive Configuration ACK
17:01:47, 16 Feb.( 109.060000) PPP LCP Send Configuration Request
17:01:47, 16 Feb.( 109.060000) PPP LCP Receive Configuration Reject
17:01:47, 16 Feb.( 109.060000) PPP LCP Send Configuration ACK
17:01:47, 16 Feb.( 109.060000) PPP LCP Receive Configuration Request
17:01:47, 16 Feb.( 109.050000) PPP LCP Send Configuration Request
17:01:36, 16 Feb.( 97.160000) PTM over DSL is up
17:00:39, 16 Feb.( 40.870000) WAN Auto-​sensing running.
16:56:28, 15 Feb.( 110.440000) WAN operating mode is VDSL
16:56:28, 15 Feb.( 110.440000) Last WAN operating mode was VDSL
16:56:26, 15 Feb.( 108.460000) PPP IPCP Receive Configuration ACK
16:56:26, 15 Feb.( 108.460000) PPP IPCP Send Configuration Request
16:56:26, 15 Feb.( 108.450000) PPP IPCP Receive Configuration NAK
16:56:26, 15 Feb.( 108.450000) PPP IPCP Send Configuration ACK
16:56:26, 15 Feb.( 108.450000) PPP IPCP Receive Configuration Request
16:56:26, 15 Feb.( 108.440000) PPP IPCP Send Configuration Request
0 Ratings
Reply
scott_johnston
Contributor
1,545 Views
Message 4 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

click on the helpdesk button next to the event log. You should be on a screen showing stats like noise margin etc

0 Ratings
Reply
djalki
Newbie
1,541 Views
Message 5 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

Sorry, my bad, wrong log, here you go - 

 

Information for Helpdesk agents
When contacting the BT Broadband helpdesk, the agent might ask you for details about your BT Home Hub. This page contains all of the information they are likely to request.
 
1. Product name:BT Home Hub
2. Serial number:+068543+NQ43152959
3. Firmware version:Software version 4.7.5.1.83.8.204 (Type A) Last updated 21/01/15
4. Board version:BT Hub 5A
5. DSL uptime:0 days, 00:39:20
6. Data rate:9995 / 39993
7. Maximum data rate:25638 / 81825
8. Noise margin:16.2 / 18.4
9. Line attenuation:17.7 / 13.7
10. Signal attenuation:17.5 / 14.1
11. Data sent/received:13.1 MB / 65.4 MB
12. Broadband username:bthomehub@btbroadband.com
13. BT Wi-fi:Yes
14. 2.4 GHz Wireless network/SSID:BTHub5-PG2N
15. 2.4 GHz Wireless connections:Enabled (802.11 b/g/n (up to 144 Mb/s))
16. 2.4 GHz Wireless security:WPA2
17. 2.4 GHz Wireless channel:Automatic (Smart Wireless)
18. 5 GHz Wireless network/SSID:BTHub5-PG2N
19. 5 GHz Wireless connections:Enabled (802.11 a/n/ac (up to 1300 Mb/s))
20. 5 GHz Wireless security:WPA2
21. 5 GHz Wireless channel:Automatic (Smart Wireless)
22. Firewall:Default
23. MAC Address:c8:91:f9:4b:a0:14
24. Modulation:G.993.2 Annex B
25. Software variant:AA
26. Boot loader:1.0.0
0 Ratings
Reply
Distinguished Guru
1,508 Views
Message 6 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

Your stats look fine for Infinity 1 - you're synced at max speed, with plenty of spare noise margin.

 

 

You can try fixing wireless problems by turning off Smart Wireless and splitting the 2.4 GHz and 5 GHz bands. To do this:

1. Go into your advanced settings on the HH5 and select the wireless tab.

2. Then select the 5GHz tab and select NO to "Sync with 2.4 GHz:".

3. Then choose a new SSID by adding "5" to the existing one, so you can tell the difference between 2.4GHz and 5GHz bands.

4. While you're there change "Channel selection:" from "Smart wireless" to the current channel.

5. Then press the "Apply" button.

6. Then choose the 2.4GHz tab and change "Channel selection:" from "Smart wireless" to the current channel on 2.4GHz.

7. Then press the "Apply" button again.

Now on your devices you can select which SSID (which band, 2.4GHz or 5GHz) to connect to.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
If you found this post helpful, please click on the star on the left
If not, I'll try again 🙂
0 Ratings
Reply
djalki
Newbie
1,504 Views
Message 7 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

I have done this, but why would this cause all clients to drop and then for the router to restart?

0 Ratings
Reply
Distinguished Guru
1,501 Views
Message 8 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

All wireless clients will drop as the Homehub changes channel, which is what Smart Wireless does.

The Homehub is unstable either because it's broken, or you have some sort of line problem.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
If you found this post helpful, please click on the star on the left
If not, I'll try again 🙂
0 Ratings
Reply
quinnster77
Contributor
1,482 Views
Message 9 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

Ray_dorset. These are similar logs to my homehub 5 that has been terrible since the last firmware upgrade. There's a number of different threads all saying similar. I'm so frustrated with it ive ordered a Draytek. I work from home & can't carry on using the homehub especially as port forwarding is also rubbish on it too.
0 Ratings
Reply
Distinguished Guru
1,478 Views
Message 10 of 12

Re: Homehub 5 keeps dropping clients and then rebooting - Log enclosed

Hope the Draytek works for you. I find them overpriced and poor quality

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
If you found this post helpful, please click on the star on the left
If not, I'll try again 🙂
0 Ratings
Reply