Package Details: omada-controller 5.14.32.3-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://www.tp-link.com/us/support/download/omada-software-controller/#Controller_Software
Licenses: custom
Conflicts: omada-sdn-controller
Submitter: schard
Maintainer: Inxsible
Last Packager: Inxsible
Votes: 6
Popularity: 0.002775
First Submitted: 2020-02-06 18:14 (UTC)
Last Updated: 2024-11-05 00:04 (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 .. 8 Next › Last »

mylux commented on 2024-11-05 01:17 (UTC)

@Inxsible, yes, it works! My VPN client was blocking my connection and I didn´t notice

Inxsible commented on 2024-11-05 01:14 (UTC)

@mylux, yes it worked for me. I am running 5.14.32.3 currently

mylux commented on 2024-11-05 01:11 (UTC) (edited on 2024-11-05 01:17 (UTC) by mylux)

@Inxsible, did the upgrade work for you? The service starts, but with a bunch of error messages on the logs and no longer works after the upgrade

Nevermind, it works! My VPN client was blocking my connection

Inxsible commented on 2024-11-05 00:04 (UTC)

Updated to 5.14.32.3

Inxsible commented on 2024-10-19 16:23 (UTC)

@mylux, yes, since I am depending on java-runtime=11, i think the webpage is not reflecting that. it just shows all versions. I could mandate jre11-openjdk but then users will have to install multiple java version if they also use a different version for some other program. I'll also have to update the omada-controller script to use java 11 instead of depending on the default -- as users could have a different default version of Java. I have Omada installed in a Proxmox Container which is only for Omada Controller, so I never have more than 1 service/programs in each container anyway.

mylux commented on 2024-10-19 01:34 (UTC)

@Inxsible, nevermind, I see that you have re-released fixing java version to 11. That is enough. I was tricked by the webpage that didn't update the java versions in the dependency

mylux commented on 2024-10-19 01:30 (UTC)

@Inxsible, that will work. I think I did basically the same to get it to work on my side. Thats why I suggested that we change the java version in the dependencies to 11, because if the end user selects another version for the runtime,such as jdk23, it will not work. Additionally, I don't imagine any good reason to allow the user to select a different java version if the functionality will be limited. Don't you think it's better?

Inxsible commented on 2024-10-18 14:03 (UTC)

@mylux, yes my previous backups were all made without using your PR. I have a nightly backup schedule to my nextcloud server from within Omada. I do see that something has changed since Sept 2024 -- previously all my backup cfgs were No Limit -- that is all data, but since Sept it is only backing up Settings. The cfg file sizes have reduced from ~300kb to ~13kb. So that's something I might have to look into again.

But I have switched to jre11-openjdk, but still using java-runtime as the dependency, instead of mandating jre11 package. Also Omada released a new version just yesterday, so I'll incorporate that as well.

Thanks for your PR. !

mylux commented on 2024-10-18 13:23 (UTC)

@Inxsible, Did your previous and non-working backups were made using a previous version of the Omada Controller? I remember having seen something regarding this no retro compatibility over those versions. Also, It's interesting to know that you had functional backups. I have never been able to make a restore working with Omada without the changes in the startup script, but I could generate the backup BTW. I don't remember testing if backups generated without the improvements in the startup script would be restored after fixing the script, though. I am glad that my PR helps and that you'll be re-releasing this package.