Root AP managed by Omada controller?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello. I currently have three EAPs for my wifi. Two EAP245s and 1 EAP225 all version 3.
I was changing some settings and got a warning when changing the channel width on the EAP225 that it is the "root AP".
I did not think there was a root AP when managed by theOmada controller.
Is there a way to changes this without resetting the AP?
Thanks in advance
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Rojoone2 wrote
Wifi works great, but I know is should not be getting a warning about a root AP
Then just disable the mesh in Wireless Settings -> Mesh to get rid of this warning.
- Copy Link
- Report Inappropriate Content
Rojoone2 wrote
I was changing some settings and got a warning when changing the channel width on the EAP225 that it is the "root AP".
You can ignore this warning if you haven't set up a mesh network.
I did not think there was a root AP when managed by theOmada controller.
That's because if controlled by the Omada controller the controller knows if (and which) nodes are connected to a mesh network. So it gives this warning only if the node is part of a mesh network.
You can always change a node's WiFi channel without resetting the EAP.
- Copy Link
- Report Inappropriate Content
Rojoone2 wrote
Hello. I currently have three EAPs for my wifi. Two EAP245s and 1 EAP225 all version 3.
I was changing some settings and got a warning when changing the channel width on the EAP225 that it is the "root AP".
I did not think there was a root AP when managed by theOmada controller.
Is there a way to changes this without resetting the AP?
Thanks in advance
"Root AP" is relative to mesh networks. Now EAP245 V3.0 doesn't support mesh feature, so it cannot build mesh network with EAP225 V3.0 now.
Just ignore this information and connect all three EAPs via an Ethernet cable. Then you should manage the EAPs successfully.
- Copy Link
- Report Inappropriate Content
They were all wired. Two of them on the main mswitch and one on a second switch in my media cabinet.
Wifi works great, but I know is should not be getting a warning about a root AP
- Copy Link
- Report Inappropriate Content
Rojoone2 wrote
Wifi works great, but I know is should not be getting a warning about a root AP
Then just disable the mesh in Wireless Settings -> Mesh to get rid of this warning.
- Copy Link
- Report Inappropriate Content
This does not get rid of the warning on an EAP225-Outdoor.
I have an EAP225 and EAP225-outdoor, both wired ethernet connections, and mesh turned off in the settings.
When I try to lower the radio power on the 5ghz band, I get the warning.
I did not get the warning when changing the 2.4ghz.
I have mesh turned off (unchecked) in the Wireless Settings of the controller, and in both AP configuration menus.
- Copy Link
- Report Inappropriate Content
@CoKro, seems that this could have been changed. For me It did work with the firmware version at the time I wrote the post.
- Copy Link
- Report Inappropriate Content
@CoKro I thought I was the only person getting this warning. But it seems to be limited to the EAP225. If I leave that EAP out, I do not get a warning. It's certainly NOT the root AP. So I got another EAP245 and the warning went away.
I hope someone at TP-Link is seeing this. Users who have the ability to hardwire all their AP's should not have to be alerted they are changing settings on a "root" AP. I wonder though if the EAP225 v3 and the EAS225 outdoor have the exact same firmware that makes the Omada controller think there is a "root"AP?
- Copy Link
- Report Inappropriate Content
Rojoone2 wrote
I wonder though if the EAP225 v3 and the EAS225 outdoor have the exact same firmware that makes the Omada controller think there is a "root"AP?
Yes, it does so with both models. And if EAP245 becomes mesahble by a new firmware announced long time ago, it probably will also trigger this message.
Of course, TP-Link should change this, but I think R&D will not put much efforts into classic Omada controller anymore, since they work on the new SDN controller, which might have this nasty bug fixed already. Usually TP-Link fixes even cosmetic bugs reported to the forum, but it will last some time until it's done.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 4212
Replies: 8
Voters 1
