Hi  @GrantD 

Currently, the ETH ports of EAP-wall are untagged by default, and they can't be modified. 

If possible, please try to give the workstation the ability to deal with untagged packets.

  @Vincent-TP 

Clearly the vlan can be set on the ports of the EAP615-wall as in the picture of my original paste.

Hi  @GrantD 

We can add the ETH ports into certain VLAN, but their egress rule is untagged and can't be changed to be tagged. This is the reason.

From the screenshot you provided, the ETH2 is in VLAN192, and the egress rule is untagged. With this configuration, only those clients which can deal with untagged packets can get internet access from this port, and the clients plugged into this port will be in VLAN192.

  @Vincent-TP yes and that works fine.... 

The issue is that the TAGGED Frames from the workstation on port one are either not stripped of their 802.1q data and forwarded out port 2 OR the incomming untagged frames from port 2 are not tagged and forwarded out port 1

  @Vincent-TP The workstation is multhomed on several networks. 

Hi  @GrantD 

Please let me know your VLAN requirements for the workstation, and I will see if they can be achieved and how to do that.

  @Vincent-TP 

Let me clarify the setup.. some things work and some things don't

I have a vlan aware device (my workstation) which tags 802.1q traffic inside the box (docker/virtualhost) for a number of subnets including it's vlan 192 as well as my managment vlan and several others. this is connected to port 1 of the 615-wall.. it works fine. it can connect to the gateways and the internet and so on for all the networks it's connected to.

I have a device that is a normal network device that doesn't know about vlans on port 2. port 2 is enabled in the omada controller and set to vlan 192. this device can connect to the gateway but cannot talk to my workstation.

This may be an implementation of private vlan within the 615-wall (if so how do I disable this)   or it may be a bug. (in which case please fix it.) 

Grant.

  @GrantD 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240816481, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!