cancel
Showing results for 
Search instead for 
Did you mean: 
tombrod
Newbie
242 Views
Message 1 of 2

BT Smart Hub keeps crashing

HI All

I have a relativey large network with a Cisco switch handling the DHCP to try to stop the BT BH crashing (4/5 times a day) but it doesnt seem to help

Ive posted some of the logs below to see if anyone has any clues as to what is making it reset I'd really appreciate it

 

Thanks very much

Tom

 

08:25:21 21 Aug.:HTTP UserBasic login from 192.168.1.236 successfully
08:23:55 21 Aug.wl1:IGMP join received for group 239.0.0.250 on interface wl1
08:23:55 21 Aug.wl1:IGMP group 239.0.0.250 on interface wl1 started by 192.168.1.236
08:23:55 21 Aug.wl1:IGMP group 239.0.0.250 on interface wl1 by 192.168.1.236 requested
08:22:32 21 Aug.:This Rule has been applied successfully: [id:5
08:22:32 21 Aug.:Adding port mapping rule by System
08:22:32 21 Aug.:Updating port mapping rule (5) by System
08:22:13 21 Aug.wl1:A WiFi device <AC:B5:7D:FD:67:0B> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
08:22:08 21 Aug.:This Rule has been applied successfully: [id:4
08:22:08 21 Aug.:Adding port mapping rule by System
08:22:08 21 Aug.:Updating port mapping rule (4) by System
08:22:07 21 Aug.:Deleting port mapping rule (3) by System
08:22:07 21 Aug.:Updating port mapping rule (3) by System
08:21:10 21 Aug.:This Rule has been applied successfully: [id:3
08:21:10 21 Aug.:Adding port mapping rule by System
08:21:10 21 Aug.:Updating port mapping rule (3) by System
08:21:09 21 Aug.:Deleting port mapping rule (2) by System
08:21:09 21 Aug.:Updating port mapping rule (2) by System
08:21:06 21 Aug.eth4:IGMP leave received for group 239.192.152.143 on interface eth4
08:21:06 21 Aug.eth4:IGMP group 239.192.152.143 on interface eth4 ended by 192.168.1.64
08:21:06 21 Aug.eth4:IGMP leave received for group 239.192.152.143 on interface eth4
08:21:01 21 Aug.eth4:IGMP join received for group 239.192.152.143 on interface eth4
08:21:01 21 Aug.eth4:IGMP join received for group 239.0.0.250 on interface eth4
08:21:01 21 Aug.eth4:IGMP join received for group 239.192.152.143 on interface eth4
08:21:01 21 Aug.eth4:IGMP join received for group 239.0.0.250 on interface eth4
08:20:48 21 Aug.:This Rule has been applied successfully: [id:2
08:20:48 21 Aug.:Adding port mapping rule by System
08:20:48 21 Aug.:Updating port mapping rule (2) by System
08:20:22 21 Aug.eth4:IGMP group 239.192.152.143 on interface eth4 started by 192.168.1.64
08:20:22 21 Aug.eth4:IGMP group 239.192.152.143 on interface eth4 by 192.168.1.64 requested
08:20:22 21 Aug.eth4:IGMP join received for group 239.192.152.143 on interface eth4
08:20:22 21 Aug.eth4:IGMP group 239.0.0.250 on interface eth4 started by 192.168.1.64
08:20:22 21 Aug.eth4:IGMP group 239.0.0.250 on interface eth4 by 192.168.1.64 requested
08:20:22 21 Aug.eth4:IGMP join received for group 239.0.0.250 on interface eth4
08:17:48 21 Aug.BR_LAN:New device (id:90) connecting on the LAN was detected
08:17:45 21 Aug.eth3:An Ethernet port is now connected (4/1000/FULL)
08:17:42 21 Aug.eth3:A device has been disconnected from an Ethernet port (4)
08:17:24 21 Aug.eth3:An Ethernet port is now connected (4/100/FULL)
08:09:07 21 Aug.wl1:A WiFi device <6C:8D:C1:B9:94:A0> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
08:05:21 21 Aug.wl1:A WiFi device <30:07:4D:F6:50:F8> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
08:05:20 21 Aug.wl0:Device <30:07:4D:F6:50:F8> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])
08:05:16 21 Aug.wl0:A WiFi device <30:07:4D:F6:50:F8> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])
05:33:11 21 Aug.ppp1:TR69 ConnectionRequest Failed
05:33:11 21 Aug.ppp1:TR69 ConnectionRequest: processing request from ACS
03:27:15 21 Aug.BR_LAN:The LAN DHCPv6 Server is active
03:27:15 21 Aug.BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0
03:27:15 21 Aug.BR_LAN:The LAN DHCPv6 Server is inactive
03:27:15 21 Aug.BR_LAN:The LAN DHCPv6 Server is active
03:27:15 21 Aug.BR_LAN:The LAN DHCPv6 Server is inactive
03:27:15 21 Aug.BR_LAN:The LAN DHCPv6 Server is active
03:27:15 21 Aug.BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0
03:27:14 21 Aug.ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36
03:27:14 21 Aug.BR_LAN: Revoked prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
03:27:14 21 Aug.BR_LAN: Allocated prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.BR_LAN: Allocated address = 2a00:23c0:6b03:a900:2a9e:fcff:fe9a:7653 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.BR_LAN: Allocated prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a901::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a900::/56 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated address = 2a00:23c0:6b03:a901:2a9e:fcff:fe9a:7651 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a901::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.BR_LAN:The LAN DHCPv6 Server is inactive
03:27:14 21 Aug.ppp1:WAN DHCPv6 Mode : Statefull
03:27:14 21 Aug.BR_LAN:The LAN DHCPv6 Server is active
03:27:14 21 Aug.BR_LAN: Revoked prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
03:27:14 21 Aug.BR_LAN: Allocated prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.BR_LAN: Allocated address = 2a00:23c0:6b03:a900:2a9e:fcff:fe9a:7653 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.BR_LAN: Allocated prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a901::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a900::/56 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated address = 2a00:23c0:6b03:a901:2a9e:fcff:fe9a:7651 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a901::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:14 21 Aug.ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36
03:27:14 21 Aug.BR_LAN:The LAN DHCPv6 Server is inactive
03:27:14 21 Aug.BR_LAN:The LAN DHCPv6 Server is active
03:27:13 21 Aug.BR_LAN: Revoked prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
03:27:13 21 Aug.BR_LAN: Allocated prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.BR_LAN: Revoked prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
03:27:13 21 Aug.BR_LAN: Revoked prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.BR_LAN: Allocated address = 2a00:23c0:6b03:a900:2a9e:fcff:fe9a:7653 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.BR_LAN: Allocated prefix = 2a00:23c0:6b03:a900::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a901::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a900::/56 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.ppp1: Allocated address = 2a00:23c0:6b03:a901:2a9e:fcff:fe9a:7651 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a901::/64 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.ppp1:WAN DHCPv6 Mode : Statefull
03:27:13 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a900::/56 (valid time = 2026291200 / preferred time = 2026291200)
03:27:13 21 Aug.ppp1: Allocated prefix = 2a00:23c0:6b03:a900::/56 (valid time = 2026291200 / preferred time = 2026291200)
03:02:35 21 Aug.ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed
03:02:33 21 Aug.ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated
03:02:33 21 Aug.ppp1:TR69 receiving InformResponse message
03:02:33 21 Aug.ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36
03:02:32 21 Aug.ppp1:The NTP server used is: ntp.homehub.btopenworld.com
02:58:56 21 Aug.BR_LAN:New device (id:101) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:99) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:98) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:97) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:96) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:93) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:92) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:91) connecting on the LAN was detected
02:58:56 21 Aug.BR_LAN:New device (id:90) connecting on the LAN was detected
0 Ratings
1 REPLY 1
Distinguished Sage
Distinguished Sage
234 Views
Message 2 of 2

Re: BT Smart Hub keeps crashing

You are expecting far too much from a basic ISP provided router. You have a lot of devices opening and closing ports using UPnP, which may be causing it to crash.

Try disabling UPnP on the home hub to see if it helps.

Otherwise use a third party router instead.

 

0 Ratings