cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Dared
Beginner
1,997 Views
Message 1 of 12

Spurious dropouts

Hi,

 

We have infinity 1 but since it was installed we have had problems where it just drops you out.  Two or three people can be on line but it will drop two people out but the other one stays connected or worst case everyone is disconnected.  Each disconnect is for 2-3 minutes then you can get back on,  But when this is happening 10 -15 times a day its a little frustrating to say the least..

 

It even shows you are connected to the hub but just no internet.

 

Very frustrating as not a problem I ever saw when we used to be with Sky!

 

 

 

0 Ratings
11 REPLIES 11
Dared
Beginner
1,992 Views
Message 2 of 12

Re: Spurious dropouts

Copy of my log

23:39:54, 28 Apr.
:HTTP UserAdmin login from 192.168.1.238 successfully
23:39:32, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:38:15, 28 Apr.
eth1:IGMP join received for group 234.81.130.66 on interface eth1
23:38:02, 28 Apr.
:HTTP UserBasic login from 192.168.1.238 successfully
23:37:39, 28 Apr.
wl1:Device <2C:F0:A2:7A:5A:2E> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:37:15, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:36:46, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::824e:81ff:fea4:581b is set active
23:36:45, 28 Apr.
eth1:IGMP join received for group 234.81.130.66 on interface eth1
23:36:44, 28 Apr.
eth1:IGMP join received for group 234.81.130.66 on interface eth1
23:36:44, 28 Apr.
eth1:IGMP leave received for group 234.81.130.58 on interface eth1
23:36:44, 28 Apr.
eth1:IGMP group 234.81.130.66 on interface eth1 started by 192.168.1.241
23:36:44, 28 Apr.
eth1:IGMP group 234.81.130.66 on interface eth1 by 192.168.1.241 requested
23:36:44, 28 Apr.
eth1:IGMP leave received for group 234.81.130.58 on interface eth1
23:36:44, 28 Apr.
eth1:IGMP group 234.81.130.58 on interface eth1 ended by 192.168.1.241
23:36:30, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:36:19, 28 Apr.
wl1:IGMP group 224.0.1.60 on interface wl1 ended by 192.168.1.101
23:36:11, 28 Apr.
eth1:IGMP join received for group 234.81.130.58 on interface eth1
23:35:42, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::824e:81ff:fea4:581b is set active
23:35:17, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set inactive
23:34:38, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:34:34, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set active
23:34:29, 28 Apr.
wl1:Device <DC:D9:16:4A:21:80> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:34:05, 28 Apr.
eth1:IGMP join received for group 234.81.130.58 on interface eth1
23:33:58, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:33:41, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set active
23:33:29, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::ded9:16ff:fe4a:2180 is set active
23:33:27, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:33:17, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set inactive
23:33:15, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set active
23:32:45, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:b814:d451:e5f9:de5 is set active
23:32:36, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set active
23:32:34, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:32:18, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::14c9:b4e4:7ee8:e6d5 is set active
23:32:17, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:b814:d451:e5f9:de5 is set active
23:32:07, 28 Apr.
wl1:Device <E8:61:7E:16:F7:33> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:32:06, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:6dfc:3d94:d0cc:4988 is added
23:32:06, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:32:06, 28 Apr.
wl1:IGMP join received for group 224.0.1.60 on interface wl1
23:32:00, 28 Apr.
eth1:IGMP join received for group 234.81.130.58 on interface eth1
23:32:00, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:b814:d451:e5f9:de5 is set active
23:31:52, 28 Apr.
:This Rule has been applied successfully: [id:730, InternalClient: 192.168.1.76, External Ports:(9308,0), Internal Ports: (9308,0), Protocol: UDP]
23:31:52, 28 Apr.
:Adding port mapping rule by System
23:31:52, 28 Apr.
:Updating port mapping rule (730) by System
23:31:52, 28 Apr.
:Deleting port mapping rule (729) by System
23:31:52, 28 Apr.
:Updating port mapping rule (729) by System
23:31:49, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:31:47, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::824e:81ff:fea4:581b is set inactive
23:31:35, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::14c9:b4e4:7ee8:e6d5 is set active
23:31:32, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set inactive
23:31:32, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::ea61:7eff:fe16:f733 is set inactive
23:31:31, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:b814:d451:e5f9:de5 is set active
23:31:31, 28 Apr.
:This Rule has been applied successfully: [id:729, InternalClient: 192.168.1.76, External Ports:(9308,0), Internal Ports: (9308,0), Protocol: UDP]
23:31:31, 28 Apr.
:Adding port mapping rule by System
23:31:31, 28 Apr.
:Updating port mapping rule (729) by System
23:31:31, 28 Apr.
BR_LAN:The DHCP options that are offered by the device (id:5): DiscoverOptions: 53,50,61,60 | DiscoverOption55: | RequestOptions: 53,50,54,55,61,60 | RequestOption55: 1,3,15,6 | HostName: | VendorId: PS4
23:31:31, 28 Apr.
:DHCP Confirmation of Request
23:31:31, 28 Apr.
:Deleting port mapping rule (728) by System
23:31:31, 28 Apr.
:Updating port mapping rule (728) by System
23:31:26, 28 Apr.
wl1:A WiFi device <E8:61:7E:16:F7:33> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:31:17, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:31:10, 28 Apr.
wl1:Device <E8:61:7E:16:F7:33> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:31:00, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::824e:81ff:fea4:581b is set active
23:30:56, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set active
23:30:56, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:30:34, 28 Apr.
:This Rule has been applied successfully: [id:728, InternalClient: 192.168.1.76, External Ports:(9308,0), Internal Ports: (9308,0), Protocol: UDP]
23:30:34, 28 Apr.
:Adding port mapping rule by System
23:30:34, 28 Apr.
:Updating port mapping rule (728) by System
23:30:33, 28 Apr.
BR_LAN:The DHCP options that are offered by the device (id:5): DiscoverOptions: 53,50,61,60 | DiscoverOption55: | RequestOptions: 53,50,54,55,61,60 | RequestOption55: 1,3,15,6 | HostName: | VendorId: PS4
23:30:33, 28 Apr.
:Deleting port mapping rule (726) by System
23:30:33, 28 Apr.
:Updating port mapping rule (726) by System
23:30:33, 28 Apr.
:DHCP Confirmation of Request
23:30:33, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::ea61:7eff:fe16:f733 is set active
23:30:28, 28 Apr.
wl1:A WiFi device <E8:61:7E:16:F7:33> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:30:28, 28 Apr.
wl1:Device <E8:61:7E:16:F7:33> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:30:28, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set active
23:30:27, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::824e:81ff:fea4:581b is set active
23:30:26, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:30:25, 28 Apr.
wl1:Device <E8:61:7E:16:F7:33> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
23:30:09, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:30:04, 28 Apr.
wl1:IGMP join received for group 224.0.1.60 on interface wl1
23:30:01, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host fe80::ea61:7eff:fe16:f733 is set inactive
23:29:55, 28 Apr.
eth1:IGMP join received for group 234.81.130.58 on interface eth1
23:29:49, 28 Apr.
:This Rule has been applied successfully: [id:727, InternalClient: 192.168.1.76, External Ports:(9307,0), Internal Ports: (9307,0), Protocol: UDP]
23:29:49, 28 Apr.
:Adding port mapping rule by System
23:29:49, 28 Apr.
:Updating port mapping rule (727) by System
23:29:49, 28 Apr.
:Deleting port mapping rule (722) by System
23:29:49, 28 Apr.
:Updating port mapping rule (722) by System
23:29:46, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:d967:c4cf:9eb:c3cf is set inactive
23:29:37, 28 Apr.
BR_LAN:LAN Neighbor Discovery : Host 2a00:23c0:302:aa00:69de:b5f9:ddb9:8d51 is set active
23:29:17, 28 Apr.
:This Rule has been applied successfully: [id:726, InternalClient: 192.168.1.76, External Ports:(9308,0), Internal Ports: (9308,0), Protocol: UDP]
23:29:17, 28 Apr.
:Adding port mapping rule by System
23:29:17, 28 Apr.
:Updating port mapping rule (726) by System
23:29:17, 28 Apr.
:Deleting port mapping rule (724) by System
23:29:17, 28 Apr.
:Updating port mapping rule (724) by System
23:29:17, 28 Apr.
:This Rule has been applied successfully: [id:725, InternalClient: 192.168.1.76, External Ports:(9305,0), Internal Ports: (9305,0), Protocol: UDP]
23:29:17, 28 Apr.
:Adding port mapping rule by System
23:29:17, 28 Apr.
:Updating port mapping rule (725) by System
23:29:17, 28 Apr.
:Deleting port mapping rule (718) by System
23:29:17, 28 Apr.
:Updating port mapping rule (718) by System
23:29:16, 28 Apr.
:This Rule has been applied successfully: [id:724, InternalClient: 192.168.1.76, External Ports:(9308,0), Internal Ports: (9308,0), Protocol: UDP]

