Business Community > Controllers > Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
< Controllers

Early Access Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)

12

Early Access Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)

19 Reply
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Wednesday

Hi  @Vincent-TP, 

 

I just found an error here. This is version 6.1.0.11

 

  0  
  0  
#12
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Thursday

Hi  @black_azrael 

 

Thanks for the feedback.

This is forwarded to the relevant team.

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#13
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Friday

  @Vincent-TP 

 

Ran the upgrade to 6.1.0.11 earlier today...no problems to report (so far), but will report back after I've used the new Controller software for a few days (Windows 11 x64).

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v6.1.0.11 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gb
  1  
  1  
#14
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Friday - last edited Friday

Finally Gateway level LAN->LAN IP Group and Port ACLs

 

In the client page are these filterings correct? I have three VLANS, IoT, Guest, Default. Most things aren't tagged with what VLAN they are on:

 

 

As an alternative I can filter most things by their VLAN tag (e.g., 20, 30) except Default (1), which only shows one item. I have my Wireless devices set Default in WLAN settings. The list is probably missing 10-15+ devices (Like its missing all of my wireless devices)...

The only devices getting proper Network tags are via my main SG2210MP. Seems my 655-Wall are stripping that info out? As my other switch, a SG2008, is connected via a 655-Wall. Actually devices plugged into that switch show as connected to the 655-Wall...

  0  
  0  
#15
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Friday

Hi  @GoodOmens 

 

Thanks for the feedback. To understand the situation better, please let us know the following info:

1. Is the topology displaying correctly?

2. For those not displaying VLAN info, are they all plugged into the switch SG2008P? If not, how are they connected to the network? re they specific clients, or does this occur randomly across all clients?

3. Please share a screenshot of the device page.

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#16
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Friday - last edited Friday

  @Vincent-TP 

 

1. Almost. It doesn't display devices connected directly to Device #8 (Media Cabinet switch). It shows them connected to #4 (Family Room) or in one case as #4 connected to the POE switch. #4 is a Ethernet NIC plugged into the Media Cabinet. LLDP is enabled for Gateway, Switch, and EAP.


 

 

2. Devices not showing a Network tag are either connected wirelessly to EAP655-wall (On 1.6) or via the SG2008 plugged into a EAP655-wall (Via the PoE port)

3.

  0  
  0  
#17
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Saturday - last edited Saturday

  @Vincent-TP V6.1 is a massive leap forward, especially with the new Health Dashboards and Device Timelines. However, the new restriction on DHCP reservations outside the pool is a significant pain point for those of us managing critical infrastructure. We typically keep servers and static assets outside the dynamic range to avoid conflicts and maintain a clean subnet architecture. Please consider making this validation optional.
 

Additionally, since the UI is becoming so fluid and health-focused, it would be a game-changer to have a 'Critical Asset' toggle for specific clients. Being able to 'flag' a server or a NAS and receive an immediate alert if it goes offline would bridge the gap between simple networking and proactive monitoring. Keep up the great work!

 

Huemmer Santana | IT & Cybersecurity Director (CTO/CISO) @ TELEBA Serviços de Informática Ltda | Omada MSSP Partner | OCNA Wireless | Securing client ecosystems through Omada and cyber defense rigor.
  6  
  6  
#18
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Yesterday

Hi  @GoodOmens 

 

Thanks for the feedback. Please see the answer below:

GoodOmens wrote

Finally Gateway level LAN->LAN IP Group and Port ACLs

 

In the client page are these filterings correct? I have three VLANS, IoT, Guest, Default. Most things aren't tagged with what VLAN they are on:

 

 

>>>Network is not equal to VLAN, it's short for Network Name. The “SSID” column displays the network connections of wireless clients, while the “Network” column displays the network connections of wired clients. In other words, just as wired clients do not have SSID connections, wireless clients do not have a value for “Network.” Therefore, the current behavior is expected.

 

As an alternative I can filter most things by their VLAN tag (e.g., 20, 30) except Default (1), which only shows one item. I have my Wireless devices set Default in WLAN settings. The list is probably missing 10-15+ devices (Like its missing all of my wireless devices)...

>>>When WLAN is set to Default, the VLAN for wireless clients is Untag, not 1. Therefore, wireless clients cannot be found by searching for VLAN 1. This is also as expected.

 

The only devices getting proper Network tags are via my main SG2210MP. Seems my 655-Wall are stripping that info out? As my other switch, a SG2008, is connected via a 655-Wall. Actually devices plugged into that switch show as connected to the 655-Wall...

>>>This is because the SG2008 is plugged into the downlink port of the EAP655-wall. It's well noted and we will optimize it in the subsequent firmware updates. Thank you for your feedback. 

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#19
Options
Re:Omada_Network_Application_V6.1.x.x Pre-Release Firmware (Updated on 16th Dec, 2025)
Yesterday

  @Huemmer 

Thanks for posting here. Please see the answer below:

 

Huemmer wrote

  @Vincent-TP V6.1 is a massive leap forward, especially with the new Health Dashboards and Device Timelines. However, the new restriction on DHCP reservations outside the pool is a significant pain point for those of us managing critical infrastructure. We typically keep servers and static assets outside the dynamic range to avoid conflicts and maintain a clean subnet architecture. Please consider making this validation optional.
  >>> We will avoid this in the official firmware release. Thank you for your feedback.

 

Additionally, since the UI is becoming so fluid and health-focused, it would be a game-changer to have a 'Critical Asset' toggle for specific clients. Being able to 'flag' a server or a NAS and receive an immediate alert if it goes offline would bridge the gap between simple networking and proactive monitoring. Keep up the great work!

 >>>Thanks for the feedback. This is a new feature request. To gather more voters and more detailed descriptions of these needs to ensure that the relevant departments fully understand and can conduct thorough assessments for functional support, you may start a feature request post.

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  1  
  1  
#20
Options
12
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.