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
It may be some VLAN setting problem.
EAP does not support DHCP Server. Maybe you can capture the packets of the LAN port of EAP225, check if the EAP225 transmit the DHCP discover/request packets from wireless clients to the DHCP Server, and does the DHCP Server respond DHCP offer/respond to wireless clients.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
You mean wireless clients can't get IP address from DHCP Server as long as the EAP225 is managed by Omada Controller. It may be some configuration of Controller, such as the VLAN setting of SSID in Controller.
- Copy Link
- Report Inappropriate Content
Hi, The different is between the setups only EAP225 is managed by Omada Controller or not. VLAN, SSID are exactly the same
Scenaro:
- EAP110* and EAP225 is managed by Omada --> 110working well with all of the services, but 225 is not forwarding DHCP response, but the others do it. (btw in the meantime I could see DHCP request on DHCP server side and it answered it)
- EAP110 is managed by Omada, EAP225 is standalone, (same SSID, same VLAN, really, everything is the same) --> 110 working and 225 too.
In the meantime switch wasn't touched.
- Copy Link
- Report Inappropriate Content
It's weird. What's the software version of Omada Controller? The recommend Controller version is 3.0.2. Maybe you can reinstall the Controller for checking.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
HI
You rebuild all AP´s connection to OMADA controller?
We are having issues with OMADA controller and dhcp.
IT works a few hours and then user can´t get ip address via dhcp
- Copy Link
- Report Inappropriate Content
I too am experiencing this issue.... most notably with devices that 'stay' connected for long lengths of time. Like my thermostats and such.... once the lease expires, the clients are not able to renew their DHCP lease from my router. Fix seems to always be to disconnect and re-associate with the AP. Then it works.
Strange...
- Copy Link
- Report Inappropriate Content
Hi,
I also have a similiar problem. I have 2 EAP225-Outdoor(EU) with omada controller 3.1.4 and two SSID's. We also have 2 other AP's with diferrent SSID. We only add the Tp-link about 1 month, meanwhile I started to get complains in some android devices and laptops that they couldn't connect to wireless.
After some time I realise that they don't get IP address from the EAP networks, but they can connect to the old AP's we have, so the problem is not the DHCP server, since it's the same for all the network.
Does any ony could solve this problem?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 10369
Replies: 11
Voters 0
No one has voted for it yet.