And hub info

Product name:
BT Hub 6A
Serial number:
+084319+NQ64771575
Firmware version:
SG4B10002244
Firmware updated:
10-Mar-2017
Board version:
1.0
Gui version:
1.32.0
DSL uptime:
4 Days, 0 Hours 1 Minutes 27 Seconds
Data rate:
20.00 kbps / 67.64 kbps
Maximum data rate:
23923 / 66229
Noise margin:
15.3 / 6.3
Line attenuation:
10.5
Signal attenuation:
VPI / VCI:
0/38
Modulation:
G_993_2_ANNEX_B
Latency type:
Fast Path
Data sent / received:
3165 MB Uploaded / 3445 MB Downloaded
Broadband username:
bthomehub@btbroadband.com
BT Wi-fi:
Active
2.4 GHz wireless network name:
BTHub6-7SP3
2.4 GHz wireless channel:
Channel 6
5 GHz wireless network name:
BTHub6-7SP3-5
5 GHz wireless channel:
Channel 48
Wireless security:
WPA2 (Recommended)
Band steering:
Off
Wireless mode:
Mode 1
Firewall:
On
MAC address:
24:20:C7:6A:E7:5B
Software variant:
-
Boot loader:
7.33.1
0 Ratings
pippincp
Distinguished Sage
1,981 Views
Message 3 of 12

