How do you enable VLAN filtering on a bridge and assign a tagged VLAN to a port?

How do you enable VLAN filtering on a bridge and assign a tagged VLAN to a port?

• A. /interface vlan add name=vlan10 vlan-id=10 interface=bridge1; /interface bridge set bridge1 vlan-filtering=yes; /interface bridge port add bridge=bridge1 interface=ether1 pvid=10
• B. /interface bridge set bridge1 vlan-filtering=yes; /interface vlan add name=vlan10 vlan-id=10 interface=bridge1; /interface bridge port add bridge=bridge1 interface=ether1 pvid=10
• C. /interface bridge port add bridge=bridge1 interface=ether1 pvid=10; /interface vlan add name=vlan10 vlan-id=10 interface=bridge1; /interface bridge set bridge1 vlan-filtering=yes
• D. /interface bridge set bridge1 protocol-mode=stp; /interface vlan add name=vlan10 vlan-id=10 interface=bridge1; /interface bridge port add bridge=bridge1 interface=ether1 pvid=10

Answer: (B)

VLAN filtering on a bridge makes the bridge aware of VLANs and how to handle tagged versus untagged traffic. To map an untagged port to a specific VLAN and carry a tagged VLAN across the network, you first enable VLAN filtering on the bridge, then define the VLAN on that bridge, and finally assign the port with a PVID so untagged frames are tied to that VLAN. This sequence is best because enabling VLAN filtering ensures the bridge processes VLAN tags correctly before you start attaching VLANs and ports. Creating the VLAN interface with the VLAN ID attaches that VLAN to the bridge, making it a recognized segment the bridge can forward. Setting the port’s PVID to the desired VLAN ID ensures untagged frames entering that port are associated with that VLAN, while the port can still carry the tagged VLAN traffic as defined. Together, these steps establish both the tagged VLAN path and the handling of untagged traffic on the port. If you omit enabling VLAN filtering or mix up the order, the bridge may not handle VLAN tags as intended, and untagged traffic could be misassigned or filtered out.

VLAN filtering on a bridge makes the bridge aware of VLANs and how to handle tagged versus untagged traffic. To map an untagged port to a specific VLAN and carry a tagged VLAN across the network, you first enable VLAN filtering on the bridge, then define the VLAN on that bridge, and finally assign the port with a PVID so untagged frames are tied to that VLAN.

This sequence is best because enabling VLAN filtering ensures the bridge processes VLAN tags correctly before you start attaching VLANs and ports. Creating the VLAN interface with the VLAN ID attaches that VLAN to the bridge, making it a recognized segment the bridge can forward. Setting the port’s PVID to the desired VLAN ID ensures untagged frames entering that port are associated with that VLAN, while the port can still carry the tagged VLAN traffic as defined. Together, these steps establish both the tagged VLAN path and the handling of untagged traffic on the port.

If you omit enabling VLAN filtering or mix up the order, the bridge may not handle VLAN tags as intended, and untagged traffic could be misassigned or filtered out.