The long explanation about how mikrotik resolves recursive routes is documentated at Mikrotik's page.
How can we workaround these issues? Simple. We setup a /32 on the Point-to-Point interface, we setup a direct route to the other peer (using the interface as next-hop for this route) and use bgp filters to change the next-hop interface.
You create the GRE interface in the same way the Mikrotik Guide does.
/interface gre add allow-fast-path=no comment="DN42 somepeer" local-address=126.96.36.199 name=gre-dn42-peer \ remote-address=188.8.131.52
Next you add the /32 address on the interface. You can install this address on a loop interface (on RouterOS this means an empty bridge) if you plan to use the same address over several GRE tunnels or other OpenVPN interfaces.
/ip address add address=172.24.0.1/32 interface=gre-dn42-peer
Next, we add the direct route as next-hop using the interface
/ip route add distance=1 dst-address=172.26.2.2/32 gateway=gre-dn42-peer pref-src=172.24.0.1
At this point, the ping with the peer should work. Also, the bgp session can be established, but the routes will not work. We need a input filter to fix the next-hop routes.
/routing filter add chain=bgp-dn42-peer-in protocol=bgp set-in-nexthop-direct=gre-dn42-peer
if you have other global input chain filters, you should add a jump in the same chain, like this:
/routing filter add action=jump chain=bgp-dn42-peer-in protocol=bgp jump-target=bgp-global-dn42-input
If you haven't created the BGP session, create it now from the Mikrotik guide. Change the peer input filter to use the chain we've just created:
/routing bgp peer set bgp-dn42-somename in-filter=bgp-dn42-peer-in
With this fix, all the routes will have set next-hop the GRE interface and there will be no need to use RouterOS' recursive route resolve.
Check the routes with:
/ip routes print detail where received-from=bgp-dn42-somename
There should an attribute like:
gateway=gre-dn42-peer gateway-status=gre-dn42-peer reachable
Last edited by DN42 Wiki (BURBLE-MNT), 2020-11-29 07:26:21