Perhaps needless to say, but wired connections always work fine, even if the wireless connection is having issues.

 Hi @Theedoek 

To better understand the issue, please help us confirm the following info:

1. How often will the issue occur?

2. When the issue arises, will it happen on all the wireless clients? Or there were some clients unaffected at the same time?

3. If the issue only happening on certain clients, please let us know what kind of clients they are.

4. Is force provisioning the only way to fix the issue? If wait for some time, such as 5-10 mins, will it recover automatically?

5. What  settings did you change on the EAP?

  @Vincent-TP 

1. How often will the issue occur?

Answer: it is random. Sometimes it takes weeks before it occurs again, sometimes only a few days. I can't pinpoint this to a specific event that may have occured.

2. When the issue arises, will it happen on all the wireless clients? Or there were some clients unaffected at the same time?

Answer: For sure an iPad, Android phone and Windows 10 laptop, so I assume it will be the same for all wireless devices.

3. If the issue only happening on certain clients, please let us know what kind of clients they are.

Answer: iPad, Android smartphone and Windows 10 Pro laptop have been confirmed.

4. Is force provisioning the only way to fix the issue? If wait for some time, such as 5-10 mins, will it recover automatically?

Answer: last time I had to wait half a day before I could address the issue, so no, it does not seem to recover automatically. I initially tried rebooting the EAP's from the controller which did not solve the issue. A hard reboot did not help either. Force provisioning did help.

I have also tried to remove the EAP's from the controller (using the "Forget" function) and re-adding them, but the issue remains.

5. What  settings did you change on the EAP?

Answer: Over time I have played around with various settings to figure out what is triggering this, to no effect. This behaviour has been observed ever since I replaced my 245's for 772's.

Hi  @Theedoek 

Thanks for the reply. One more thing we want to confirm:

 but for example sending WOL packets to a node or connecting to specific services via specific TCP ports doesn't work anymore.

>>> Which ports are you using? Or what kind of services you are using?  how is the error page showing? If you don't mind, please also share with some screenshots. Thanks.

  @Vincent-TP 

Hi Vincent,

We occasionally use wake-on-lan (WOL) to power up a small computer for casting purposes. When the failure occurs, the magic packets just don't go through and the machine does not power on. The same applies to a couple of web API's and GUI's running on alternative ports (varying TCP ports in the range of 7000 to 9999). They are simply not reachable anymore.

Not much to screenshot to be honest, but I will try and take screenshots and logs of whatever I can find when it occurs again.

To rule out a known WPA3 CCMP issue which has very similar symptoms, I had disabled the 6GHz band.

Unfortunately this morning I heard that the wifi network is having this issue again.

While tetsing, these are my findings:

- PiHole web-UI unreachable (http://<ip>:8888). Via wired network it all works fine and the page opens instantly.

- Bowsing SMB shares from an iOS device connected to wifi doesn't work anymore. It does when connected by wire.

- Wake-on-LAN packets don't work anymore

- No suspicious messages on the Omada Cloud dashboard

- No events reported in the event log

- EAP's were rebooted this morning (reboot schedule)

Hi  @Theedoek 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID241239711, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!