V7.1 recursive routes

ZackP · August 15, 2020, 5:43pm

Hi, I have a problem with USB LTE Huawei E3372 with my mikrotik RB750Gr3. After search a lot in this and others forums I found only one solution and this is to update to last version 7.1.

I do it but I have a new problem, in older version I put recursive routes to do a failover. LTE its a backup connection. But the two routes with 0.0.0.0 destination address have the invalid tag and are in red color.

Someone can help me? Thanks.

/ip route
add check-gateway=ping distance=1 gateway=9.9.9.9
add distance=2 gateway=1.1.1.1
add distance=1 dst-address=1.1.1.1/32 gateway=192.168.8.1 scope=10
add distance=1 dst-address=9.9.9.9/32 gateway=192.168.1.1 scope=10

neutronlaser · August 23, 2020, 3:59pm

I wish I could flash mine

raimondsp · August 26, 2020, 5:35am

What are IP addresses assigned to the router interfaces? Please show us the output of

/ip route print detail

mrz · August 31, 2020, 11:34am

Adjust scopes correctly.

/ip route
add dst-address=9.9.9.9/32 gateway=192.168.1.1 scope=11 target-scope=10
add gateway=9.9.9.9 target-scope=11

luxnetwork · August 15, 2021, 4:28pm

I have same problem with recursive routes on development version, are there any solutions for v7.1 beta 6. I will try to attach here screenshots my situation if I use V7 and if I use 6.xx

dave864 · August 18, 2021, 7:40pm

I’ve no idea if you’re setup correctly as mine looks different to yours. But, v7 software routing is not complete and recursive does not work yet - as far as I’m aware.
I’m on long term. V6.47.10 I believe.

rplant · August 19, 2021, 1:16am

I have working recursive routes.

Note:
The route display updating in winbox is flaky, you need to switch to another tab and back to the route tab
to see if things have changed.

/ip route
add check-gateway=ping comment=“check up using optus dns” disabled=no distance=10 dst-address=
0.0.0.0/0 gateway=203.2.75.2 pref-src=“” routing-table=main scope=5 suppress-hw-offload=no
target-scope=20
add check-gateway=ping comment=“for recursive via optus DNS” disabled=no distance=1 dst-address=
203.2.75.2 gateway=192.168.1.1 pref-src=“” routing-table=main scope=5 suppress-hw-offload=no
target-scope=10

add comment=“disallow optus dns except via .1.1” disabled=no distance=100 dst-address=203.2.75.2/32
gateway=nowhere pref-src=“” routing-table=main scope=30 suppress-hw-offload=no target-scope=10

Note: Packets destined for gateway nowhere have a reject with icmp unreachable firewall filter rule on them.

luxnetwork · August 19, 2021, 5:50am

Yes this setup works in lower version, I used same config file on same device but it didn’t work.
Thanks for your answer

I am not sure, I will try your setup schema on my version 7.1beta 6 and I will ping you soon about situation. Thanks

luxnetwork · August 19, 2021, 9:52pm

My apologies, my first setup works recursive routes but I have to waiting longer than usual for back on main route(ISP1) about 3 minutes. I simulated broken internet, I pulled out coaxial cable from border router(ISP1) not direct UTP cable betvine ISP1 and my MT.(this solution works imidietly)
It is works but I must waithing some time for switching gateway ISPs.
Many thanks

Aokiji · December 14, 2021, 7:10pm

good day sitting with the exact problem after upgrading to 7.1 , was working 100% on previous version

bpwl · December 14, 2021, 8:19pm

As @mrz implicitly said: the ROS7 recursive routes have different rules than ROS6 for matching values.

In ROS6: “target scope” must be bigger or equal to “scope”: eg “target scope=10” and “scope=10” do match: "target scope >= “scope”
In ROS7: "target scope must be bigger than “scope” to match: eg “target scope=11” needed to match with “scope=10”: “target scope” > “scope”

target scope=10" is a default value.

Searched, but did not find this in the release notes, wiki or help : http://forum.mikrotik.com/t/recursive-routes/147430/1

Chupaka · December 14, 2021, 8:50pm

Actually, target-scope of next route should be strictly less (or not set, as with connected routes) than target-scope of your route. So, ‘target-scope=10’ does match a route with ‘scope=10’ unless that route has target-scope >= 10

bpwl · December 14, 2021, 8:55pm

Without documentation, one can only reverse engineer, guesswork

What is it now? : http://forum.mikrotik.com/t/recursive-routes/147430/1

Chupaka · December 14, 2021, 8:58pm

Yeah, that’s the topic where I initially commented: http://forum.mikrotik.com/t/recursive-routes/147430/6

bpwl · December 14, 2021, 9:21pm

There even seems more to this recursive route in V7.1 . Did it change from 2020 to 2021? Here (2020) @MRZ shows A , in the other post (2021) it’s B. (target scope > scope)
And there are other changes mentioned in the HELP.

“There are changes in RouterOS v7 nexthop lookup.” : https://help.mikrotik.com/docs/display/ROS/How+Packets+Are+Routed

mducharme · December 14, 2021, 11:26pm

I think target-scope must be greater than the other route’s target-scope is correct. mrz’s response as to why they did that (prevents recursion loops) didn’t really make much sense to me for target-scope needing to be greater than scope. It does make sense if target-scope needs to be greater than target-scope, and I can understand how that would prevent recursion loops.

Aokiji · December 15, 2021, 8:21am

shot thanks guys got it to work again

notice as well that the recursive via x.x.x.x is not showing anymore? not a train smash atleast

i see on the other post similar observations

FelipeGlauber · January 17, 2026, 6:30am

I updated my Mikrotik today from v6 to v7 and I was trying to figure out if it was an error or the new default. It seems to be new default the missing “recursive via x.x.x.x” message.

Thanks community for helping me about new behavior for scope and target scope.