Anyone using /bgp/vpn across VRFs and can confirm it works? Mikrotik won't

Thanks the both of you!

I was able to create a minimum config that fully reproduces the issue (Note: this is a full configuration that reproduces the issue).

/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no
set [ find default-name=ether2 ] disable-running-check=no
/interface list
add name=WAN
/ip vrf
add interfaces=ether2 name=vrf-main
add interfaces=ether1 name=vrf-fiber
/routing bgp instance
add as=64513 name=bgp-rtleaks
/interface list member
add interface=ether1 list=WAN
/ip address
add address=10.99.0.2/24 interface=ether1 network=10.99.0.0
add address=192.168.10.1/24 interface=ether2 network=192.168.10.0
/ip firewall filter
add action=passthrough chain=forward in-interface=vrf-fiber log=yes log-prefix="PASS1 "
add action=passthrough chain=forward in-interface=vrf-main log=yes log-prefix="PASS2 "
add action=accept chain=forward connection-state=established,related,untracked
add action=drop chain=forward connection-state=invalid log=yes log-prefix=INVALID
add action=accept chain=forward connection-state=new
/ip firewall nat
add action=masquerade chain=srcnat dst-address=10.99.0.0/24 src-address=192.168.10.0/24
/ip route
add dst-address=0.0.0.0/0 gateway=10.99.0.1@vrf-fiber routing-table=vrf-main
add disabled=yes distance=1 dst-address=192.168.10.0/24 gateway=ether2@vrf-main routing-table=vrf-fiber comment="This uses static leak instead of /bgp/vpn to ether2@vrf-main; Works if enabled."
add disabled=yes dst-address=192.168.10.0/24 gateway=ether2@vrf-main routing-table=main comment="This makes the route resolvable via main table. Also works if enabled."
/routing bgp vpn
add export.redistribute=connected .route-targets=64513:100 import.route-targets=64513:999 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=vrf-fiber route-distinguisher=64513:3 vrf=vrf-fiber
  • Client 192.168.10.10 pings 10.99.0.1
  • With a static route leak (if/ip route add distance=1 dst-address=192.168.10.0/24 gateway=ether2@vrf-main routing-table=vrf-fibe is enabled), ping works
  • If it is disabled (and the /bgp/vpn route is selected) is fails
  • Additionally, if /ip route add dst-address=192.168.10.0/24 gateway=ether2@vrf-main routing-table=main is enabled, it works too

My hypothesis: The vrf@vrf syntax results in two routing decisions and this process somehow looses the link to VRF: The second lookup is looked up via "main" which explains why it works if the route can be resolved via "main".

At this point I want to emphasize that the whole point of this is to not use main VRF at all and as a reminder, /bgp/vpn officially does not support main VRF! So if main becomes a requirement to make leak from vrf-main to vrf-fiber work, this whole thing is broken.


Yes it is the same setup (but different issue). SunGate2 is the CHR, SunGate1 the hEX. Thanks for following up on this issue too, it's not resolved yet and still on my TODO list. It's will respond on this in the other thread once I've done more analysis (it's harder for me to debug because every attempt brings down the entire network)

Sadly no change.