@SoulRaven 

ok, yes, I don't quite know where it stops, I've done some tests here now, it's not a cisco switch but an access point direct in the router.
created a managed vlan 100, and vlan 1 and 14. everything worked right away. I also have cisco switch at customers with config that I sent earlier, it also works fine. but there is probably a small missconfigurtion somewhere.

but you probably cannot use trunk only against these access points, I think you must have a native vlan configured on the port. (an untagged port)
I don't think I can help you much more, you'll probably have to escalate this to support.

it would be nice if you could update us when you find a solution 

  @MR.S the problem somehow is escalded from Romania support,

But what i have undestand is necessary to have tagged and untagged traffic in the same time, and is not possibile in cisco using the same port,

in cisco untagged == access port, tagged == trunk. Is impossibile to have both in the same time.

  @SoulRaven 

you can use both

try add this in port config

switchport access vlan 1

  @MR.S is added already and ignored, because the default is vlan 1. any other vlan is accepted because is not default. but adding switchport access vlan 1 will be ignored because already is 1

  @SoulRaven 

Ok,what happen when you add this

switchport trunk native vlan 1

this do a trunk port native. if you connect a computer it should get ip from vlan1

KJK wrote

  @SoulRaven 

 

The trunk configuration looks fine, but I’m not sure how you have configured the AP.

 

What’s the IP address of the AP? Is it from the subnet of VLAN 1 or VLAN 100? If your native VLAN is 100, use an IP address from its subnet. Of course, the AP needs to be also set up to send tagged traffic in all VLANs, except for the native one.

  @KJK 

thanks for jumping in here :-) yes you might be on to something. now it is almost impossible to misconfigure these apps, but everything is possible.

can you send us a screenshot of how you have set up vlan on your ssid.

i have done some tests here and this setup works perfectly fine, management vlan is 100

  @MR.S here are the screenshots

the UI is easy to setup, the problem is how the eap225 worki with trunks and what is the reason that is not working with recular cisco switches.

each VLAN has a subnetwork

VLAN 14 - 10.10.14.0/24

VLAN 1 - 192.168.1.0/24

VLAN 100 - 10.10.100.0/24

  @SoulRaven 

Disable vlan on ssid with vlan 1 it dont work. 

  @MR.S done

is not working, still only the management is working

the DHCP server has traffic only from VLAN100

and the cisco switch has: switchport trunk allowed vlan 1,14,100

my concusion is that management is working with tagged traffic and the vlan 1 and 14 from the AP perspectiv is with untagged traffic.

but is imposibile to have tagged and untagged trafic from cisco