@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