@bruskieZA 

Hey

Sounds like you are on the right path (last paragraph)

In short, static VLANs like VLAN40 in your case should only be applied to a switch port that is connected directly to a endpoint (PC, Laptop etc).  If the port is connected to an AP, this needs to be a trunk port.  

In the short reasoning, if you tell the switchport to only accept VLAN40 traffic, the AP cant talk to the switch as it needs to handle more than just the clients VLAN40 traffic, it also needs routing and management, other SSIDs etc..  therefore needs to be a trunk port.  

Ok so below is a screenie of my AP Port Profile (literally called APs Profile).    The native network is LAN as thats the network the AP is getting its IP and Management from, the Tagged Networks are the 3 SSIDs that i want to allow traffic (each seperate vlan) through the AP to the switch.   Untagged is the local AP to Switch traffic (again LAN)

So you would need Native : LAN (or whatever your mangement is)...   Tagged as VLAN40 and others if you have...   untagged same as Native..

Then just add the VLAN number into the SSID setup under WiFi.  

If you create this profile and apply it to the port on your switch, it should work within a few seconds.

  @Philbert Thanks for this. I will create a new profile as I am not able to save changes to the profile the system creates for each Vlan. I forgot to mention that I need the bridging port to provide IP ranges within that Vlan40 as the client will have a switch connected to this EAP245 bridging port to connect printers etc.

  @bruskieZA 

Hey

Yeah you cant edit the default created profiles so just create a new one, thats what I did

In terms of using the 2nd LAN Port, this isnt going to allow you place a VLAN on that port as the 2nd LAN port is really only for uplinking to another AP.   Anything connected to this port would be on the management / trunk network and not the VLAN40

You would be better reconsidering your networking setup rather than using this port for a switch.

  @Philbert unfortunately we are very limited in certain areas of the building on what we can pull through. In this case one LAN is the only option. 
 

Are there any TP Link Omada access points that have a secondary port that allows for Vlan?

  @bruskieZA 

Sadly none of the APs have a switch / vlan feature built in, however in fairness compeditors dont do this either (to the best of my knowledge)

However, if you have a cable in that area (area of AP), what about putting a cheap 8 port switch in there and then running the AP and printers off it instead?   Something like the SG2008P would be perfect and that way you can have the printers on port1 VLAN40 and AP on Port8 trunked etc etc..  I have sneaked switches into roof tiles before to overcome issues like this, may be an option?

  @Philbert yea, was thinking the same but found a super quick solution and bought a basic wireless to lan and plugged the printer in. Cheap and works like a dream. Printer doesn't need much to operate thank goodness.

Appreciate all the assistance.