Business Community > Controllers > Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
< Controllers

Early Access Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)

191011

Early Access Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)

106 Reply
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
a week ago

  @Vincent-TP went to go update the linux sdn fro v5.15.20 as i realized the startup logs showed a timeout of 3 months ago So i updated to this prelease hoping it would fire up but still nothing it just hangs at "Starting Omada Controller" then the log cuts off with "blob data 612b" or something  so given it's an encrypted blob data a point in the right direction here could be helpful all 3 of my AP's are up and running fine. I see constant DNS queries for "omada." all being thrown out by my unbound DNS server. I tried pointing it to my production system where I run the omada controller hoping it would fire up but still nothing so I reverted that DNS changfe. again any help appreciated

  0  
  0  
#94
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
a week ago

  @Vincent-TP 

 

I have a couple of switches that clearly need firmware updates but still work.

 

Is there any way to turn the nag off in the gui to go get an update (which is not likely to be available)?

 

Thanks 

 

 

  0  
  0  
#95
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Saturday

  @Vincent-TP I noticed that a new Omada iOS app with version 5.0.24 was just released.  It doesn't mention support for version 6 controller in the changelog.  Does this version support controller version 6?

  0  
  0  
#96
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Sunday

  @mackworth 

 

Yes it does.

  1  
  1  
#97
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Sunday

  @n0izee 

 

Looks like you're on your own with this one.  Let's see what the AI has to say cool

  0  
  0  
#98
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Monday

Hi  @URL 

 

Yes,  you can turn off the following button under Global View > Settings > UI Interaction

URL wrote

  @Vincent-TP 

 

I have a couple of switches that clearly need firmware updates but still work.

 

Is there any way to turn the nag off in the gui to go get an update (which is not likely to be available)?

 

Thanks 

 

 

 

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  2  
  2  
#99
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Monday - last edited Monday

  @Vincent-TP 

 

Thanks for the reply - I will go test this - I had assumed that this would stop it checking for an update as OPOSED to flagging/nagging that the device firmware was unsupported.

 

Thanks

  0  
  0  
#100
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Monday

  @Vincent-TP 

 

I found out what is going on with random people seeing SSL cert errors.  Here is a summary that hopefully someone from the development team can help address as while it can be worked around, it could be a problem for random people:

 

The Problem

Three JARs contain tpKeyStore:

  • cloudsdk-1.2.3.jar (934 bytes) - NEW certificate (Feb 2025)
  • device-gateway-core-6.0.0.23.jar (846 bytes) - OLD certificate (2018)
  • omada-datatrack-6.0.0.23.jar (846 bytes) - OLD certificate (2018)

 

Non-deterministic JAR loading order: When using -cp /opt/tplink/EAPController/lib/*, the JVM loads JARs in filesystem order, which varies by:

  • Docker filesystem driver (overlay2, aufs, etc.)
  • Kernel version
  • Filesystem type
  • Whether files were extracted, copied, or created fresh

 

Wrong keystore loaded randomly: ClassLoader.getSystemResourceAsStream("tpKeyStore") returns the FIRST tpKeyStore it finds in the classpath:

  • If cloudsdk-1.2.3.jar loads first → Gets NEW cert (Feb 2025) → WORKS!
  • If device-gateway-core-6.0.0.23.jar or omada-datatrack-6.0.0.23.jar loads first → Gets OLD cert (2018) → FAILS!

 

TP-Link rotated their CA in February 2025: Their cloud servers now present certificates signed by the NEW CA, but some users get the OLD CA from the wrong JAR!

 

Why It's Machine-Specific

  • Same Docker image, but filesystem ordering varies
  • Persistent data doesn't matter (it's not stored there)
  • Copying to a new machine might change the JAR loading order

 

The Fix

TP-Link needs to:

  • Remove duplicate tpKeyStore files from device-gateway-core and omada-datatrack JARs
  • OR update all three keystores to contain the same certificate
  • OR change code to use CustomSSLContext.class.getResourceAsStream("/tpKeyStore") instead of ClassLoader.getSystemResourceAsStream()

 

User Workaround

Users can force the correct JAR order by modifying the startup command:

java -server -Xms128m -Xmx1024m ... \
  -cp /opt/tplink/EAPController/lib/cloudsdk-1.2.3.jar:/opt/tplink/EAPController/lib/*:/opt/tplink/EAPController/properties: \
  com.tplink.smb.omada.starter.OmadaLinuxMain
 
  3  
  3  
#101
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Monday

  @mbentley 

 

I was affected by the SSL cert problem; I couldn't register with Omada Cloud or check firmware. Mbentley's work-around has fixed the problem for me, as have the new docker images that were just released. My thanks to mbentley. His docker images are a huge asset to the Omada community.

 

Other than the cloud related problem, Omada 6.0.0.23 has been working reliably for me. Additionally, the new Omada iOS app is now working with 6.0.0.23.

  0  
  0  
#102
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 28th Sep, 2025)
Tuesday

Hi  @URL 

 

After disabling that button, the SDN devices will no longer automatically check for firmware updates, which means you won't receive update notifications. Isn't this exactly what you wanted? What do you mean about device firmware was unsupported?

URL wrote

  @Vincent-TP 

 

Thanks for the reply - I will go test this - I had assumed that this would stop it checking for an update as OPOSED to flagging/nagging that the device firmware was unsupported.

 

Thanks

 

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#103
Options
191011
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.