Have any of you ever had issues with RouterOS looking in the main routing table for entries that are in a VRF?
e.g. After creating a bgp instance and specifying the routing table to use and also having the interface in a VRF, when i try to bring up the peer, it gets stuck on connect. Logs reveal "there is no route to host"... meaning its looking for the peer in the main routing table instead of in the VRF. This a /30 address i can ping the two routers over the VRF but somehow BGP though the VRF has been specified in the instance, still looks in the main Routing Table.
Had a similar problem after changing the next-hop address of a route learnt via VPNv4 to be that of the tunnel interface on the other end of the VRF. Next-hop is added and exists in the VRF routing table, but RouterOS still tries to look for the nexthop in the main routing table instead of the VRF table.
All this works flawlessly on Cisco IoS