← Directory

EAPcontroller

Self-hosted TP-Link EAP (Easy Access Point) Controller for centrally managing hundreds of TP-Link Omada EAP wireless access points across multiple sites from…

  • Network Services
  • Tools & Utilities
Self-hosted TP-Link EAP (Easy Access Point) Controller for centrally managing hundreds of TP-Link Omada EAP wireless access points across multiple sites from a single server location.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

21/100 Low

Maintained
0last commit 1704 days ago
Popular
2516 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today, links checked 13 days ago

GitHub stars
16
Open issues
0
Last commit
2022-02-12
License
GPL-3.0
Activity
stale

Checked 7 days ago - source: GitHub (macexx/EAP-Controller)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 10 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Unraid /config Path Requirement The /config host path must point to a direct path (e.g. /mnt/cache or /mnt/disk1). Unraid's shfs overlay filesystem is not supported and will prevent the internal MongoDB from starting. source
  • Custom Certificate To install a custom certificate, stop the container, place the file at /config/cert named 'mydomain.p12', and set its password to 'tplink'. source

Fetched 6 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why won’t MongoDB start when /config is mapped to Unraid shfs, mergerfs, or another fuse mount?

MongoDB does not start if the /config directory is mapped to a fuse mount such as shfs or mergerfs. Use a direct host path instead.

How do I install a custom certificate for the controller’s HTTPS interface?

Stop the container, place the certificate in /config/cert, name it mydomain.p12, and set the password to tplink.

What container network mode should be used for EAP discovery?

Run the container with host networking or a macvlan network so it can find the APs.

Are the controller’s admin username and password restored from a backup?

No, restoring a backup restores AP, SSID, and other settings, but not the base controller username or password.

Which ports serve the controller web UI?

The web UI is served on port 8088 for HTTP and port 8043 for HTTPS.

Can more than one Omada controller be used on the same LAN?

No, only one Omada controller is allowed on the same local area network, and an EAP can only be managed by one controller.

Answers sourced from community.tp-link.com, github.com

Community

Collected 9 days ago - public community threads