eap225 outdoor (with oc200) - clients can't get DHCP ip address
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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?
Hi,
We have never received such feedback. Here are some suggestions for you to have a try.
1. Please check if you have managed the EAP successfully. Normally when we manage the EAP successfully, we will see the AP in the "Connected".
2. When the Omada Controller manages the EAP, please check if the EAP gets an IP address successfully.
3. When the client devices connect to the EAP, can you see the client status in the Omada Controller?
There is definitely a problem with your cabling or with your network setup if you use VLANs.
Our customers use EAP225-Outdoors wired to an Omada controller running on OC200 or running on servers without any problems. Clients get an IP and won't be disconnected until they disappear. Look at the "Active time" column (last one):
You wrote the EAP225-Outdoor works when meshed. I suggest to check your cable for loose contacts. Also make sure to use properly shielded cables and grounding as required for any outdoor device.