BGP supplied route marked unreachable

RouterOS Forwarding Protocols
1

I’m trying to redistribute routes to our internal devices - but as the routes are all marked as unreachable they are not being advertised.

41404  Db  dst-address=2c0f:fd90::/32 gateway=2001:19f0:ffff::1 gateway-status=2001:19f0:ffff::1 unreachable distance=20 scope=40 target-scope=30 bgp-as-path="64515,20473,17819,2914,3356,37084,37185" bgp-origin=igp 
        bgp-communities=64515:44 received-from=peer6_vultr 

41405  Db  dst-address=2c0f:fda8::/32 gateway=2001:19f0:ffff::1 gateway-status=2001:19f0:ffff::1 unreachable distance=20 scope=40 target-scope=30 bgp-as-path="64515,20473,17819,4826,6939,37349" bgp-origin=igp 
        bgp-communities=64515:44 received-from=peer6_vultr 

41406  Db  dst-address=2c0f:fdb0::/48 gateway=2001:19f0:ffff::1 gateway-status=2001:19f0:ffff::1 unreachable distance=20 scope=40 target-scope=30 bgp-as-path="64515,20473,17819,2914,37100,33765" bgp-origin=igp 
        bgp-communities=64515:44 received-from=peer6_vultr 

41407  Db  dst-address=2c0f:fdc0::/32 gateway=2001:19f0:ffff::1 gateway-status=2001:19f0:ffff::1 unreachable distance=20 scope=40 target-scope=30 bgp-as-path="64515,20473,17819,2914,6453,36930" bgp-origin=igp 
        bgp-communities=64515:44 received-from=peer6_vultr 

41408  Db  dst-address=2c0f:fdc8::/32 gateway=2001:19f0:ffff::1 gateway-status=2001:19f0:ffff::1 unreachable distance=20 scope=40 target-scope=30 bgp-as-path="64515,20473,17819,4826,6939,37105,37049" bgp-origin=igp 
        bgp-communities=64515:44 received-from=peer6_vultr

Is there a way I can ignore the fact the router thinks they are unreachable?

Is there a way I can convince the router they are reachable? (it all works, and the next hop is reachable)

/ping 2001:19f0:ffff::1
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                                                                                 
    0 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    1 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    2 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    3 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    4 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    5 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    6 2001:19f0:ffff::1                          56  64 0ms   echo reply                                                                                                                                                             
    sent=7 received=7 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
2

If this is for recursive routing, you need to manually add a static route in the tables for the gateway IP address. MT doesn’t do recursive routing correctly in IPv6, it’s a known bug.

3

@savage it does not apply in this case. Recursive routing does not work only with link-local gateways.

@troykelly See here to solve your problem
https://wiki.mikrotik.com/wiki/Manual:Using_scope_and_target-scope_attributes

4

I beg to differ…

[cknipe@WCLH-BR01.cpt.za.as203319.net] > /ipv6 route print detail where gateway=2a07:b2c5::3    
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable 
 0 ADb  dst-address=2002::/16 gateway=2a07:b2c5::3 gateway-status=2a07:b2c5::3 recursive via 2a07:b2c5::61 GRE - SMARTDC-BR01.rtd.nl distance=200 scope=40 target-scope=30 bgp-as-path="6939" 
        bgp-local-pref=1000 bgp-med=0 bgp-origin=igp bgp-communities=65000:4703 received-from=AS203319v6 - WCLH-CR01.cpt.za 

 1 ADb  dst-address=2026:10c:6003::/48 gateway=2a07:b2c5::3 gateway-status=2a07:b2c5::3 recursive via 2a07:b2c5::61 GRE - SMARTDC-BR01.rtd.nl distance=200 scope=40 target-scope=30 
        bgp-as-path="6939,34224,51830" bgp-local-pref=1000 bgp-med=1 bgp-origin=igp bgp-communities=65000:3020 received-from=AS203319v6 - WCLH-CR01.cpt.za 

 2 ADb  dst-address=2400:1000::/32 gateway=2a07:b2c5::3 gateway-status=2a07:b2c5::3 recursive via 2a07:b2c5::61 GRE - SMARTDC-BR01.rtd.nl distance=200 scope=40 target-scope=30 bgp-as-path="6939,10021" 
        bgp-local-pref=1000 bgp-med=1 bgp-origin=igp bgp-communities=65000:3020 received-from=AS203319v6 - WCLH-CR01.cpt.za 
.....

[cknipe@WCLH-BR01.cpt.za.as203319.net] > /ipv6 route disable [ /ipv6 route find where dst-address=2a07:b2c5::3 ]
[cknipe@WCLH-BR01.cpt.za.as203319.net] > 
[cknipe@WCLH-BR01.cpt.za.as203319.net] > /ipv6 route print detail where gateway=2a07:b2c5::3
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable 
 0  Db  dst-address=2002::/16 gateway=2a07:b2c5::3 gateway-status=2a07:b2c5::3 unreachable distance=200 scope=40 target-scope=30 bgp-as-path="6939" bgp-local-pref=1000 bgp-med=0 bgp-origin=igp 
        bgp-communities=65000:4703 received-from=AS203319v6 - WCLH-CR01.cpt.za 

 1  Db  dst-address=2026:10c:6003::/48 gateway=2a07:b2c5::3 gateway-status=2a07:b2c5::3 unreachable distance=200 scope=40 target-scope=30 bgp-as-path="6939,34224,51830" bgp-local-pref=1000 bgp-med=1 
        bgp-origin=igp bgp-communities=65000:3020 received-from=AS203319v6 - WCLH-CR01.cpt.za 
...

Not only link locals… It’s a sad, sad day when MT does not even know the extent of their own bugs.

5

I have a similar problem.

With HE.net and NetAssist I make BGP by tunnel method. At the same time, I start a direct BGP session with Vultr.

The Full Table from Vultr is unfortunately listed as “unreachable”.

Could you support this issue?

6

Probably you need to resolve gateway recursively, but for it to work properly it must be resolved over route with global address (link local will not work).

7

@mrz @savage I am facing same issue with vultr. Please help me.

8

for ipv6 recursive routing we use route filters and set the next hop link local gateways with a check gateway ping. That way if one of the paths goes down it doesn’t blackhole traffic and it’s still dynamic (we dont use static routes unless absolutly neccessary).

9

So I can use the link local of eth1 interface as next hop using filter and remove the static route to the peer ip of vultr?