BUG in ROS 3.3: vlan interfaces aren't runing after boot!

Hello,

RB333, RouterOS 3.3.

I have 3 vlans on wlan1 interface in bridge mode and 3 bridges with
vlanX and etherX in each.

/interface vlan
add arp=enabled comment="" disabled=no interface=wlan1 mtu=1500 name="vlan1" vlan-id=30
add arp=enabled comment="" disabled=no interface=wlan1 mtu=1500 name="vlan2" vlan-id=40
add arp=enabled comment="" disabled=no interface=wlan1 mtu=1500 name="vlan3" vlan-id=50

/interface bridge
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes comment="" disabled=no forward-delay=15s
max-message-age=20s mtu=1500 name="bridge2" priority=0x8000 protocol-mode=none transmit-hold-count=6
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes comment="" disabled=no forward-delay=15s
max-message-age=20s mtu=1500 name="bridge3" priority=0x8000 protocol-mode=none transmit-hold-count=6
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes comment="" disabled=no forward-delay=15s
max-message-age=20s mtu=1500 name="bridge1" priority=0x8000 protocol-mode=none transmit-hold-count=6
/interface bridge port
add bridge=bridge1 comment="" disabled=no edge=auto external-fdb=auto horizon=none interface=ether1 path-cost=10
point-to-point=auto priority=0x80
add bridge=bridge2 comment="" disabled=no edge=auto external-fdb=auto horizon=none interface=ether2 path-cost=10
point-to-point=auto priority=0x80
add bridge=bridge3 comment="" disabled=no edge=auto external-fdb=auto horizon=none interface=ether3 path-cost=10
point-to-point=auto priority=0x80
add bridge=bridge1 comment="" disabled=no edge=auto external-fdb=auto horizon=none interface=vlan1 path-cost=10
point-to-point=auto priority=0x80
add bridge=bridge2 comment="" disabled=no edge=auto external-fdb=auto horizon=none interface=vlan2 path-cost=10
point-to-point=auto priority=0x80
add bridge=bridge3 comment="" disabled=no edge=auto external-fdb=auto horizon=none interface=vlan3 path-cost=10
point-to-point=auto priority=0x80
/interface bridge settings
set use-ip-firewall=no use-ip-firewall-for-vlan=no

Everything works great... but vlan interfaces aren't running after reboot!!!

Flags: X - disabled, R - running, S - slave

NAME MTU ARP VLAN-ID INTERFACE

0 vlan1 1500 enabled 30 wlan1
1 vlan2 1500 enabled 40 wlan1
2 vlan3 1500 enabled 50 wlan1

I have to get up each of them manually or by the script.
Is this feature or bug?

I have found some info in the docs but it's not clear.
"If the interfaces were successfully created, both of them will be running. If computers are connected incorrectly (through network device that does not retransmit or forward VLAN packets), either both or one of the interfaces will not be running."

I have tried to set disable-running-check=yes for wlan1 but it didn't help.

Is it possible to configure vlan interfaces to bring up after reboot?

Now I'm using scheduler as a solution.
/system scheduler
add comment="" disabled=no interval=0s name="schedule1" on-event=":delay 5\r\ninterface vlan enable vlan1\r\ninterface vlan
enable vlan2\r\n" start-time=startup

--
ash

I can’t believe that nobody is interested in solution of this real problem. Even MikroTik staff?

email a supout to support when this is happening… they will fix it if its a bug.

I had the same problem with RB532, RB133C, RB511 ROS 3.2, 3.3 after upgrading from 2.9.50.
The problem was resolved - just delete your vlan & eoip interfaces, reboot and recreate it. After next reboot all should be ok.

Interesting:

What’s new in 3.4:

[…]
*) fixed VLAN on wireless not running after reboot issue;

MT staff has successfully ignored my topic but then fixed this bug. This was at least unfair!

Nevertheless thanks for good job!