Business Community > Routers > ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
< Routers

Early Access ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)

12

Early Access ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)

Early AccessER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-20 08:05:31 - last edited 2024-05-20 09:13:13
Tags: #Firmware Update
Model: ER7212PC  
Hardware Version: V1
Firmware Version: 1.2.0 Build 20240517 (Beta)

This Article Applies to:

 

ER7212PC(UN) V1 1.2.0_Build 20240517 (Beta)

 

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 support for adoption of 20 EAPs.

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

 7. Expanded Device Support: Added support for wireless router ER706W and ER706W-4G. 

8. Facebook Wi-Fi Removal: Due to changes implemented by Facebook, the Facebook Wi-Fi function has been removed.

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

 

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)

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:

 

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]

 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  3      
 
  3      
 
#1
Options
19 Reply
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-20 18:29:32

  @Clive_A Updated and no obvious issues yet

 

When will scheduled AI WLAN Optimization return? Message shown is "Notice: Sorry, this function is temporarily offline. It will return online after further optimization. Please pay attention to subsequent version updates. Optimization schedule settings (if any) will be lost. You can initiate WLAN Optimization manually."
 

  0  
  0  
#2
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-21 00:56:18

Hi @GoodOmens 

Thanks for posting in our business forum.

GoodOmens wrote

  @Clive_A Updated and no obvious issues yet

 

When will scheduled AI WLAN Optimization return? Message shown is "Notice: Sorry, this function is temporarily offline. It will return online after further optimization. Please pay attention to subsequent version updates. Optimization schedule settings (if any) will be lost. You can initiate WLAN Optimization manually."
 

There is no ETA for this feature. Please pay attention to the future beta/firmware update.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  1  
  1  
#3
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-21 12:22:19 - last edited 2024-05-21 12:24:28

  @Clive_A 

 

I noticed if you assigned a PIV to a port other then 1 the device becomes unreachable from other devices and seems to not pass internet traffic.

 

Have my Hue Hub and Lutron hub plugged directly into the router assigned a PIV of 30 (my IoT network). They stopped responding after the update. IP was unpingable even from the 30 VLAN. Their respective cloud network showed them as offline. The cloud controller showed them as havng a 192.168.30.x IP address.

 

My network is simple (1,20,30) and other devices on the 30 lan are pingable from the main 1 lan. Switching back the device to the 1 LAN resolved the issue and device is reachable / can get traffic from the internet.

 

Both devices have 100mbit Ethernet ports so unsure if that's part of the bug. Haven't tried a gigabit device.

  0  
  0  
#4
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-21 20:32:16 - last edited 2024-05-21 20:33:08

  @Clive_A So switching the PVID back to 30 worked as expected.

 

Maybe it was a bug from the update or restoring from a backup settings I had did but it's working as expected. SImply changing the PVID for that port from 30->1->30 allowed the device to be reachable again.

  0  
  0  
#5
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-22 00:55:51

Hi @GoodOmens 

Thanks for posting in our business forum.

GoodOmens wrote

  @Clive_A 

 

I noticed if you assigned a PIV to a port other then 1 the device becomes unreachable from other devices and seems to not pass internet traffic.

 

Have my Hue Hub and Lutron hub plugged directly into the router assigned a PIV of 30 (my IoT network). They stopped responding after the update. IP was unpingable even from the 30 VLAN. Their respective cloud network showed them as offline. The cloud controller showed them as havng a 192.168.30.x IP address.

 

My network is simple (1,20,30) and other devices on the 30 lan are pingable from the main 1 lan. Switching back the device to the 1 LAN resolved the issue and device is reachable / can get traffic from the internet.

 

Both devices have 100mbit Ethernet ports so unsure if that's part of the bug. Haven't tried a gigabit device.

So, based on what you described, you've looked at the LAN interface and found out nothing wrong with that part.

What was the PVID before?

Here's a known thing we have all the ports marked as tagged. Unlike other models in standalone, you have the option to change the ports to untagged. It forces to be tagged in controller mode. It should not hurt anything in your situation.

 

Read your other comments that it is resolved after you changed it twice.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  1  
  1  
#6
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-22 15:41:12

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

  1  
  1  
#7
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-22 16:12:08 - last edited 2024-05-22 16:14:21

I updated to the Beta version on ER7212PC v1.0 so now the controller version is 5.14.0.33.

 

Which is high version number than 5.13.22 (Linux) I love the DNS Proxy and DNS cache in 5.13.22.

I was hoping this update would provide the features like DNS Proxy and DNS cache in the Settings > Services tab.

 

Omada Controller v 5.13.22 (Linux)

 

 

ER7212PC v1.0 1.2.0 Build 20240517 Rel.10671 Controller 5.14.0.33

 

 

  1  
  1  
#8
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-23 03:14:16

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.

Noted. Will check this with the test team.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  2  
  2  
#9
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-23 03:15:51

Hi @YuukiA 

Thanks for posting in our business forum.

YuukiA wrote

I updated to the Beta version on ER7212PC v1.0 so now the controller version is 5.14.0.33.

 

Which is high version number than 5.13.22 (Linux) I love the DNS Proxy and DNS cache in 5.13.22.

I was hoping this update would provide the features like DNS Proxy and DNS cache in the Settings > Services tab.

 

Omada Controller v 5.13.22 (Linux)

 

 

 

ER7212PC v1.0 1.2.0 Build 20240517 Rel.10671 Controller 5.14.0.33

 

 

 

Noted. Thanks for your feedback on this. Have recorded your request.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  1  
  1  
#10
Options
Re:ER7212PC V1_1.2.0_Build 20240517 Beta for Omada Controller V5.14 (Released on May 20th, 2024)
2024-05-23 08:28:01 - last edited 2024-05-23 08:28:56

I've spotted the same issue. I was really looking forward these DNS features

  1  
  1  
#11
Options
12

Information

Helpful: 3

Views: 1785

Replies: 19

Tags

Firmware Update
Related Articles
How to update Omada software on ER7212PC?
1367 1
ER7212PC - Omada Controller
1576 0
Port Mirroring in ER7212PC V1_1.0.4_Build 20230724 Beta Firmware
901 0
ER7212PC firmware not to date
599 0
Will ER7212PC update with IDS/IPS?
271 1
Expected Firmware Release for ER7212PC Router
471 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.