The Ethernet interfaces on the AP's can operate as either uplink ports to the wired network and the Internet, or as local client device serving ports, bridging or routing their traffic over to the rest of the network.
As was just stated above, the Ethernet ports can operate in one of two modes, an uplink mode, or a client access port mode. This mode is automatically determined and cannot be manually configured. To make this determination, the AP will listen for DHCP traffic on the Ethernet interface, if it hears an active DHCP server responding to lease requests, then it sets it as an uplink port, however, if it hears DHCP lease requests, but no DHCP server responses, then it sets its port mode to act as a client access port.
Based on the above logic, this means that in order for the AP to accept traffic from Ethernet connected client devices, it first must hear a DHCP lease request on it’s Ethernet interface. Thus if you have a device with a static IP assignment on it that you want to use, you must pair it with another device that will generate a DHCP lease request, such as a switch or other device, so the AP will hear the request and switch the port into the appropriate state.
The decision on whether it routes or bridges that traffic is decided based on the Cloudtrax network configuration. Within the Cloudtrax network, in the "Configure -> Advanced" area, you'll see two toggle option there:
If any of the AP SSID’s are bridged, you will see that listed in the “Bridge SSID” dropdown selection. Any wired clients connected to the AP will be treated like wireless clients connected to the SSID selected in “Bridge wired clients”. Thus, if the SSIDs are configured like in the two dropdown options shown above, then the traffic from the wired clients will be routed (wired clients not in bridged SSID), but if the SSIDs shown in the two dropdown options shown above match, then the traffic will be bridged (wired clients bridged into an SSID that is bridged).