@TandS 

The 2nd ethernet port is a dumb switch, so that same client will appear as if physically connected to the same switch port as the 245 is.

The -Wall units have the ability to assign VLAN's to the extra ports.  Maybe consider replacing the 245 with an EAP615-Wall?

  @d0ugmac1 

Thanks for the reply and this is what I thought..

What I'm unsure of is the ability to be able to assign a custom IP address to this client.  I tried doing so and it doesn't want to take.

Wondering if it's a potential bug either in the EAP firmware or with the Omada controller.

  @TandS 

At the very least you should be able to assign that client an IP from the same pool as the EAP245.  It gets trickier if you want it on a different subnet/VLAN.

If it's a PC, you could probably statically assign it an IP and VLAN tag and have that VLAN attached to the same port feeding the 245.  Having two untagged VLANs on the same port could lead to race conditions if both have DHCP services running on them.  Probably best to assign it an IP from the device pool (ie same subnet as EAP245, then apply ACLs and policy routes to isolate it).