Bridge Configuration works (but not really)!

So I recently upgraded (for a second time) my main router to v7.1.1 and have a weird problem.

I have RB3011 with two bridge chips and I want to put both to use. My configuration works as expected on ROS6 and also works when a router is upgraded to ROS7.
However, If I reset the router and try to configure the same configuration, suddenly the bridges can’t talk to each other anymore.

A few highlights: I add ports ether3-ether5 to bridge 1 which is used as a CAPsMAN datapath. ports ether6-ether10 are added to a second bridge which is used to connect hardwired devices. I know it has to be something very very obvious because the configuration works on ROS6 and even works when the router is upgraded to ROS7 but only fails due to my own lack of understanding.

I’d be really thankful if someone could point me to what’s missing between my configuration(s) that is causing the bridges to be unable to talk to each other.
I do not have any VLANS or Firewall Rules to block bridges from communicating.

I’ve attached two rsc files the problem export is one that doesn’t work.

Any pointers are highly appreciated.
my_problem_export.rsc (5.75 KB)
my_backup_export.rsc (7.91 KB)

It’s not what you’re missing, it’s what you have extra, namely your two brand new PCC rules, they apply also to connections between local subnets, and those packets are sent to internet as a result.

I was using PCC for failover on v6 without any issue. I configured PCC as per https://help.mikrotik.com/docs/display/ROS/Firewall+Marking#FirewallMarking-LoadBalancingWithPerConnectionClassifier

Is there something that’s missing from the above guide?

It doesn’t explicitly mention multiple LAN subnets, but if you pay attention, you should be able to figure out that you have to exclude them too (at the beginning):

/ip firewall mangle
add action=accept chain=prerouting dst-address=10.20.20.0/24 in-interface-list=LAN
add action=accept chain=prerouting dst-address=10.10.10.0/24 in-interface-list=LAN

Thanks for the suggestion, I’ll give it a try tomorrow.

Thanks for your help, your suggestion has solved the issue and given me a new perspective towards RouterOS :slight_smile: