Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-04-27 | Revert "bgp: T3734: only support "l2vpn-evpn advertise-all-vni" in default VRF" | Christian Breunig | |
This reverts commit bfe57cf80f4c71236f0885408d704a69575f0b30. | |||
2023-04-17 | bgp: T3734: only support "l2vpn-evpn advertise-all-vni" in default VRF | Christian Breunig | |
2021-05-06 | vrf: bgp: T3523: add route-map support for kernel routes | Christian Poessinger | |
2021-04-29 | bgp: xml: T2387: restructure include files and make them easier to recognize | Christian Poessinger | |
2021-04-08 | bgp: T2271: zebra route-map can only be set for default VRF | Christian Poessinger | |
2021-03-29 | bgp: T1711: remove ASN tagNode and move to "local-as" | Christian Poessinger | |
Every time when set configuration bgp, you need set AS number. There is very less benefit in this system so the AS number is moved from a tagNode level down to a leafNode with the name "local-as", same as on the neighbor or peer-group level. This changes the CLI configuration from: set protocols bgp 100 neighbor 10.10.1.2 remote-as 200 to set protocols bgp local-as 100 set protocols bgp neighbor 10.10.1.2 remote-as 200 | |||
2021-03-14 | vrf: bgp: T2271: create individual BGP process for specified VRF name | Christian Poessinger | |
The following VyOS CLI config vrf red { bgp 100 { neighbor 1.1.1.1 { peer-group foo } peer-group foo { passive password bar remote-as 200 } } } Will generaste the FRR configuration: ! router bgp 100 vrf red no bgp ebgp-requires-policy no bgp network import-check neighbor foo peer-group neighbor foo remote-as 200 neighbor foo password bar neighbor foo passive neighbor 1.1.1.1 peer-group foo ! | |||
2021-03-14 | vrf: bgp: T2271: re-arrange xml include building blocks | Christian Poessinger | |
As the amount of include files now has reached a certain amount, this also introduces "per topic" subdirectories on the filesystem to keep a clean structure. This commit is related to the change in the OSPF structure done in 952c52ef01 ("vrf: ospf: T2271: re-arrange xml include building blocks"). | |||
2021-03-10 | bgp: evpn: T1513: add support for per VNI route-distinguished and route-target | Christian Poessinger | |
set protocols bgp 65010 address-family l2vpn-evpn vni 100 route-target both 516:10516 set protocols bgp 65010 address-family l2vpn-evpn vni 100 rd 192.168.0.1:514 Todo: add verify() step to check if at least one evpn enabled BGP neighbor exits, else FRR will error out with: This command is only supported under EVPN VRF | |||
2021-03-08 | bgp: T3391: migrate old IPv4 only maximum-paths config to new syntax | Christian Poessinger | |
2021-03-07 | bgp: T3391: add per AFI maximum-paths support | Christian Poessinger | |
* set protocols bgp ASN address-family ipv4-unicast maximum-paths * set protocols bgp ASN address-family ipv4-unicast maximum-paths-ibgp * set protocols bgp ASN address-family ipv6-unicast maximum-paths * set protocols bgp ASN address-family ipv6-unicast maximum-paths-ibgp | |||
2021-02-27 | smoketest: bgp: T2100: fix "simple" testcase for ebgp-requires-policy | Christian Poessinger | |
Commit 4bf55f97 ("BGP: T2100: Adding RFC8212 option toggle.") added a CLI option to enable RFC8212 ebgp-requires-policy checks. The extended smoketests assumed that this will lead to an FRR configuration line of "bgp ebgp-requires-policy" - which is not the case as this is a default option and FRR hides default options from the config. In order to properly verify this functionality we must conduct the negative test and ensure the option is not present in the CLI at all. | |||
2021-02-26 | Merge pull request #744 from Cheeze-It/current | Christian Poessinger | |
bgp: T2100: Changing RFC8212 behavior and option toggle | |||
2021-02-26 | BGP: T2100: Adding RFC8212 option toggle. | Cheeze_It | |
In this commit we add the default operation within BGP to have RFC8212 disabled for eBGP routes. This default should preserve the normal behavior for VyOS from earlier releases of FRR to the current latest release. Another option that we add is the ability to toggle whether or not RFC8212 is enabled or disabled. | |||
2021-02-23 | routing: T3211: Add redistribute protocol IS-IS to bgp ospf rip | sever-sever | |
2021-02-14 | bgp: T1513: add per VNI advertise-default-gw, advertise-svi-ip options | Christian Poessinger | |
2021-02-14 | bgp: T2844: add IPv4 disable-send-community support | Christian Poessinger | |
2021-02-14 | bgp: T3308: add graceful-shutdown option | Christian Poessinger | |
2021-02-14 | bgp: T1513: make vni a multi node | Christian Poessinger | |
2021-02-13 | bgp: T1513: extend supported evpn support/cli options | Christian Poessinger | |
Add CLI options for: - advertise-pip - rt-auto-derive - flooding - rd - route-target | |||
2021-02-09 | bgp: T1513: initial implementation of L2VPN EVPN support | Christian Poessinger | |
2021-02-05 | xml: add new common "interface-name" validator | Christian Poessinger | |
2021-01-23 | bgp: T2174: proper use ipv4net/ipv6net value helpers | Christian Poessinger | |
2021-01-22 | bgp: T1875: update CLI description under protocols and template indention level | Christian Poessinger | |
2021-01-21 | Merge pull request #690 from Cheeze-It/current | Christian Poessinger | |
bgp: T1875: Adding BGP listen range FRR feature | |||
2021-01-20 | bgp: T1875: Adding BGP listen range FRR feature | Cheeze_It | |
In this commit we are adding the FRR BGP listen range feature. Specifically it is useful for being able to specify a range in which BGP peers can connect to the local router. | |||
2021-01-16 | bgp: T3222: Fix help descriptions for dampening | sever-sever | |
2021-01-14 | bgp: T2174: enable new implementation | Christian Poessinger | |
2021-01-13 | bgp: T2174: xml cleanup, re-use more includable snippets | Christian Poessinger | |
2021-01-13 | bgp: T2174: bugfix FRR template generation | Christian Poessinger | |
2021-01-12 | bgp: T2387: single-source xml templates to improve reusability | Christian Poessinger | |
2021-01-12 | bgp: T2387: Fix template for bgp redistribute proto ospv3 | sever-sever | |
2020-12-27 | xml: fix valueHelp format strings | Christian Poessinger | |
A pre-defined list of common format strings to be used inside the <format> node of <valueHelp> is available from [1]. Adjust all currently in use <format> nodes to re-use the predefined strings over writing them on their own by even encapsulating the <> signs as < and >. [1]: https://github.com/vyos/vyatta-cfg/blob/5aec1a0429f2f/etc/bash_completion.d/vyatta-cfg#L515-L566 | |||
2020-12-12 | xml: use "u32:" keyword when identifying port ranges | Christian Poessinger | |
This will render the completion help more nicely. | |||
2020-11-03 | bgp-xml: T2387: Fix validators for neighbor update-source | sever-sever | |
2020-11-02 | bgp-xml: T2387: Fix validators and add capability for new format bgp | sever-sever | |
2020-10-27 | bgp: T2387: Fix XML sheme for new bgp and bgp.py handler | sever-sever | |
2020-06-01 | bgp: T2387: move "aggregate address" to XML include | Christian Poessinger | |
2020-05-26 | bgp: xml: T2387: fix warning: missing terminating ' character | Christian Poessinger | |
2020-05-19 | bgp-xml: T2387:Commands in XML for [conf_mode] bgp | sever-sever | |