Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
BT Smart Hub 2 router 'disrupting' home networks
29 views
Skip to first unread message
Java Jive
May 10, 2021, 8:06:37 AM5/10/21
to
BT Smart Hub 2 router 'disrupting' home networks
https://www.bbc.co.uk/news/technology-56949262
"BT Smart Hub 2 users are complaining of connection issues between their
wifi-enabled devices.
The telecom giant's router operates using two different wireless
frequencies: 2.4Ghz and 5Ghz.
Users are complaining that any devices not linked to the same frequency,
such as a phone and a speaker, are refusing to communicate with each other.
BT is offering firmware updates to those affected.
Numerous complaints have appeared on the company's community forums over
the last few months."
--
Fake news kills!
I may be contacted via the contact address given on my website:
www.macfh.co.uk
https://www.bbc.co.uk/news/technology-56949262
"BT Smart Hub 2 users are complaining of connection issues between their
wifi-enabled devices.
The telecom giant's router operates using two different wireless
frequencies: 2.4Ghz and 5Ghz.
Users are complaining that any devices not linked to the same frequency,
such as a phone and a speaker, are refusing to communicate with each other.
BT is offering firmware updates to those affected.
Numerous complaints have appeared on the company's community forums over
the last few months."
--
Fake news kills!
I may be contacted via the contact address given on my website:
www.macfh.co.uk
NY
May 10, 2021, 8:54:26 AM5/10/21
to
"Java Jive" <ja...@evij.com.invalid> wrote in message
news:s7b7k9$1j4k$1...@gioia.aioe.org...
others that are also on 2.4 GHz, but cannot communicate with ones connected
to 5 GHz? That sounds a pretty nasty bug in the router software.
news:s7b7k9$1j4k$1...@gioia.aioe.org...
> BT Smart Hub 2 router 'disrupting' home networks
> https://www.bbc.co.uk/news/technology-56949262
>
> "BT Smart Hub 2 users are complaining of connection issues between their
> wifi-enabled devices.
>
> The telecom giant's router operates using two different wireless
> frequencies: 2.4Ghz and 5Ghz.
>
> Users are complaining that any devices not linked to the same frequency,
> such as a phone and a speaker, are refusing to communicate with each
> other.
>
> BT is offering firmware updates to those affected.
>
> Numerous complaints have appeared on the company's community forums over
> the last few months."
Is this saying that a computer connected to 2.4 GHz can communicate with
> https://www.bbc.co.uk/news/technology-56949262
>
> "BT Smart Hub 2 users are complaining of connection issues between their
> wifi-enabled devices.
>
> The telecom giant's router operates using two different wireless
> frequencies: 2.4Ghz and 5Ghz.
>
> Users are complaining that any devices not linked to the same frequency,
> such as a phone and a speaker, are refusing to communicate with each
> other.
>
> BT is offering firmware updates to those affected.
>
> Numerous complaints have appeared on the company's community forums over
> the last few months."
others that are also on 2.4 GHz, but cannot communicate with ones connected
to 5 GHz? That sounds a pretty nasty bug in the router software.
Mark Carver
May 10, 2021, 8:58:13 AM5/10/21
to
On 10/05/2021 13:54, NY wrote:
>
> Is this saying that a computer connected to 2.4 GHz can communicate
> with others that are also on 2.4 GHz, but cannot communicate with ones
> connected to 5 GHz? That sounds a pretty nasty bug in the router
> software.
BT's latest ads say their routers produce an unbreakable WiFi and
>
> Is this saying that a computer connected to 2.4 GHz can communicate
> with others that are also on 2.4 GHz, but cannot communicate with ones
> connected to 5 GHz? That sounds a pretty nasty bug in the router
> software.
internet connection, so how odd this should happen eh ;-/
Another good reason to stick the BT HH back in its box, and go and buy a
proper router.
notya...@gmail.com
May 10, 2021, 11:46:31 AM5/10/21
to
Andy Burns
May 10, 2021, 11:55:42 AM5/10/21
to
Java Jive wrote:
> The telecom giant's router operates using two different wireless
> frequencies: 2.4Ghz and 5Ghz.
>
> Users are complaining that any devices not linked to the same frequency,
> such as a phone and a speaker, are refusing to communicate with each other.
I'd havbe though there was just a bridge between the 2.GHz radio, the
> The telecom giant's router operates using two different wireless
> frequencies: 2.4Ghz and 5Ghz.
>
> Users are complaining that any devices not linked to the same frequency,
> such as a phone and a speaker, are refusing to communicate with each other.
5GHz radio and the eth device on the internal switch, that's basically
how every wireless router I've seen operates.
I have a homehub5 and it has no problems like that.
Graham J
May 10, 2021, 12:09:06 PM5/10/21
to
Andy Burns wrote:
[snip]
> I'd have though there was just a bridge between the 2.GHz radio, the
and WiFi - can't remember which model, and I didn't have management
control so had to ask to have an opening made.
--
Graham J
[snip]
> I'd have though there was just a bridge between the 2.GHz radio, the
> 5GHz radio and the eth device on the internal switch, that's basically
> how every wireless router I've seen operates.
>
> I have a homehub5 and it has no problems like that.
I saw a Cisco router which implemented a firewall between the wired LAN
> how every wireless router I've seen operates.
>
> I have a homehub5 and it has no problems like that.
and WiFi - can't remember which model, and I didn't have management
control so had to ask to have an opening made.
--
Graham J
NY
May 10, 2021, 12:24:56 PM5/10/21
to
"Andy Burns" <use...@andyburns.uk> wrote in message
news:ift3bs...@mid.individual.net...
connected to additional inputs on the switch, alongside the Ethernet
sockets, so all would be handled equally: all traffic between 5
GHz-connected devices would remain on that port (and not be replicated
elsewhere), and likewise for 2.4-connected devices. But any traffic between
2.4 and 5, or between either of those and an Ethernet device would be
allowed through the switch.
Sounds as if someone's made a boo-boo in the firmware. Is it something that
used to work for that router and no longer works - a dodgy update - or has
it never worked (eg on newly-released hardware)?
news:ift3bs...@mid.individual.net...
> Java Jive wrote:
>
>> The telecom giant's router operates using two different wireless
>> frequencies: 2.4Ghz and 5Ghz.
>>
>> Users are complaining that any devices not linked to the same frequency,
>> such as a phone and a speaker, are refusing to communicate with each
>> other.
>
> I'd havbe though there was just a bridge between the 2.GHz radio, the 5GHz
> radio and the eth device on the internal switch, that's basically how
> every wireless router I've seen operates.
Yes I'd expect the 2.4 and 5 GHz wireless access points in the router to be
>
>> The telecom giant's router operates using two different wireless
>> frequencies: 2.4Ghz and 5Ghz.
>>
>> Users are complaining that any devices not linked to the same frequency,
>> such as a phone and a speaker, are refusing to communicate with each
>> other.
>
> I'd havbe though there was just a bridge between the 2.GHz radio, the 5GHz
> radio and the eth device on the internal switch, that's basically how
> every wireless router I've seen operates.
connected to additional inputs on the switch, alongside the Ethernet
sockets, so all would be handled equally: all traffic between 5
GHz-connected devices would remain on that port (and not be replicated
elsewhere), and likewise for 2.4-connected devices. But any traffic between
2.4 and 5, or between either of those and an Ethernet device would be
allowed through the switch.
Sounds as if someone's made a boo-boo in the firmware. Is it something that
used to work for that router and no longer works - a dodgy update - or has
it never worked (eg on newly-released hardware)?
David Wade
May 10, 2021, 2:25:05 PM5/10/21
to
have a Drayton Wiser heating controller 2.4Ghz and the app often had
issues when my phone running the control app is on 5ghz.
Creating a separate SSID for the controller seems to solve the problems.
Dave
NY
May 10, 2021, 3:02:47 PM5/10/21
to
"David Wade" <g4...@dave.invalid> wrote in message
news:s7btpv$mjd$1...@dont-email.me...
GHz everywhere, as well as some devices (my PC, the Philips Hue hub, the
Hive heating hub) connected by Ethernet to the various nodes. Phones,
tablets and laptops can communicate everywhere with equal easy no matter how
they are connected.
The only problem is that it is a real pain to get the nodes talking to each
other after a power cut - as I found out not half an hour ago when the power
went off for about 5 seconds. The problem is that all the nodes turn on
simultaneously (when the power comes back) but for some reason they need to
be turned on in sequence: first the primary node that is connected by
Ethernet to the router, then the two secondary nodes that can see the
primary, then the tertiary nodes that can see a secondary but not the
primary. I think it's because Linksys Velop uses 5 GHz for its node-to-node
comms, which governs how far apart the nodes can be (5 GHz doesn't travel as
far as 2.4 GHz). But this means that almost every node can see the 2.4 GHz
that is given out by all the other nodes, and some nodes give up the ghost
as they try in vain to find a vacant 2.4 GHz channel to use. And we need to
leave 2.4 turned on, firstly because we have a couple of security cameras
that can only use 2.4 and not 5, and secondly to give usable coverage in the
garden without having to use yet *another* node.
news:s7btpv$mjd$1...@dont-email.me...
> Splitting things between different wireless bands often causes issues. I
> have a Drayton Wiser heating controller 2.4Ghz and the app often had
> issues when my phone running the control app is on 5ghz.
>
> Creating a separate SSID for the controller seems to solve the problems.
I've not come across any problems with our mesh network which has 2.4 and 5
> have a Drayton Wiser heating controller 2.4Ghz and the app often had
> issues when my phone running the control app is on 5ghz.
>
> Creating a separate SSID for the controller seems to solve the problems.
GHz everywhere, as well as some devices (my PC, the Philips Hue hub, the
Hive heating hub) connected by Ethernet to the various nodes. Phones,
tablets and laptops can communicate everywhere with equal easy no matter how
they are connected.
The only problem is that it is a real pain to get the nodes talking to each
other after a power cut - as I found out not half an hour ago when the power
went off for about 5 seconds. The problem is that all the nodes turn on
simultaneously (when the power comes back) but for some reason they need to
be turned on in sequence: first the primary node that is connected by
Ethernet to the router, then the two secondary nodes that can see the
primary, then the tertiary nodes that can see a secondary but not the
primary. I think it's because Linksys Velop uses 5 GHz for its node-to-node
comms, which governs how far apart the nodes can be (5 GHz doesn't travel as
far as 2.4 GHz). But this means that almost every node can see the 2.4 GHz
that is given out by all the other nodes, and some nodes give up the ghost
as they try in vain to find a vacant 2.4 GHz channel to use. And we need to
leave 2.4 turned on, firstly because we have a couple of security cameras
that can only use 2.4 and not 5, and secondly to give usable coverage in the
garden without having to use yet *another* node.
Theo
May 10, 2021, 4:29:20 PM5/10/21
to
NY <m...@privacy.invalid> wrote:
> Yes I'd expect the 2.4 and 5 GHz wireless access points in the router to be
> connected to additional inputs on the switch, alongside the Ethernet
> sockets, so all would be handled equally: all traffic between 5
> GHz-connected devices would remain on that port (and not be replicated
> elsewhere), and likewise for 2.4-connected devices. But any traffic between
> 2.4 and 5, or between either of those and an Ethernet device would be
> allowed through the switch.
I have one of these, but it's been a while since I used it. I did see
> Yes I'd expect the 2.4 and 5 GHz wireless access points in the router to be
> connected to additional inputs on the switch, alongside the Ethernet
> sockets, so all would be handled equally: all traffic between 5
> GHz-connected devices would remain on that port (and not be replicated
> elsewhere), and likewise for 2.4-connected devices. But any traffic between
> 2.4 and 5, or between either of those and an Ethernet device would be
> allowed through the switch.
problems like has been reported, although I simply replaced with my own AP.
I *think* the nub of the problem is devices roaming between 2.4 and 5G. The
device would drop off the end of the 5G as you moved around, but the switch
would still send it's packets to the 5G port where they were lost. Because
the client kept the same MAC address the switch didn't learn the new route.
At least that's what I vaguely remember guessing, but I didn't diagnose the
fault as I was replacing it anyway.
> Sounds as if someone's made a boo-boo in the firmware. Is it something that
> used to work for that router and no longer works - a dodgy update - or has
> it never worked (eg on newly-released hardware)?
has come up now.
Theo
Andy Burns
May 10, 2021, 5:21:16 PM5/10/21
to
Theo wrote:
> I *think* the nub of the problem is devices roaming between 2.4 and 5G
I use separate SSIDs per frequency, so devicesstay on the frequency of
> I *think* the nub of the problem is devices roaming between 2.4 and 5G
the SSID that I put them on, the occasional thing takes offence ... e.g.
all my chromecast audio devices are on a 2.4GHz SSID, if ever i need to
factory reset one from my phone (which normally lives on a 5GHz SSID) I
have to move the phone to the 2.4GHz SSID for the duration of the
initial config, after that the phone can go back to its normal SSID, it
can still see the audio devices and all is well.
Theo
May 10, 2021, 6:47:23 PM5/10/21
to
Theo <theom...@chiark.greenend.org.uk> wrote:
> I *think* the nub of the problem is devices roaming between 2.4 and 5G. The
> device would drop off the end of the 5G as you moved around, but the switch
> would still send it's packets to the 5G port where they were lost. Because
> the client kept the same MAC address the switch didn't learn the new route.
>
> At least that's what I vaguely remember guessing, but I didn't diagnose the
> fault as I was replacing it anyway.
Oh, I remember a bit more now. I think this was when I *added* the AP. I
> I *think* the nub of the problem is devices roaming between 2.4 and 5G. The
> device would drop off the end of the 5G as you moved around, but the switch
> would still send it's packets to the 5G port where they were lost. Because
> the client kept the same MAC address the switch didn't learn the new route.
>
> At least that's what I vaguely remember guessing, but I didn't diagnose the
> fault as I was replacing it anyway.
set it on the same SSID and devices would drop off the HH and roam to the AP
just fine. But the HH couldn't cope with devices flipping between ethernet
and its own wifi and so would carry on sending packets to the wifi even
though the device was now on the AP that was connected via ethernet.
So not the same problem, but a related issue (mostly of my own making).
> This was about 2 years ago (with a HH from ~2017) so a bit surprised this
> has come up now.
Smart Hub 2.
Theo
NY
May 11, 2021, 5:09:08 AM5/11/21
to
news:iftme9...@mid.individual.net...
If you only configure auto-connect on a given device for one of the SSIDs, I
can see how this would work. But if you have configured both SSIDs in, it
will connect to whichever is the "better" signal - and the device may have
an algorithm which chooses a weaker 5 GHz over a stronger 2.4 GHz, up to
some limiting signal strength.
A router which can't handle devices moving from 5 GHz when closer to the
router to 2.4 GHz when further away hasn't been designed to cope with the
fact that phones, tablets and laptops are mobile devices which may be moved
around. The code needs to cater for the situation where a device no longer
responds on the original network and registers on the other network: the act
of registering a newly-seen MAC on a network should delete all references to
that MAC on other wireless networks or other Ethernet sockets, so the
packets get routed correctly.
can see how this would work. But if you have configured both SSIDs in, it
will connect to whichever is the "better" signal - and the device may have
an algorithm which chooses a weaker 5 GHz over a stronger 2.4 GHz, up to
some limiting signal strength.
A router which can't handle devices moving from 5 GHz when closer to the
router to 2.4 GHz when further away hasn't been designed to cope with the
fact that phones, tablets and laptops are mobile devices which may be moved
around. The code needs to cater for the situation where a device no longer
responds on the original network and registers on the other network: the act
of registering a newly-seen MAC on a network should delete all references to
that MAC on other wireless networks or other Ethernet sockets, so the
packets get routed correctly.
0 new messages