R1D2 wrote

Do not run the original Controller as root on a public server. Instead use the community version to run it with privilege separation (and yes, it will start after reboot if enabled as a service, while in the official release there is a long-standing bug preventing that).

See this post for latest version of EAP Controller v2.6.1 for Linux: https://forum.tp-link.com/showthread.php?106969-Omada-EAP-controller-for-Linux&p=240551&viewfull=1#post240551

I'm not running it as root, however I am running it as a privileged user with admin rights added to the sudo list. The version I'm running is 2.5.3. How do I run it as a service in linux and did you say there is a bug in version 2.5.3 with it loading on system start?

BTW, it's not a public server. It's sitting behind a router on a private network not serving except for the EAP controller. I also created an ACL policy rule to not allow any secondary SSIDs access to the entire subnet it resides on. Mainly for the guest network.

R1D2 wrote

If you grant the user administrative rights, the process runs with those rights, no matter wether you start it as root or using sudo.

I installed it per the instructions provided in the EAP Controller PDF as it indicated to use sudo. After doing so, I didn't set the permissions for users to execute the tpeap start/stop script. I left it as is after the installation. There are no other users on the workstation and the workstation won't have access to the internet except when I am ready to do updates. Forgive me, i'm not that well versed in Linux except for my years of experience in working with Raspberry Pi's. Should I be doing this differently in my setup. Can you give me a good reason why it's not a good idea to run it as a sudo user?

If you want to use portal pages in the guest network, you need to grant access to the system running EAPC also for guest users (at least to TCP port 8043).

Thank you for pointing that out. I will have to remember this if I decide to reconfigure the guest network to use portal authentification. At the moment I'm only using a WPA2/AES password for guests.

But if you prefer to run v2.5.3, you can do so.

I don't have to run v2.5.3 from the TPLink website, I just wanted to try it out and see how it runs on the workstation with Linux. This unit is only for a household and not a business.