Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-16 13:32:33
Model: Deco M9 Plus  
Hardware Version: V1
Firmware Version: 1.5.1 Build 20210126 Rel. 62679

Using WiFi via the three M9 Plus' I have meshed up (two connected via ethernet) has frankly become a nightmare - I'd appreciate any support (although given the limited options in the control apps I'm not sure there's much I can do other than hope for a firmware update?).

 

With my iPhone, I can have great WiFi in my study, but when I move to the Living Room, the connection drops. I can see a full signal, but there's no IP address getting issued. Seems like there's issues with roaming within a mesh.

 

The devices are in Access Mode (no routing) behind a KPN Experia 10 modem. Everything hard wired is working okay.

 

If I had to guess, it seems to be an issue assigning IP addresses?

 

Anyway, current situation is not sustainable - everyone in the house is getting annoyed at me so I'm inclined to go with an alternative solution (i.e. another vender) and ditch the M9s if this can't get fixed. I also would like to see WPA3 implemented in a firmware update - and I see that there's not been any firmware update for over a year but clearly there ware issues reading through these community posts?

 

Here's a sample from the errors...

 

```

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:56:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:56:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:56:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:56:22 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:56:24 2022 daemon.err client_mgmt: wireless client associate or disassociate.

Sun Oct 16 14:56:24 2022 daemon.err client_mgmt: client_mac:00-40-8C-A8-35-27, client_ifname:ath0, client_action:disassociate

Sun Oct 16 14:56:24 2022 daemon.err client_mgmt: client(00-40-8C-A8-35-27) disassocaite by if(ath0).

Sun Oct 16 14:56:32 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:56:32 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:56:32 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:56:32 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:56:32 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:56:42 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:56:42 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:56:42 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:56:42 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:56:42 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:56:52 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:56:52 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:56:52 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:56:52 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:56:52 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:02 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:57:02 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:57:02 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:57:02 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:57:02 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:04 2022 daemon.err client_mgmt: wireless client associate or disassociate.

Sun Oct 16 14:57:04 2022 daemon.err client_mgmt: client_mac:00-40-8C-A8-35-27, client_ifname:ath0, client_action:associate

Sun Oct 16 14:57:04 2022 daemon.err client_mgmt: client(00-40-8C-A8-35-27) assocaite by if(ath0).

Sun Oct 16 14:57:12 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:57:12 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:57:12 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:57:12 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:57:12 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:22 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:57:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:57:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:57:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:57:22 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:32 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:57:32 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:57:32 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:57:32 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:57:32 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:42 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:57:42 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:57:42 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:57:42 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:57:42 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:52 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:57:52 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:57:52 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:57:52 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:57:52 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:57:56 2022 daemon.err client_mgmt: wireless client associate or disassociate.

Sun Oct 16 14:57:56 2022 daemon.err client_mgmt: client_mac:00-40-8C-A8-35-27, client_ifname:ath0, client_action:disassociate

Sun Oct 16 14:57:56 2022 daemon.err client_mgmt: client(00-40-8C-A8-35-27) disassocaite by if(ath0).

Sun Oct 16 14:58:02 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:58:02 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:58:02 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:58:02 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:58:02 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:58:04 2022 daemon.err tmpsvr[3348]: Error: tmp_trans_relay

Sun Oct 16 14:58:12 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:58:12 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:58:12 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:58:12 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:58:12 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

Sun Oct 16 14:58:22 2022 user.err csrMeshGw[7266]:

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sun Oct 16 14:58:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sun Oct 16 14:58:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sun Oct 16 14:58:22 2022 user.err csrMeshGw[7266]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sun Oct 16 14:58:22 2022 user.err csrMeshGw[7266]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

```

  0      
  0      
#1
Options
6 Reply
Re:Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-16 13:53:38
Switching off Fast Roaming and Beamforming seems to help a little, but there's still 10-20 seconds to switch to the closer access point when roaming around the mesh.
  0  
  0  
#2
Options
Re:Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-16 15:23:09

jonnymaserati wrote

Switching off Fast Roaming and Beamforming seems to help a little, but there's still 10-20 seconds to switch to the closer access point when roaming around the mesh.

  @jonnymaserati 

 

Your smartphone will not instantly migrate to different access point as you walk to it: scanning WiFi networks too often drains battery fast. When you turned off Fast Roaming, you forced smartphone to roam even less aggressively. 

Having said that, if your smartphone stays without WiFi signal for 10-20 seconds, that's not an expected WiFi mesh behavior. Can you clarify, if your iPhone actually loses WiFi signal for 10-20 seconds.

 

