Which command enables VLAN filtering on a MikroTik bridge?

Which command enables VLAN filtering on a MikroTik bridge?

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

Answer: (B)

VLAN filtering on a MikroTik bridge is activated by turning on the bridge’s VLAN processing. When you enable vlan-filtering, the bridge starts enforcing VLAN tags and applying per-port VLAN rules, which you can then configure with the bridge VLAN table. The correct command does exactly that: /interface bridge set bridge1 vlan-filtering=yes. This switches on VLAN processing for the bridge named bridge1, allowing you to define which VLANs are allowed on which ports and how untagged traffic is treated. The other actions don’t enable this feature themselves: adding a port with a default PVID is part of VLAN handling but won’t turn on filtering globally; creating a VLAN interface attaches a VLAN to an interface but doesn’t enable the bridge’s VLAN filtering; and setting protocol-mode to STP relates to spanning tree behavior, not VLAN filtering.

VLAN filtering on a MikroTik bridge is activated by turning on the bridge’s VLAN processing. When you enable vlan-filtering, the bridge starts enforcing VLAN tags and applying per-port VLAN rules, which you can then configure with the bridge VLAN table.

The correct command does exactly that: /interface bridge set bridge1 vlan-filtering=yes. This switches on VLAN processing for the bridge named bridge1, allowing you to define which VLANs are allowed on which ports and how untagged traffic is treated.

The other actions don’t enable this feature themselves: adding a port with a default PVID is part of VLAN handling but won’t turn on filtering globally; creating a VLAN interface attaches a VLAN to an interface but doesn’t enable the bridge’s VLAN filtering; and setting protocol-mode to STP relates to spanning tree behavior, not VLAN filtering.