Hub One - 5GHz WiFi issue

[#1]

Can't see it being the LED and there couldn't be more Plusnet/BT routers in the vicinity of my test environment if I tried!

I'm also on a floor where practically everybody is using bluetooth connected mice/headsets so there's a bucketload of competing radio traffic!

[#2]

Reset the router it helped a little.

Turned router off for 5 mins ... it cooled a little.  When turned it on then things were a little beter for a while.

Speed on 5ghz was 70+ Mbps at first then started slowing then intermittent connection.

2.4ghz was around 68 Mbps but when 5ghz became intermittant then 2.4ghz  became slower.

One tech at plusnet told me that so long as ethernt was working it didn't matter wether wifi mattered or not.

Rang back again and am having another router set out.  Tried a TT router but that was locked to TT.  If the new router that is sent out has the same problem  as the current one I don't want to pay for a 3rd party router.

[#3]

@bobpullen 

https://www.ispreview.co.uk/index.php/2019/11/glitchy-5ghz-wifi-hits-users-of-uk-isp-plusnets-hub-on...

A Plusnet Spokesperson told ISPreview.co.uk:

“We’re working to fix an intermittent Wi-Fi connectivity issues affecting a small number of customers following a firmware update earlier in the year. We’re working with our technology partner to find a solution as quickly as possible, and helping affected customers with temporary fixes in the meantime.

Customers who are experiencing this issue may wish to try temporarily disabling the 5GHz radio in the router settings, or contact us on 0800 432 0200 or @Plusnethelp and we’ll be happy to help.”

[#4]

@bobpullen 

Update

Changed the password on 5ghz connected but no internet

Set to using as one no avail

Split channels again and strange thing happened ... 2.4ghz required the 5ghz password!!!

Removed the usb TP-Link adaptor and connected to 2.4ghz (using the laptop's internal adaptor) and required password but this time the 2.4gh password was needed.

Reconnected the TP-Link adaptor (to the laptop) and the 2.4ghz required the password again ... this time the correct 2.4ghz password was required.

Strange why (after joining/spliting 2.4ghz and 5ghz) the 2.4 ghz required the 5ghz password???

[#5]

There is confusion going on here. My problem seems to be with the 2.4GHz feed yet Plusnet directed me to this thread and split my 2 streams.
Suddenly, over all the house everything connected by WiFi drops out. The problem is that devices say they are connected, but no internet so phones don't switch to a mobile signal. Also echo devices stop. Now before anyone shoots me down by saying this thread is for 5GHz problems, why is Plusnet treating my problem as being linked.
So, is it not about time to up the anti. Although free, it makes no difference. The router was supplied as part of the contract and I had to pay delivery. Is it fit for purpose? And sorry, I am not impressed and will not say thanks for all the work you are doing to try and fix this. Of course the answer is simple. Don't supply a router but make it the responsibility of the end user. But you did supply a router and it should work. Not next week, not next month but now.
Just as an aside, Plusnet is being integrated more with BT as shown by the CEO of Plusnet I believe stepping down.
Plusnet, at the moment you are not doing me proud

[#6]

---

@Trixiemay wrote:

Rang back again and am having another router set out.  Tried a TT router but that was locked to TT.  If the new router that is sent out has the same problem  as the current one I don't want to pay for a 3rd party router.

---

If you're affected by the problem described at the start of this thread then a replacement router (assuming the same model?) will not help. I'm aware of the ISP Review article you have linked to. What steps have you tried from the post at the beginning of this thread?

The password observation is very odd, I'll make sure this info is relayed to the team on the offchance it provides some clues.

@briston wrote:
There is confusion going on here. My problem seems to be with the 2.4GHz feed yet Plusnet directed me to this thread and split my 2 streams. Suddenly, over all the house everything connected by WiFi drops out. The problem is that devices say they are connected, but no internet so phones don't switch to a mobile signal. Also echo devices stop. Now before anyone shoots me down by saying this thread is for 5GHz problems, why is Plusnet treating my problem as being linked.

The 2.4GHz observatgion has been commented on here.

And sorry, I am not impressed and will not say thanks for all the work you are doing to try and fix this.

Well, it may not be appreciated but I would like to try a modified firmware build on your router. I'll be in touch separately with further detail.

Plusnet is being integrated more with BT as shown by the CEO of Plusnet I believe stepping down.

Not relevant. Let's keep this thread concentrated on the matter at hand

[#7]

Disabled the 5 GHZ radio all was well, until we connected a Samsung TV to the 2.4 GHZ, quite frequent now we get buffering and dropping out. I think this is mostly to do with too much traffic running off the 2.4 GHZ network.

As a work around I have now used my Secondary Router, an Apple Extreme Airport 4th Generation and just use the Hub One as my modem.

I now believe the problem has now extended to the 2.4 GHZ, mostly because everything is using the 2.4 GHZ.

I think though in the long term I will probably scrap my Hub One and use a 3rd Party.

I do believe this is a firmware/hardware issue, because other than speed issues occasionally the service did me well.

Can I please downgrade my firmware to the original state before this one was rolled out, I believe the problem will get worse before it gets fixed.

[#8]

Maybe connected some devices when you register the network, start the WPS procedure the flashing orange light, I have disbaled the WPS function and dont use the WPS feature on devices that support it

[#9]

Just changed the Samsung TV from 2.4 to 5 on my Apple Extreme Router rth Generation,WIFI is disabled on the Hub One, but got the orange flashing light, looking at the event log there were some blockages, doesn't happen on all devices, I suspect this is to do with the firewall built into the system

12:44:13, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.69]:41814-​>[216.58.211.174]:443 on ppp3)
12:44:13, 24 Jan.	BLOCKED 3 more packets (because of Packet invalid in connection)
12:44:13, 24 Jan.	IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254-​>224.0.0.22 on ptm0.101)
12:44:11, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:37988-​>[99.86.255.187]:80 on ppp3)
12:44:09, 24 Jan.	BLOCKED 11 more packets (because of Packet invalid in connection)
12:44:09, 24 Jan.	IN: BLOCK [12] Spoofing protection (IGMP 46.208.233.230-​>224.0.0.22 on ppp3)
12:44:08, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:35652-​>[34.210.161.232]:443 on ppp3)
12:44:08, 24 Jan.	BLOCKED 22 more packets (because of Packet invalid in connection)
12:44:06, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:60629-​>[18.153.6.79]:443 on ppp3)
12:44:06, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:44124-​>[52.28.197.171]:443 on ppp3)
12:44:01, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:38737-​>[54.149.8.31]:443 on ppp3)
12:44:01, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:46826-​>[18.153.6.92]:443 on ppp3)
12:44:00, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:49291-​>[35.167.240.207]:443 on ppp3)
12:43:59, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:40755-​>[52.41.212.53]:443 on ppp3)
12:43:57, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:35257-​>[44.230.132.84]:443 on ppp3)
12:43:55, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:51257-​>[54.93.140.41]:443 on ppp3)
12:43:48, 24 Jan.	(36079.940000) Lease for IP 192.168.1.83 renewed by host localhost (MAC 00:7c:2d:7f:9c:04). Lease duration: 1440 min
12:43:48, 24 Jan.	(36079.940000) Device connected: Hostname: localhost IP: 192.168.1.83 MAC: 00:7c:2d:7f:9c:04 Lease time: 1440 min. Link rate: 1000.0 Mbps
12:43:47, 24 Jan.	(36079.820000) Lease requested
12:43:47, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:43:44, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:54471-​>[216.58.204.14]:443 on ppp3)
12:43:41, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:52800-​>[54.87.240.216]:2350 on ppp3)
12:43:34, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.147]:64117-​>[17.57.146.84]:443 on ppp3)
12:43:24, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:49542-​>[34.210.161.232]:443 on ppp3)
12:43:19, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:43:19, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.147]:64117-​>[17.57.146.84]:443 on ppp3)
12:43:18, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:33144-​>[52.48.207.83]:443 on ppp3)
12:43:17, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:59786-​>[18.153.6.90]:443 on ppp3)
12:43:13, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:35724-​>[52.28.197.171]:443 on ppp3)
12:43:13, 24 Jan.	BLOCKED 2 more packets (because of Packet invalid in connection)
12:43:12, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:47204-​>[54.93.140.41]:443 on ppp3)
12:43:12, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:43:11, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:51983-​>[34.254.167.188]:443 on ppp3)
12:43:09, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:37968-​>[216.58.213.106]:443 on ppp3)
12:43:08, 24 Jan.	(36040.100000) Lease for IP 192.168.1.83 renewed by host Samsung (MAC 00:7c:2d:7f:9c:04). Lease duration: 1440 min
12:43:08, 24 Jan.	(36040.100000) Device connected: Hostname: Samsung IP: 192.168.1.83 MAC: 00:7c:2d:7f:9c:04 Lease time: 1440 min. Link rate: 1000.0 Mbps
12:43:08, 24 Jan.	(36040.000000) Lease requested
12:42:59, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.84]:56767-​>[104.28.5.107]:443 on ppp3)
12:42:56, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:52800-​>[54.87.240.216]:2350 on ppp3)
12:42:49, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.84]:56767-​>[104.28.5.107]:443 on ppp3)
12:42:49, 24 Jan.	BLOCKED 7 more packets (because of Packet invalid in connection)
12:42:47, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.84]:56767-​>[104.28.5.107]:443 on ppp3)
12:42:45, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:43838-​>[216.58.205.42]:443 on ppp3)
12:42:42, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:47902-​>[216.58.198.174]:443 on ppp3)
12:42:40, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:42:38, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:52064-​>[142.250.13.188]:5228 on ppp3)
12:42:32, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:49904-​>[216.58.210.33]:443 on ppp3)
12:42:32, 24 Jan.	BLOCKED 5 more packets (because of Packet invalid in connection)
12:42:31, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.90]:49904-​>[216.58.210.33]:443 on ppp3)
12:42:31, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:49904-​>[216.58.210.33]:443 on ppp3)
12:42:27, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.69]:49910-​>[216.58.204.14]:443 on ppp3)
12:42:22, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.69]:58990-​>[172.217.20.142]:443 on ppp3)
12:42:18, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.84]:56767-​>[104.28.5.107]:443 on ppp3)
12:42:11, 24 Jan.	(35983.260000) Device disconnected: Hostname: Jakes-​iPhone IP: 192.168.1.82 MAC: 02:0f:b5:3d:5c:b3
12:42:11, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:52800-​>[54.87.240.216]:2350 on ppp3)
12:42:11, 24 Jan.	IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254-​>224.0.0.22 on ptm0.101)
12:42:04, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:42:04, 24 Jan.	IN: BLOCK [12] Spoofing protection (IGMP 46.208.233.230-​>224.0.0.22 on ppp3)
12:42:02, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.84]:56804-​>[34.197.79.17]:443 on ppp3)
12:41:57, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:47902-​>[216.58.198.174]:443 on ppp3)
12:41:56, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.69]:58990-​>[172.217.20.142]:443 on ppp3)
12:41:56, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:37968-​>[216.58.213.106]:443 on ppp3)
12:41:53, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:52064-​>[142.250.13.188]:5228 on ppp3)
12:41:47, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:46181-​>[64.233.184.188]:5228 on ppp3)
12:41:44, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:41:43, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:41:41, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.69]:49910-​>[216.58.204.14]:443 on ppp3)
12:41:37, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:57258-​>[216.58.206.132]:443 on ppp3)
12:41:36, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.69]:58990-​>[172.217.20.142]:443 on ppp3)
12:41:35, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:41:33, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.84]:56767-​>[104.28.5.107]:443 on ppp3)
12:41:31, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.69]:58990-​>[172.217.20.142]:443 on ppp3)
12:41:31, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:41:31, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.69]:58990-​>[172.217.20.142]:443 on ppp3)
12:41:30, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:43838-​>[216.58.205.42]:443 on ppp3)
12:41:29, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:41:28, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:41:27, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:41:25, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:41:25, 24 Jan.	BLOCKED 4 more packets (because of Packet invalid in connection)
12:41:25, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:54628-​>[216.58.204.74]:443 on ppp3)
12:41:24, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:41:24, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)
12:41:24, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:41:23, 24 Jan.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.90]:35928-​>[216.58.213.106]:443 on ppp3)
12:41:17, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.103]:57020-​>[172.217.169.35]:443 on ppp3)
12:41:12, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:47902-​>[216.58.198.174]:443 on ppp3)
12:41:10, 24 Jan.	IN: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [64.233.184.188]:5228-​>[46.208.233.230]:46181 on ppp3)
12:41:08, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:52064-​>[142.250.13.188]:5228 on ppp3)
12:40:57, 24 Jan.	IN: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [216.58.210.46]:443-​>[46.208.233.230]:39728 on ppp3)
12:40:56, 24 Jan.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.83]:54214-​>[88.221.51.98]:443 on ppp3)
12:40:56, 24 Jan.	BLOCKED 1 more packets (because of Packet invalid in connection)

