EAP225 IP address issue
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP is offline ("DISCONNECTED")
Omada controller (via browser) has not updated the ip address of the EAP225.
IP address in Omada is 192.168.1.58
LAN (wired) address is actually 192.168.1.246 (matched MAC address from router and pinged with CMD)
How can I get this EAP back online so that it's connected and acting as an AP?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Reset the device via the small reset button adjacent to the ethernet port (hold it down until the LED changes state ~5s). Re-adopt via Omada, should be good to go.
- Copy Link
- Report Inappropriate Content
@d0ugmac1 Tried that. Had to re-load and re-provision Omada, but no devices found. Both EAP225s are on my network (via cmd ping). Is there a way to manually specify the ip addresses in Omada?
- Copy Link
- Report Inappropriate Content
Is the Omada controller managing your router (605 or 7206?), or is it your ISPs? If not Omada controlled, then you need to fix the IPs using your router's web interface AND you need to disable the DHCP server in the OC200. Next you may need to use the Discovery tool (download from TPlink) to help the Controller find the APs as I think the Omada DHCP server sets certain DHCP option fields to facilitate the devices finding the controller.
- Copy Link
- Report Inappropriate Content
@asdasdasdasdasd If your Controller a hardware OC200? Or Software Controller?
If it is software controller you may need to disable firewall/antivirus on your PC. The Controller use port 29810-29814 to communicate with EAP.
- Copy Link
- Report Inappropriate Content
@d0ugmac1 It's my router (Archer AX50). OC is not managing my router. Discover Util shows no devices even when I enter the ip address. After resetting the EAPs, OC says "No Devices Found." I think there's something wrong with Omada Controller.
I got an alert that "failed to log in to the controller from 127.0.0.1." I don't use that range on my lan, so no idea why OC would router to this.
- Copy Link
- Report Inappropriate Content
The 127.0.0.1 (locahost address) is a big clue that you are running your Omada Controller on your own hardware as it means the Omada app and your browser are using the same network interface (which isn't possible on an OC200).
Another post recently noted that an update to Windows 11 unticks .NET and this must be re-enabled for the Omada app to run properly AS WELL AS the above, where you will almost certainly have to open up your Windows firewall to allow the controllers ports. If you are running this on a Linux box, well, that's a different set of rules.
Start by opening your firewall ports as @somnus mentioned above, and verifying that .NET is also allowed to traverse the firewall as an app.
- Copy Link
- Report Inappropriate Content
@d0ugmac1 The Omada Sofware Controller is running on my hardware -- my Win10 computer, but not my router. My router does not distribute addresses to the 127.x.x.x.x range.
Turning off the firewall worked so thanks for that. However, opening port 29810-29814 (TCP and UDP) and turning the firewall back on results in "missed heartbeat" and then "disconnected."
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@asdasdasdasdasd If you router is not Omada, you don't need to change any Network LAN settings on Omada. They won't work.
All device's IP should be obtained by your main router.
BTW it seems that you are using Software controller on a PC. You can just uninstall the Controller and delete all config file, then install it again from beginning. This time please note you don't need to do any other settings, just change th SSID and password is good enough.
If the Controller still cannot detect your EAP after re-install, you will need to disable firewall/anti-virus on this PC.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 884
Replies: 9
Voters 0
No one has voted for it yet.