cjoseph wrote:
If you are using multiple VLANs on a VAP in bridged mode, it is tagging the client traffic and sending it to the ethernet port of the AP. If the VLAN that the user ends up in is not on a trunk that the AP is in, it will be dropped by the switch. A strategy would be to tag the client traffic with the same VLAN as the default-vlan in the AP system profile so that it would simply bridge the traffic to the same VLAN as the AP. That way the client will simply get an ip address on the same subnet as the AP, which will change, based on where the AP is, but it does not force you to make a custom configuration for different sites. If you plan your wired subnets okay, you should not have a problem.
If you want more space to bridge clients to different vlans, however, you need to put those access points on trunks.
Can't use the same VLAN as the AP.
The port the AP connects to is a trunk (on a S2500), with AP VLAN as native, and all other VLAN tagged.
And we are using the same VLAN ID on all sites, so should be 1 VAP per type of client for all sites, so no custom config for different sites.
For this particular test, I have configured the VLAN field in the VAP as 102-103 (also on the trunk port in switch as tagged members).
I works great on VLAN 102, but I looks like the AP never tags traffic on VLAN 103.
How will the AP know when to send traffic to VLAN 102 or VLAN 103, when both is in the VAP?