vyos-1x.git/interface-definitions/vrf.xml.in, branch rolling

T8041: update comments referring to deprecated priority.pl

2025-11-25T19:22:27+00:00

T7803: Make failover route vrf-aware

2025-10-08T12:07:59+00:00

* Added 'protocol failover' to 'set vrf name': set vrf name red protocols failover route 10.11.0.110/32 next-hop 10.0.0.2 * Added vrf and interface to target: set ... next-hop 10.0.0.2 check target '10.120.0.21' vrf blue set ... next-hop 10.0.0.2 check target '10.120.0.21' interface eth1 Last two are needed when check VRF is not same as route VRF. In this case icmp can use any/both options, tcp requires `vrf` and arp requires `interface`

kea: T6211: add VRF support for KEA dhcp server

2025-08-15T07:31:49+00:00

T7432: RPKI VRF Support

2025-05-28T02:16:00+00:00

vrf: T6189: render FRR L3VNI configuration when creating VRF instance

2024-05-01T18:55:57+00:00

When adding and removing VRF instances on the fly it was noticed that the vni statement under the VRF instance in FRR vanishes. This was caused by a race condition which was previously designed to fix another bug. The wierd design of a Python helper below the VRF tree to only generate the VNI configuration nodes is now gone and all is rendered in the proper place.

xml: T5738: extend VRF building blocks with common constraint definition

2024-04-01T18:27:24+00:00

T6001: add option to disable next-hop-tracking resolve-via-default in VRF context

2024-02-16T07:33:13+00:00

* set vrf name ip nht no-resolve-via-default * set vrf name ipv6 nht no-resolve-via-default

vrf: netns: T3829: T31: priority needs to be after netns

2023-09-30T14:05:02+00:00

A network namespace can have VRFs assigned, thus we need to get the priorities right. This lowers both priorities in general as a VRF or NETNS needs to be available very early as services can run on top of them.

vrf: T5150: l3vni must be removed prior to removing BGP VRF process

2023-04-21T19:21:07+00:00

T5150: initial VRF support for Kernel/Zebra route-map filtering

2023-04-13T07:01:31+00:00