@Vincent-TP 

My EAPs have been up for almost 2 days now without dropping connections on my IoT devices. They have never gone this long.

This probelm had nothing to do with Multicast-To-Unicast Conversion (I turned this back on). It had to do with WPA3 and PMF = Capable. I had DISABLED PMF on my IoT SSID but kept it ENABLED on my Primary SSID. Disabling on BOTH SSIDs solved this issue.

To test, I ENABLED on my Primary SSID and left it disabled on my IoT SSID. Doing so led to the IoT devices dropping connections in about an hour.

I would like to be able to use WPA3 on my Primary SSID. Is there a firmware fix in the works to solve this? If not, would you please open a ticket?

  @Vincent-TP

Let me be clear:

I have two SSIDs. These are separate VLans.

- Primary (192.168.1.1/24)

- IoT (192.168.2.1/24)

If I set PMF = Capable on my Primary SSID and PMF = Disable on my IoT SSID, my IoT devices connected to my IoT SSID fail to connect after an hour or so.

My IoT devices are not trying to connect to my Primary SSID because they don't have that password and are blocked from accessing the Primary network through an ACL rule. They have Fixed IP addresses on the IoT network.

EXPECTED BEHAVIOR:

The following settings should work:

- Primary Network: PMF = Capable

- IoT Network: PMF = Disable

Instead, these settings cause my IoT devices on my IoT network to fail to connect after a couple hours.

Here is a person having the same problem:

https://community.tp-link.com/en/business/forum/topic/746938

  @CoffeeAndTech For those viewing this thread in the future and experiencing this same issue, I was able to solve it by setting Band Steering = Disable (by default it is set to "Prefer 5Ghz/6Ghz”) and disabling 5Ghz on my IoT SSID.

  @Vincent-TP 

Fun fact:

The EAP670v2 with the current firmware (1.1.1) continues to do this. After an undefined period of time, the IoT devices are disconnected. All “big” clients, such as phones, computers are still connected. I have had the problem for two versions of the firmware.

Multicast to Unicast off does not help

Deactivation 6Ghz does not help.

PMF capable/off does not help

From my point of view it is explicitly a problem with the EAP670. Until a few days ago, the EAP670 was my only EAP and I restarted it automatically every two days as a prophylactic measure.

Since a few days I have the EAP772v2 as main AP and the EAP670v2 is connected as Mesh AP with Wifi uplink.

The problem persists. After an undefined time, the EAP670 disconnects all 2.4 Ghz clients.

The EAP772v2 continues to run unimpressed and takes over all clients, even if they have poor RSSI values.

After a restart of the EAP670v2, the clients are distributed between the two APs again as desired - until the next disconnection.

I have a total of around 40 wifi clients, of which around 20 are IoT clients, all of them can at least use 802.11n/“Wifi4” and they are not super old either. The simple fact that the EAP772v2 runs without any problems with the same clients for several days is an indication for me that it is somehow due to the EAP670v2 itself.

Both EAPs are controlled via controller and both distribute the same SSIDs with the same settings.

All devices in the network have the latest firmware installed.

Can we expect a solution at some point?