diff --git a/omada-controller/data/config/.gitkeep b/omada-controller/data/config/.gitkeep new file mode 100644 index 000000000..e69de29bb diff --git a/omada-controller/data/logs/.gitkeep b/omada-controller/data/logs/.gitkeep new file mode 100644 index 000000000..e69de29bb diff --git a/omada-controller/docker-compose.yml b/omada-controller/docker-compose.yml new file mode 100644 index 000000000..c8d9d0b26 --- /dev/null +++ b/omada-controller/docker-compose.yml @@ -0,0 +1,45 @@ +services: + server: + image: mbentley/omada-controller:6.3.0.111@sha256:10a6e4d3bdae2fa4d9d6f54fe5f2b5758b672227b1dda28137e89fc6b4ddd8b0 + restart: on-failure + stop_grace_period: 60s + # Host networking is required so the controller can discover and adopt Omada devices on the local network + network_mode: host + ulimits: + nofile: + soft: 4096 + hard: 8192 + environment: + PUID: 1000 + PGID: 1000 + MANAGE_HTTP_PORT: 8072 + PORTAL_HTTP_PORT: 8072 + volumes: + - ${APP_DATA_DIR}/data/config:/opt/tplink/EAPController/data + - ${APP_DATA_DIR}/data/logs:/opt/tplink/EAPController/logs + + # Omada always redirects its HTTP port to its own self-signed HTTPS port. + # This proxy serves the web UI as plain HTTP on the app port, so umbrelOS can add its own HTTPS in front. + web: + image: caddy:2.11.9-alpine@sha256:0bbb055bda6793c999bde78b1b5ce3e89f829fb031af2cf50056ea1246559fee + user: "1000:1000" + restart: on-failure + network_mode: host + command: + - sh + - -c + - | + cat > /tmp/Caddyfile <<'CADDY' + { + admin off + } + :8074 { + reverse_proxy https://127.0.0.1:8043 { + transport http { + tls_insecure_skip_verify + } + header_down Location ^https?://[^/]+:(8043|8072) "" + } + } + CADDY + exec caddy run --config /tmp/Caddyfile --adapter caddyfile diff --git a/omada-controller/umbrel-app.yml b/omada-controller/umbrel-app.yml new file mode 100644 index 000000000..7f07a282d --- /dev/null +++ b/omada-controller/umbrel-app.yml @@ -0,0 +1,50 @@ +manifestVersion: 2.0 +id: omada-controller +storage: + dataRoot: data +category: networking +name: Omada Controller +version: "6.3.0.111" +tagline: Manage your TP-Link Omada network from your Umbrel +description: >- + ⚠️ Omada Controller needs at least 2 GB of free memory. + + + Omada Controller (also called Omada Network) is TP-Link's free software controller for Omada access points, switches and routers. It lets you adopt, configure and monitor all of your Omada devices from one place, without a hardware controller or a cloud subscription. + + + On first launch you can create a local account, or sign in with a TP-Link ID if you want to use Omada's optional Cloud Access and mobile app remotely. + + + Omada devices on the same local network as your Umbrel are discovered automatically and can be adopted from the Devices page. + + + Features: + + + - Central management for Omada access points, JetStream switches and Omada gateways + + - Live network topology, dashboards and client insights + + - Guest Wi-Fi with captive portals and vouchers + + - Firmware updates, scheduled reboots and backups for all devices + + - Multi-site management from a single controller +developer: TP-Link +website: https://www.omadanetworks.com +submitter: hugofnm +submission: https://github.com/getumbrel/umbrel-apps/pull/1196 +repo: https://github.com/mbentley/docker-omada-controller +support: https://community.tp-link.com/en/business/forum/582 +port: 8074 +requiresHttps: true +gallery: + - 1.webp + - 2.webp + - 3.webp +releaseNotes: "" +dependencies: [] +path: "" +defaultUsername: "" +defaultPassword: ""