TP Link Omada ControllerThis article describes the installation and configuration steps for TP-Link Omada Cloud-Based Controller.
You will need Omada Controller v5.3.1 or above in order to proceed. Our test was performed with Omada Cloud controller v5.9.41.
Connecting
Connecting
Login to Omada Controller.
Go to the Authentication / Portal page.
Configure as follows:
Authentication Type – External RADIUS Server
Authentication Timeout – 8 hours
NAS ID – TP-Link
Authentication Mode – PAP
Portal Customization – External Web Portal – wifihotspot.io/login/omada
Landing Page – The Original URL
To configure the RADIUS server go to the Authentication / RADIUS Profile page and configure with:
Name – starthotspot-radius (or whatever you wish)
VLAN Assignment – Disabled
Authentication Server IP – 13.92.228.228
Authentication Port – 1812
Authentication Password – (contact our office)
Radius Accounting – Enabled
Accounting Server IP– 13.92.228.228
Accounting Port – 1813
Go to Authentication / Profile / Access Control, enable Pre-Authentication Access, and add the following domains:
wifihotspot.io
cdn.wifihotspot.io
starthotspot.com
cdnhotspot.azureedge.net
cdn.starthotspot.com
t-msedge.net
static.cloudflareinsights.com
13.92.228.228
13.90.247.200
40.117.190.72
40.121.151.4
Apply changes.
If you want to change default Omada Controller SSL and implement your own domain, you need to modify Login URL in the Hotspot – Advanced page as: https://domain:port”
In case you get 500 Internal Server error, please check if there is an option to configure which parameters are being sent in the redirect, and their names.
We should recive:
target=192.168.1.79
targetPort=8843
clientMac=99-F9-D3-1F-78-XX
clientIp=192.168.1.93
apMac=99-99-99-00-XX-99
gatewayMac=
scheme=https
ssidName=*Guest+Omada+5
vid=
radioId=0
originUrl=http%3A%2F%2Fwww.gstatic.com%2Fgenerate_204
hostname=192.168.1.79