Business Community > Controllers > Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Closed on 12 Nov)
< Controllers

Early Access Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Closed on 12 Nov)

191011...

Early Access Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Closed on 12 Nov)

144 Reply
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-26 08:48:07

  @Vincent-TP

 

Other issues I detected:

1- The serial number of the ER605 V2 device is not displayed.

2- Clients appear to still be connected, when they are actually not. This is very strange.

NOTE: And, even stranger is seeing that it indicates a wired connection, when there is only a wireless connection in this case.

 

3- I initially thought it was the latest firmware for the EAP670V1 US (although version EAP670v1_1.3.50_[20250819-rel57463] clearly has signal performance and internet bandwidth issues), but the disconnections don't seem to be caused by this.

Two smartphones are experiencing the same issue. I need to do more testing to better assess this, but I don't recall my smartphone exhibiting this behavior before the update to v6 on the OC200 controller.

I hope I helped.

  0  
  0  
#60
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-26 05:59:11

  @Vincent-TP

 

Taking advantage of a detail I noticed, the update search for new beta, release candidate, and stable firmware updates, despite querying TP-Link's database, seems to be finding nothing in the database for the last two months. At least, that's what I noticed when I checked firmware updates that were several weeks old and didn't see any updates identified by the controller as options.

I'd like to understand more details about this here:
To ensure the proper functioning of new device features, please make sure that TCP port 29817 is open and accessible on your network.

  0  
  0  
#59
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-26 05:02:49 - last edited 2025-09-26 08:23:23

  @Vincent-TP 

 

Dear friend,

Thank you for always being attentive to our needs.

To explain the situation, the link is indeed not being detected, despite it being active.

What I could confirm was that I first tried disconnecting and reconnecting it through the controller itself in the visual tab, as shown in the image above. However, the connection status, even after some time, remains offline for both WAN1 and WAN2.

I tried turning the network operator routers off and on again, but the status was the same for both WANs. Now, I've tried unplugging and replugging the cable in both network operator routers. Both remain offline.

I'm always waiting for the detection times. As I mentioned, this isn't working satisfactorily in version 6. In version 5, I noticed a similar issue with WAN2. However, disconnecting and reconnecting the cable returned the link to WAN2. However, after a while, it went offline again.

So, clearly, when the connection goes down, I don't have identification and forwarding to the WAN2 link. WAN1 remains active.

With a simple Linux solution, you can get this working perfectly. I hope TP-Link finally manages to fix this properly on the ER605 V2. My firmware is 2.3.0 Build 20250826 Rel.41004.

 

UPDATE
 

I was concerned about the recent tests I performed.

Load balancing isn't working. That's super strange.
I ran a few more tests to check both load balancing and failover. However, neither test worked with my router from the other provider. And in version 5, it worked correctly, despite some errors in online detection.

I think this needs to be thoroughly reviewed.
I ran a small test by changing the ports, and the behavior was the same. I thought at the time that my router might have a DNS issue, but that wasn't the case. Testing with a laptop, I was able to properly measure its performance.

I'll wait for more information.

Later, I'll try to run some more tests, as I've seen reports that this detection could take up to 6 minutes. I consider that time to be extremely long.

 

 

 

  

  0  
  0  
#58
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-26 02:37:08

  @Artur.Aragao 

 

The key changes in V6 compared to V5 are outlined in the Release Notes. Due to the extensive content, this is currently just a high-level overview. Our teams are progressively releasing supporting materials including: An FAQ list (covering 16 major/impactful features like VLAN, Switch Port, and Air Capture), Video tutorials and Updated User Guides
 Please stay tuned for official updates on our website.

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<
  2  
  2  
#57
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-25 15:34:22

Actually really surprised how fast the OC200 V2 handles this.  Not saying its fast from the jump, it is kinda slow.  But what do I expect from the cheapest controller appliance.  But I'm impressed that 6.0 works like normal.  good job!

I can not teach anyone anything - I can only make them think - Socrates
  1  
  1  
#56
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-25 06:13:09

Hi  @Artur.Aragao 

 

Thank you for your kind words. Listing the changes between V6 and V5 is indeed a good suggestion, but it will take some time. I'll try to work on this.

 

To verify, is this situation similar to what @GRL  shared below:

https://community.tp-link.com/en/business/forum/topic/841724?replyId=1612334

 