Re: Spurious dropouts

Not So Smart Hub?

Keith_Beddoe
Distinguished Sage
Distinguished Sage
1,969 Views
Message 4 of 12

Re: Spurious dropouts


@Dared wrote:

Hi,

 

We have infinity 1 but since it was installed we have had problems where it just drops you out.  Two or three people can be on line but it will drop two people out but the other one stays connected or worst case everyone is disconnected.  Each disconnect is for 2-3 minutes then you can get back on,  But when this is happening 10 -15 times a day its a little frustrating to say the least..

 

It even shows you are connected to the hub but just no internet.

 

Very frustrating as not a problem I ever saw when we used to be with Sky!

 

 

 


 

These just look like wireless disconnects, which are a common problem with the new smart hub which only has access to three of the 13 possible wireless channels.

 

Have you tried splitting the wireless bands, as that sometimes helps?

 

http://bt.custhelp.com/app/answers/detail/a_id/56419/~/how-do-i-split-my-bt-hubs-ssid-%28wireless-ne...

 

0 Ratings
Dared
Beginner
1,931 Views
Message 5 of 12

Wireless failing repeatedly

Hi,

 

Internet seems to be stable as hard wired devices ok but anything connected via wireless is dropping out 15-20 times a day.  Sometimes even shows you as still connected but nothing.  Just have to wait a few minutes then it reconnects.

 

Any ideas?

0 Ratings
Dared
Beginner
1,921 Views
Message 6 of 12

Re: Spurious dropouts

Hi,

 

Yes have tried splitting the devices but same problem.

 

Are you actually saying this is a known problem with these hubs? so they do not actually work as they should?  If so what are BT doing about it as obviously not fit for purpose?

0 Ratings
Keith_Beddoe
Distinguished Sage
Distinguished Sage
1,915 Views
Message 7 of 12

Re: Spurious dropouts

Have you tried changing the wireless mode from mode 1, to another one?

 

0 Ratings
Dared
Beginner
1,913 Views
Message 8 of 12

Re: Spurious dropouts

Hi,

 

yes tried 2 and 3 same problem. 

0 Ratings
Keith_Beddoe
Distinguished Sage
Distinguished Sage
1,881 Views
Message 9 of 12

Re: Spurious dropouts


@Dared wrote:

Hi,

 

yes tried 2 and 3 same problem. 


Then its just the smart hub. As it only has three wireless channels out of 13 possible channels, then once they become congested, you are going to get disconnections.

Its a serious deficiency in the HH6, I do not know what the designers were thinking at the time Smiley Sad

 

The general recommendation is to either get hold of a HH5, or better still, buy your own router, they start at about £35 upward.

 

Wireless range depends on ERP (Effective Radiated Power). All wireless routers are limited to 100mW power output, so its important to make effective use of this small power limitation.

 

Internal aerials like those on the home hub, are not as effective as external aerials, as power gets absorbed within the internal circuitry.

 

Good third party routers have two or more external aerials, which ensure that nearly all or the signal is transmitted to air, with minimal loss.

 

0 Ratings
Dared
Beginner
1,832 Views
Message 10 of 12

Re: Spurious dropouts

So what you are actually saying is the BT router is not fit for purpose?  Any chance I can have that in writing from BT?

 

If that is tha case then I may as well go back to SKY as never had this type of problem with them.  How do I contyact BT to cancel my subscription?

0 Ratings