[#10]

---

@TeamGB  wrote:
i then sent an email to Andy Baker (CEO) and within days was advised that they know of an issue with the routing on the hub one that causes this issue on some connections. They then sent a different type of router.

https://community.plus.net/t5/My-Router/Plusnet-aware-of-issue-affecting-Hub-one-router-routing/td-p... 

[#11]

Now I am more confused and as I have been shot down in flames for even mentioning that the structure of Plusnet is changing I now see someone else has contacted the CEO of Plusnet. Yet I also read Published: 16:25
Thursday 07 November 2019
The boss of Plusnet is leaving and almost all head office staff are set to be transferred to BT in a major shake up at the Sheffield telecoms company.

Chief executive Andy Baker is leaving after six years and his job will be deleted.

All non-call centre workers face being TUPE’d across into the parent company from February 2020.

Can I ask those who have knowledge, as I have been accused of calling such people idiots.
There is nothing wrong with my incoming feed according to Plusnet.. All devices drop out what seems to be randomly, mobile phones report connected connected which they are not so they do not fall back to mobile internet.
Plusnet directed me to this thread and split my streams.
I have gone through all the channels to see if there is congestion. No difference that I can detect.
Has anyone purchased a 3rd party router and solved the problem? If so, is not the solution obvious. Or am I being an idiot?

[#12]

@briston
You told us that Plusnet splitting your SSIDs had solved the problem & suggested it would work for us all even though most of us on here had done that years ago.
You have now realised it didn't solve your problem either.
Please take up the offer from @bobpullen of a test firmware to see if this can shed any light on the problem to help us all.
It is frustrating but we need to help Plusnet to find a solution to this.
We need to work together on this.

[#13]

---

@briston wrote:
Now I am more confused and as I have been shot down in flames for even mentioning that the structure of Plusnet is changing I now see someone else has contacted the CEO of Plusnet. Yet I also read Published: 16:25
Thursday 07 November 2019
The boss of Plusnet is leaving and almost all head office staff are set to be transferred to BT in a major shake up at the Sheffield telecoms company.
Chief executive Andy Baker is leaving after six years and his job will be deleted.
All non-call centre workers face being TUPE’d across into the parent company from February 2020.

---

No one's disputing this, but it has nothing to do with the topic of discussion. If you want to discuss the direction of Plusnet as a company, or recent changes in employment/structure etc. then please create a separate thread.

There is nothing wrong with my incoming feed according to Plusnet.. All devices drop out what seems to be randomly, mobile phones report connected connected which they are not so they do not fall back to mobile internet.
Plusnet directed me to this thread and split my streams.
I have gone through all the channels to see if there is congestion. No difference that I can detect.

We're fairly accepting that your isues are likely to be with the router, and there are a number of suggested workarounds included in my post at the start of this thread. This said, please hang fire and I'll send you a message directly.

@briston wrote:
Has anyone purchased a 3rd party router and solved the problem?

There are a few examples of this in the thread linked from the original post. People seem to have a decent degree of success with the BT Smarthubs.

[#14]

I have responded to the private message, thanks.
I would note however the comment
People seem to have a decent degree of success with the BT Smarthubs.

So a fair degree is not success. However, by 3rd party I was thinking a completely different device unless the BT smarthubs are completely different. I was trying to divorce myself and comments from any BT related product considering the relationship between BT and Plusnet.
My continued reference to the CEO, or not, of Plusnet was because another post suggested an intervention by higher manager to solve his particular problem. I noted the name and by chance has seen an article regarding this person as stepping down. Hence the confusion.

Your comment
We're fairly accepting that your isues are likely to be with the router,
Although not actually saying the problem is with the router, then I stand by my comment. The solution is obvious. The router does not work. I contend that you advertise that you supply a router and this can be regarded as part of the essence of the contract. As such the supplied kit is not fit for purpose.

[#15]

@briston
I completely agree.
Even the BT HH6 is a Sagemcom router with shoddy firmware with obvious bugs.
The only winners here are Sagemcom & BT group don't seem to care because they pay them with our money.
That said, nothing is going to change unless between us we can find the firmware/software bugs and prove that they can be fixed or that we need a new router.
There is no magic wand unfortunately.
The best we can hope for is that BT take over an ISP with routers, firmware & internal systems that actually work.
It is interesting to note that even the John Lewis Broadband homepage seems to pass on all responsibility for absolutely everything to Plusnet before you even sign up for it!
How we ended up here is beyond me but the only way out of it now is try to help.
As I have stated before, we can all try going down other channels to push this, but the quickest solution by far will be for us collectively to help Plusnet find the firmware problem.
In my case the Hub One hardware worked for 2.5 years. I suspect the BT HH6 hardware is also very capable. Somewhere in the Sagemcom/BT group relationship is a quality control problem.
Plusnet could just send us all the John Lewis Zyxel router but I doubt that will happen. But then again, it is Plusnet's router, nothing to do with John Lewis.....