Business Community > Controllers > Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
< Controllers

Early Access Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)

12345

Early Access Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)

42 Reply
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
23 hours ago

  @Vincent-TP 

 

 

yes its working now

Omada & VIGI | Using at 3 Locations | Controller: V6.0.0.19 (Linux) | GW: ER7206 | SW: SG2428P & SG2210P | APs: 2 × EAP610 | WAN: Jio&Airtel | NVR2016H & 8 Cam's.
  1  
  1  
#24
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
21 hours ago

  @Vincent-TP Amazing, it supports capturing the 802.11 packets now. But what is Steam mode, how it works?

  0  
  0  
#25
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
19 hours ago

  @Vincent-TP 

 

now i have been testing for a few days. everything works much better and once i have learned where all the new things are it looks good. but one thing should be changed. switch port profile without being able to configure vlan is in my opinion completely pointless. here is an example of how switch port profile configuration should be.

 

I don't know if it's a bug in the beta version or if it's how it's supposed to be, do you have any ideas about that Vincent?

 

here is a screenshot of how the vlan configuration should be in a switch port profile.

 

  0  
  0  
#26
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
15 hours ago - last edited 15 hours ago

@MR.S 

@Vincent-TP 

 

OMG, i just realised what you are on about.  Port profiles no longer control the native/tagged/untagged of a port!! now its just things like loopback, port isolation, flow control etc etc......but not the actual vlans

 

This is really quite terrible, its far, FAR easier to edit vlans of old-style pre v6 profiles and have it apply to every port which its set on automatically than having to go through hundreds of ports to change some vlans! No.......just no. Seriously

 

I agree with Mr.S - its pointless having a profile for non-vlan type settings (flow control, loopback etc) if you have to edit the port directly now and can set it when you in there

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
  0  
  0  
#27
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
15 hours ago - last edited 10 hours ago

  @Vincent-TP 

 

There are two people who reported issues with the controller reaching out to check things like firmware updates and issues with connection to the cloud services:

https://github.com/mbentley/docker-omada-controller/discussions/620

https://github.com/mbentley/docker-omada-controller/discussions/621

 

The logs of the error: https://gist.github.com/mbentley/66a11f6e401802d3228d4a86373d055d

 

I don't exactly understand how the controller gets the TP-Link root CA but I did see a message on my controller, which is working fine on v6, where it has a message about:

 

09-08-2025 19:02:11.207 INFO [check-ca-certificate-update-work-group-0] [] c.t.s.o.m.c.f(): Checking Last Ca Certification...

 

So I wasn't sure if that process might have failed for those people or what exactly, assuming that is what the process does - grab the root CA but I am 100% guessing here.  I've checked to make sure it isn't a keystore CA issue but their java keystores look good - have all of the standard root CAs but obviously not the custom TP-Link one.

 

One user provided some debug logs I had them enable: https://github.com/user-attachments/files/22212133/omada6.log

 

From the logs, it's like there is a CN=tp-link-CA that gets trusted but it's missing the TP-Link Cloud Root CA.  Of course I could totally be misinterpreting the errors.

 

 

  0  
  0  
#28
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
15 hours ago - last edited 12 hours ago

  @Vincent-TP 

 

Some further observations

 

Is it Labels, or Tags?

(also, im not really sure what the point of these are since we can give the port a name anyway?)

 

Missing Storm Cotnrol Threshold % in Direct port editing - profile overrides, but it IS there in editing a port profile (such as they are)

 

Should be "Reboot Schedule" and not just "Schedule"

 

 

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
  0  
  0  
#29
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
14 hours ago - last edited 13 hours ago

the new Omada 6.0 changed totally the Switch Profile.

On Omada 5.15.24 and before:

Switch Profile = VLAN configuration (Native VLAN, tagged VLAN, untagged VLAN) + other port configurations including STP, Storm Controller, Loop Detection, etc..

And when you create a VLAN, the controller will automatically create a Switch Profile for this VLAN.

 

On Omada 6.0:

they split the VLAN configuration and the other port configurations. So the profile you see on Omada 6.0 no longer contains the VLAN configurations.

The VLAN now need to be configured on port level, but you can configure them in batch.

and when you create a VLAN, it will not automatically generate the port profile, because it's not necessary now.

 

I cannot say which one is better, probably the new design is better for more exprienced users when they know clearly how to configure the VLAN on the ports. And now they can use one Port Profile for multiple different VLANs, this should be more convenient if you have hundreds of VLANs and most of these VLANs are using the same port configurations.

 

Good thing is that the configurations has been seamlessly inherited without issue. We just need some time to get used to the new implementation.

  1  
  1  
#30
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
13 hours ago

   @Vincent-TP You should mention on the notes that all the BETA controller published here don't have Cloud Access. Some bold users may just upgrade it on the production environment.

  0  
  0  
#31
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
13 hours ago
why does it need TCP port 29817 opened to have wireless clients appear on the dashboard? It's not even mentioned on the release note.
  0  
  0  
#32
Options
Re:Omada SDN Controller_V6.0.0.19 Pre-Release Firmware (released on 5th Sep, 2025)
13 hours ago - last edited 13 hours ago

  @Kenallo 

 

I disagree.  Its far easier and safer to have a central port profile containing the vlan settings that if you need to change (say, moving IP cameras onto a new vlan) you dont have to go through, in my case, over 180 switch ports in one giant unbroken list.  Even though you can select more than one port for bulk config the risk of accidentally selecting an incorrect port (say a switch uplink) is high and then poof, a whole network segment goes down and you cannot fix that remotely.  And who wants to do that every single time you want to change a vlan?  With the old style profiles its one change and BAM - all affected ports get the change all at once.  you only needed to do the initial setup of the profile-per-port once

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
  0  
  0  
#33
Options
12345
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.