No internet and BT Home Hub seems to be restarting constantly

Edmund23 — Mon, 13 Mar 2023 14:45:52 GMT

The internet went slow and then almost completely off about a week ago.

A BT engineer and an Openreach engineer have had a look at the hub and the connection. The line was down for several days and BT could see this now it seems find but the hub constantly restarts, cycling between orange, flashing purple lights. Openreach said the line is working but they didn't say much about the hub. Frustratingly the broadband was working fine when the Openreach engineer was in the house but quickly stopped working as soon as he left.

Any help would be hugely appreciated

The log is as follows:

4:13:53, 13 Mar.

eth1:IGMP join received for group 224.0.1.60 on interface eth1

14:11:52, 13 Mar.

:HTTP UserAdmin login from successfully

14:11:45, 13 Mar.

eth1:IGMP join received for group 224.0.1.60 on interface eth1

14:09:48, 13 Mar.

eth1:IGMP join received for group 224.0.1.60 on interface eth1

14:07:42, 13 Mar.

wl0.1:WiFi security settings have been successfully saved

14:07:42, 13 Mar.

wl0:WiFi security settings have been successfully saved

14:07:42, 13 Mar.

eth1:IGMP join received for group 224.0.1.60 on interface eth1

14:07:42, 13 Mar.

wl1:WiFi security settings have been successfully saved

14:07:38, 13 Mar.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

14:07:37, 13 Mar.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated

14:07:37, 13 Mar.

ppp1:TR69 receiving InformResponse message

14:07:34, 13 Mar.

ppp1:TR69 event found : 4 VALUE CHANGE

14:07:33, 13 Mar.

ppp1:TR69 sending Inform message

14:07:33, 13 Mar.

:WAN DHCPv6 Client Prefix : 2a00:23c6:698d:3000::/56 (valid time = 315360000 / preferred time = 315360000)

14:07:30, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

14:07:30, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

14:07:30, 13 Mar.

ppp1:The NTP server used is: ntp.homehub.btopenworld.com

14:07:28, 13 Mar.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

14:07:28, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is active

14:07:28, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is inactive

14:07:28, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is active

14:07:28, 13 Mar.

ppp1:TR69 event found : 4 VALUE CHANGE

14:07:28, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is inactive

14:07:27, 13 Mar.

ppp1:TR69 sending Inform message

14:07:27, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is active

14:07:26, 13 Mar.

eth1:IGMP join received for group 224.0.1.60 on interface eth1

14:07:26, 13 Mar.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

14:07:26, 13 Mar.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:07:26, 13 Mar.

BR_LAN: Allocated prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

BR_LAN: Allocated address = 2a00:23c6:698d:3001:5a90:43ff:fee3:423d (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

BR_LAN: Allocated prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/56 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated address = 2a00:23c6:698d:3000:5a90:43ff:fee3:423b (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is inactive

14:07:26, 13 Mar.

ppp1:TR69 creating new session with ACS

14:07:26, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is active

14:07:26, 13 Mar.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:07:26, 13 Mar.

BR_LAN: Allocated prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

BR_LAN: Allocated address = 2a00:23c6:698d:3001:5a90:43ff:fee3:423d (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

BR_LAN: Allocated prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/56 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated address = 2a00:23c6:698d:3000:5a90:43ff:fee3:423b (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:26, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is inactive

14:07:25, 13 Mar.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:07:25, 13 Mar.

BR_LAN: Allocated prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:07:25, 13 Mar.

BR_LAN: Revoked prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

BR_LAN: Allocated address = 2a00:23c6:698d:3001:5a90:43ff:fee3:423d (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

BR_LAN: Allocated prefix = 2a00:23c6:698d:3001::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/56 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

ppp1: Allocated address = 2a00:23c6:698d:3000:5a90:43ff:fee3:423b (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/56 (valid time = 2026291200 / preferred time = 2026291200)

14:07:25, 13 Mar.

ppp1: Allocated prefix = 2a00:23c6:698d:3000::/56 (valid time = 2026291200 / preferred time = 2026291200)

14:07:22, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

14:07:22, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

14:07:22, 13 Mar.

ppp1:WAN DHCPv6 Mode : Statefull

14:07:22, 13 Mar.

ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0

14:07:21, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

14:07:21, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

14:07:21, 13 Mar.

ppp1:WAN DHCPv6 Mode : Statefull

14:07:20, 13 Mar.

:WAN: SENSING AUTO VDSL

14:07:20, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

14:07:20, 13 Mar.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.15.67]

14:07:20, 13 Mar.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.15.67]

14:07:20, 13 Mar.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

14:07:20, 13 Mar.

ppp1:PPP: PPP INFO

14:07:20, 13 Mar.

ppp:PPP: IPCP_NAK

14:07:20, 13 Mar.

ppp:PPP: CHAP_SUCCESS

14:07:20, 13 Mar.

ppp:PPP: CHAP_RESPONSE

14:07:20, 13 Mar.

ppp:PPP: LCP_GOOD_ACK

14:07:20, 13 Mar.

ppp:PPP: LCP_REQUEST

14:07:19, 13 Mar.

:PPPoE error: timeout

14:07:17, 13 Mar.

:Timeout during PPP initialization LCP/IPCP

14:06:53, 13 Mar.

:TR69 connectivity to (pbthdm.bt.mo) has failed

14:06:53, 13 Mar.

:TR69 unable to send Inform message

14:06:53, 13 Mar.

:TR69 event found : 4 VALUE CHANGE

14:06:52, 13 Mar.

ppp:PPP: LCP_REQUEST

14:06:52, 13 Mar.

:TR69 sending Inform message

14:06:52, 13 Mar.

eth1:IGMP join received for group 224.0.1.60 on interface eth1

14:06:51, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is active

14:06:51, 13 Mar.

:The DYN ROUTE [81.139.57.100/32 gw 172.16.15.67] is deleted

14:06:51, 13 Mar.

:The DYN ROUTE [81.139.56.100/32 gw 172.16.15.67] is deleted

14:06:51, 13 Mar.

BR_LAN:The LAN DHCPv6 Server is inactive

14:06:50, 13 Mar.

ppp1:TR69 creating new session with ACS

14:06:50, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

14:06:50, 13 Mar.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

14:06:46, 13 Mar.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

14:06:45, 13 Mar.

ppp1:WAN DHCPv6 Mode : Statefull

14:06:45, 13 Mar.

:WAN: SENSING AUTO VDSL

14:06:45, 13 Mar.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.15.67]

14:06:45, 13 Mar.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.15.67]

14:06:45, 13 Mar.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:06:44, 13 Mar.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:06:44, 13 Mar.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

Re: No internet and BT Home Hub seems to be restarting constantly

DavidM — Mon, 13 Mar 2023 16:31:27 GMT

Hi @Edmund23 and welcome to our community.

I'm sorry you're having problems with the connection. Is the hub connected to the master socket or extension? Is there any noise on your line?

Cheers

David

Re: No internet and BT Home Hub seems to be restarting constantly

Edmund23 — Wed, 15 Mar 2023 18:05:03 GMT

Hi @DavidM

The hub is plugged directly into an openreach mk4 socket.

i tried the quiet line test and i could not detect any interference on the line.

best edmund

This topic

No internet and BT Home Hub seems to be restarting constantly

Re: No internet and BT Home Hub seems to be restarting constantly

Re: No internet and BT Home Hub seems to be restarting constantly