I have noticed a possible issue in the Omada SDN Controller Web UI regarding VLAN configuration on switch ports. When setting up a port profile, the native (untagged) network is always preselected (grayed out and cannot be changed), which is expected behavior. However, the UI allows selecting additional VLANs in the Untagged Network section, even though technically, a port can only have one untagged VLAN at a time.

From a VLAN perspective:

• The native (untagged) VLAN is automatically assigned to all untagged traffic on that port.
• Additional tagged VLANs should be selectable for trunking, but multiple untagged VLANs on a single port should not be possible.
• If multiple VLANs are selected under “Untagged Network,” it appears to make no actual difference in functionality, as only the primary untagged VLAN is applied.

Issue Summary:

• The UI allows selecting multiple VLANs under "Untagged Network," even though this should not be possible.
• The switch behavior suggests that only the first untagged VLAN is applied, making the additional selections redundant.
• This may confuse users into thinking they can assign multiple untagged VLANs to a single port, which is not valid according to VLAN standards.

Expected Behavior:

• The UI should only allow selecting one VLAN under "Untagged Network."
• If the system needs to allow multiple VLANs for some specific reason, an explanation tooltip should clarify what the setting actually does.
• If selecting multiple VLANs has no functional impact, this should be fixed or removed from the UI to prevent misconfigurations.

Question for the Community:

• Has anyone else noticed this behavior?
• Are we misunderstanding how this setting is supposed to work, or is this an actual UI bug?
• If this is unintended behavior, would TP-Link consider updating the UI to prevent misleading configurations?

Looking forward to feedback from others!