EAP245 v1 disconnected from omada controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi
Im having the issue that my EAP 245 v1 APs get immediately disconnected from the Omada Controller, once the configuration has been applied the configuaration to the AP. The EAP seems to have lost its IP. Strange is, that the EAP still works but you cannot ping it or even login. You have to hard reset it.
My Controller is in the same subnet as the APs. I tried the Windows Omada controller version 3.0.2 and 2.7.0. I run a ping on from the controller to the EAP which is 100% stable. So should not be a network issue.
My EAPs get power from the power supply that was delivered together with the EAP. For testing a used a 30w Power Injector instead of the Power Supply, which didn't work as well.
A firmware update of the EAP APs to the latest version didh´t help as well.
Any idea?
Regards Michael
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Im having the issue that my EAP 245 v1 APs get immediately disconnected from the Omada Controller, once the configuration has been applied the configuaration to the AP. The EAP seems to have lost its IP. Strange is, that the EAP still works but you cannot ping it or even login. You have to hard reset it.
You mean the EAP245 had lost it's IP address after you configured EAP by Omada Controller? If the IP address of EAP is changed, then it will disconnect from Omada Controller, since Controller communicate with EAP with the former IP.
The default IP setting of EAP in Controller is dynamic IP, if you have set static IP address in EAP first, then you adopt this EAP by Controller and configure it, the EAP will try to get a dynamic. If the dynamic IP is different from the static IP you set before, then the EAP will disconnect from Controller.
And you can also check if it is the DHCP Server problem.
- Copy Link
- Report Inappropriate Content
The AP aperently lost the IP but is still working. However the Omada Controller shows a 192.168.0.254 address. That subnet is actually not in my network. Weird is that an Network monitor doesn't show up the AP's old IP but the 192.168.0.254 broadcasting to 255.255.255.255.
- Copy Link
- Report Inappropriate Content
The AP aperently lost the IP but is still working. However the Omada Controller shows a 192.168.0.254 address. That subnet is actually not in my network. Weird is that an Network monitor doesn't show up the AP's old IP but the 192.168.0.254 broadcasting to 255.255.255.255.
The 192.168.0.254 is the fallback IP. Only when EAP can't get a IP address from DHCP Server then it will fall back to 192.168.0.254. I think you need to check your DHCP Server in your Router/Switch.
- Copy Link
- Report Inappropriate Content
Hi
I don't think so. My DHCP server is on coming from my FW. So even used a Windows DHCP Server instead in the same subnet, it hasn't been working. In addition a bought a EAP 225 which hasn't working as well.
The weird thing is that the AP is still working even though disconnected and not reachable anymore via its IP. Therefore I think that I don't have a DHCP issue.
- Copy Link
- Report Inappropriate Content
I got it finally working. Instead of the Windows Omada Controller Software I'm using now the docker version. I assume the Windows controller is having issues with the EAP245 and 225 as the docker is working in the same environemnt in which the Windows controller hasn't been working so far. But many thanks to 7eleven for helping me.
- Copy Link
- Report Inappropriate Content
i have the same problema. right now.. what is that docker version? where can i download that?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5217
Replies: 7
Voters 0
No one has voted for it yet.