Hello,

I am running the Omada SDN Controller 5.13.22_linux_x64 on Red Hat Enterprise Linux 9.3.

Omada SDN software does not start automatically after system reboot. It must be started manually.

This is because the Omada SDN Controller software doesn't provide a Systemd service file, it only provides a System V init.d file.

Enterprise Linux switched to Systemd since version 8 (many years ago.) This means that init.d service files are long since deprecated and not used anymore without extra manual adjustment which is not supported by Red Hat.

I should add that this forum is not a place to get into the pro and crontra of Systemd vs. init.d--it doesn't matter! Use whatever you like. However the reality is that many many Linux distributions have long since switched to Systemd, not just RHEL. For example Debian, Ubuntu, CentOS, Fedora, and more use Systemd.

A plea to tp-link: Please add Systemd support to Omada SDN for Linux to also support these most popular (by usage) Linux distributions.

Thnx.

PS. Maybe there is a beta or a self-made unit file that someone wants to share. =)