summaryrefslogtreecommitdiff
path: root/data
AgeCommit message (Collapse)Author
2021-03-26http api: T3412: use FastAPI as web framework; support application/jsonJohn Estabrook
Replace the Flask micro-framework with FastAPI, in order to support extensions to the API and OpenAPI 3.* generation. This change will remain backwards compatible with previous versions. Notably, the multipart forms version of requests remain supported; in addition application/json requests are now natively supported.
2021-03-25configd: T3426: include bgp, isis, ospf and static protocols in processingJohn Estabrook
vyos-configd now supports calling a script with a passed argument; re-include the conf_mode scripts that were excluded in ba251b3f2c.
2021-03-23vyos.configd: T3423: exclude bgp, isis, ospf and static protocols from ↵Christian Poessinger
processing vyos-configd does yet not support calling a script with a passed argument, thus we will exclude the routing protocols during this time from the vyos-configd processing.
2021-03-21isis: T3417: drop artificial "domain" node identifying the IS-IS process nameChristian Poessinger
As we and FRR do not support multiple FRR process instances, there is no need to make this configurable for a user. We rather rely on a solid default "VyOS".
2021-03-21isis: T3417: add VRF supportChristian Poessinger
VRF support can be tested using: set vrf name red table 1000 set vrf name red protocols isis domain FOOO set vrf name red protocols isis net 49.0001.1921.6800.1002.00 set vrf name red protocols isis interface eth1
2021-03-21isis: T3417: move from cli tagNode to nodeChristian Poessinger
As there can only be one running IS-IS process (FRR limitation) there is no need in having a tagNode here. This adds artifical restrictions/limitations when moving on to support VRFs for IS-IS protocol.
2021-03-14vrf: 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-14vrf: bgp: T2271: create individual BGP process for specified VRF nameChristian 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-14vrf: ospf: T2271: create individual OSPF process for specified VRF nameChristian Poessinger
VyOS CLI config: vrf red { ospf { default-information { originate { always } } default-metric 30 passive-interface default } } Will create the FRR configuration snippet: ! router ospf vrf red auto-cost reference-bandwidth 100 timers throttle spf 200 1000 10000 passive-interface default default-metric 30 default-information originate always !
2021-03-13nat66: T2518: Align the log and comment of nat66 template with natjack9603301
2021-03-10bgp: evpn: T1513: add support for per VNI route-distinguished and route-targetChristian 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-10rpki: T3399: Fix template dashes replacesever-sever
(cherry picked from commit 55c4dd3586a3b0e2fe53ccad75c996b55d9979eb)
2021-03-10syslog: T3396: Fix remote IPv6 hostsever-sever
2021-03-09Merge pull request #762 from jack9603301/T2518Christian Poessinger
nptv6: T2518: Support IPv6 address translation
2021-03-09nptv6: T2518: Support masquerade and cancel new migratorsjack9603301
2021-03-08bgp: T3391: migrate old IPv4 only maximum-paths config to new syntaxChristian Poessinger
2021-03-09nptv6: T2518: Support IPv6 address translationjack9603301
2021-03-07bgp: T3391: add per AFI maximum-paths supportChristian 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-03-04Merge pull request #729 from bstepler/T3300Christian Poessinger
dhcp: T3300: add DHCP default route distance
2021-03-04pppoe: T3386: Fix client ip-pool stop rangesever-sever
2021-03-02dhcpv6-server: T3379: Add option global-parameters name-serversever-sever
2021-03-01pppoe: T3353: Fix regex for listen interface vlan-idsever-sever
2021-02-28pppoe: T3353: Modify template for vlan-mon and interfacesever-sever
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-26https: T3357: redirect http request on non-standard https portJohn Estabrook
2021-02-24route: static: T2450: add missing "dhcp-interface" route optionChristian Poessinger
As thought in the beginning the dhcp-interface route option can not be superseeded by the interface option. When a route is installed for a DHCP interface, that interface is usually a broadcast interface which can not be used for plain interface-based routes. The old Vyatta logic was migrated to Python where the current received next-hop address from the DHCP interface is installed as next-hop address.
2021-02-23dhcp-server: T2927: Add empty args if does not possible to determine variablesDmitriyEshenko
2021-02-21console-server: T2490: do not use cli-shell-api in systemd unitChristian Poessinger
(cherry picked from commit d5804b19d3ffecdd4fe6bd89d50ac84dabb549fd)
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-16bfd: T3310: use end to exit FRR scopeChristian Poessinger
We need to exit from the bfd context by end instead of exit, else FRR reload will get confused: frr-reload output: 168 2021-02-16 21:13:19,014 DEBUG: LINE ip prefix-list GLOBAL seq 10 permit 192.168.100.1/32: append to current_context_lines, ['bfd']
2021-02-16ospf: T3047: support virtual-link interfaces on "passive-interface-exclude"Christian Poessinger
This superseeds GitHub pull request #723 by implementing support to add an OSPF virtual-link interface which connects different areas to the "no passive-interface" configuration option when the system uses "passive-interface default". Setting "protocols ospf passive-interface-exclude vlink0" on the VyOS CLI will render the FRR OSPF configuration "no passive-interface VLINK0".
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-16ospfv3: T3313: move interface related options to "protocols ospfv3 interface"Christian Poessinger
2021-02-15Merge pull request #732 from c-po/t3310-bfdJohn Estabrook
bfd: T3310: migrate to get_config_dict() and FRR reload
2021-02-15bgp: T1513: add per VRF vni supportChristian Poessinger
2021-02-15bfd: T3310: implement peer profile supportChristian Poessinger
2021-02-15bfd: T3310: migrate to get_config_dict() and FRR reloadChristian Poessinger
2021-02-15dhcp: T3300: add DHCP default route distanceBrandon Stepler
2021-02-14templates: convert DOS -> UNIX line endingsChristian Poessinger
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