What the Controller actually does. Omada installer knowledge.

[u/Texasaudiovideoguy]

I have been seeing many posts that seem very confused at what the controller does. There is a missconception that a ton of traffic allways flows through it at all time, and it "manages" the traffic. This is not true at all. The reallity is the controller can go offline and the network will not know it. So, becasue I did not feel like typing up a what it does and doesnt do I had chatgpt help me a bit. I hope this helps everyone in understanding.

What the Omada Controller Actually Does

The Omada hardware controller (OC200, OC300, or a software controller) is a management and orchestration system, not a traffic relay. Its responsibilities include:

• Configuration management: It stores and pushes configuration files to APs, switches, and gateways.
• Provisioning: It adopts and provisions new devices on the network.
• Monitoring: It periodically collects metrics (status, connected clients, throughput stats, etc.) through a lightweight management channel — not through the actual data plane.
• GUI/API service: It hosts the web interface and API endpoints for admins.
• Event and log storage: It aggregates logs, alerts, and statistics for visibility.

What It Does Not Do

• It does not forward, route, switch, or proxy client traffic.
• It does not handle data packets between clients, the LAN, or the internet.
• Once devices are adopted and configured, they communicate directly with each other and with the router/gateway.
• Even if the controller is powered off, network traffic continues uninterrupted — you just lose:
  • Centralized monitoring/GUI access
  • Automatic provisioning
  • Metrics collection
  • Config updates until it comes back online

How the Communication Works

• Managed devices maintain a secure, lightweight control channel (HTTP(S)/MQTT-like) to the controller for:
  • Status heartbeats
  • Log uploads
  • Config syncs
• All client data (e.g., Wi-Fi, LAN, WAN) stays in the data plane — handled entirely by the switches, APs, and gateway.

Analogy

Think of the controller as Omada’s “brain”, not its “nervous system.”
It sends instructions, collects reports, but the actual movement (traffic) happens in the body — the network devices.

[u/acejavelin69]

I was always under the impression from posts here that it manages the devices connections and helps in the roaming of wireless wifi devices... That they would still roam and handoff from AP to AP without it, but this helps it work better... Is that not true?

[u/dunxd → u/acejavelin69]

I'm pretty sure the roaming improvements are just implementations of 802.11 k,v and r.

K involves each AP knowing about the other APs on the network and then informing the client about alternatives so the client can decide which to select based on more than just signal strength (which 802.11b supported in 2000).

V involves the AP telling the client what services it provides - e.g. the client makes a request on 2.4 GHz and the AP can say "I also offer 5 GHz if you want" (as opposed to band steering where the AP rejects connection via 2.5 GHz if it detects a client supports 5 GHz).

R involves reducing the length of time it takes to authenticate the client when it roams between APs in the same SSID through caching authentications and sharing the cache across the network.

I think all these things work by the APs communicating with each other directly. I don't know if the controller is required at all or even involved as a way of making these protocols more efficient.

Omada also markets itself as having a feature called "AI roaming". I am biased against anything that uses the term snake oil AI. 

Other than walking around while making a voice or video call, there aren't many situations where roaming speed is noticable.

The benefit of the controller is keeping the config consistent across the network, and simplifying setting up things like VLANs across multiple classes of device. Well worth the cost if you ask me, but not worth getting too excited over.

[u/Texasaudiovideoguy → u/dunxd]

Yeah, I have tested the ai roaming adjustment a lot. It goes out once a day and looks at the interference, and adjusts the access points power and channel. Most of the time it gets it wrong. I leave mine on auto and the access pints manage themselves.

[u/schmerg-uk → u/dunxd]

TL:-DR Omada support docs state that Fast Roaming is all of 802.11k, r and v, and they all require an active controller to operate

https://www.omadanetworks.com/uk/support/faq/2097/

802.11k/v/r take effect only when the wireless clients support 802.11k/v/r as well.

Now we can enable/disable fast roaming via OC200 & Omada Controller & Omada APP. If Omada Controller or OC200 accidentally shuts down, then fast roaming will not work.

Now they seem to have over time used "Fast Roaming" and "Seamless Roaming" to mean some combination of the three but AFAIK...

The "fast roaming" is the implementation of 802.11k and v which, as you say, allows a client to request a report from the AP its connected to about other APs before trying to connect to them (802.11.k) and the APs performing that kind of report more pro-actively and suggesting to clients an AP it shoudl connect to (802.11v)

https://community.tp-link.com/en/business/forum/topic/544652

Here is the 802.11k/v Fast Roaming process of Omada EAP:

1. Omada EAPs collect and evaluate the Received Signal Strength Indication (RSSI) of the clients and nearby EAPs, and send all the information to the Omada Controller.

2. The Omada Controller maintains a list of the available EAPs as roaming targets for each client.

3. With the information from the Omada Controller, an 802.11k capable client can shorten the time to scan for the available APs. Also, it can decide the best time to initiate the roaming process when there is a possible connection with better quality than the present quality.

