cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
1,219 Views
Message 11 of 16

Re: Hub constantly dropping

You haven't got FTTP if it is not going to be available until 2026. I suspect FTTC is what you have.

System uptime only says how long the power has been connected and not your actual connection. I suspect you have an intermittant connection due to a fault on the line which needs investigating by an Openreach engineer.

Posting the full stats you accessed earlier (advanced settings/technical log) would show that.

1,197 Views
Message 12 of 16

Re: Hub constantly dropping

No i didnt restart the hub, but it dropped out three times that morning. When the master socket was moved  they re routed the  original cable.

0 Ratings
Reply
1,182 Views
Message 13 of 16

Re: Hub constantly dropping

Quick update, i contacted BT today regarding the problem and was told the service provided could have been disrupted by the electricians who rewired the room and moved the master socket which they shouldnt have done. I have another engineer booked for Tuesday but this time they say they are sending me a network engineer instead of a home engineer, If i need to move the master socket i need to contact them for a socket move engineer. I was also tole i could get fibre halo 3 for an extra £5 a month that would give me better speeds, im reluctant as i still have this disconnection issue, agent said he cold guarantee fibre halo 3 with all new equipment set up for me would definately sort this disconnection problem, did sound like a sales pitch to me as i still have the same cable coming into the home through the same socket, not wanting to pay more for more of the same im holding fire, any ideas about this?

0 Ratings
Reply
1,178 Views
Message 14 of 16

Re: Hub constantly dropping

wait until openreach visit on tuesday and then think about any changes if openreach still cannot fix problem



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
1,170 Views
Message 15 of 16

Re: Hub constantly dropping

There are so many variables it's hard to know where to start. I'd suggest that you start keeping a log of every disconnection. Time, whether the hub lights changed & whether after it comes back, the System & Network up times are the same or not.

It's not clear what the relevance of the TV is unless you were watching a subscription or IP channel & that continued to play. If that's the case then also include what happens to the TV each time you get a drop.

If the Network & System up times always match, I'd suspect a power supply issue rather than a line fault. That could be anything from a poorly wired socket, faulty AC adapter or the Hub itself.

As @imjolly says, do nothing other than keeping the log of events & see what Tuesday brings.

1,111 Views
Message 16 of 16

Re: Hub constantly dropping

This has just happened for me again, this is the log information if anyone can suggest a fix ?

 

15:35:36, 16 Dec.

Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT

daisymike_0-1702741841587.png

 

15:35:36, 16 Dec.

Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT

daisymike_1-1702741841587.png

 

15:35:36, 16 Dec.

Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT

daisymike_2-1702741841587.png

 

15:35:35, 16 Dec.

Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT

daisymike_3-1702741841587.png

 

15:35:35, 16 Dec.

Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT

daisymike_4-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: HDM socket closed successfully.

daisymike_5-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: HTTP authentication success from pbthdm.x.x.x

daisymike_6-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: HDM socket opened successfully.

daisymike_7-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: session completed successfully

daisymike_8-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: HDM socket closed successfully.

daisymike_9-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: HTTP authentication success from pbthdm.x.x.x

daisymike_10-1702741841587.png

 

15:34:53, 16 Dec.

CWMP: HDM socket opened successfully.

daisymike_11-1702741841587.png

 

15:34:52, 16 Dec.

CWMP: Server URL: https://pbthdm.x.x.x; Connecting as user: ACS username

daisymike_12-1702741841587.png

 

15:34:52, 16 Dec.

CWMP: HTTP authentication Fail from pbthdm.x.x.x

daisymike_13-1702741841587.png

 

15:34:52, 16 Dec.

CWMP: HDM socket opened successfully.

daisymike_14-1702741841587.png

 

15:34:52, 16 Dec.

CWMP: Server URL: https://pbthdm.x.x.x; Connecting as user: ACS username

daisymike_15-1702741841587.png

 

15:34:51, 16 Dec.

CWMP: Session start now, server: https://pbthdm.x.x.x, Event code: 4 VALUE CHANGE

daisymike_16-1702741841587.png

 

15:34:51, 16 Dec.

CWMP: Initializing transaction for event code 4 VALUE CHANGE

daisymike_17-1702741841587.png

 

15:33:43, 16 Dec.

NTP synchronization success

daisymike_18-1702741841587.png

 

15:33:43, 16 Dec.

NTP Server: ntp.homehub.btopenworld.com

daisymike_19-1702741841587.png

 

15:33:35, 16 Dec.

LTE Modem owl_tx_lte_set_rate_shaper_script command sent

daisymike_20-1702741841587.png

 

15:33:34, 16 Dec.

LTE Modem owl_tx_lte_set_rate_shaper_script command sent

daisymike_21-1702741841587.png

 

15:33:32, 16 Dec.

WAN Sensing Auto sensing Complete, interface selected

 

WAN IPv6 Global unicast prefix / length: 2a00:23c4:c412:1f00::/56

daisymike_22-1702741841587.png

 

15:33:28, 16 Dec.

WAN IPv6 Global unicast address allocated: 2a00:23c4:c412:1f00::1/64

daisymike_23-1702741841587.png

 

15:33:28, 16 Dec.

WAN DHCPv6 events: BOUND

daisymike_24-1702741841587.png

 

