I was able to set a static default route in a hAP lite running v6.49.2 with no issues. The route became active and it was forwarding traffic successfully.
However when I try doing the same in v7.1.1 the route stays “filtered”, traffic is not forwarded and the route disappears after a few minutes. I have global IPv6 addresses set on my WAN port and LAN bridge, with a /64 prefix (advertised) on the LAN side and /127 on the WAN side (not advertised) for a point-to-point connection with my ISP’s gateway, as instructed by them. Same thing happens on both my hAP lite and RB5009 running v7. I didn’t change any of the default settings when adding the route in ROS v6 or v7.
The added static route does not show up in the output of “/routing/route/print detail”, nor in “/ipv6/route/print detail”.
In the output of “export” the action of adding it shows up as “add disabled=no dst-address=/0 gateway=(my IPv6 gateway’s address)”.
Addition:
When I click the “plus” icon in WinBox /IPv6/Routes I see “filtered” at the bottom of the new window from the very start, before putting anything in or applying.
In a desperate attempt, I tried adding general “accept” rules for “input” and “forward” in /IPv6/Firewall, however static route is still filtered.
So far you didn’t post any concrete diagnostic information for the rest to work on. So post output of /ipv6/address/export, /ipv6/route/export and /ipv6/route/print as starting point.
When you add and apply a static route using the GUI, the destination address is preset to “::/0”. HOWEVER, afterwards, in the output of “/ipv6/route/export” in terminal it shows “dst-address=/0”! Adding a static route in terminal with a destination address “::/0” works and the route becomes active.
This is a software bug.
RB5009UG+S+ (arm64)
RouterOS v7.1.2