eap225 outdoor (with oc200) - clients can't get DHCP ip address
I have a problem with the eap225 outdoor. I have two eap225 v3 models that have been working great with the oc200 Omaha controller.
i just got the eap225 outdoor. When I adopt it into the Omaha cluster, any client connected to it can’t get an IP address. They can get an ip address no problem when connected to either of the other access points. If I drop the eap225 outdoor out of the cluster and give it its own sid, clients can get an IP address just fine. it just doesn't work when it's in the omada cluster
is this a known issue?
will it be addressed in the next firmware release?