15:33:28, 16 Dec.

NTP synchronization start

daisymike_25-1702741841587.png

 

15:33:27, 16 Dec.

WAN DHCPv6 events: INIT

daisymike_26-1702741841587.png

 

15:33:27, 16 Dec.

DSL Link Up: Down Rate=78178kbps, Up Rate=20000kbps; SNR Margin Down=6.3dB, Up=9.5dB

daisymike_27-1702741841587.png

 

15:33:27, 16 Dec.

WAN Sensing Auto sensing Complete, interface selected

daisymike_28-1702741841587.png

 

15:33:27, 16 Dec.

WAN Sensing Auto sensing Running

daisymike_29-1702741841587.png

 

15:33:27, 16 Dec.

Success - secondary DNS servers

daisymike_30-1702741841587.png

 

15:33:27, 16 Dec.

Success - primary DNS servers

daisymike_31-1702741841587.png

 

15:33:27, 16 Dec.

WAN connection WAN2_INTERNET_PTM connected

daisymike_32-1702741841587.png

 

15:33:26, 16 Dec.

PPP: IPCP up

daisymike_33-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPCP Receive Configuration ACK

daisymike_34-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPV6CP Receive Configuration ACK

daisymike_35-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPCP Send Configuration Request

daisymike_36-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPCP Receive Configuration NAK

daisymike_37-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPCP Send Configuration ACK

daisymike_38-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPCP Receive Configuration Request

daisymike_39-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPV6CP Send Configuration ACK

daisymike_40-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPV6CP Receive Configuration Request

daisymike_41-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPV6CP Send Configuration Request

daisymike_42-1702741841587.png

 

15:33:26, 16 Dec.

PPP IPCP Send Configuration Request

daisymike_43-1702741841587.png

 

15:33:26, 16 Dec.

PPP: CHAP authentication succeeded

daisymike_44-1702741841587.png

 

15:33:26, 16 Dec.

PPP CHAP Receive success : authentication successful

 

 

Selected:

All

Time and date

Message

15:33:25, 16 Dec.

PPP: LCP up

daisymike_45-1702741841587.png

 

15:33:25, 16 Dec.

PPP LCP Receive Configuration ACK

daisymike_46-1702741841587.png

 

15:33:25, 16 Dec.

PPP LCP Send Configuration ACK

daisymike_47-1702741841587.png

 

15:33:25, 16 Dec.

PPP LCP Receive Configuration Request

daisymike_48-1702741841587.png

 

15:33:25, 16 Dec.

PPP LCP Send Configuration Request

daisymike_49-1702741841587.png

 

15:33:25, 16 Dec.

PPP: Received PADS

daisymike_50-1702741841587.png

 

15:33:25, 16 Dec.

PPP: Sending PADR

daisymike_51-1702741841587.png

 

15:33:25, 16 Dec.

PPP: Received PADO

daisymike_52-1702741841587.png

 

15:33:25, 16 Dec.

PPP: Sending PADI

daisymike_53-1702741841587.png

 

15:33:20, 16 Dec.

PPP: Starting PPP daemon

daisymike_54-1702741841587.png

 

15:33:19, 16 Dec.

WAN Auto-sensing detected port DSL WAN

daisymike_55-1702741841587.png

 

15:33:01, 16 Dec.

admin timeout from 192.168.1.69

daisymike_56-1702741841587.png

 

15:32:56, 16 Dec.

SIP WAN DOWN

daisymike_57-1702741841587.png

 

15:32:47, 16 Dec.

SIP WAN DOWN

daisymike_58-1702741841587.png

 

15:32:47, 16 Dec.

WAN Sensing Auto sensing Complete, interface selected

daisymike_59-1702741841587.png

 

15:32:47, 16 Dec.

WAN Sensing Auto sensing Running

daisymike_60-1702741841587.png

 

15:32:45, 16 Dec.

WAN Sensing Auto sensing Complete, interface selected

daisymike_61-1702741841587.png

 

15:32:45, 16 Dec.

WAN Sensing Auto sensing Running

daisymike_62-1702741841587.png

 

15:32:45, 16 Dec.

WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]

daisymike_63-1702741841587.png

 

15:32:44, 16 Dec.

PPP: Stopped PPP daemon(0,1,5)

daisymike_64-1702741841587.png

 

15:32:44, 16 Dec.

PPP LCP Send Termination Request (User request)

daisymike_65-1702741841587.png

 

15:32:44, 16 Dec.

PPP: IPCP down

daisymike_66-1702741841587.png

 

15:32:44, 16 Dec.

PPP: LCP down

daisymike_67-1702741841587.png

 

15:32:44, 16 Dec.

DSL Link Down: duration was 526585 seconds

15:32:41, 16 Dec.

Receive a DHCP request

daisymike_68-1702741841587.png

 

15:32:40, 16 Dec.

WHW INFO A station (SmartHub2)IF[5G](0C:8E:29:7E:14:62):STA(0E:AD:DD:A7:60:75)(Legacy Device) join WHW infrastructure

daisymike_69-1702741841587.png

 

15:32:40, 16 Dec.

WHW INFO A station STA(0E:AD:DD:A7:60:75) leave WHW infrastructure

 

0 Ratings
Reply