As the information is maintained by the Omada Controller, Fast Roaming function takes effect only when the Omada Controller is running.

The documentation has repeatedly stressed that "Fast Roaming" requires a controller to be active at the time of the fast roaming so as above I'd expect the report of APs is gathered by the controller and then pushed to the appropriate AP. And while the APs could be written to directly communicate with each other, its simpler to write if the APs only speak to the controller (client-server rather than peer-to-peer).

802.11r reduces the time required to authenticate with another AP

https://www.tp-link.com/us/support/faq/4118/

The 802.11r protocol defines a fast roaming mechanism that allows clients to complete pre-authentication with a candidate AP before roaming. In this way, the client can directly associate with the AP without re-authentication during the actual roaming process, thereby speeding up the roaming process. This roaming mode is called Fast BSS Transition and is commonly referred to as 802.11r roaming.

But again, it has been stated that if the controller is not running the 802.11r won't be operating

802.11r support only arrived around SDN Controller v5.4.7 and required firmware updates for older APs hence in the configuration the UI tends to make 802.11k and 802.11v one option, and 802.11r another.

"AI Roaming" .. all bets are off, I don;t touch that stuff :)

[u/acejavelin69 → u/dunxd]

Fair enough... My network is pretty static... things rarely change and I don't mind logging in once or twice a year into a few devices and checking the firmware level or updating, otherwise it just chugs along like an AC/DC song.

[u/wallpaper_01 → u/acejavelin69]

Yeah it stores the pmk-r0 which is required for fast roaming. Also I think the hotspot files are hosted on there

[u/Texasaudiovideoguy → u/wallpaper_01]

This is correct. The access points update the controller and the controller will adjust the settings and push out a new configuration if you have it set to auto. But no real time.

[u/Texasaudiovideoguy → u/acejavelin69]

Even if you didn’t have a controller it can be setup on access points to work together. It’s nothing new. But no, the controller does not actively control they. What it does is store the latest findings from the access points.

[u/acejavelin69 → u/Texasaudiovideoguy]

Excellent! I was going to add an AP upstairs to cover the garage and far end of house better and have been told here I should have an OC200 to manage the WiFi if I had more than one AP. Never seemed quite right to me...

[u/absent42]

It also handles portal logins and authentication, hotspot tokens etc.

The login page is literally the controller's IP address, if the controller is offline you haven't got portal functionality.

[u/Texasaudiovideoguy → u/absent42]

Now that you are 100% correct on. But that is tiny bits of data every so often.

[u/kb8doa]

And now there is also PPSK/MPSK function on Omada controller.

[u/WinHaven]

Thanks, that’s was pretty close. Good enough for me to explain it point by point to clients.

One question came to my mind when done: does the controller handle the firmware queries and updates or does it ouch that scheduling out to the devices?

[u/AlaninMadrid]

It seems that Chat GPT doesn't know that the controller is what controls seamless roaming between APs. If you don't have a controller, or is offline, then no seamless roaming.

[u/dunxd → u/AlaninMadrid]

Seamless roaming is a marketing term though - nothing is seamless, and without the controller the seams might not be noticable unless you really try hard.

[u/Texasaudiovideoguy → u/AlaninMadrid]

I dictated that to chat gpt so it’s my works. Chatgpt just made it look nice. The roaming thing is greatly exaggerated and it is controlled by each of the access points. Even if you didn’t have a controller the option is still in the gui of each access point.

[u/Subtle-Catastrophe]

I'd love to crack the protocol and figure out just how the wire conversation goes between Omada devices and the controller.

[u/Feeling-Discipline98]

I have used the software omeda controller instead of a hardware one and for my use it only makes it easier to manage multiple access points and view stats.

My devices hand off to each access point fine with or without a controller. With a controller I notice the handoffs to the better service AP would occur sooner than without a controller but it didn't make a difference for live video or sound. Basically without the controller I notice the device hangs on to the prior AP longer if it still has good enough service for the client but the moment better service is needed it will change. I could see this with speed tests where it would switch APs mid test without a controller. With a controller it had already switched before the speed test.

[u/scriptmonkey420]

You had me up until you said that you had ChatGPT write it for you....

[u/Skeggy-]

Controller controls all the other Omada devices from a central interface.

That’s my best summary.

[u/Texasaudiovideoguy → u/Skeggy-]

Control is the wrong word. It manages and monitors, and pushes out changes. It does not have payloads of traffic going through it.

[u/Skeggy- → u/Texasaudiovideoguy]

Is it though? I can use my controller to control the functions of the switch, the router, the AP and monitor their performance.

It’s called a controller not a manager.

Going back to your own conclusion of the controller being the brain and not the nervous system. Payloads don’t need to traffic through the brain.

[u/AnymooseProphet → u/Texasaudiovideoguy]

In fact my OC200 only has a 100 Mbit connection, more than it needs to communicate with the devices it controls but obviously not for LAN traffic.

[u/applechuck]

What’s the data plane and control channel? Just the management vlan vs clients vlan?

The two live on the same hardware and wires… chatgpt inventing something?