bpwl can you tag a WLAN??
Yes
What happens with the WLAN1 wireless settings … when set to
(case 1) If “Vlan mode = use tag”, “VLAN ID = 5” , the packets from the bridge will be filtered on VLAN ID, will be tagged when sent to the bridge, untagged when sent to wifi
WLAN1 now acts a a VLAN aware switch, where the wifi side is an access port for PVID=5, and the bridge side is a trunk port
(*) !
(case 2) If “Vlan mode = no tag”, “VLAN ID = 1” , no VLAN filtering done, the packet tags will not be touched when sent out to wifi, or when received from wifi
WLAN1 now acts as a dump switch, totally unaware of VLANs, and just forwards everything as is.
Your Access port
case 1: WLAN wifi will send packets it receives as tagged with the correct VLAN ID from the bridge as untagged wifi , and delivers wifi received untagged as VLAN tagged to the bridge : not as expected for a bridge access port
case 2: the VLAN 5 packets will be untagged by the bridge (access port) and as such sent and received as untagged by WLAN wifi (as is / untouched / dumb / transparent )
Your Trunk port
case 1: WLAN wifi will send and receive VLAN tagged packets from and to the bridge with the correct VLAN ID, and wifi send or receive them as untagged wifi.
case 2: the VLAN packets if delivered as VLAN tagged by the bridge are sent and received untouched as VLAN tagged wifi by WLAN (VLAN over wifi is no problem, even hybrid)
(*) access lists overrule the VLAN ID and VLAN Mode “use tag” or “no tag” setting per connection , if set in the access list rule !!! I expect RADIUS attributes to do similar things.
case 1 : WLAN1 bridge side is tagged, wifi side is untagged
case 2 : WLAN1 unaware of VLAN, just forwards as is
Double VLAN tags to be studied. (VLAN tunneling, Q-in-Q, Tag stacking, … ) … pfffff