Hi All, TP-Link is aware of the vulnerability in Apache Log4j used in Omada Controller (CVE-2021-44228: Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not

I started having difficulty with my smart home devices, and staying connected to wifi. I have 4 visible SSID created, 3 with both 5GHz and 2.4GHz, plus a specific SSID created for these devices, with

Was wondering if DFS is supported for the EAP610 and or the EAP620 given that the usual 5ghz channels are getting rather congested. Is there also a difference between the EAP610v1 and the EAP610v3?

TPEAP stopped working, I upgraded it to the latest I could find (4.4.6). Still doesn't work. All my stuff seems to be to spec but maybe I'm reading something wrong. Omada_SDN_Controller_v4.4.6_Linux_x

How long is it going to be before you guys release a fix for the Log4j exploit? If you're not going to patch this anytime soon I will be forced to take the controller offline and run everything in sta

The Omada SDN software includes the vulnerable Log4j java files. Hopefully TP-Link provides a patch soon as all information indicates this 0-Day is being actively exploited, what that means to the Oma