vyos-1x.git/interface-definitions/vrf.xml.in, branch circinus-public-unmaintained

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

T5150: initial implementation of new Kernel/Zebra route-map support

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

It is possible to install a route-map which filters the routes between routing daemons and the OS kernel (zebra) As of now this can be done by e.g. * set protocols ospf route-map foo * set protocols ospfv3 route-map foo * set protocols bgp route-map foo Which in turn will install the following lines into FRR * ip protocol ospf route-map foo * ipv6 protocol ospf6 route-map foo * ip protocol bgp route-map foo The current state of the VyOS CLI is incomplete as there is no way to: * Install a filter for BGP IPv6 routes * Install a filter for static routes * Install a filter for connected routes Thus the CLI should be redesigned to close match what FRR does for both the default and any other VRF * set system ip protocol ospf route-map foo * set system ipv6 protocol ospfv3 route-map foo * set system ip protocol bgp route-map foo * set system ipv6 protocol bgp route-map foo The configuration can be migrated accordingly. This commit does not come with the migrator, it will be comitted later.

xml: T1579: merge generic-description.xml.i and interface/description.xml.i

2023-01-07T08:07:40+00:00

No need to have two distinct include blocks as one superseeds the other. Also this makes the entire behavior of "description" CLI node simpler.

xml: reword static routing completion help

2022-05-29T09:48:46+00:00

eigrp: vrf: T2773: prepare XML definitions for VRF instance

2022-05-29T08:14:27+00:00