cancel
Showing results for 
Search instead for 
Did you mean: 
Moderator
Moderator
258 Views
Message 11 of 18

Re: Service worse after engineer visit

Hi @Micker,

Can you post back the router stats now that your connected to the test socket?

Thanks

PaddyB

0 Ratings
Reply
Micker
Contributor
247 Views
Message 12 of 18

Re: Service worse after engineer visit

Will do when I get home, the engineer installed this new master socket:

 

IMG_20180621_071520.jpg

0 Ratings
Reply
Micker
Contributor
228 Views
Message 13 of 18

Re: Service worse after engineer visit

8:38:54, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:38:54, 20 Jun. WAN Sensing Auto sensing Running
18:38:54, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:38:51, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
18:38:51, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
18:38:51, 20 Jun. WAN DHCPv6 events: BOUND
18:38:51, 20 Jun. WAN Sensing Auto sensing Running
18:38:51, 20 Jun. Success - secondary DNS servers
18:38:51, 20 Jun. Success - primary DNS servers
18:38:51, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
18:38:51, 20 Jun. WAN DHCPv6 events: INIT
18:38:30, 20 Jun. WAN Auto-sensing detected port DSL WAN
18:38:30, 20 Jun. DSL Link Up: Down Rate=44986kbps, Up Rate=17787kbps; SNR Margin Down=0.0dB, Up=0.0dB
18:35:23, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:35:22, 20 Jun. WAN Sensing Auto sensing Running
18:35:22, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:35:22, 20 Jun. WAN Sensing Auto sensing Running
18:35:16, 20 Jun. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
18:35:04, 20 Jun. DSL Link Down: duration was 1270 seconds
18:14:15, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:14:15, 20 Jun. WAN Sensing Auto sensing Running
18:14:15, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:14:13, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
18:14:13, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
18:14:13, 20 Jun. WAN DHCPv6 events: BOUND
18:14:13, 20 Jun. WAN Sensing Auto sensing Running
18:14:13, 20 Jun. Success - secondary DNS servers
18:14:13, 20 Jun. Success - primary DNS servers
18:14:13, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
18:14:13, 20 Jun. WAN DHCPv6 events: INIT
18:14:07, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:14:06, 20 Jun. WAN Sensing Auto sensing Running
18:14:06, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:14:05, 20 Jun. WAN Auto-sensing detected port DSL WAN
18:13:59, 20 Jun. WAN Sensing Auto sensing Running
18:13:59, 20 Jun. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
18:13:54, 20 Jun. DSL Link Up: Down Rate=46076kbps, Up Rate=17682kbps; SNR Margin Down=5.8dB, Up=6.2dB
18:11:33, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:11:33, 20 Jun. WAN Sensing Auto sensing Running
18:11:33, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
18:11:32, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
18:11:32, 20 Jun.
0 Ratings
Reply
Micker
Contributor
227 Views
Message 14 of 18

Re: Service worse after engineer visit

Product name:Smart Hub
Serial number:+088044+1801001519
Firmware version:v0.09.05.11160-BT
Firmware updated:Mon Apr 23 20:09:42 2018
Board version:01
DSL uptime:0 days,21 Hours29 Mins02 Secs
Data rate:17.787 Mbps / 44.986 Mbps
Maximum data rate:22.265 Mbps / 52.259 Mbps
Noise margin:6.4 / 6.1
Line attenuation:25.1 / 19.0
Signal attenuation:24.8 / 19.1
Data sent / received:2.4 GB / 26.3 GB
Broadband username:bthomehub@btbroadband.com
BT Wi-fi:No
2.4 GHz wireless network name:BTHub6-J537
2.4 GHz wireless channel:Automatic (Smart Wireless)
5 GHz wireless network name:BTHub6-J537-5
5 GHz wireless channel:Automatic (Smart Wireless)
Wireless security:WPA2
Wireless mode:Mode 1
Firewall:Default
MAC address:EC:F4:51:C9:6B:02
Software variant:-
Boot loader: 0.1.6-BT (Fri Sep 9 10:05:09 2016)
0 Ratings
Reply
Micker
Contributor
205 Views
Message 15 of 18

Re: Service worse after engineer visit

