EAP Controller - https://www.tp-link.com/common/Spotlight/EAP_controller.html
Running on the latest Phusion release (ubuntu 16.04), with EAP Controller v2.5.3 ONLY X86!!!!!
Pull image
docker pull mace/eap-controller
Run container
docker run -d --net="host" --privileged --name=<container name> -v <path for eap config files>:/config -v /etc/localtime:/etc/localtime:ro mace/eap-controller
Please replace all user variables in the above command defined by <> with the correct values. Use --net="host" or --net="macvlan0"
Web-UI
http://<host ip>:8088
https://<host ip>:8043
Example
docker run -d --net="host" --privileged --name=eapcontroller -v /mylocal/directory/fordata:/config -v /etc/localtime:/etc/localtime:ro mace/eap-controller
Additional notes
- For a custom cert, stop the container and put the cert in "/config/cert" it needs to be named "mydomain.p12" and have the password "tplink"
- The owner of the config directory needs sufficent permissions (UUID 99 / GID 100). (For manual configs, backups etc on the host system)
- Mongodb dosent start if "/config" is mapped to an fuse mount, shfs, mergerfs etc...
- Should be run with network "host" or "macvlan", so it can find the AP´s
- Username and password will be linked to controller (if you restore a backup this will only restore AP,SSID,etc... settings, not the base controller username/pass()EAP limitation)
- Always make an backup of your settings before a new release "EAP controller version"(for a reinstall with same version it´s not necessary)
- If it dosen´t start make sure there is just one controller on the same subnet (EAP limitataion)
- This buils is only X86 with TP-Links budeled binaries
Change notes
-
2018.06.19 Add keystore to config for custom certs
-
2018.02.16 Initial release