Hello everyone, we are currently using several of your switches as part of our backbone infrastructure. To simplify configuration, we are making use of interface lists (e.g., for applying common policies, VLAN configurations). While this approach works well in general, we have got the problem, tha…

[image] freaknils: add bridge=*2D Very likely not related, stiill check point #21 here: [image] GP & CSA (Good Practice and Common Sense Advice) for Mikrotik devices Beginner Basics Preamble and disclaimer: The following is a numbered list of what is us…

Thanks, this was orphaned entry. But I think, that's not the cause of my problem

Well, yes and no. It surely accounts for 27 out of 105 seconds of your cycle, i.e. roughly between 1/4 and 1/3. As I see it, the operation that take the more time (21-27 seconds) is: bridge,info "bridge1" peer becomes primary F4:1E:57:0D:6A:5E and you are executing it three times (and 1 is rela…

Hi thanks for your reply, I think the bridge,info "bridge1" peer becomes primary F4:1E:57:0D:6A:5E comes from my MLAG setup. But why does RouterOS turn off the hardware offloading? In my eyes this is not an expected behaviour. Additionaly: When I add an interface to a interface list, which will…

Bridge restarts on adding an interface list to members

RouterOS

jaclaz April 13, 2026, 9:00am 2

Very likely not related, stiill check point #21 here: