MikroTik

Policy routing is very cumbersome adding all directly connected subnets to main table manually. Mikrotik should have local table lookup to make it easy.

Policy routing is very cumbersome adding all directly connected subnets to main table manually. Mikrotik should have local table lookup to make it easy.

I agree that the policy routing with mangle table is quite cumbersome (route-map is so handy in Cisco). I've never been successful trying to set up a "management VRF" for instance, because ROS just doesn't want to look into a VRF routing table when originating management traffic packets.

However, if you were to just place all connected routes into all tables (as in this feature request), that would horribly break the entire concept of private routing tables. You may very well be splitting up a router such that interfaces 1&2 are in routing table 1 and interfaces 3,4,&5 are in routing table 2. It would be frustrating if after doing this, all 5 ports could still see each other.

There is always a use case. I have a ccr with two connections in a active active setup and the mangle rules combined with 3 routing tables is massive. The cisco route-map option and vrf configurations are so easy. Ideally if i could configure the ccr the same way with ports 1-4 in an instance and the rest of the ports in another like two virtual routers would be the best way. Or two separate routers but that is a great waste of router ports and performance.

There is always a use case. I have a ccr with two connections in a active active setup and the mangle rules combined with 3 routing tables is massive. The cisco route-map option and vrf configurations are so easy. Ideally if i could configure the ccr the same way with ports 1-4 in an instance and the rest of the ports in another like two virtual routers would be the best way. Or two separate routers but that is a great waste of router ports and performance.

Try looking into the IP > Route > Rules
You can set rules there which force lookup in specific tables / standard table / etc - based on ingress interface, etc.
It looks a lot more like route maps when you use this.