✶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.
1101112...

✶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-04-06 15:40:41

@MichaelJTDesign 

MichaelJTDesign wrote

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 :) 

 

 

First all, you need to run the docker image locally. you can't put it in kubernetes or on a virtual server in cloud somewhere. Because he won't discover new devices.

Also I had the problem when I was exposing the ports mentioned to a local address on my intranet.  So for example: -p 192.168.1.254:8043:8043 instead of -p 8043:8043. It was correctly exposed, but the controller couldnt connect anymore.  So I left them like -p 8043:8043. Now I was able to adopt new Accesspoints. But haven't tested it on the latest version. I will check that. And drop one of my accesspoints to adopt is again. I earlier succeeded with a meshing eap225-outdook too.  Also in docker there is an option called --network=host. You might wanna add that option to docker run.  I haven't tried that yet, because it was working ok like this.

  0  
  0  
#122
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-06 16:04:18
Ok I did a Forget AP on both with and without --network host. And in both case after 2 or 3 minutes it came back on the pending list.
  0  
  0  
#123
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-06 16:49:33 - last edited 2020-04-06 16:55:04

 

Ronald1965 wrote

 

First all, you need to run the docker image locally. you can't put it in kubernetes or on a virtual server in cloud somewhere. Because he won't discover new devices.
 

 

You can link EAPs to the controller over Layer 3. If the controller in a docker container can be accessed from the local host, it can also be accessed from remote sites which can connect to the local host in any way. Only automatic discovery of EAPs is limited to the local subnet, but there are other ways to tell EAPs the IP of the controller: either by using the Discovery Utility or by using DHCP option 138 / CAPWAP in the remote network's DHCP server. See this FAQ for details using the CAPWAP method.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#124
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-04-12 18:10:38

@R1D2 What I did was, since everything was set up previously on a local controller, I've tried the site export. 

 

The import didn't work so well. I then fired the EAP Discover tool - what a blessing. It found all of my AP on my local network, I just then simply specified my Controller Hostname/IP address, credentials and voila ! 

 

Everything is now working on my dockerized container on a private server over the internet - life is a bliss...

 

 

  0  
  0  
#125
Options
Re:✶Update 04/2020✶ Omada Controller 3.2.9 for Debian, Raspbian and any other Linux system
2020-04-13 10:47:15

Update notification for new version of Omada Controller 3.2.9

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#128
Options
Re:✶Update 04/2020✶ Omada Controller 3.2.9 for Debian, Raspbian and any other Linux system
2020-04-14 17:12:15

@R1D2 I also updated the docker image to your new version 3.2.9-1.  Thanks for making again.  Tested and is running on my PI 3B+.

 

# docker pull ronaldo1965/omada-controller:3.2.9-1

  2  
  2  
#131
Options
Re:✶Update 04/2020✶ Omada Controller 3.2.9 for Debian, Raspbian and any other Linux system
2020-04-14 21:26:09

@Ronald1965, thank you very much!

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#132
Options
Re:✶Update 04/2020✶ Omada Controller 3.2.9 for Debian, Raspbian and any other Linux system
2020-04-19 01:23:02

docker container works a treat thanks!  Way easier than having to download oracle java etc.

 

Only issue is that from the mobile app i had to keep adding the controller manually as it would save the connect config with the internal docker ip (172.x.x.x instead of the actual network 10.x.x.x).  deleting the container and changing the run command to network="host" has fixed this.  My pi only runs this and pihole in docker containers and both have network=host and all seems fine.

 

Thanks again!

 

 

  0  
  0  
#133
Options
Re:✶Update 04/2020✶ Omada Controller 3.2.9 for Debian, Raspbian and any other Linux system
2020-04-29 22:10:35

@R1D2 I'm on 3.2.6 and I was going to upgrade to this version, but I noticed that 3.2.10 is now available. Are there any plans for a .deb version of 3.2.10 soon or should I go ahead and install 3.2.9?

  0  
  0  
#134
Options
Re:✶Update 04/2020✶ Omada Controller 3.2.9 for Debian, Raspbian and any other Linux system
2020-04-30 11:01:01

Hi saajid, I have just made a package of version 3.2.10, see first post.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#135
Options