Mixed EAP AP setup -> DHCP not working on EAP225
Mixed EAP AP setup -> DHCP not working on EAP225
Hi
In my cluster I have different AP
2piece: EAP110(EU) |
1.0/2.0 |
1.3.0 Build 20180418 Rel. 74831 |
1piece:EAP110-Outdoor(EU) |
1.0 |
1.2.0 Build 20180418 Rel. 74942 |
1piece: EAP225(EU) |
3.0 |
2.3.0 Build 20180628 Rel. 54512 |
- VLAN & Switch confiugration, channel setup working well.
- EAP Controller running on Ubuntu16.10
- EAP version: 3.0.2 (but had the same issue with older versions too)
If 225 is added to Omada Controller then DHCP response didn't arrive to the client, I could see DHCPRequest message on the network from those clients who were connected to EAP255 but clients never got DHCP address, just repeated sequencially the request. Connecting to other AP and roaming between them is seamless.
Roaming between AP sometimes working from EAP110 to EAP225
But when EAP225 is removed from Omada Controller and has the same VLAN, SSID,password setup like the others as standalone, then DHCP answer arrives immediatly and network connection is good.
Does anybody had the same issue? Maybe because HW version is different that causing the issue?
Same problem on laptops, tables, chromecast, phones.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have this same 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 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 said, clients can get an IP address just fine.
The eap225 outdoor is definitely acting differently than the eap225 v3 model with respect to dhcp
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 10305
Replies: 11
Voters 0
No one has voted for it yet.