Deco M5 network sometimes in a bad state, maybe related to iOS private addresses?

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

Deco M5 network sometimes in a bad state, maybe related to iOS private addresses?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Deco M5 network sometimes in a bad state, maybe related to iOS private addresses?
Deco M5 network sometimes in a bad state, maybe related to iOS private addresses?
2020-11-25 22:31:48
Model: Deco M5  
Hardware Version: V1
Firmware Version: 1.5.1 Build 202021022

I have been a happy customer with a 3 node Deco M5 setup for a few years now. Howver, in the last few months, I have had issues where the deco system ends up in a bad state where some units can connect to the wireless network but no network traffic is forwarded. I typically notice this with an iPhone, and at first it almost always works to either enable or disable Private Address for the unit, which gives the unit a new MAC address. After a while though, this trick stops working. The laptop or iPad right next to the troubled phone typically works without problems, at least for a while. Then progressively, less and less units works. I have found that restarting the Main deco addresses this issue quite effectively, and everyhing works as it should for maybe a day or so, however, it seems like number of functioning hours that I get from a deco restart is decreasing after each incremental restart, and after a while it only helps for a handful of minutes. At this point I have found that disconnecting all the decos from power for a bit brings back the system to a good state and everything typically works for weeks after this.

 

I hope the above description is useful to people that might encounter similar problems. I also have a few theories about what might be going on. A few months ago iOS 14 was released. This household has many iOS units. One of the features of that OS is to use Private Address, which means that the phone (or iPad) will use a randomised MAC address that will change on each connect instead of using the same one on every connect. The fact that switching this feature on or off and when doing that getting a new MAC address resolves the issue initially when it pops up makes me think that the Deco firmware keeps track of seen mac addresses in memory in some way and that when the system (the 3 decos working in tandem) have used up the allocated memory for these mac addresses things start to break down. It also seems likely that the different units forwards their lists of seen mac addresses to each other in some way, such that the three units all need to be turned off for the list of MAC addresses to be completely emptied out.

 

That was a bit of speculation from me, I would be very happy to hear anyone else chime in with thought or ideas, and I hope that tp-link resolves this issue in an upcoming firmware version.

  1      
  1      
#1
Options
2 Reply
Re:Deco M5 network sometimes in a bad state, maybe related to iOS private addresses?
2020-11-26 06:28:56

@noa 

Good day,

Could you please help me confirm the following information:

  1. Did this issue start just after the IOS14 update, or get more frequently since the IOS14 update?
  2. Would only IOS device get effected?
  3. Did the issue start at the same time, or randomly on different devices?
  4. If you disabled the private address on IOS device completely, would the same issue still exist?
  5. When the device was connected to the Wi-Fi but no internet, could you please help me check the IP address and default gateway on it and please also have a look at the device status on the Deco APP;--some pictures would be highly appreciated;
  6. Have you tried to do the address reservation on the Deco to see if that helped?

Thank you very much!

 

  0  
  0  
#2
Options
Re:Deco M5 network sometimes in a bad state, maybe related to iOS private addresses?
2020-11-26 08:22:29 - last edited 2020-11-26 08:24:49
  1. It is difficult to know conclusively whether it was exactly coinciding with the iOS 14 release. I have also bought new hardware that was not on the network previously, and there has been at least two Deco firmware updates. 
  2. The problem does not only affect iOS, but all things that are WiFi connected such as smart speakers and laptops.
  3. If one client exhibits the problem it the unit next to it would sometimes also, and sometimes not. However, unless I restarted the Decos the situation would deteriorate to the point where nothing or almost nothing worked after a few hours.
  4. I have not done that consistently, no. We have 7 iOS devices in the family at the moment, with more coming in over the holidays. The next time it happens I will gather as much data as I can, but after that I might try disabling private addresses on all iOS devices and see if that changes anything.
  5. When a phone ended up in the state where it was connected to WiFi but not the internet it would at first keep the old lease for DHCP configuration, and everything would be configured as it should. After a while the lease would expire and since the phone could not receive DHCP responses it would self configure with a non-routable local IP. If I capture the DHCP traffic from the phone, I would observe that the DHCP sever sees the DHCPDISCOVER messages being repeated over and over again but presumably the DHCPOFFER seemingly would not make it all the way to the phone.
  6. Since I use a separate DHCP/NAT server, address reservation in the deco is not an option. I have tried adding a correct IP configuration manually, but there was still no connectivity despite this.
  0  
  0  
#3
Options