Omada Controller Access Control Configuration for External Captive Portal

Omada Controller Access Control Configuration for External Captive Portal

Omada Controller Access Control Configuration for External Captive Portal
Omada Controller Access Control Configuration for External Captive Portal
2026-01-28 09:13:33
Model: EAP225  
Hardware Version:
Firmware Version:

I am running an Omada Controller on DN1. We also have a dashboard with a backend hosted on DM2, and an external captive portal hosted on DM3.

I would like to know which domain names and IP addresses should be allowed in the Access Control section of the Omada Controller.

At the moment, I have already added:

  • The domain name and IP address of the external captive portal
  • The domain name of the dashboard

My questions are:

  • Do I also need to add the domain name or IP address of the Omada Controller itself on the access control list?

Notes:

  • No RADIUS server is used for authentication.
  • Internet Access for Wi-Fi users is handled via APIs developed on the backend of the dashboard.
  • These APIs communicate with the Omada Controller using the following Omada endpoints:

    • CONTROLLER_IP:PORT/CONTROLLER_ID/api/v2/hotspot/login
    • CONTROLLER_IP:PORT/CONTROLLER_ID/api/v2/hotspot/extPortal/auth
  0      
  0      
#1
Options
2 Reply
Re:Omada Controller Access Control Configuration for External Captive Portal
2026-01-30 07:09:09

Hi  @malek_ 

 

Thanks for posting here.

 

Here are all Omada domain names, you may have a look:

Omada Cloud’s domain names

  0  
  0  
#2
Options
Re:Omada Controller Access Control Configuration for External Captive Portal
2026-01-30 14:54:02

Thanks for your reply but my question is which domain names (DM1, DM2, DM3) need to be allowed in order to successfully integrate an external captive portal with the SDN controller?

  0  
  0  
#3
Options