Programs use specific ports to send or receive data via a network. An Omada software controller or EAP Discovery Utility uses the ports on the host, while an Omada hardware controller uses the ports on its own hardware.
Ports fall into two groups: TCP (Transmission Control Protocol) ports and UDP (User Datagram Protocol) ports. Port numbers are limited, ranging from 1 to 65535 among each group. Such fact gives rise to a port collision when a program tries to use a certain port on a host, only to find the very port is occupied by another program.
From this article, you can learn which ports an Omada controller and an EAP Discovery Utility use, and how to troubleshoot a port-related problem when it happens.
An overview of the default ports
The ports which Omada Controller and EAP Discovery Utility use by default are listed in the following table.
| Ports | Omada Hardware Controller | Omada Software Controller | Omada Discovery Utility | When the port is required |
| Web Management and Portal | ||||
| TCP 80 | ✔ | 1. Your browser opens the Omada controller’s management page via an “http” connection. (For Omada Hardware Controller)2. Users are authenticated via an HTTP portal. (For Omada Hardware Controller v3.x and before version) | ||
| TCP 443 | ✔ | 1. Your browser opens the Omada controller’s management page via an “https” connection. (For Omada Hardware Controller)2. Users are authenticated via an HTTPs portal. (For Omada Hardware Controller v3.x and before version) | ||
| TCP 8088 | ✔ | ✔ | 1. Your browser opens the Omada controller’s management page via an “http” connection. (For Omada Software Controller)2. Users are authenticated via an HTTP portal. (For Omada Controller v4.x and later version) | |
| TCP 8043 | ✔ | 1. Your browser opens the Omada controller’s management page via an “https” connection. (For Omada Software Controller)2. Users are authenticated via an HTTPs portal. (For Omada Software Controller v3.x and before version) | ||
| TCP 8843 | ✔ | ✔ | Users are authenticated via an HTTPs portal. (For Omada Controller v4.x and later version) | |
| EAP Discovery, Adoption, Management, and Upgrade | ||||
| UDP 29810 | ✔ | ✔ | ✔ | Discover Omada devices(Applied to all versions of Omada Controller and Omada Discovery Utility.) |
| TCP 29811&29812 | ✔ | ✔ | ✔ | Adopt & Manage Omada devices.(Applied to Omada Controller v4.x and before version, Omada Discovery Utility v4 and before version.) |
| TCP 29814 | ✔ | ✔ | ✔ | Adopt & Manage Omada devices.(Applied to Omada Controller v5.x and later version, Omada Discovery Utility v5 and later version.) |
| TCP 29813 | ✔ | ✔ | Upgrade Omada devices.(Applied to Omada Controller v4.x and before version.) | |
| TCP 443 | ✔ | Upgrade Omada devices.(Applied to Omada Hardware Controller v5.x and later version.) | ||
| TCP 8043 | ✔ | Upgrade Omada devices.(Applied to Omada Software Controller v5.x and later version.) | ||
| Initialization Check | ||||
| UDP 27001 | ✔ | 1. Check whether another controller is running in the LAN during initialization. (For Omada Software Controller v3.x)2. In Omada Controller v4.x and later version, this port is mainly used for discovering the Omada Controller in the LAN by Omada App. | ||
| TCP 27002 | ✔ | Gather information about another controller in the LAN. (Only for Omada Software Controller v3.2.4 and before version. This port has been discarded in the later version) | ||
| Database Access | ||||
| TCP 27017/27217* | ✔ | The Omada Software Controller accesses the built-in database. |
Note:
TCP 27217 is used to access the built-in database for Controller Software V3.0.0 or later version. Before Controller Software V3.0.0, TCP 27017 is used instead.