"Wifi Registration Failed"

[#1]

Hi,

I'm getting multiple drops in connection via WiFi.  Event logs show multiple "Wifi Registration Failed".  It's just dropped my smart tv connection 3 times in 30 mins or so.  This kind of problem has existed for ages (months/years) - finally hit a wall of not being able to take it any longer!

I have a Plusnet Hub One | Software version 4.7.5.1.83.8.237.2.2 | Last updated 03/08/17, which is a few years old.  I've seen on this forum others have seen a fix to the problem with firmware update.  How would I go about this?

Thanks

[#2]

Hi @thetomevans

Sorry to hear that you're experiencing wifi connection issues - your connection looks good from this side, so likely a wifi issue as you've surmised.

I'm sure that my colleague @bobpullen will be able to assist with your firmware update - in the interim, take a look at the info here and get your wifi frequencies split to see if this helps.

[#3]

Thanks @RandallFlagg.  I've already got the frequencies split, but I double checked anyway.   Should I expect @bobpullen to be in touch?

Cheers

[#4]

Hi Tom,

Yes - he's on the forums regularly.

If he hasn't responded by this time tomorrow, I'll raise this directly with the products team via a different route.

Best wishes

Dave

[#5]

Moderators Note
This topic has been moved from Fibre Broadband to My Router.

[#6]

Hi Tom,

Just a quick confirmation that I've raised this directly with our products team for you - we'd expect the update to be pushed over the next 2/3 working days.

Best wishes

Dave

[#7]

@thetomevans, your router has dropped off our hardware management platform for some reason. If you factory reset the device by inserting something into the pinhole at the back until the status light flashes green then you should see the latest firmware pushed to the device within a day or two.

[#8]

I've got the latest firmware now I think - Plusnet Hub One | Software version 4.7.5.1.83.8.263 | Last updated 17/03/19

Haven't noticed my TV dropping connection to WiFi since, but the same problem has continued to exist with a Nest Cam.  It repeatedly loses connection.

Noticed a lot of Event logs, like this:

18:45:40, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:44:35, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:44:35, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:44:30, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:44:30, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:44:27, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:44:27, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:44:20, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:44:20, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:44:15, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:44:14, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:44:09, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:44:09, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:43:51, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:43:51, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:43:48, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:43:46, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:43:43, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated
18:43:43, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client disassociated
18:43:40, 20 Mar.	ath00: STA 64:16:66:41:7c:39 IEEE 802.11: Client associated

And from the logs, this one device did this for about 25/30 mins in total.  Any other ideas what might be going on please?

[#9]

Just a bit more event log info if useful.  My Nest Cam said the connection was lost at 18:44.  These are some other logs around the same time:

18:45:50, 20 Mar.	(240054.260000) CWMP: session completed successfully
18:45:50, 20 Mar.	(240054.090000) CWMP: HTTP authentication success from https://dbtpnhdm.bt.mo
18:45:43, 20 Mar.	(240047.190000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
18:45:43, 20 Mar.	(240047.180000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
18:44:46, 20 Mar.	(239989.750000) CWMP: session closed due to error: Could not resolve host
18:44:46, 20 Mar.	(239989.720000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
18:44:46, 20 Mar.	(239989.710000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
18:44:15, 20 Mar.	(239959.280000) CWMP: session closed due to error: Could not resolve host
18:44:15, 20 Mar.	(239959.250000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
18:44:15, 20 Mar.	(239959.240000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
18:44:15, 20 Mar.	(239958.790000) CWMP: Initializing transaction for event code 4 VALUE CHANGE

[#10]

Hi Tom,

Connection still looks good from this side.

Could you confirm that you've split out the wifi frequencies as per our previous correspondence and that you've assigned the nestcam to the 5ghz frequency as a dedicated connection?

Thanks

Dave

[#11]

Hi Dave, 

I can indeed confirm the WiFi frequencies are split and have been since I reset the router.  I've just made sure the NestCam is connected to the 5ghz, but I'm not sure how I can make it a dedicated connection.  For the moment I've just made sure nothing else is connected to the 5ghz...

But literally whilst I was typing this the TV dropped connection whilst we're streaming on BBC iPlayer.

Thanks, 

Tom

20:20:25, 22 Mar.	(418526.000000) Lease for IP  renewed by host SamsungTV40 (MAC ). Lease duration: 1440 min
20:20:25, 22 Mar.	(418526.000000) Device connected: Hostname: SamsungTV40 IP: MAC:  Lease time: 1440 min. Link rate: 105.6 Mbps
20:20:25, 22 Mar.	(418525.920000) Lease requested
20:20:23, 22 Mar.	ath00: STA  IEEE 802.11: Client associated
20:18:48, 22 Mar.	BLOCKED 3 more packets (because of ICMP replay)
20:18:47, 22 Mar.	OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 46.208  on ppp3)
20:17:56, 22 Mar.	(418376.600000) Device disconnected: Hostname: SamsungTV40 IP: 192. MAC:
20:17:56, 22 Mar.	(418376.600000) Device disconnected: Hostname: Toms-​iMac IP: 192.MAC:
20:17:54, 22 Mar.	ath00: STA IEEE 802.11: Client disassociated
20:17:54, 22 Mar.	ath00: STA IEEE 802.11: Client disassociated
20:17:54, 22 Mar.	ath00: STA  IEEE 802.11: WiFi registration failed
20:17:54, 22 Mar.	ath00: STA  IEEE 802.11: WiFi registration failed

[#12]

Contrary to the advice given thus far.....

You may wish to try the Nest* and the TV on 2.4GHz, then see how it goes. No promises but I have kinda proven something with the 5GHz and my phone also connecting to the 5GHz only .... the 5GHz wifi range is poor, worse than I first thought

I'm getting these events for my phone and this is the only device on my home network using the 5GHz.

(full mac address removed)

I actually caused these events to occur and (thus far for me anyway) it's also repeatable on the 2.4GHz too! The 2.4GHz is better range wise anyway, hence my suggestion of moving yours to 2.4GHz. Hopefully you'll see an improvement?

The cause of the events, for me anyway, is by moving my phone more than 6 metres from the routers location. Yes, only 6 metres :(.

Your TV for example is highlighting a 'range issue' as it's only connecting at 105.6Mbps. Don't confuse the connection speed to the router and the speed of you device to the www. My phone, during this reply, is connecting at 433Mbps to my router and being as it's not moved more than 3 metres from where the hub is, the failed/disassociated/associated events have stopped for this phone.

*if the nest works, it might be a good idea to move the device you're using to view it also to 2.4GHz as I've personally witnessed poor interaction when each device is on different spectrums. Your iMac is probably on 5GHz too?

The other issue, imho, appears to be related to the hub caching devices, which eventually kicks them off the router intermittently. A 'workaround' seems to be by turning the router off at the mains, but doing this too many times isn't good for your connection.

So, try 2.4GHz first, if it cure your issues then great, if it continues then at least 1) you can say you've tried both and 2) ignoring a firmware hiccup, if a power off and on cures this then it does kinda sound like a caching issue...

(ps, tweak your post above to hide your full 46.208.**.** IP address, more so if it's static ;))

[#13]

Thanks DS, The cam and the tv were both on 2.4ghz before, and it has always been a problem on that.  The range problem is interesting, the TV is probably 4/5 metres away, but with a wall between rooms.  The nest cam is in the same room as the TV... but a metre or so closer to the router.  I would have thought the wifi should be able to cope with that sort of distance, but perhaps not!

Tweaked my post to remove ip's and other stuff, never thought of that, cheers!

I'm basically a day or two away from just buying a better wireless router or a mesh system....

[#14]

On my previous router, which is actually within 2 feet of the TV, I initially set it on 5GHz and even then it was dropping!!

Since then, although I could use ethernet, I've used 2.4GHz with better success....

Then came the latest firmware...... oh dear ...... there's a few of us having issues. Here's just one (not mine) and it's looking like there's a bigger problem with this firmware.

Then came a replacement hub (yesterday) running 259 and so far (on 2.4GHz) all's well. I'm expecting mine to go wrong once the firmware updates.

I've also been giving another router a thought. We shouldn't have to, but needs must!!