Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-04-11 | bgp: T3344: handle FRR vrf daemon configuration more elegant | Christian Poessinger | |
2021-04-10 | bgp: T3460: add verify() steps for local-as override | Christian Poessinger | |
It is only possible to set one local-as override per BGP neighbor/peer-group. In addition to this, the override AS number is not allowed to be the same as the one from the global BGP process. If this would still be the case frr-reload would error out: > frr-reload output: 184 % Cannot have local-as same as BGP AS number | |||
2021-04-08 | bgp: T3464: use common helper functions to verify route-maps and prefix-lists | Christian Poessinger | |
2021-04-05 | bgp: T3418: peer-group and remote-as must be present under interface node | Christian Poessinger | |
When configuring a BGP neighbor via an interface, FRR requires that the peer-group and remote-as node from under the interface statement is used. This is now enforced by a verify() check. | |||
2021-04-02 | frr: T3217: Abbility to save routing configs | sever-sever | |
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-23 | routing: T3217: Save configs of daemon per commit | sever-sever | |
2021-03-14 | bgp: T3325: fix missleading error message on listen-range verify() steps | Christian Poessinger | |
2021-03-14 | vrf: T3344: move dynamic routing protocols under "vrf name <name> protocols" | Christian Poessinger | |
Instead of having the dynamic routing protocols OSPF and BGP residing under the "protocols vrf <name> [ospf|bgp]" nodes, rather move them directly under the "vrf name <name> protocols [ospf|bgp]" node. Now all VRF related parts are placed under the same root node. This eases the verify steps tremendously, as we do not need to check wheter a VRF eists or not, it will always exist as we operate under a child node. | |||
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-02-27 | bgp: T3225: is_addr_assigned should check only ipv4 ipv6 neighbors | sever-sever | |
2021-02-26 | bgp: T3320: Add checks for peer-group | sever-sever | |
2021-02-26 | bgp: T3225: Move is_addr_assigned check to netighbor | sever-sever | |
2021-02-26 | bgp: T3225: Checks if neighbor configured as system address | sever-sever | |
2021-02-26 | bgp: T3324: Add checks for peer password | sever-sever | |
2021-02-26 | bgp: T3323: Add verify for ttl-security and ebgp-multihop | sever-sever | |
2021-02-19 | bgp: T3332: fix UnboundLocalError when using route-reflector-client | Christian Poessinger | |
local variable 'peer_group' referenced before assignment. | |||
2021-02-15 | bgp: T3311: remove remote-as from address-family | Christian Poessinger | |
When moving from Quagga to FRR the BGP address-family was extended by an invalid peer-group statement. FRR always moved a configured peer-group from the AFI level down to the neighbor level. With the migration to FRR reload we must take care about this by ourselves. | |||
2021-02-14 | frr: harden "router" regex | Christian Poessinger | |
2021-02-14 | bgp: T2387: route-reflector-client is only supported for iBGP peers | Christian Poessinger | |
2021-02-10 | frr: T2638: remove dedicated per protocol debugging | Christian Poessinger | |
With commit 015651a8 ("T2638: Enable more debugging in the FRR library") a global debug mechanism was added by creating a file named /tmp/vyos.frr.debug. With this change we can drop the duplicated debug code from every protocol. | |||
2021-01-22 | bgp: T1875: support processing by vyos-configd | Christian Poessinger | |
2021-01-21 | bgp: T1875: validate() that peer-group specified via listen range exists | 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-18 | bgp: T2174: fix validator for neighbor interface config | Christian Poessinger | |
2021-01-18 | bgp: T2174: print debug output before passing config down to FRR | Christian Poessinger | |
2021-01-17 | bgp: T2174: add debug option | Christian Poessinger | |
2021-01-14 | bgp: T2174: remove invalid "no bgp default ipv4-unicast" from default config | Christian Poessinger | |
2021-01-14 | bgp: T2174: enable new implementation | Christian Poessinger | |
2021-01-13 | bgp: T2174: bugfix FRR template generation | Christian Poessinger | |
2021-01-12 | bgp: T2174: bail out early if config node does not exist | Christian Poessinger | |
2021-01-07 | bgp: T2174: verify() existence of route-map and prefix-list | Christian Poessinger | |
2021-01-06 | bgp: T2174: verify() proper existance of remote-as | Christian Poessinger | |
2020-12-08 | bgp: T2174: Fix Template. Update to use FRRConfig framework | sever-sever | |
2020-11-27 | vyos.template: T2720: always enable Jinja2 trim_blocks feature | Christian Poessinger | |
2020-11-22 | bgp: T2174: refactor Jinja template and reduce redundant paths | Christian 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-12 | bgp-new: T2174: Fix abbility to del global route-map param | sever-sever | |
2020-10-27 | bgp: T2387: Fix XML sheme for new bgp and bgp.py handler | sever-sever | |
2020-09-01 | frr-template: T2850: Add BGP template for FRR | sever-sever | |
2020-06-01 | bgp: T2387: proof-of-concept using get_config_dict() | Christian Poessinger | |