Beta Software ER7212PC V1_1.2.0_Build 20240705 Beta for Omada Controller V5.14 (Updated on Jul 19th, 2024)
This Article Applies to:
ER7212PC(UN) V1 1.2.0_Build 20240517 (Beta) (May 20th, 2024)
ER7212PC(UN) V1 1.2.0_Build 20240705 (Beta) (Jul 9th, 2024)
ER7212PC(UN) V1 1.2.0_Build 20240716 (Beta) (Jul 19th, 2024)
Release Notes:
Supported device models and firmware
- EAP
EAP783, EAP773
EAP690E HD, EAP683 LR, EAP680, EAP673, EAP670, EAP660 HD
EAP655-Wall, EAP653, EAP650-Outdoor, EAP650-Wall, EAP650, EAP620 HD
EAP615-Wall, EAP615-Wall, EAP613, EAP610-Outdoor, EAP610
EAP265 HD, EAP235-Wall, EAP230-Wall, EAP225-Outdoor, EAP223
EAP215-Bridge KIT, EAP211-Bridge KIT
EAP115-Bridge KIT, EAP115-Wall, EAP113-Outdoor
EAP245 V3, EAP225 V3, EAP225-Wall V2, and above versions
EAP115 V4, EAP110 V4, EAP110-Outdoor V3, and above versions
- Switch
SX6632YF SG6428X, SG6428XHP, SG6654X, SG6654XHP
SG3218XP-M2, SG3210X-M2, SG3210XHP-M2
SX3016F, SX3008F, SX3206HPP
SG3452XP, SG3452X, SG3452P, SG3452
SG3428X-M2, SG3428XPP-M2
SG3428XMP, SG3428XF, SG3428X, TL-SG3428X-UPS
SG3428MP, SG3428, SG3210XHP-M2
SG2428P, SG2218P, SG2218, SG2016P, SG2210MP, SG2008P, SG2005P-PD
SG3210 V3, SG2210P V3.2, SG2008 V3, SL2428P V4, and above versions
- Gateway
ER8411
ER7206 V1 (TL-ER7206 V1) and V2, ER707-M2, ER706W-4G, ER706W
ER605W, ER605 V1 (TL-R605 V1) and V2
New Features & Enhancements:
1. Added the Tools page to the Site view, containing the following tools.
- Network Check. Select an Omada device and perform a ping or traceroute test to check the network connectivity.
- Packet Capture. Select an Omada EAP, set the capture filter, and perform a packet capture for troubleshooting. Omada Controller uses TCP port 29815 to download the packets.
- Terminal. Select an Omada device, open Terminal, and then you can execute CLI or Shell commands. Omada Controller uses TCP port 29816 to create remote control terminal sessions with the devices.
2. Optimized the network topology function.
3. Added the "Lock to AP" feature. Open a client's Properties window, go to Config, enable the function, and select one or multiple EAPs, then the client will be locked to the selected EAPs. This feature helps prevent a static client from roaming frequently between multiple EAPs and requires new firmware updates for Omada EAPs.
4. Expanded more Language Support, see Global View--->Settings--->Controller Settings--->Languagefor details.
5. Added the "SSID Rate Limit" feature. Bandwidth is shared among all clients connected to the same wireless band of the same EAP. This feature requires new firmware updates for Omada EAPs, and the rate limit settings will only take effect on those EAPs running firmware that supports the feature.
6. Expanded Device Support: Added support for wireless router ER706W and ER706W-4G.
7. Facebook Wi-Fi Removal: Due to changes implemented by Facebook, the Facebook Wi-Fi function has been removed.
8. AI WLAN optimization: Improved algorithm and interaction for better optimization results.
Bug Fixed:
1. Fixed the bug that when disabling the PoE function of a port, and PoE is enabled again after rebooting the device.
2. Fixed the bug of not being able to restore backups in some cases.
3. Fixed bug with displaying unknown IP addresses on cloud portal.
4. Fixed some known issues and bugs. (Build 20240716 is based on Build 20240705)
Firmware Download:
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
(2) You may follow the following guide to upgrade your Omada devices. How to Upgrade/Downgrade Omada Gateways
Firmware Download Link
ER7212PC(UN) V1_1.2.0_Build 20240517 (Beta)
ER7212PC(UN) V1_1.2.0_Build 20240705 (Beta)
ER7212PC(UN) V1_1.2.0_Build 20240716 (Beta)
Notes:
(1) The above firmware is applied to ER7212PC(UN) V1/1.6.
(2) Your device’s configuration won’t be lost after upgrading.
(3) This version of the controller is fully applied to the Omada APP of version 4.3.X or above.
(4) Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
If somehow you encounter an issue during or after the upgrade, it's suggested to contact us with the following info:
- Omada Controller version
- Device Firmware version with Build number (previous and current)
If your router gets bricked during the firmware upgrade, you may follow the guide below to recover the firmware.
How to use the Emergency Mode to recover the firmware for Omada Gateways
Update Log:
Jul 19th, 2024:
Build 20240716 was released.
Update the download link and release note.
Jul 10th, 2024:
Update the release note.
Jul 9th, 2024:
Build 20240705 was released.
May 20th, 2024:
Release of this post.
Recommended Threads:
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada Router Related Issues [Actively Updated, Post for Subscription]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @GoodOmens
Thanks for posting in our business forum.
GoodOmens wrote
@Clive_A Correct ... The 30 LAN interface was working for all other devices on the network, some on a SG 2008 switch (THough those were tagged with the profile) and others through the WiFi APs (Via tagging the SSID). Going into the update I had the port (11 and 12) tagged at PVID 30 (all others as 1). After the update those were the only devices unreachable out of my 30+ devices (A mix of three LAN interfaces, 1, 20, 30).
Between the update and noticing the device was unreachable I had performed a restore of settings from a backup that was done on ER7212PC 1.1.3 Build 20240403 and back to a config that was saved from V1_1.2.0_Build 20240517 (I had saved a backup just prior to restoring from the 1.1.3 version), so it was either the retoring the config backup or the update that caused the devices to be unreachable. As soon as I switched the PVID to 1 the device was reachable and it worked as expected when going back to the PVID 30 I wanted it on.
We cannot replicate the said issue. Can you please export the backup for us?
Will create a ticket for you. Please prepare your backup and login username and password.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A!
Any plans to increase the number of adopted switches to more than 2? 10 would be great!
- Copy Link
- Report Inappropriate Content
@Clive_A I am getting daily "[Failed]The controller failed to mail global logs to ********@gmail.com automatically."
SMTP is disabled under Server Settings (it's unchecked) ... is there another place to disable the emailing of logs? I can't find that setting anywhere.
"Alert emails" is checked under my user settings but the box is grayed out (I can't uncheck it) and it says to enable SMTP....
- Copy Link
- Report Inappropriate Content
Hi @GoodOmens
Thanks for posting in our business forum.
GoodOmens wrote
@Clive_A I am getting daily "[Failed]The controller failed to mail global logs to ********@gmail.com automatically."
SMTP is disabled under Server Settings (it's unchecked) ... is there another place to disable the emailing of logs? I can't find that setting anywhere.
"Alert emails" is checked under my user settings but the box is grayed out (I can't uncheck it) and it says to enable SMTP....
So, you've unchecked this one. Correct?
What about the Log > Notification > System? Do you uncheck these? Please paste a screenshot.
- Copy Link
- Report Inappropriate Content
@Clive_A That server setting shown in your SS was unchecked/ disabled at the time I was receiving the before mentioned errors.
Log > Notification > System did have some email settings checked (That I have unchecked). I'll report back if I continue to receive the error. You'd think that having the mail server disabled would prevent it from trying to send emails.
I don't recall ever checking anything under notification->system.
- Copy Link
- Report Inappropriate Content
Hi @GoodOmens
Thanks for posting in our business forum.
GoodOmens wrote
@Clive_A That server setting shown in your SS was unchecked/ disabled at the time I was receiving the before mentioned errors.
Log > Notification > System did have some email settings checked (That I have unchecked). I'll report back if I continue to receive the error. You'd think that having the mail server disabled would prevent it from trying to send emails.
I don't recall ever checking anything under notification->system.
Some settings are by default enabled with the new controller version. Esp the logs. In case people never take a look at those new added log recorders.
- Copy Link
- Report Inappropriate Content
Hi @GoodOmens
Thanks for posting in our business forum.
GoodOmens wrote
@Clive_A Correct ... The 30 LAN interface was working for all other devices on the network, some on a SG 2008 switch (THough those were tagged with the profile) and others through the WiFi APs (Via tagging the SSID). Going into the update I had the port (11 and 12) tagged at PVID 30 (all others as 1). After the update those were the only devices unreachable out of my 30+ devices (A mix of three LAN interfaces, 1, 20, 30).
Between the update and noticing the device was unreachable I had performed a restore of settings from a backup that was done on ER7212PC 1.1.3 Build 20240403 and back to a config that was saved from V1_1.2.0_Build 20240517 (I had saved a backup just prior to restoring from the 1.1.3 version), so it was either the retoring the config backup or the update that caused the devices to be unreachable. As soon as I switched the PVID to 1 the device was reachable and it worked as expected when going back to the PVID 30 I wanted it on.
Well, we cannot reproduce what you reported.
Can you show me a network diagram of your network? I also request a backup of your config.
Please zip your diagram picture and the backup file in one zip. And use your registered email address as the password to unzip your compressed file. Share the file here or share a link.
I also need a picture of how you configure the VLAN on the client end where you connect to PVID 30 port if you are connecting a switch or whatsoever.
- Copy Link
- Report Inappropriate Content
@mimi234 I meant @Clive and not Steve - sorry for that!
mimi234 wrote
Hi Steve! I managed to upgrade the firmware successfully. I'm still checking some issues with PPSK without Radius (i'm in touch with support), that I had with firmware 1.1.4 (users are now checking if the issue persists). I was really hoping that 5.14 will bring the embedded Radius Server (which I understand are available even in earlier versions) with Radius users (though understandably it would be with limited user base).
- Copy Link
- Report Inappropriate Content
@Clive_A Updated to the latest beta without issue.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 4688
Replies: 21