I have route to 10.150.45.0/24(getting from BGP) in vrf vrfTest1.
I was able to leak this route into vrf vrfTest2.
However "Immediate Gateway" for this route in vrf vrfTest2 is unknown, the host in 10.150.45.0/24 is not reacheble.
When I create static route to 10.150.45.0/24 everythink works.
RouterOS v7.14, 7.15beta no changes
What is wrong?

without adding a static route, can u ping the other end?

without adding a static route, can u ping the other end?

no, as I already mentioned "the host in 10.150.45.0/24 is not reacheble." Static route works, BGP route doesn't work

Just trying to change BGP to OSPF, everything works fine, it seems it is BUG

I would say that it is misconfiguration. VPNv4 requires at least LDP, otherwiseVPNv4 MPLS label cannot be resolved.

I would say that it is misconfiguration. VPNv4 requires at least LDP, otherwiseVPNv4 MPLS label cannot be resolved.

I just need dynamic VRF-lite route leaking on the local router https://help.mikrotik.com/docs/pages/vi ... uteleaking
Is it working with BGP routes?

VPNv4 works perfectly fine on v7

i have the same scenario, bgp route leak for vrf lite, unable to reach, any luck @ericdriver

CHECK ATTACHMENT

SCENARIO IS SIMPLE

I HAVE SEVERAL VRF-LITE, SAY A VRF-A, I HAVE SEVERAL ROUTES LEARNED FROM iBGP
This iBGP routes successfully exported to another VRF-B, using /routing/bgp/vpn.

Routing table show all reachable, but while pinging the destination with specific source IP, is says invalid arguement(status:22)

0 22 (Invalid argument)
1 22 (Invalid argument)
2 22 (Invalid argument)
3 22 (Invalid argument)

7.15.2
simplest way i could route leak (to effectively append BGP AS) was with inter-VRF BGP peering. or at least for ipv4.
both 172.16.0.0 and .1 can ping each other and BGP peering is successful.
however, exact same setup doesn't work for ipv6, ping returns "hop limit exceeded" but only when trying to ping from VRF AS65001 to main VRF, the other way around does ping.
is this a known bug or do i need to do something extra?
i'm assuming it's a bug since it only pings one-way if i don't specify the source. if i do it doesn't ping.

> ping 172.16.0.1 src-address=172.16.0.0
SEQ HOST SIZE TTL TIME STATUS
0 172.16.0.1 56 64 38us

> ping 172.16.0.0 src-address=172.16.0.1 vrf=AS65001
SEQ HOST SIZE TTL TIME STATUS
0 172.16.0.0 56 64 45us

> ping fd00::1 src-address=fd00::
SEQ HOST SIZE TTL TIME STATUS
0 fd00:: 104 64 124us hop limit e...

> ping fd00:: src-address=fd00::1 vrf=AS65001
SEQ HOST SIZE TTL TIME STATUS
0 fd00:: 104 64 52us hop limit e...

the weird ones indicating a bug, since ipv4 works the same just fine even without specifying src address.

> ping fd00::1
SEQ HOST SIZE TTL TIME STATUS
0 fd00::1 56 64 33us echo reply

> ping fd00:: vrf=AS65001
SEQ HOST SIZE TTL TIME STATUS
0 fd00:: timeout