8:42:24, 21 Jun. admin login success from 192.168.1.151
18:42:13, 21 Jun. admin timeout from 192.168.1.151
18:42:01, 21 Jun. DHCP device Connected: 192.168.1.69, 88:87:17:4a:dd:f3, unknown
18:42:01, 21 Jun. DHCP lease issued 192.168.1.69 to 88:87:17:4a:dd:f3 , lease duration is 86400 seconds
18:42:00, 21 Jun. Receive a DHCP request
18:41:17, 21 Jun. 5G Client disassociate from 1c:87:2c:78:ad:4c (IP=192.168.1.101) RSSI=0, Rate=0Mbps
18:41:07, 21 Jun. 5G Client disassociate from 1c:87:2c:78:ad:4c (IP=192.168.1.101) RSSI=0, Rate=0Mbps
18:40:50, 21 Jun. Multicast stream started by client 192.168.1.194
18:40:50, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:40:50, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:40:24, 21 Jun. Multicast stream started by client 192.168.1.194
18:40:24, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:40:24, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:39:34, 21 Jun. NTP synchronization success
18:39:23, 21 Jun. Receive a DHCP request
18:39:22, 21 Jun. NTP synchronization start
18:38:45, 21 Jun. Multicast stream started by client 192.168.1.194
18:38:45, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:38:45, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:38:16, 21 Jun. Multicast stream started by client 192.168.1.194
18:38:16, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:38:16, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:36:44, 21 Jun. Multicast stream started by client 192.168.1.194
18:36:44, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:36:44, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:36:13, 21 Jun. DHCP device Connected: 192.168.1.170, a8:a7:95:10:58:29, unknown
18:36:13, 21 Jun. 5G Client associate from a8:a7:95:10:58:29 (IP=192.168.1.170) RSSI=-62, Rate=6Mbps, host
18:36:12, 21 Jun. Multicast stream started by client 192.168.1.194
18:36:12, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:36:12, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:36:12, 21 Jun. Receive a DHCP request
18:36:10, 21 Jun. Receive a DHCP request
18:35:36, 21 Jun. Receive a DHCP request
18:34:32, 21 Jun. Multicast stream started by client 192.168.1.194
18:34:32, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:34:32, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:34:05, 21 Jun. Multicast stream started by client 192.168.1.194
18:34:05, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:34:05, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:32:52, 21 Jun. 5G Client disassociate from a8:a7:95:10:58:29 (IP=192.168.1.170) RSSI=0, Rate=0Mbps
18:32:40, 21 Jun. DHCP device Disconnected: 192.168.1.170, a8:a7:95:10:58:29, unknown
18:32:26, 21 Jun. Multicast stream started by client 192.168.1.194
18:32:26, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:32:26, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:32:05, 21 Jun. Multicast stream started by client 192.168.1.194
18:32:05, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:32:05, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:30:28, 21 Jun. Multicast stream started by client 192.168.1.194
18:30:28, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:30:28, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:29:53, 21 Jun. Multicast stream started by client 192.168.1.194
18:29:53, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:29:53, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:28:20, 21 Jun. Multicast stream started by client 192.168.1.194
18:28:20, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:28:20, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:27:45, 21 Jun. Multicast stream started by client 192.168.1.194
18:27:45, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:27:45, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:26:16, 21 Jun. Multicast stream started by client 192.168.1.194
18:26:16, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:26:16, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:25:49, 21 Jun. Multicast stream started by client 192.168.1.194
18:25:49, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:25:49, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:24:11, 21 Jun. Multicast stream started by client 192.168.1.194
18:24:11, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:24:11, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:23:37, 21 Jun. Multicast stream started by client 192.168.1.194
18:23:37, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:23:37, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:22:01, 21 Jun. Multicast stream started by client 192.168.1.194
18:22:01, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:22:01, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:21:55, 21 Jun. admin timeout from 192.168.1.191
18:21:38, 21 Jun. Multicast stream started by client 192.168.1.194
18:21:38, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:21:38, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:19:59, 21 Jun. Multicast stream started by client 192.168.1.194
18:19:59, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:19:59, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:19:35, 21 Jun. Multicast stream started by client 192.168.1.194
18:19:35, 21 Jun. Multicast event client join group:234.81.130.251 client:192.168.1.194
18:19:35, 21 Jun. Multicast stream request. client:192.168.1.194 group:234.81.130.251
18:18:44, 21 Jun. DHCP device Connected: 192.168.1.191, f0:0f:ec:be:04:0a, Honor_10-6bdb0d68e6ed885f
18:18:43, 21 Jun.
0 Ratings
Reply
Micker
Contributor
188 Views
Message 16 of 18

Re: Service worse after engineer visit

What do I do about this is it a faulty face plate, there is no additional wiring, so will I just leave it in the test socket until the engineer visit again on monday
0 Ratings
Reply
Moderator
Moderator
174 Views
Message 17 of 18

Re: Service worse after engineer visit

Hi @Micker,

If it's working best in the test socket it may be best to leave it there. If the connection is working ok in the test socket do you only need a replacement face plate?

Thanks

DanielS

0 Ratings
Reply
Micker
Contributor
167 Views
Message 18 of 18

Re: Service worse after engineer visit

Yep looks like the faceplate plate is faulty as there is no wiring from socket
0 Ratings
Reply