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)

1101112...

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-24 04:12:11 - last edited 2025-09-24 16:30:36

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

  0  
  0  
#50
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-24 03:45:46

  @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

  @Vincent-TP 

 

 

Something sinister happened here.

I thought I'd lost access to everything.

The OC200 V1 suddenly got the IP address 192.168.0.100 after I tried to disable a feature on port 3, because the profile I had configured for VLANs no longer works the same way it did before.

I need to understand this better.

After I regained access, I changed it to a different IP address, but it just saved.
Suggestion: When saving this configuration, prompt the user to reboot for it to take effect through a warning.

 

 


 

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.

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

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

  @Vincent-TP 

 

 

Something sinister happened here.

I thought I'd lost access to everything.

The OC200 V1 suddenly got the IP address 192.168.0.100 after I tried to disable a feature on port 3, because the profile I had configured for VLANs no longer works the same way it did before.

I need to understand this better.

After I regained access, I changed it to a different IP address, but it just saved.
Suggestion: When saving this configuration, prompt the user to reboot for it to take effect through a warning.

 

 

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  
#48
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-23 23:49:32

  @Vincent-TP 

 

 

Something sinister happened here.

I thought I'd lost access to everything.

The OC200 V1 suddenly got the IP address 192.168.0.100 after I tried to disable a feature on port 3, because the profile I had configured for VLANs no longer works the same way it did before.

I need to understand this better.

After I regained access, I changed it to a different IP address, but it just saved.
Suggestion: When saving this configuration, prompt the user to reboot for it to take effect through a warning.

 

  0  
  0  
#47
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-23 03:32:45

Hi  @ceejaybassist 

 

Thanks for the reply.

I had create a support ticket to follow up this feedback, the case ID is TKID250950971. Please check your email inbox. Thanks.

 

ceejaybassist wrote

  @Vincent-TP It's Nord. I can connect to the app and camera just fine using Nord if LAN isolation is disabled.

 

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  
#46
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-21 15:00:33

  @Vincent-TP 

 

Installed on a OC200 V2 and it is running like normal.  I have not ran through it yet.  but it's working so far. 

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

Hi  @Vincent-TP ,

 

I think I found another spelling mistake, in both hardware and linux controller. Disabed and Priview instead of disabled and preview.

 

 

 


 
  1  
  1  
#44
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-20 17:23:49 - last edited 2025-09-20 17:26:12

  @Vincent-TP 

 

Had a major show-stopping (quite literally, as i work in theatre) bug with v6 today - Switch adoption at remote site

 

Experienced something i haven't seen before with adopting a new device at a remote site. This remote site is adoped over IPsec site-to-site VPN, and has the controller IP set as option 138 in this sites management vlan DHCP I was asked to swap a SG2008 to a SG2008P for some POE provision at this site - i had a spare SG2008P available in my stock so i made sure it was factory reset, and gave it to my theatre technician to take with him to the other location.

 

He unplugged the SG2008, and plugged in the SG2008P. I saw it show up as pending - great, I clicked adopt - and it got stuck at "configuring" - no amount of him pin-hole factory resetting / readopting it cleared this - it always got stuck at configuring.

 

I ended up having to go there, and after some time realized what was happening, and I haven't seen this before!

 

All my remote sites management IP have a vlan tag that reflects their IP range - in this case the site management is 172.22.0.0 /24 and so this vlan tag is 220, which is set as native PVID on all the router ports (switch connected direct to router, an ER605 v2)

 

Before v6, this worked well. Plug in a new device, it gets auto configured with vlan 220 as its management vlan, it gets DHCP, it adopts fine.

 

This time something weird was happening - when it tried to adopt the switch, it was creating a whole new VLAN on this site, called the MAC address of the switch, id 1, and not assigning it to any of the router ports. and the controller was assigning this as the management vlan of the switch - so when it was adopting and it set that new mystery vlan as the management vlan of the switch, communication died and it got stuck.

 

To successfully adopt the switch, i had to delete this new mystery vlan, change the management vlan ID to 1. The switch immediately adopted and configured fine and i could proceed with setting it up. I have now changed all my remote sites management vlan to id 1 just in case.

 

Im sorry i dont have any screenshots or configs for you, i had to get this sorted urgently for the show tonight. I could pull some controller logs if needed.

  1  
  1  
#43
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-19 07:26:22

Hi  @GRL 

 

Thank you so much for all the feedback. Here are some updates:

GRL wrote

Some obervations as I go along

1) My SSIDs clearly exist, and were carried over from previous FW fine, but are not shown in my pre-existing EAP ACLs

 

 

Deleting the ACLs allowed me to recreate them and select the SSIDs again.

 

>>>This is located and will be addressed

 

2)  Managing a gateway -  Advanced > Advanced?   Maybe Advanced > LLDP and seperate Advanced > Echo Server

>>>We will make corresponding adjustments

 

3) Glitchy behaviour when selecting and unselecting ports grouped in a LAG (video attached)

 >>>This will be fixed

 

4) Switch profiles.  Since these no longer set VLANs, allow us to rename them - including the "All" profile and those generated when you make a vlan, and the undeleteable one for the default vlan.  That way we can at least give them more sensible names now.  For example, i set 802.1p values in mine so i could rename the All profile to "QOS - Trusted" and rename the others to things like "QOS - 7" etc, rather than having to make a whole new set.

 >>>We currently cannot implement this, Considering that the official version of the software controller supports users switching back to the old version UI, we have temporarily made no adjustments to the All/Default Profile to avoid potential exceptions that may occur after users revert to the old version UI.

 

6) The old ISP Load widget on the dashboard was very useful, where can i find this information now (specifically ISP latency?)

>>>The ISP load widget is now located in Insights - Report - Wired dashboard, and the Internet Activity in the Dashboard also includes the WAN traffic part, but currently there is no Latency; we are plan to add the Latency curve to this chart.

 

 

7)  I cant trackpad/2 finger scroll here (top arrow) but i can in the lower section (bottom arrow).  On the port display at the top i have to use the teeny scroll bar

>>>This will be fixed

 

8)  The way this new graph thing works is just awful. Everything disappears on it if you hover over a client.  WHY is that one client a bigger green circle than the rest?  The red line indicating the poor signal level is a bit vivid and jarring compared to the rest of it.  The label text is all very faint and unreadable.

>>> All will be optimized.

 

9) There is no way to quickly forget or batch forget clients!  They have to be done one at a time by clicking into them and then hitting the three dots menu>forget This would be a total pain if you want to declutter the clients list and get rid of client history on old clients

>>>We are planning to add an addition of a forget option in the Action column of the Client list for quick forgetting.

 

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  
#41
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-09-19 07:04:13

  @GRL 

 

Please see the answer to these questions:

 

GRL wrote

  @Vincent-TP 

 

Also a couple questions about Isolated VLANs.   

 

1) Is it only isolated at the gateway interface, or does this also create "background" switch rules that prevent inter-vlan routing on switch interfaces as well ?

>>>It only take effective on Gateways.

2) Can they be ovveridden to a specific vlan with a gateway or switch rule, similar to how WiFi "Guest Mode" can be overriden with an EAP rule ?

>>>Yes, ACL has higher priority than isolated VLAN.

 

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  
#40
Options
1101112...

Tags

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