Hello fellow members

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.

I have tried searching for an existing thread.

I must be doing something wrong. Thank you.

It's interesting, because AFAIK it should not work in v6:

You can assign /127 address and it works, however there is a problem if this address is used as gateway. Gateways from /127 addresses cannot be resolved.

But it should work in v7:

... /127 is suppoerted and works in ROSv7

And my quick test confirms both.

I also have the exact problem. Default route shows as filtered and disappeared in seconds. ROS 7.1

"filtered" means that route was rejected by your routing filters.

There is no filters in my router.

If you have specified filter chain in the and did not add any rules then by default chain rejects everything.

If you have specified filter chain in the and did not add any rules then by default chain rejects everything.

----------------------------------------------^^^ in the WHAT?

Routing filters are applied to automatic routing protocols, not to static routes, right?

Static route cannot be filtered. Please send output of "/routing/route/print detail" where it shows that static route is filtered.

Static route cannot be filtered. Please send output of "/routing/route/print detail" where it shows that static route is filtered.

Thank you for your reply.

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.

I was also facing exact same problem. I forced to downgrade. It works well on latest ROS version 6.

I have upgraded to ROS v7.1.2 - issue persists.

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.

FOUND IT!

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

Thank you all for your replies.