TP-Link Omada Controller

Key Features

• Centralized management of TP-Link Omada access points, switches, and routers through single web interface
• Zero-touch device provisioning with automatic firmware updates and configuration deployment
• Advanced wireless features including band steering, load balancing, and seamless roaming between access points
• Network topology visualization with real-time device status monitoring and alert notifications
• Guest network management with captive portal, voucher system, and time-based access controls
• VLAN configuration and management across switches and wireless networks with inter-VLAN routing
• Detailed analytics and reporting including client usage statistics, bandwidth monitoring, and network performance metrics
• Role-based administrator access with granular permissions for different management functions

Common Use Cases

• 1Small business wireless network deployment with multiple access points requiring centralized configuration management
• 2Educational institution campus network with guest access controls and student device management
• 3Homelab enthusiasts building professional-grade networks with TP-Link Omada hardware for learning and testing
• 4Co-working spaces needing segregated networks for different tenants with bandwidth management and access controls
• 5Retail environments requiring guest WiFi with captive portals and marketing integration capabilities
• 6Remote office management where IT administrators need centralized control over distributed TP-Link network infrastructure
• 7Event venues and conference centers needing temporary network deployments with scalable access point management

Prerequisites

• Docker and Docker Compose installed with at least 2GB available RAM for controller operation
• Network ports 8043, 8088, 27001-27002, and 29810-29813 available and not blocked by firewall
• TP-Link Omada series hardware (access points, switches, or routers) connected to the same network segment
• Basic understanding of networking concepts including VLANs, DHCP, and wireless security protocols
• Administrative access to network infrastructure for initial device adoption and configuration
• Sufficient storage space for configuration backups, logs, and network monitoring data (minimum 5GB recommended)

docker-compose.yml

1services: 
2  omada: 
3    image: mbentley/omada-controller:latest
4    container_name: omada
5    restart: unless-stopped
6    environment: 
7      TZ: UTC
8    volumes: 
9      - omada_data:/opt/tplink/EAPController/data
10      - omada_logs:/opt/tplink/EAPController/logs
11    ports: 
12      - "8088:8088"
13      - "8043:8043"
14      - "27001:27001/udp"
15      - "27002:27002"
16      - "29810:29810/udp"
17      - "29811:29811"
18      - "29812:29812"
19      - "29813:29813"
20
21volumes: 
22  omada_data: 
23  omada_logs: 

.env Template

1# No additional config needed

Usage Notes

Quick Start

1# 1. Create the compose file
2cat > docker-compose.yml << 'EOF'
3services:
4  omada:
5    image: mbentley/omada-controller:latest
6    container_name: omada
7    restart: unless-stopped
8    environment:
9      TZ: UTC
10    volumes:
11      - omada_data:/opt/tplink/EAPController/data
12      - omada_logs:/opt/tplink/EAPController/logs
13    ports:
14      - "8088:8088"
15      - "8043:8043"
16      - "27001:27001/udp"
17      - "27002:27002"
18      - "29810:29810/udp"
19      - "29811:29811"
20      - "29812:29812"
21      - "29813:29813"
22
23volumes:
24  omada_data:
25  omada_logs:
26EOF
27
28# 2. Create the .env file
29cat > .env << 'EOF'
30# No additional config needed
31EOF
32
33# 3. Start the services
34docker compose up -d
35
36# 4. View logs
37docker compose logs -f

One-Liner

Run this command to download and set up the recipe in one step:

1curl -fsSL https://docker.recipes/api/recipes/omada-controller/run | bash

Troubleshooting