Hi @IT-Moutier, I have a 265HD which also has two ports. The vlan setting on the second port is in the device's Ports options.  This setting was not there when I initially adopted my EAP-265HD (quite a while back), but later appeared.  I can't recall if it was the AP firmware or a controller update that made the difference.  I would assume that the 783 would work the same way as it's much newer, but if you don't see the Ports section then maybe not.

  @Vincent-TP 

Thanks for your reply.

We’re deploying a city-wide Omada infrastructure for municipal buildings and schools — including dozens of EAP783 access points, all connected to TP-Link Omada-managed switches (SG3428XPP-M2).

We are using the second LAN port (LAN2) on the EAP783 in environments where only one network outlet is available (e.g., classrooms, daycares, offices). The idea is to:

• use LAN1 as a trunk port (with VLANs for SSIDs and management),

• and use LAN2 as a downstream access port for a dedicated VLAN (VLAN XX) to plug in a PC or printer.

These are simple wired clients (e.g. Windows PC) which do not support tagged VLANs, so LAN2 must deliver untagged traffic from VLAN 54 — just like on the EAP-Wall series, where this configuration is available.

Using an extra switch just for that would add unnecessary complexity and cost, and defeats the purpose of having a second port on the access point.

Considering that the EAP783 is a high-end model with dual 2.5 Gbps ports, we expected LAN2 to be usable in enterprise deployment scenarios like this one.

Is there any roadmap to allow LAN2 to be VLAN-configurable via the Omada controller or future firmware?

Many thanks for your support.

@IT-Moutier, there might be a work around to acheive what you want.  Assuming you're not using the default VLAN(1) think about trying this...

• On the EAP783 go to Config->Services->Management VLAN and set the Management VLAN to Custom and the LAN Network to your management VLAN
• Create a Switch Profile for the EAP783/Access Port
  • Set the Native Network/Untagged Network to be the VLAN you want to use for the end device (what you wanted to set on the AP's second LAN port)
  • Add the Management VLAN and the other SSID mapped VLANs as Tagged Networks
• Assign the Switch Profile to the port on the SG3428 where the EAP783's connected
• If an SSID on the AP uses the same VLAN as the end device, then that SSID would need to map to the default VLAN (WLAN setup or override) and the switch will tag it

I did a quick test with my 265's second port set to the default VLAN and it seems to be a viable solution.

If the devices you want to connect to the 783 requires many different VLANs, this setup will be a pain due to the number of switch profiles and WLAN templates/overrides needed.  If you use VLAN54 for everything, maybe not so bad.

  @D-C 

This method does indeed work - i actually use if for a SG2008 hanging off a dumb POE switch that is native vlan for all the security cameras in that part of the building