I just had the most disappointing experience with Mikrotik support: For months I have had a ticket regarding route leaks with /bgp/vpn not working across VRFs. I provided a detailed problem description, full supout.rif and after a few rounds the answer is just "We still cannot repeat the problem". This is so disappointing and seemingly there isn't even any interest in fixing a potential bug.
I am also starting to self-doubt myself ... is there an obvious reason this shouldn't even work? And Mikrotik doesn't even bother to mention it?
So I'm hoping someone from the community has mercy and can confirm/disconfirm:
Two VRFs: vrf-fiber contains the internet uplink (via vlan2) and vrf-main contains the rest:
[admin@SunGate2] > /ip/vrf/print
Flags: * - BUILTIN
0 name="vrf-main" interfaces=vlan99,vlan4,vlan3,vlan10,vlan11,vlan12,vrrp3,wg-mobile,vrrp12,vrrp11,vrrp99,vrrp4,xvrf-main
1 name="vrf-fiber" interfaces=vlan2,xvrf-fiber
2 * name="main" interfaces=all
vrf-main has a default route leak:
[admin@SunGate2] > /ip/route/print where routing-table=vrf-main
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, s - STATIC, o - OSPF, d - DHCP
Columns: DST-ADDRESS, GATEWAY, ROUTING-TABLE, DISTANCE
DST-ADDRESS GATEWAY ROUTING-TABLE DISTANCE
DAd 0.0.0.0/0 135.180.56.212@vrf-fiber vrf-main 100
[...]
For return packets coming back from the internet, vrf-fiber needs to have routing entries for each network in vrf-main. As an example, let's take vlan3 (10.227.79.0/24). If I put a static route leak in the routing table everything works as expected:
[admin@SunGate2] > /ip/route/print where routing-table=vrf-fiber
Flags: D - DYNAMIC; A - ACTIVE; c - CONNECT, s - STATIC, d - DHCP
Columns: DST-ADDRESS, GATEWAY, ROUTING-TABLE, DISTANCE
DST-ADDRESS GATEWAY ROUTING-TABLE DISTANCE
DAd 0.0.0.0/0 135.180.56.212@vrf-fiber vrf-fiber 1
1 As 10.227.79.0/24 vlan3@vrf-main vrf-fiber 1
DAc 135.180.56.212/22 vlan2@vrf-fiber vrf-fiber 0
DAc 172.18.0.0/24 xvrf-fiber@vrf-fiber vrf-fiber 0
[...]
From a random station in vlan3/vrf-main, e.g. 10.227.79.104, I can ping www.kernel.org (151.101.129.55) without issues and the packet sniffer confirms it too:
Then I remove the static route and use /bgp/vpn instead:
[admin@SunGate2] > /routing/bgp/export
2026-11-07 14:44:22 by RouterOS 7.25.1
system id = ***********
/routing bgp instance
add as=64513 disabled=no name=bgp-rtleaks
/routing bgp vpn
add export.redistribute=connected .route-targets=64513:100 import.route-targets=64513:101,64513:102 instance=bgp-rtleaks label-allocation-policy=per-vrf name=vrf-main route-distinguisher=64513:1 vrf=vrf-main
add export.redistribute=connected .route-targets=64513:101 import.route-targets=64513:100 instance=bgp-rtleaks label-allocation-policy=per-vrf name=bgp-mpls-vpn-2 route-distinguisher=64513:3 vrf=vrf-fiber
The routes look ok in the main table:
/routing route print detail where routing-table=main afi=vpnv4
[…]
Ay afi=vpnv4 contribution=active dst-address=10.227.79.0/24&64513:1 routing-table=main label=136 gateway=vlan3@vrf-main
immediate-gw=vlan3 distance=200 scope=40 target-scope=30 belongs-to="vrf-main-connected-export"
bgp.ext-communities=rt:64513:100 .origin=incomplete
debug.fwp-ptr=0x203043C0
However, in vrf-fiber’s table something fails and the intermediate gateways are not resolved properly (you can see gateway=vrf-main@vrf-main and intermediate-gw=vrf-main which doesn't look right, IMO it should be **vlan3@**vrf-main as in the output above):
/routing route print detail where routing-table=vrf-fiber
y afi=ip contribution=best-candidate dst-address=10.227.79.0/24 routing-table=vrf-fiber gateway=vrf-main@vrf-main
immediate-gw=vrf-main distance=200 scope=20 target-scope=10 belongs-to="bgp-mpls-vpn-2-vrf-main-connected-export-import"
bgp.ext-communities=rt:64513:100 .origin=incomplete
route-distinguisher="64513:1"
debug.fwp-ptr=0x203047E0
Now needless to say, the moment I disable the static route and use /bgp/vpn, ping starts to timeout. In the packet sniffer it's clearly visible than the ping reply arrives at vlan2@vrf-fiber and is then sent to vrf-main interface:
In my opinion, it should go to vlan3 (vlan2@vrf-main), not vrf-main itself. Mikrotik is even unwilling to confirm that.
Please, has anyone used /bgp/vpn and can confirm it works? If yes, anything that could explain the issue I am seeing?

