LittleNo wrote

where do I set that? I only found one checkbox to enable band steering

Just tried EAP Controller on an embedded system and noticed that it needs ages to start. On a 1 GHz 64-bit AMD system I had lying around EAPC needs 2m 18s for startup. On RaspberryPi 3B it needs around 2m 4s. Thus, in order to get a meaningful message for a successful server start from tpeap -w start, you will need to increase the WAIT_TIME according to the real time your system needs for the start of EAPC.

Note that if a time-out occurs in tpeap, the EAP Controller might nevertheless be started successful some seconds after the time-out. This is caused because the server need to run in the background, so tpeap needs to check for a successful start by polling the web UI (that's what the portt script is for) until it eventually times out after WAIT_TIME seconds have passed.

Long story short: if you run the EAP Controller on an embedded or other slow platform, change line 48 in tpeap from:
   WAIT_TIME=90
to something like:
   WAIT_TIME=180
or even a higher value if tpeap still times out.

The remainder of the original posting has become irrelevant meanwhile in new improved tpeap v1.1, see the post #26 below.

A new version of the tpeap start script for starting the Omada EAP Controller has been released. This new version can be used on different platforms such as x86_64, x86_32 and ARM systems with almost no changes to the script.

New features:

1. Better error indication on headless systems: if a second EAP Controller already runs in the same network, the error message from tpeap clearly states that in the error message. No more searching in the server's log file needed. The error message looks like:

Start failed - found other Omada Controller started at host 192.168.1.20, going to stop

2. Fixed kind of a "dead-lock": If EAP Controller #1 terminates because of another Controller #2 is running elsewhere in the network, #1 forgets to stop the mongo database server. Thus, if EAP Controller #2 is terminated and #1 is started again, the start will fail because now a mongod is still listening on port 27017. Therefore, tpeap now terminates mongod if it detects that EAPC #1 did exit because of another EAP Controller running in the same network.

3. Logging: message about starting and stopping the EAP Controller are now in file startup.log, file stop.log is gone. The file server.log will be created as a new file on every start - this is needed to make the above feature 1 work.

4. The portt binary from TP-Link is replaced by a portable script to get rid of dependencies to a certain processor architecture. tpeap can now be used on any Linux platform to start EAP Controller.

5. Likewise, the Java JRE 7 embedded in the EAP Controller distribution from TP-Link isn't needed on certain platforms such as the RasberryPi running Raspbian, which comes with Oracle's official JRE 8 pre-installed.

6. The mongo database service embedded in the EAP Controller distribution can be replaced also by a native package from the repositories on almost any Linux platform.

7. By removing dependencies to a processor architecture as outlined in 4, 5 and 6, the EAP Controller can be used on any Linux platform. Another advantage of above features supported by tpeap beside the platform-independence is a better support of security fixes in official Java and mongodb distributions.

Download the new version (read first!):

- If you have EAP Controller 2.6.1 installed already, please save me some bandwidth (I pay for it!) and just download the single archive tpeap-1.1. Create a directory (for example eapc) change into it, download the TAR archive and extract it:

$ mkdir eapc
$ cd eapc
$ ftp ftp.rent-a-guru.de
...220 ftp.rent-a-guru.de FTP server ready.
Name (ftp.rent-a-guru.de:username): ftp
331 Anonymous login ok, send your complete email address as your password.
Password: yourmail
...
ftp> cd /private
ftp> get tpeap-1.1.tar.gz
...
7179 bytes received in 0.04 secs (174.8969 kB/s)
ftp> quit

Check the SHA256 sum!
$ sha256sum -b tpeap-1.1.tar.gz
3b2886d0d77106df0a103990df984f88efb152fbcd80a151c36301d2505cafd7 *tpeap-1.1.tar.gz

$ su
Password: yourpw
# tar xzvf tpeap-1.1.tar.gz
...

Now see the README.x86_64 for 64 bit x86 or the README.arm for other platforms to learn about the new features. Then install tpeap and portt in your existing EAP Controller bin directory.

- If you need to download EAP Controller 2.6.1, you don't need to download tpeap-1.1. It is already included in the archive. Create a directory (for example eapc) change into it and download the TAR archive. DO NOT extract it after download - just extract the READMEs and read them first for further instructions:

$ mkdir eapc
$ cd eapc
$ ftp ftp.rent-a-guru.de
...
220 ftp.rent-a-guru.de FTP server ready.
Name (ftp.rent-a-guru.de:username): ftp
331 Anonymous login ok, send your complete email address as your password.
Password: yourmail
...
ftp> cd /private
ftp> get eapc-2.6.1.tar.gz
...
7179 bytes received in 0.04 secs (174.8969 kB/s)
ftp> quit

Check the SHA256 sum!
$ sha256sum -b eapc-2.6.1.tar.gz
8761cd203ba2af53fb5dcf4dc74cc6899db1b3031d2c722ad067957dfa477289 *eapc-2.6.1.tar.gz

$ tar xzvf eapc-2.6.1.tar.gz README.x86_64 README.arm
...

Follow the instructions in the README.x86_64 for 64 bit x86 or the README.arm for other platforms.

Have fun!

speckone wrote

I just migrated over to your port. It's working great so far! Thank you so much!

I moved over my data directory from a 2.4.8 instance and it worked without any issues (that I know of). Great work! TP-Link should cut you a check! :D

theyort wrote

Thank you very much !
it work like a charm, really nice job.

You're welcome. Thanks for feedback! Now four instances have been reported to work fine.

StephenR0 wrote

For some reason, the US download of the EAP Controller for Windows is version 2.6.0 and the UK version is 2.6.1. Does anyone know if there's some good reason for this difference?