Thank you. I resolved the issue by associating the Layer 3 VLAN with the bridge, making VLAN1 a subinterface of the bridge. I then connected ether1 to the bridge as a port. Following that, I enabled VLAN filtering and configured ether1 to be untagged for VLAN 1, so that packets leaving ether1 have their VLAN 1 tag removed.With your config example the vlan1 is completely useless.
- VLAN is a L2 concept, it has nothing to do with layer 3 from the OSI model.
- Your laptop is on the normal (untagged) broadcast domain
But you set your router on the vlan 1 broadcast domain(thus packets are tagged from ether1)
The devices are in 2 different broadcast domains(L2) this is why they cannot communicate- You cannot bridge a parent interface with its child subinterface(ether1 and vlan1 tied to ether1)
By the way, I believe that what are referred to as Layer 3 VLANs should actually be termed virtual interfaces. However, in MikroTik terminology, virtual interfaces and Layer 2 VLANs share the same designation.
Additionally, I find it peculiar that MikroTik treats the bridge as both a Layer 2 switch and a Layer 3 interface.
Statistics: Posted by ansky — Mon Mar 11, 2024 1:57 pm