summaryrefslogtreecommitdiff
path: root/data/templates/frr/bgp.frr.tmpl
AgeCommit message (Collapse)Author
2021-02-27bgp: T3365: After commit bf9c914 config interface become out of the checksever-sever
2021-02-27bgp: T3365: Fix remote-as ordering for neighborsever-sever
2021-02-26Merge pull request #744 from Cheeze-It/currentChristian Poessinger
bgp: T2100: Changing RFC8212 behavior and option toggle
2021-02-26BGP: 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-21Merge pull request #737 from sever-sever/T3332Christian Poessinger
bgp: T3322: Fix timers for neighbor
2021-02-21bgp: T3322: Fix timers for neighborsever-sever
2021-02-19bgp: T3330: Fix capability orf prefix-listsever-sever
2021-02-16bgp: T2100: always set "no bgp network import-check"Christian Poessinger
In order to keep the current behavior when upgrading from 1.2 -> 1.3 -> 1.4 FRR requires us to set this option. This configuration modifies the behavior of the network statement. If you have this configured the underlying network must exist in the rib (default). If you have the [no] form configured then BGP will not check for the networks existence in the rib. For FRR versions 7.3 and before frr defaults for datacenter were the network must exist, traditional did not check for existence. For versions 7.4 and beyond both traditional and datacenter the network must exist. VyOS uses "traditional".
2021-02-14bgp: T2315: add CLI options for addpath-tx-(all-paths|bestpath-per-AS)Christian Poessinger
* protocols bgp 65000 neighbor 192.0.2.1 address-family ipv4-unicast addpath-tx-all * protocols bgp 65000 neighbor 192.0.2.1 address-family ipv4-unicast addpath-tx-per-as * protocols bgp 65000 neighbor 2001:db8::1 address-family ipv6-unicast addpath-tx-all * protocols bgp 65000 neighbor 2001:db8::1 address-family ipv6-unicast addpath-tx-per-as
2021-02-14bgp: T1513: add per VNI advertise-default-gw, advertise-svi-ip optionsChristian Poessinger
2021-02-14bgp: T2844: add IPv4 disable-send-community supportChristian Poessinger
2021-02-14bgp: T2387: bugfix missing options not added to FRRChristian Poessinger
The following options were not represented in the Jinja2 template: - port - advertisement-interval - strict-capability-match In addition the smoketests have been extended to support IPv6 neighbors, too.
2021-02-14bgp: T3308: add graceful-shutdown optionChristian Poessinger
2021-02-14bgp: T1513: make vni a multi nodeChristian Poessinger
2021-02-13bgp: T2387: bgp_neighbor macro should access address family dict with items()Christian Poessinger
2021-02-13bgp: T1513: extend supported evpn support/cli optionsChristian Poessinger
Add CLI options for: - advertise-pip - rt-auto-derive - flooding - rd - route-target
2021-02-09bgp: T1513: initial implementation of L2VPN EVPN supportChristian Poessinger
2021-02-09bgo: T3183: T2100: enable "no bgp ebgp-requires-policy"Christian Poessinger
2021-01-24bgp: T3247: bugfix import/export filter-listChristian Poessinger
2021-01-24bgp: T3247: bugfix import/export prefix-list and distribution-listChristian Poessinger
This is an amendment to commit 5ab6882f ("bgp: T2347: bugfix import/export route-map") which did not take care about fixing the other two if/elif statements.
2021-01-24bgp: T2347: bugfix import/export route-mapChristian Poessinger
There can be both an import and an export route-map - the Jinja2 template syntax only allowed one direction and not the other.
2021-01-24bgp: T2850: bugfix templating neighbor interface statementsChristian Poessinger
2021-01-22bgp: T1875: update CLI description under protocols and template indention levelChristian Poessinger
2021-01-21Merge pull request #690 from Cheeze-It/currentChristian Poessinger
bgp: T1875: Adding BGP listen range FRR feature
2021-01-20bgp: T1875: Adding BGP listen range FRR featureCheeze_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-18bgp: T2174: use better variable names when creating peersChristian Poessinger
2021-01-14bgp: T2174: remove invalid "no bgp default ipv4-unicast" from default configChristian Poessinger
2021-01-13bgp: T2174: bugfix FRR template generationChristian Poessinger
2021-01-12bgp: T2387: Fix template for bgp redistribute proto ospv3sever-sever
2020-12-08bgp: T2174: Fix Template. Update to use FRRConfig frameworksever-sever
2020-11-22bgp: T2174: refactor Jinja template and reduce redundant pathsChristian Poessinger
The Jinja2 template contained a lot of redundant paths which only differed in either the address-family or neighbor vs. peer-group. This paths have been combined into for loops and a macro for generating a neighbor statement as peer-groups and regular neighbors share ~95% of the config.
2020-11-03bgp: T2850: Fixing the priority of template processing and missing paramssever-sever
2020-11-02bgp-xml: T2387: Fix validators and add capability for new format bgpsever-sever
2020-10-29bgp: T2850: Fix FRR template for new bgp schemesever-sever
2020-10-27bgp: T2387: Fix XML sheme for new bgp and bgp.py handlersever-sever
2020-09-01frr-template: T2850: Add BGP template for FRRsever-sever
2020-08-04cleanup: convert multiple files from DOS to UNIX line endingChristian Poessinger
2020-06-01bgp: T2387: proof-of-concept using get_config_dict()Christian Poessinger
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-15 10:16:02 +0000