- Difficulty level
- Easy (less than an hour)
I will look into it. I think it is feasible to add to 1.x, but we have to think about the cli. We have to treat the default VRF in a way, so it doesn't come in the way of users who don't want/need to use VRFs.
If this will be included, someone has to make deep testing of quagga vrf-related patchset. Looks like it's described here: http://permalink.gmane.org/gmane.network.quagga.devel/11770 but I'm not sure, whether it's included in upstream quagga or not.
Absent full vrf or vrf-lite behavior, there is a means of achieving a subset of this behavior using only iptables.
My principal use case would be the creation of a "Management Interface."
I will bring this up again. We have now in 1.2 all we need.
Kernel 4.18 which can be build with vrf enabled
FRR which can handle VRF
iproute2 which can handle VRF
So we need a kernel build with vrf enabled and have the command templates for it.