Last Update: 2020-01-16
I just made a .deb package with Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system providing the dpkg installer. Please find the release notes at the end of this post.
This .deb package is in the tradition of the community version of Omada Controller, meaning it contains the same Java classes and remaining files as the official TP-Link version except for the binaries bundled with it (JRE, mongodb) and the start/stop script control.sh (which is replaced by my own version omadactl).
You will need netstat (package: net-tools), curl and the native versions of JRE, jsvc and mongod (installed by default in Raspbian based on Stretch, unfortunately not so in Debian). Setting up the Oracle JRE and jsvc is left to you as an exercise; here are some suggestions:
Debian and any other Linux distribution:
Install mongodb from the standard repository and JRE8 from Oracle's website. As for jsvc, don't use the Debian binary package, it requires OpenJDK last time I checked this. Instead, get the source code for jsvc (command apt-get source jsvc), compile it and install jsvc manually. Sorry for this inconvenience, but TP-Link decided to use jsvc for Privilege Separation rather than the much more common standard start-stop-daemon or daemonize programs already present on almost any Linux system. Don't blame me for this – omadactl still can use both methods, but you need to use jsvc for Omada Controller versions V3.x.
Raspbian (see also »Limitations« below):
Oracle JRE8, jsvc and mongodb are pre-installed by default in Raspbian (make sure you did not explicitly choose OpenJDK as an alternative for the Oracle JRE). You can easily check whether the required programs are installed on your Raspbian:
$ java -version
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) Client VM (build 25.65-b01, mixed mode)
$ update-java-alternatives -l
jdk-8-oracle-arm32-vfp-hflt 318 /usr/lib/jvm/jdk-8-oracle-arm32-vfp-hflt
$ mongod -version
db version v2.4.14
Thu Jan 16 18:10:51.272 git version: nogitversion
Donwload the all-architectures .deb package
Connect via ftp client (not a web browser) to ftp.rent-a-guru.de, use passive mode. Log in using anon ftp (username: anonymous, Password: your mail address). Once connected, change directory to /private. You won't see any files therein, it's a private directory. Just issue the command:
to download the file. Compute and compare the checksum of the downloaded .deb file:
md5sum: 501339a240409d3040717f07a5a69274 *omada-controller_3.2.6-1_all.deb
sha256sum: 9aaaf8af7da9eaa3e041941adaed722faddde6bc40981f1e4448f8a68a8870e1 *omada-controller_3.2.6-1_all.deb
First, make a backup of your Omada Controller's settings before installing. Either use the web UI or copy the whole content of the subdirectory data in /opt/tplink/OmadaController to a backup directory. You can later move the data directory back into the new controller version.
Install the new version of Omada Controller with:
dpkg -i omada-controller_3.2.6-1_all.deb
After a successful installation the controller will be started automatically.
- Ignore the warnings from dpkg about some directories which can't be deleted. dpkg will remove files from older versions of the same package omada-controller, but it won't delete the old database directory (unless you do a manual purge before installing). This means that your database and settings from previous versions of Omada Controller will be retained - you can copy the files in the data subdirectory over to the new version. See »Restoring Omada Controller settings« below.
- Installation directory is /opt/tplink/OmadaController-3.2.6. The symlink /opt/tplink/OmadaController is a short-hand alias to the installation directory.
- Start/stop script has been renamed from tpeap to omadactl (deprecated tpeap is still there, it's a symlink to omadactl).
- If installing using dpkg, you won't be able to switch between versions of Omada Controller using omadactl's switch command.
- Some options of omadactl have no effect with only one version of the controller installed, that is if you install the .deb-Package. dpkg will override the old version before installing the new one. However, since the installation directoy reflects the version (intentionally!), you find all settings in the data subdirectory of the old version's installation directory. See »Restoring Omada Controller settings« below.
- On my RasPi the start of the controller needs up to 61 seconds. You might want to increase the standard time-out (70 sec.) for starting the controller if it needs more time on your RasPi (time depends on other active processes during the start). To change the default time-out, use omadactl -S num, where num is the new time-out in seconds. This command will store the new time-out permanently in omadactl's config file and exits immediately (without starting Omada Controller).
Restoring Omada Controller settings
There is an easy way to restore your controller's settings using omadactl. Let's say you want to update Omada Controller 3.2.4 to 3.2.6. The directory OmadaController-3.2.4 will be cleaned by dpkg before it installs the new version in a new directory OmadaController-3.2.6. However, user files will be retained (dpkg prints warnings about which directories are not removed). Now stop the new controller using omadactl and use omadactl with the copydb command:
omadactl -w stop
omadactl copydb OmadaController-3.2.4 OmadaController-3.2.6
This will copy all settings under the data subdirectory from the old version to the new version. Restart the controller and you will see all your EAPs, settings, maps etc. If everything works, you can safely remove the old directory using rm -rf OmadaController-3.2.4.
Keep in mind that under Rasbian, which still is a 32-bit OS for compatibility with older Pis, mongodb has a 2GB limit for the size of the database. You could compile a 64-bit kernel / userland programs to get rid of this limit.
If Omada Controller doesn't start automatically on reboot of the RasPi, check with systemctl whether the omadad.service is enabled.
Omada Controller on RasPi is slooooooow, especially if initializing the environment at the first start. Start it with omadactl -W 240, note the time it needs to start (omadactl will print a message) and set the time + a 10 seconds reserve using omadactl -S num, where num is the new time-out in seconds (see the manpage).
For help with omadactl see its manpage attached to this post or use the command: man omadactl
For customization of omadactl see the config file /etc/default/omada.
For selection of the correct JRE and the starting method for the controller (either jsvc or standard Unix/Linux daemonizers) see file CONFIG in /opt/tplink/OmadaController.
For a list of all files installed by the .deb package use the command: dpkg -L omada-controller
If you want to uninstall this .deb package (except the database and other files created at run-time), use the »remove« option of dpkg: dpkg -r omada-controller
If you want to uninstall this .deb package (including the database and other files created at run-time), use the »purge« option of dpkg: dpkg -P omada-controller
Release notes for Omada controller version 3.2.6
New features/enhancements by TP-Link:
- Change the mechanism that when adopting an EAP, the Controller will retain the IP configuration of EAP in Standalone mode.
- Change the mechanism that multiple Omada Controllers can run on the same subnet.
- Added a checkbox »Start Omada Controller after installation?« (enabled by default).
- Extend the Max Associated Clients in Load Balance menu to 255.
- Optimized the Channel Utilization UI.
- Optimized the authentication page of portal.
- Optimized portal UI to disable the "Apply" button while uploading a photo.
Bugs Fixed by TP-Link:
- Fixed the bug that the page of MAC filter might not display all groups when there are more than 5 groups.
- Fixed the bug that after deleting a site, the voucher code and local user of this site still exist.
- Fixed the bug that the site configuration will fail to restore when the imported site contains same voucher code as the current controller.
- Fixed the bug when a mesh AP is powered off during upgrade, the controller may fail to upgrade other APs with prompt message »Other APs are upgrading?«.