Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)

Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)

146 Reply
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)
16 hours ago

Hi  @URL 

 

Thanks for the feedback.

You mean that the ones displayed on the ports have their IP addresses and MAC addresses shown in the client list, while those not displayed on the switch ports also don’t show their IP and MAC addresses in the client list? Is it a one-to-one correspondence?

What are the types of clients that are displayed? And what types are the ones not displayed? Also, can these clients without displayed IPs access the internet normally?

URL wrote

Hi there

 

Any thoughts as to why some devices show the device icon and the MAC address next to some ports but not others?

 

The "Current Client" list does not show any client MAC or IP for devices not shown in the images.

 

I am running latest drop of 6.X on Windows

 

 

 

Thanks in advance!

 

  0  
  0  
#146
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)
16 hours ago

Hi  @pustekuchen 

  • The Apply Network option only takes effect for DNS requests sent by clients to other DNS servers (i.e., addresses other than the Gateway’s own LAN port IP). DNS requests directed to the Gateway’s LAN port IP would not be affected by DNS Override.
  • DNS requests from LAN networks that are not selected will be forwarded directly without being intercepted.

For more details, please refer to the following:

How to configure DNS override on Omada Gateway

pustekuchen wrote

  @Vincent-TP 
I've activated the DNS Proxy, because im running AdHome as DNS Server in my Network and want all DNS Request to be cached. AdHome has configured Fallback-DNS-Server, if the Upstream-DNS-Server do not respond.

 

Will the DNS Request from the Primary / Secondary DNS Override be passed throug? Or will this end in a loop?

 

  0  
  0  
#147
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)
14 hours ago

  @Vincent-TP  

 

Dear TP-Link Omada Team,

 

I am facing an issue with the Omada Controller related to pending (unsupported) devices.

 

Here’s the situation:


I have two sites — Site A and Site B. When a device that actually belongs to Site B appears as pending, it is being shown under both Site A and Site B in the controller.

 

Ideally, if the device belongs to Site B, it should only appear under Site B, not both sites.

 

This behavior causes confusion when managing devices across multiple sites.


Please kindly look into this and fix the issue in an upcoming update.

 

I have also attached a screenshot for your reference.

 

Thank you for your support and continuous improvements to the Omada platform.

 

 

Omada & VIGI | Using at 4 Locations | Controller: V6.0.0.24 (Linux) | GW: ER7206 | SW: SG2428P & SG2210P | APs: 2 × EAP610 | WAN: Jio&Airtel | NVR2016H.
  0  
  0  
#148
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)
12 hours ago - last edited 12 hours ago

Hi  @Babun-Sikder 

Thanks for the feedback.

Did you notice this situation only after upgrading to V6?

When using the same controller to manage devices in different locations, most people, like you, create two corresponding sites in the controller. However, there are also scenarios where devices are in different locations, but the administrator only needs to manage them under the same site. In such cases, all devices should be displayed.

In your situation, after adopting the devices in the corresponding site, they should no longer appear in the other site.

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

  @JRenaud 

I've had a look at this, there doesn't seem to be any way to make it use radius to get the VLAN.

 

It appears this is more for setting certain MAC address ranges to be on a specific VLAN

 

  0  
  0  
#150
Options
Re:Omada SDN Controller_V6.0.0.x Pre-Release Firmware (Update on 31st Oct, 2025)
10 hours ago - last edited 10 hours ago

  @Vincent-TP 

 

Thank you for your reply.

 

Yes, I noticed this issue not only after upgrading to V6 — the same problem existed in the previous versions as well.

 

Even before the upgrade, when I had one unsupported pending device belonging to Site B, it still showed up under both Site A and Site B in the controller.

 

My suggestion: if the device is not supported, it should not be displayed at all in the controller.

 

For reference, I currently have two unsupported TP-Link AP devices:

 

  • EAP110 (US) v1.0 / v2.0

  • Firmware version: 1.3.0

Omada & VIGI | Using at 4 Locations | Controller: V6.0.0.24 (Linux) | GW: ER7206 | SW: SG2428P & SG2210P | APs: 2 × EAP610 | WAN: Jio&Airtel | NVR2016H.
  0  
  0  
#151
Options