ROS 7.3 ipv6 mangle doesn't work

Hello, I have RB5009 and ROS 7.3.1 installed on it. I have a wireguard tunnel established to remote VPS server. The default route is my ISP gateway. From the external BGP I get thousands of ipv4/ipv6 addresses and they are added to the main routing table with wireguard gateway. This all works fine.

However, I want some manually added addresses to be forcely routed either to ISP or to wireguard tunnel regardless the main routing table. To implement this I’ve done the following steps:

  1. I created 2 additional routing tables (black-list and white-list). White list should go to ISP, black list should go to wireguard tunnel.
  2. I added 2 routing table entries ::/0 for those routing tables with corresponding gateways.
  3. In the ipv6 → firewall → address lists section I added few addresses to the black-list/white-list
  4. In the ipv6 → firewall → mangle I added 2 rules for each list (chain: prerouting, dst address list: , action: mark routing, new routing mark: , passthrough: yes)

But in the traceroute I see that my packets towards addresses from the lists go according to the main routing table, not whilte-list/black-list routing tables. Am I missing something or it’s a ROS bug?

BTW, the same setup works well for ipv4.

I have the same issue , ipv6 mangle uses only main routing table. And I’m on 7.8 stable ( using rb5009 ).

same here
http://forum.mikrotik.com/t/routing-table-parameter-for-ipv6-routes-not-in-effect-v7-5/161488/1
no reply from mikrotik yet

One year later, v7.13.4, and it still doesn’t work.