✶Update 09/2020✶ Omada Controller 3.2.10 for Debian, Raspbian and other Linux systems

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
191011...

✶Update 09/2020✶ Omada Controller 3.2.10 for Debian, Raspbian and other Linux systems

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
168 Reply
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-22 17:28:37 - last edited 2020-03-22 17:29:21

@karimkb, glad it works now. Yes, there might be changes in the v4 package name of mongodb and also options have been removed instead of just handling them as deprecated (which both is a pretty bad practice by the mongodb developers/package maintainers). Have fun with Omada controller!

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#112
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-25 19:04:12 - last edited 2020-03-25 23:07:31

@R1D2

Installed the Controller following your Guide in v3.2.6 but I'm having problems to start the Controller.

Raspberry Pi 3 Model B Rev 1.2, w is set to 300 (testing with 999 brings no succes)

 

I get following Output starting with sudo omadactl -w -v start

-------------------------------------------------------
! Executing tail -f, type ^C (interrupt) to terminate !
-------------------------------------------------------
Going to init controller!
Going to start controller!
startup...
Mär 22, 2020 12:58:18 AM org.hibernate.validator.internal.util.Version <clinit>
INFO: HV000001: Hibernate Validator 4.3.1.Final
Failed to start omada controller, going to exit
ShutdownHook: service stopped.
Service exit with a return value of 1
 

i'm a beginner and don't know how to fix the problem ..

Thx for your time and work

 

 

 

  0  
  0  
#113
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-25 22:11:43

@Knolay 

Knolay wrote

@R1D2

Installed the Controller following your Guide in v3.2.6 but I'm having problems to start the Controller.

w is set to 300

I get following Output starting with sudo omadactl -w -v start

-------------------------------------------------------
! Executing tail -f, type ^C (interrupt) to terminate !
-------------------------------------------------------

 

 

I have -w set to 999. Omada takes a long time to start on my Raspberry Pi Model B rev 2

  0  
  0  
#114
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-26 01:24:27

Knolay, first make sure that mongod is not running if started automatically during boot. Then make sure that Omada controller (the one that failed to start) is not running. Next, disable automatic start of mongod on system boot (see systemctl manpage on how to do so). Finally try again to start Omada controller using omadactl. As rockin wrote, use a big timeout value if running on older RasPi platforms.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#115
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-05 10:41:17 - last edited 2020-04-06 15:42:47

@R1D2  

 

To make it more easy I made a docker image around you deb file.  And you only need a full commands to get it running.

 

apt-get -f install docker.io

systemctl enable docker

systemctl start docker

echo "vm.swappiness = 5" >> /etc/sysctl.conf

echo "docker start omada-controller" >> /etc/rc.local

 

mkdir -p /opt/tplink/OmadaController/data
mkdir -p /opt/tplink/OmadaController/work
mkdir -p /opt/tplink/OmadaController/logs

groupadd -g 508 omadad
useradd -u 508 -g 508 -d /opt/tplink/OmadaController omadad

chown -R 508:508 /opt/tplink/OmadaController

omadadata="/opt/tplink/OmadaController/data"
omadawork="/opt/tplink/OmadaController/work"
omadalogs="/opt/tplink/OmadaController/logs"

docker run -d \
--name omada-controller \
-e TZ=Europe/Amsterdam \
-p 8088:8088   -p 8043:8043  \

-p 27001:27001/udp   -p 27002:27002   -p 29810:29810/udp \

-p 29811:29811   -p 29812:29812   -p 29813:29813  \
-v $omadadata:/opt/tplink/OmadaController/data   -v $omadawork:/opt/tplink/OmadaController/work  \

-v $omadalogs:/opt/tplink/OmadaController/logs ronaldo1965/omada-controller:3.2.6-1

 

Thats all.

 

You can also build it your self with by checking it out from git:

 https://github.com/ronald-den-otter/omada-controller

 

There is no support on it. But it works great!

Because omada-controller is heave weight for a Pi3 don't run much more on it.

  0  
  0  
#116
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-05 11:35:22

Hello Ronald1965,

 

thanks very much. That's definitely helpful for many users.

 

However, we don't use docker here (company policy). So please have an eye on future new deb-packages if you want to keep the docker image of Omada controlelr up-to-date.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#117
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-05 12:52:33 - last edited 2020-04-05 13:18:29

@R1D2 It tells me there is no omada-controller_3.2.6-1_all.deb file, doign a update?
never mind.. my bad.. forgot to cd /private ;)

  0  
  0  
#118
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-05 13:33:02

Been using the Omada Controller in a container and it's been working fine except, I couldn't adopt newly installed Access Points - I had to adopt them "locally" using Omada Controller on my computer then export them. Not the best solution I'm afraid. 

 

1- Can the "cloud" controller adopt newly installed AP (a la Ubiquiti) ? 

2- Can we move AP from Site to Site ? because it came to Default Site and everything was reset (names, radio channel etc...) 

 

Thanks :) 

 

 

  0  
  0  
#119
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-05 13:42:02 - last edited 2020-04-05 13:52:32

 

MichaelJTDesign wrote

1- Can the "cloud" controller adopt newly installed AP (a la Ubiquiti) ?  

 

The TP-Link cloud just connects you to the »real« Omada controller, that's either a software controller or an OC200 running elsewhere, e.g. behind a firewall of some local network.

 

But if you deploy an Omada SW controller directly in the cloud instance (or on any public Internet server), you don't need the TP-Link cloud to connect to the controller and it can be used to manage EAPs in several different networks. For example, we still manage plenty of our customer's EAPs through an Omada controller running on our public Internet server.

 

2- Can we move AP from Site to Site ? because it came to Default Site and everything was reset (names, radio channel etc...) 

 

Yes, moving EAPs from site to site in the same Omada controller is possible since first version of the software. See »Access PointsAction«:

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#120
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-05 14:20:41
But if you deploy an Omada SW controller directly in the cloud instance (or on any public Internet server), you don't need the TP-Link cloud to connect to the controller and it can be used to manage EAPs in several different networks. For example, we still manage plenty of our customer's EAPs through an Omada controller running on our public Internet server. Exactly what I meant - on internet. There's a confusion for the term cloud controller here, my bad. By cloud controller you mean TP Link Omada Cloud, I meant self hosted controller on internet accessible server :) Thank you very much for your feedback.
  0  
  0  
#121
Options