Omada Controller 3.2.6 has been released.
Dear friends,
We are glad to share you that we have published Omada Controller 3.2.6 (same as OC200 3.2.5), which is optimized based on the previous 3.2.4, and fixed some bugs.
The most important feature of this version the change of mechanism. With this version, when adopting an EAP, the Controller will retain the IP configuration of EAP in Standalone mode. (In older versions, all configuration of the EAP in Standalone will be reset when the AP is adopted by the Omada Controller.)
Note: The Controller will retain the IP configuration of EAP in Standalone mode only when we upgrade the firmware of EAP to corresponding version. The firmware should be released these days.
For more inforation about Controller 3.2.6, please refer to the following release note:
New Feature/Enhancement:
1. Change the mechanism that when adopting an EAP, the Controller will retain the IP configuration of EAP in Standalone mode.
2. Change the mechanism that multiple Omada Controllers can run on the same subnet.
3. Add the button of “Start Omada Controller after installation” and check it by default.
4. Extend the Max Associated Clients in Load Balance to 255.
5. Optimize the UI of Channel Utilization.
6. Optimize the authentication page of portal.
7. Optimize the UI of the portal that you cannot click Apply when you are uploading a photo.
Bug Fixed:
1. Fixed the bug that the page of MAC filter may not display all groups when there are more than 5 groups.
2. Fixed the bug that after deleting a site, the Voucher code and Local user of this site still exist.
3. Fixed the bug that the site configuration will fail to restore when the imported site contains same Voucher code as the current Controller.
4. Fixed the bug that when mesh AP is powered off during upgrade, Controller may fail to upgrade other APs, with a prompt message “Other APs are upgrading”.
Notes:
1. To use Omada Controller 3.2.X new features, you need to upgrade your EAP's firmware to the corresponding version.
2. Once upgraded to this version of Omada Controller, you will NOT able to downgrade to an earlier version.
3. Portal configuration will be lost after upgraded to Omada Controller 3.2.X from 2.4.X or earlier version.
We don't recommend you to use Controller 3.2.6 to manage the EAP220.
We can see the models in the bundled firmware.
Hello forrest,
I just got a call from one of our customers who needed to adopt a new EAP into an existing OC200 running Omada controller 3.2.5 inside a management VLAN. So, what would be better opportunity to test the new feature of EAP firmware with setting a static IP for the EAP directly via the web UI to prepare for adoption by Omada controller.
It can work, but only if one knows the trick. However, I did note that the customer had problems with following three steps of the procedure:
- The web UI setup wizard of EAP forbids to set the new login credentials to »admin/admin« after logging in the first time. Thus, adopting with OC200 later will fail and one has to retry with the password assigned in the web UI. It works, but is a bit inconvenient for IT-unsafe people in my opinion. I suggest to let users choose »admin« as the new password in the web UI for easy adoption by OC200 later.
- The web UI wizard demands to set a SSID before one can reach the »Management« page. I suggest to add a button »Skip« which allows to skip this step as it can be done in Omada controller.
- The EAP uses the static IP set through the web UI to connect to the OC200. When it is adopted and being configured, OC200 sets the EAP's IP back to default 192.168.0.254 again (since it is the default setting for a new EAP in OC200 which can't be changed unless the EAP is in Provisioning state). Please see screenshots below.
So, correct me if I'm wrong, but it seems that OC200 v1.2.1 aka controller v3.2.5 does not retain the IP set in standalone mode over Configuring state after adoption.
What does work: set a static IP in EAP standalone mode (so it changes immediately) or set fallback IP (and reboot), adopt the EAP (fails due to password, see 1.), retry adoption with the new passwort, now really quickly change the EAP DHCP fallback IP in OC200 configuration as soon as the EAP is in »Provisioning« state, but before it gets finally configured by OC200.
I could get it working this way, but our customer still not.
Screenshots:
Set static IP 192.168.1.142 in EAP:
Adoppending EAP, changes state to provisioning:
Changes to state Configuring, but now gets configured back to 192.168.0.254 and gets disconnected:
Logfile:
Now if you forget the EAP, it gets in a pretty weird state: EAP is forgotten, has now default IP 192.168.0.254 again (set by OC200), but device password is still the one configured by the controller. So you need to login using the device password, reset EAP to standalone mode, and retry the whole procedure again.
Suggestions:
– Overwrite default IP setting in Omada controller using the IP learned from EAP during Pending state when it is adopted.
– Or allow to pre-define default values in OC200 config such as the default IP/network settings for EAPs not yet adopted. Could be a side-wide setting.
- Or allow adoption by defining the MAC address and IP of a specific EAP in Omada controller.
Hope this feedback is useful for you.
We don't recommend you to use Controller 3.2.6 to manage the EAP220.
We can see the models in the bundled firmware.