As a general recommendation, you should disable the private or random MAC address feature on your iPhone. I can't provide a link in this forum, so here is screenshot with list  of steps to do that, and replace reference to Linksys router by Deco mesh, as I lifted that document from Linksys Tech Support site:

  2  
  2  
#3
Options
Re:Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-17 08:31:02

  @Alexandre, thanks for the quick response!

 

To clarify, the signal is not lost, I have full signal shown and the iPhone is locked onto the network, it's just not getting an IP assigned as if there's an issue with the handshake via the Deco access point.

 

To summarize the recommendations, basically switch off all the enhanced performance and security features? That seems like a step backwards and forfeiting of value add that I've paid for but that I'm not able to realize?

  0  
  0  
#4
Options
Re:Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-17 13:34:48 - last edited 2022-10-17 15:16:12

  @jonnymaserati 

 

These are my recommendations:

 

1. Turn back on Fast Roaming and Beamforming. You need these enabled for proper functioning of WiFi mesh, including roaming between WiFi nodes. 

 

2. Turn off MAC address randomization in iPhone for Deco WiFi SSID. Follow steps I provided earlier. Note that you are only turning it off for Deco mesh at your house, there is no security compromise.

 

3. Turn off 2.4GHz for Deco Main Network. That will force iPhone roam faster between Deco nodes and might fix some other issues:

 

 

I have Deco M9 Plus units in my Deco mesh for about two years now, and I run my Deco mesh with that configuration. Every device coming to my house has MAC address randomization disabled. 

I have never seen an issue you described, and at my house people stream video while walking through the house, and use VoIP on smartphone while going from one room to another. If any of my family members had their device "stuck" for 10-20 seconds while walking through the house, I would have known about it.

I also tested it myself when I got Deco mesh, by streaming 4K video on tablet and walking by such route so that device will roam through multiple Deco nodes.

 

------------

What I like about Deco mesh is it does not have very many settings to try. You would not be reading through 50-page manual and spending days trying to guess which obscure parameter to tweak to fix some issue.

There are very few configuration settings you could try. If they work - fine, if problems do not go away - just pack that Deco hardware and send it back. Try different WiFi mesh brand.

  0  
  0  
#5
Options
Re:Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-18 08:56:33

  @Alexandre.

 

Thanks! Unfortunately I can't switch off the 2.4 GHz channels since my (TP-Link) smart plugs all operate on that.

 

I've switched the beamforming and fast roaming back on and switched off the Private Wi-Fi Address option on the iPhone(s). It's working for now (might also help having just changed out the KPN Experiabox model from v10 to v12 (despite the terrible GUI on the new one)).

 

It's still not switching well... it's odd because the phone will be registered on say the Deco in the Study with say 2 out of 3 bars on the iPhone (confirmed by looking on the Deco app under that Deco's client list - I can see the phone listed there), but on the iPhones Wi-Fi settings, it can see the closer Deco in the Living Room and shows 3 bars, but is not getting switched over network side - so I'm not sure what actually triggers the switch to the closer Deco unit?

  0  
  0  
#6
Options
Re:Loads of errors and sketchy WiFi connectivity on Deco M9 Plus v1
2022-10-18 14:10:30 - last edited 2022-10-18 14:11:41

  @jonnymaserati 

 

Smartphone will roam to closest WiFi mesh node when signal from node it is currently connected to gets weak. Software developer who wrote the code defines what is "weak" and what is not yet. It is smartphone and even OS version dependent.

Smartphone can be told by WiFi mesh to roam to closer node, using Fast Roaming protocol, but this is just a suggestion smartphone can ignore.

Smartphone will not actively scan WiFi networks, as this drains battery quickly.

 

The problem with 2.4GHz is it works well on long distances, but on slow speed. Smartphone may stick to remote node just because 2.4GHz signal strength from that node is still adequate.

WiFi 5GHz provides faster speed on shorter range. It means, smartphone running exclusively on 5GHz will get faster Internet speeds and will also roam faster to closest WiFi mesh node. It is Win-Win.

This is applicable not just to Deco, but to any WiFi mesh.

 

You said you run your Deco mesh in AP mode. This is same setup as at my house, and I faced same problem. I solved it by utilizing Guest Network for devices that can only connect on 2.4GHz. This is my Deco Wi-Fi Settings page:

 

 

  0  
  0  
#7
Options

Information

Helpful: 0

Views: 1031

Replies: 6

Related Articles