vyos-1x.git/src/conf_mode/protocols_bgp.py, branch rolling

bgp: T8865: Reject `vni` sub-block in VRF l2vpn-evpn when `advertise-all-vni` is globally active

2026-06-26T07:28:05+00:00

When `advertise-all-vni` is configured in the global/default BGP instance, VyOS generated a `vni ` sub-block under each VRF BGP `address-family l2vpn evpn` context. This conflicts with advertise-all-vni: FRR already owns all kernel VNIs and returns `% Failed to create VNI` when frr-reload.py attempts to apply the VRF-level vni sub-block. FRR then performs an early exit from config processing, silently dropping the entire l2vpn evpn address-family for all subsequent VRF BGP instances.

bgp: T5526: Fix BGP neighbor validation not raising when interface does not exist

2026-06-25T08:28:11+00:00

Validation of interface-based BGP neighbors relied on checking physical interface existence, which silently skipped the check when interface didn't exist yet, letting invalid config reach FRR. Fix by checking whether the neighbor is not an IP address instead, and improve the error messages to show the correct command.

Merge pull request #5231 from natali-rs1985/T8223

2026-06-17T12:36:46+00:00

bgp: T8223: Prevent `advertise-all-vni` in multiple BGP VRF instances simultaneously

T8923: normalize "can not" to "cannot"

2026-06-16T18:24:44+00:00

Replace two-word "can not" / "Can not" with "cannot" across comments, ConfigError messages, CLI help text, and op-mode output. Standard SNMP MIB files under mibs/ are left unchanged.

bgp: T8223: Prevent `advertise-all-vni` in multiple BGP VRF instances simultaneously

2026-06-09T15:41:56+00:00

FRR only allows one BGP instance to hold `advertise-all-vni` at a time (FRR issue #9405). When a default BGP instance is present it is always started before named VRF instances, so if a named VRF holds the flag FRR silently rejects it on every boot (regardless of default EVPN config), causing the running config to diverge from what is stored in VyOS. Enforce the following policy in verify(): - Default BGP instance may always hold `advertise-all-vni`. - A named VRF may hold it only when no default BGP instance exists. - Only one BGP instance (default or named VRF) may hold it at a time. The default BGP verify path additionally scans dependent VRFs so that adding or modifying the default BGP instance while a named VRF already holds the flag is caught even when the VRF node is not part of the current commit.

bgp: T8607: Add CLI support for BGP update-delay and establish-wait

2026-05-11T09:24:43+00:00

T8410: Fix typos and mistakes for operational and configuration commands

2026-03-24T17:02:56+00:00

Fix typos and mistakes in the commands and comments No functional changes

frr: T8034: use dict_search() for routing protocols to check if VRF is used

2025-11-25T15:22:57+00:00

dict_search() is save when passing in keys that do not exist in the dict we are working on.

Revert "bgp: T7760: deprecate per bgp vrf instance system-as node"

2025-10-06T16:03:39+00:00

This reverts commit d871fe9c4c65de87232802ed54b263c9b2824391.

Revert "bgp: T7760: remove per vrf instance system-as node"

2025-10-06T15:48:48+00:00

This reverts commit 85fe32f0e1a91a47fe4a6d4a5cdd6ac516dcc3b9.