Dear Victor,
Currently I have it working with an additional switch, maybe this way it is more clear:
========= =========
| Vlan1| ---- | Rap e0|
------------| | | |
Uplink | Vlan5| ---- | Rap e1|
(Trunk) ========= =========
My problem is I have only one cable to the ceiling where the RAP stays. So I have to use the same cable for the 'external' side of the RAP (ipsec tunnel) and for the internal side (where the clients connect).
I can use the same vlan id on the controller and on the client side, so it won't be an issue to configure the port as trunk. My initial idea was to configure the E0 port as 'trunk' and have the rap to use untagged/vlan1 as 'external' side and have the 'internal' network as tagged vlan on the same cable. But it didn't work, it seems that the RAP doesn't send me out any tagged traffic on the uplink port.
So I'm currently using the additional switch to consolidate both networks into one wire again. It's not beautiful because I have an additional ugly box hanging on the ceiling next to the Aruba AP but this solution currently works. It would be much smarter if we find a way to use the same port as uplink and for the wired clients on the AP. This would even allow me to use an AP105 as RAP and power it via PoE, so I can also remove the power cords ;)
Thanks & Bye,
Chris