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.192788
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

« First ‹ Previous 1 .. 3 4 5 6 7 8

Inxsible commented on 2022-03-20 22:34 (UTC)

I have adopted and updated this package to the latest version - 5.0.30.

schard commented on 2021-12-14 13:56 (UTC)

This line of Omada controllers is affected by CVE-2021-44228. Do not use this package!

$ ls /opt/omada-controller/lib/log4j*
/opt/omada-controller/lib/log4j-api-2.8.2.jar  /opt/omada-controller/lib/log4j-core-2.8.2.jar  /opt/omada-controller/lib/log4j-slf4j-impl-2.8.2.jar

thylacine222 commented on 2021-05-07 05:15 (UTC)

FYI, have created a PKGBUILD for the SDN version here: https://aur.archlinux.org/packages/omada-sdn-controller/

Inxsible commented on 2021-01-12 21:41 (UTC)

Fair enough. I just wanted to confirm before I upload a new version for v4.2.4 as the PKGBUILD would pretty much be a copy of yours.

schard commented on 2021-01-12 21:37 (UTC)

@Inxsible as noted in the pinned comment, this is a package fro the legacy EAP controller, not the newer SDN controller. Why? Because this is what I use. If you want the SDN version, nobody is stopping you from packaging it.

Inxsible commented on 2021-01-12 21:34 (UTC)

Any reason why you haven't updated to the latest v4.2.4? I understand that it would require a firmware update on the AP, so maybe you can have this stay at 3.2.14 and also upload another package for v4.2.4?