Artur.Aragao wrote

  @Vincent-TP 

 

Vincent-TP wrote

Hi  @Artur.Aragao 

 

Thanks for the feedback. Generally, we don't need to reboot controller to make any feature to take effective. To understand the situation better, could you please give us more details? such as, port3 is for from which device? what settings did you try to to save/change?

Artur.Aragao wrote

 

Well.

I tried disabling a port profile. It seems to have changed how it works. I decided to disable it. However, something went wrong during the process, and I ended up losing access to the controller.

I reset the AP and the Switch to confirm what was happening. And, even with the devices re-adopted, I still couldn't access it.
I had to remove the network cable from port 3, where the port profile was applied.
I plugged it into the router port, and then I was able to access it. I changed the port profile to activate it as it was before. I removed it, put the connections back in as before, and when I tried to access it again, I couldn't.

At that point, I thought there was a more serious problem. But then I did some troubleshooting and realized that the IP had changed to the default IP, with the final octet 100.

It was at this point that when I tried to change it, I noticed that it saved, but it didn't reboot. I saved it again, and it just said it had been saved. Nothing more. So, I decided to reboot, because since it was a pre-release firmware, there could be implementation issues.

After restarting the controller, everything went back to normal.

Look, I really want to thank you for what you did with this firmware. I see in some comments that there's still room for improvement and provisioning more features to be enabled. What you did here was great. It's a shame that the OC200 can't achieve better performance, but the improvements you made in this version 6 are really good. I notice more controlled loading and a few things that are faster.

I'd like an overview of which features were removed and which were changed and added. Especially those that were modified, as I noticed this port profile issue and need to better understand this change and its best use.

A page showing a table with the before and after would be great. So we can delve deeper into this.

Thank you.

 

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  
#55
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-25 06:03:20

Hi  @Artur.Aragao 

Thanks for the feedback.

From the screenshots, the Internet for the two WANs is not affected, only their detection status was abnormally displaying as Offline, is this correct?

 

The link on WAN1 went down and didn't go through to WAN2 after some time, due to the offline detection indication.

>>> How did the link of WAN1 went down? Did you unplug WAN1 for a test? or what else? (I see the link backup was disabled)

Artur.Aragao wrote

  @Vincent-TP

 

I almost forgot something I consider very important.

I had reported the Load Balancing feature's functionality in version 5, and at the time, it was reported that it could be a problem with the provider.

 

I noticed a bug report in the release notes for Load Balancing that appears to have been fixed. However, I believe there are still issues with online detection.

 

I'm using this configuration as a test.

In "Load Balancing Weight," I've already tried 1:1 and am now testing 1:10.

However, looking at the next image, we can see that the link is being indicated as offline. This validation algorithm needs improvement. It's not satisfactory.

I need to make a small observation: both links are now offline. The detection timeout is 3 minutes. This is really not good. I hope you can improve this.

 

The link on WAN1 went down and didn't go through to WAN2 after some time, due to the offline detection indication.

 

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  
#54
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-24 19:35:58 - last edited 2025-09-24 19:37:54

  @Vincent-TP 

37. Added support for overriding default LAN DHCP settings during adoption in Network Config > Network Settings > LAN > Default.

Does this mean that when adopting a router you can leave its DHCP settings (incl. subnet definitions) alone? I.e. You can first set up DHCP in the standalone controller. Then adopt it later and keep its DHCP settings intact?

This would be great to prevent the chicken and egg run-around when cascading routers!

  0  
  0  
#53
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-24 18:07:36

  @Vincent-TP 

 

Hi,

 

Are you going to release it for the ER7212PC v1 too ? 

 

Thanks

  1  
  1  
#52
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-24 15:49:32

  @Vincent-TP 

 

Today I decided to delete the backup files that are listed under Global View, Settings, Maintenence, Backup Files List.  Unfortunately, I have been lazy and have not been deleting older files on a regular basis.  Now the list is long and there is no way to batch delete them.  They have to be deleted one by one.

 

I recommend that a Batch Delete function be added similar to that for the log files.

 

1x ER7406 1x OC300 4x SG2008 1x EAP610 3x EAP650-Desktop 1x EAP772-Outdoor
  1  
  1  
#51
Options
191011...

Tags

Firmware Update Official Highlighted Thread
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.