VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling 2026-06-26T07:28:05+00:00 2026-06-26T07:28:05+00:00 Oleksandr Kuchmystyi o.kuchmystyi@vyos.io 2026-06-26T07:23:54+00:00 urn:sha1:4e11adfb927c22e2f977c897d56a4d243860e877 When `advertise-all-vni` is configured in the global/default BGP instance, VyOS generated a `vni <id>` 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. 2026-06-09T15:41:56+00:00 Nataliia Solomko natalirs1985@gmail.com 2026-05-26T15:27:56+00:00 urn:sha1:b49e8f00560bdbd69f85539396afb6391b281519 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. 2025-10-06T16:03:39+00:00 John Estabrook jestabro@vyos.io 2025-10-06T15:49:34+00:00 urn:sha1:bc73a4f7452434f25119267129f337640d8a959c This reverts commit d871fe9c4c65de87232802ed54b263c9b2824391. 2025-10-06T15:48:48+00:00 John Estabrook jestabro@vyos.io 2025-10-06T15:48:48+00:00 urn:sha1:d238a582e47e89c12b34b010a6a02a07f5099819 This reverts commit 85fe32f0e1a91a47fe4a6d4a5cdd6ac516dcc3b9. 2025-09-09T15:59:58+00:00 Christian Breunig christian@breunig.cc 2025-09-09T15:57:44+00:00 urn:sha1:85fe32f0e1a91a47fe4a6d4a5cdd6ac516dcc3b9 VyOS 1.5 and onwards will no longer have the following CLI node available: set vrf name <name> protocols bgp system-as <asn> 2025-09-09T15:58:26+00:00 Christian Breunig christian@breunig.cc 2025-08-28T12:46:48+00:00 urn:sha1:d871fe9c4c65de87232802ed54b263c9b2824391 Originating from the bug in T7665. To avoid potential issues down the line - and given that there's no compelling technical reason to retain the system-as CLI node under per-VRF BGP configuration, which cannot be achieved through alternative means - the maintainers have collectively decided to deprecate the following command: set vrf name <name> protocols bgp system-as <asn> Starting with VyOS 1.4.4, this CLI command will be considered deprecated. While it will still be accepted, it will no longer have any operational effect. A deprecation warning will be displayed at commit time, indicating that the BGP ASN from the global BGP configuration is now used instead. A migration script will handle the transition and perform the following actions: * Ensure a global BGP configuration exists; if not, initialize one. * Iterate over all configured VRFs to determine whether a BGP instance exists * For any insance, update the configuration to use the global system-as and apply the local-as ASN no-prepend replace-as option on all affected neighbors to preserve existing behavior. * If a neighbor is already configured with a local-as directive, that neighbor will be excluded from the migration process, as it already follows a custom configuration. * Add allowas-in per neighbor option. Required to not deny prefix received updates due to as-path contains our own global ASN. 2025-02-13T19:39:54+00:00 Christian Breunig christian@breunig.cc 2025-02-13T19:39:14+00:00 urn:sha1:6ab9de170c7a4ad51b60ed0c576db25831ce745a * set protocols bgp address-family <ipv4-unicast|ipv6-unicast> redistribute table <n> [metric <n>] [route-map <name>] 2024-02-01T10:18:50+00:00 aapostoliuk a.apostoliuk@vyos.io 2024-02-01T09:55:47+00:00 urn:sha1:32a13411f47beffcbe4b49a869c99cb42374d729 Denied using command 'route-target vpn export/import' with 'both' together in bgp configuration. 2023-04-13T07:01:31+00:00 Christian Breunig christian@breunig.cc 2023-04-12T19:11:50+00:00 urn:sha1:7d642a2862dcd0c7c2f80ac42ea9427970804d06 2022-07-30T19:45:12+00:00 Cheeze_It none@none.com 2022-07-20T01:11:05+00:00 urn:sha1:967c53e2f3e4a7ae36577ba28dd60046909224dc bgp: T4257: Changing BGP "local-as" to "system-as" This change is to change the global BGP name for the node "local-as" to "system-as" This is needed so that there's less ambiguity with the local-as feature per neighbor. bgp: T4257: Changing BGP "local-as" to "system-as" bgp: T4257: Changing BGP "local-as" to "system-as" This change is to change the global BGP name for the node "local-as" to "system-as" This is needed so that there's less ambiguity with the local-as feature per neighbor.