@Baton wrote:
The documentation is written "When configuring the Ethernet ports on dual-port APs, note the following requirements for the AP configures as a mesh portal: Connect Ethernet 0 to the managed device to obtain an IP address. The wired AP profile controls Ethernet 1."
and
Trunk mode contains a list of allowed VLANs. Any packet received on the port that is tagged with an allowed VLAN is forwarded to the managed device. Untagged packets are forwarded to the managed device on the configured Native VLAN. Packets received from the managed device and sent out the port remain tagged unless the tag value in the packet is the Native VLAN, in which case the tag is removed. Define the Native VLAN in the Trunk mode native VLAN field and the other allowed VLANs in the Trunk mode allowed VLANs field.
Why use 2 ports if all packets first arrive at the managed device through the port Eth0?
I can use only 1 port Eth0 connected to the switch, not to the managed device and set the trunk mode for it?
What is the topology you're trying to create? It sounds like this is a terminology issue.
For a mesh portal, e0 is used for the portal AP to tunnel back to the controller (managed device), so only e1 is available for bridging to other devices. Physically, the mesh portal connects the e0 port to a switch, since APs do not typically connect directly to a controller.
For a mesh point, aka a mesh AP which uses it's wireless radio connection to connect back to the controller, e0 and e1 are both available for wired port profiles.