Are you saying that when you turn on vlan-filtering, that vlan200 access ports on the switches do not work? It seems to me it should allow vlan 200 to work through vlan 200 access ports on the downstream switches.If I turn on VLAN filetring on Bridge --> situation turns 180 degress.
ethr1 to ethr4 works normally and gives DHCP addresses, and Trunk side just dies and doesnt want to give anything.
When you turn on vlan-filtering, you are making the bridge "vlan-aware", and it will no longer be "vlan-transparent". This means that any traffic from vlan-interfaces (which are adding tag to the frames) will be dropped by the bridge unless those vlans are specifically allowed with an /interface bridge vlan entry for the vlan. The following is what you currently have:
Code:
/interface bridge vlanadd bridge=TrunkBridge tagged=TrunkBridge,ether5,ether6,ether7,ether8 \ untagged=ether1,ether2,ether3,ether4 vlan-ids=200
Code:
/interface bridge vlanadd bridge=TrunkBridge tagged=TrunkBridge,ether5,ether6,ether7,ether8 \ untagged=ether1,ether2,ether3,ether4 vlan-ids=200add bridge=TrunkBridge tagged=TrunkBridge,ether5,ether6,ether7,ether8 \ vlan-ids=100add bridge=TrunkBridge tagged=TrunkBridge,ether5,ether6,ether7,ether8 \ vlan-ids=800add bridge=TrunkBridge tagged=TrunkBridge,ether5,ether6,ether7,ether8 \ vlan-ids=1000
Statistics: Posted by Buckeye — Sat Mar 02, 2024 11:35 am