From https://wiki.mikrotik.com/wiki/Manual:B ... witch_chip, we have:
Code: Select all
/interface bridge
add name=bridge1
/interface bridge port
add bridge=bridge1 interface=ether1 hw=yes
add bridge=bridge1 interface=ether2 hw=yes pvid=20
add bridge=bridge1 interface=ether3 hw=yes pvid=30
/interface bridge vlan
add bridge=bridge1 tagged=ether1 untagged=ether2,ether3 vlan-ids=20,30
add bridge=bridge1 tagged=ether1,bridge1 vlan-ids=99
/interface vlan
add interface=bridge1 vlan-id=99 name=MGMT
/ip address
add address=192.168.99.1/24 interface=MGMT
/interface bridge
set bridge1 vlan-filtering=yes
Code: Select all
add bridge=bridge1 tagged=ether1 untagged=ether2,ether3 vlan-ids=20,30 // a1
Code: Select all
add bridge=bridge1 tagged=ether1 untagged=ether2 vlan-ids=20
add bridge=bridge1 tagged=ether1 untagged=ether3 vlan-ids=30
Code: Select all
add bridge=bridge1 interface=ether2 hw=yes pvid=20
add bridge=bridge1 interface=ether3 hw=yes pvid=30
since PVID is already defined for each bridge port, why we need to define it here again ?
b) why there is "bridge1" interface for tagged parameter used here:
Code: Select all
add bridge=bridge1 tagged=ether1,bridge1 vlan-ids=99
Code: Select all
add bridge=bridge1 interface=ether2 hw=yes pvid=20 ingress-filtering=no
- if tagged packet with vlan id 30 will enter this port it'll be still processed and directed to bridge (if port belongs to bridge)
d) what means ingress-filtering for bridge (if it is already defined for bridge ports)