Package Details: omada-controller 5.15.20.18-1

Git Clone URL: https://aur.archlinux.org/omada-controller.git (read-only, click to copy)
Package Base: omada-controller
Description: Omada SDN Controller
Upstream URL: https://support.omadanetworks.com/us/product/omada-software-controller/?resourceType=download
Licenses: custom
Conflicts: omada-sdn-controller
Submitter: schard
Maintainer: Inxsible
Last Packager: Inxsible
Votes: 7
Popularity: 0.130738
First Submitted: 2020-02-06 18:14 (UTC)
Last Updated: 2025-04-04 20:47 (UTC)

Dependencies (6)

Required by (0)

Sources (2)

Pinned Comments

Inxsible commented on 2023-12-01 15:01 (UTC) (edited on 2023-12-01 15:07 (UTC) by Inxsible)

@teJECSke Please stop flagging this package as out of date unless a new version is available on the link marked as Upstream URL on this page !!!

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

mylux commented on 2025-04-21 02:43 (UTC)

@Inxsible, did not test! Actually, I am always a little afraid to change what's been working, but as soon as I have I chance I will try to test this and let you know.

Inxsible commented on 2025-04-15 19:53 (UTC)

@mylux, did you try it with mongodb version other than 4.4 ? I seem to be having issues with any version of mongodb except 4.4

mylux commented on 2025-04-15 15:13 (UTC)

@kleptophobiac, yes, that are some ways of doing those, it really depends on what you want to do specifically. If you don't care about setting the java environment on your entire system, you can: - 1 Create a symlink to the directory where your java binary is to the version you want. - 2 Use a tool like sdkman to set the desired java version to your PATH

If you don't, then you can edit bin/control.sh file on line 25 and put there the path to the java installation you want.

kleptophobiac commented on 2025-04-15 14:45 (UTC)

Is there a good way to direct the service which JDK to use? I appear to have more than one installed, and it's trying to run with JDK 11 rather than JDK 17.

Inxsible commented on 2025-04-04 20:52 (UTC) (edited on 2025-04-04 20:53 (UTC) by Inxsible)

upgraded to v5.15.20.18 and Java 17. I checked the backup & restore and it seems to be working as expected. However, have any of you been able to use mongodb 7 or 8 with the newer versions? If I use anything but mongodb 4.4, the omada package compiles and builds, but then fails to run. I tested the following combinations: 5.15.8.2 with Java 11 and MongoDB 7, 5.15.8.2 with Java 17 and MongoDB 7, 5.15.20.18 with Java 17 and MongoDB 7, 5.15.20.18 with Java 17 and MongoDB 8.

They all failed. However, 5.15.8.2 with Java 11 and MongoDB 4.4 and 5.15.20.18 with Java 17 and MongoDB 4.4 are the only ones that work for me

Inxsible commented on 2025-04-02 00:17 (UTC)

updated to 5.15.8.2 using jdk11 and mongodb upto version 7.

Waiting for the tar.gz version for 5.15.20.18. However this version no longer supports jdk below 17 -- so the restore function may or may not work after updating to 5.15.20.18. Also it supports mongodb 8

dcelasun commented on 2025-02-06 13:49 (UTC)

As of 5.14.20, Omada supports MongoDB 7. Please update the dependency.

kleptophobiac commented on 2025-01-25 16:24 (UTC)

Note that this package does not build if you do not already have user:group omada:omada

Inxsible commented on 2025-01-07 17:13 (UTC) (edited on 2025-01-07 17:14 (UTC) by Inxsible)

Upgraded to 5.15.6.7. Seems TP Link also updated their webpages. I have changed the upstream url with this release as well to point to the new download page.

mylux commented on 2025-01-02 17:28 (UTC)

@Inxsible, there is a new version available here: https://support.omadanetworks.com/en/product/omada-software-controller/?resourceType=download

I know it is not exactly the same as the upstream URL, but for some strange reason the US page does not show the latest version from December 12th.

Would you mind updating it?

1 2 3 4 5 6 .. 9 Next › Last »