Is it “native” or “trunk”?
In Mikrotik world, “native” translates to “access port” to that VLAN[*] … and MT default config uses VID=1 as well … but it’s untagged over “cpu-facing bridge port” (see te first link below) as well. By trying to use VLAN 1 as if it was tagged (on CPU-facing bridge port), you’re messing around.
Mikrotik’s implementation of VLANs on bridge is a bit … different than other vendors did. So perhaps you’d want to read these two de-facto bibles:
- different bridge personalities: http://forum.mikrotik.com/t/routeros-bridge-mysteries-explained/147832/1
- VLANs on bridge: http://forum.mikrotik.com/t/using-routeros-to-vlan-your-network/126489/1
And I suggest you to read them in indicated order.
[*] native VLAN is actually always transmitted without 802.1Q headers (i.e. untagged) over the link (wire, fiber). Which means that in theory it’s possible to use different VID inside each piece of equipment to deal with it … in practice tough this makes things very confusing. It is perfectly fine to use VID=1 as native VLAN in mikrotik, but one has to be aware of how default config treats VID=1 and change it everywhere. Since it’s default config, it doesn’t get shown by simple /export command (this ocmmand shows only delta to default config), which does make handling of VID=1 quite a bit harder (but not impossible).