summaryrefslogtreecommitdiff
path: root/interface-definitions
AgeCommit message (Collapse)Author
2021-03-14vrf: T3344: set explicit priority values for routing protocolsChristian Poessinger
We must ensure that an interface is already added to a VRF before it is referenced inside a VRF context, e.g. OSPF.
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-14xml: include: fix typo on include commentChristian Poessinger
When including XML files they all contained a comment from where the snipped had actually been included from. The comment had been "included start" and "included end" instead of "include start" and "include end". This commit corrects the glitch.
2021-03-14xml: ospf: consolidate router-id and distance settings in common include filesChristian Poessinger
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: bgp: T2271: re-arrange xml include building blocksChristian 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-14xml: include: move route-map from ospf to generic sectionChristian Poessinger
2021-03-14bgp: T2387: add completion helper when specifying a peer-groupChristian Poessinger
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-13vrf: ospf: T2271: re-arrange xml include building blocksChristian Poessinger
In order to fully re-use the XML based OSPF CLI definition for per-VRF routing, the file structure needs to be reorganized and the common OSPF definition is moved to its dedicated ospf-common-config.xml.i file, which can then be fully re-included at the VRF level. 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.
2021-03-13tunnel: T3406: support ipv6 encaplimit "none" which disables the fielChristian Poessinger
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-09console-server: T3382: remove priority as we do not have any dependenciesChristian Poessinger
2021-03-09console-server: T3382: proper check for existence of /dev/serial/by-busChristian Poessinger
The completion helper was directly called on the /dev/serial/by-bus directory, but it was not verified if the directory exists at all.
2021-03-09Merge pull request #762 from jack9603301/T2518Christian Poessinger
nptv6: T2518: Support IPv6 address translation
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-07vxlan: T3319: use default ttl of 16Christian Poessinger
VyOS 1.2 had a default ttl of 16 hardcoded to the node.def file [1], so until this is handled via a migration script we have to obey that particular setting. [1]: https://github.com/vyos/vyatta-cfg-system/blob/crux/templates/interfaces/vxlan/node.def#L23
2021-03-06bgp: T2387: add interface completion helper for update-sourceChristian Poessinger
2021-03-04Merge pull request #729 from bstepler/T3300Christian Poessinger
dhcp: T3300: add DHCP default route distance
2021-03-03tunnel: T2966: add ip6gretap encapsulation supportChristian Poessinger
2021-03-03Merge branch 'T3379' of https://github.com/sever-sever/vyos-1x into currentChristian Poessinger
* 'T3379' of https://github.com/sever-sever/vyos-1x: dhcpv6-server: T3379: Add option global-parameters name-server
2021-03-03geneve: T1799: add additional per tunnel optionsChristian Poessinger
Support setting additional options to the GENEVE tunnel like: - ttl - tos - do not fragment bit - ipv6 flowlabel
2021-03-02dhcpv6-server: T3379: Add option global-parameters name-serversever-sever
2021-02-28vxlan: T1513: add dont-fragment CLI optionChristian Poessinger
2021-02-28l2tpv3: T3366: migrate local-ip and remote-ip CLI optionsChristian Poessinger
Rename CLI options local-ip to source-address and remote-ip to remote to get a consistent CLI experience for the user.
2021-02-28validators: fqdn: T3370: support "private" or "local" domain namesChristian Poessinger
2021-02-28vxlan: T3369: add underlay IPv6 supportChristian Poessinger
2021-02-28macsec: T3368: add support for gcm-aes-256 cipherChristian Poessinger
2021-02-28tunnel: T3366: rename remote-ip to remoteChristian Poessinger
Streamline the CLI configuration where we try to use remote on other interfaces like vxlan, geneve.
2021-02-28tunnel: T3366: rename local-ip to source-addressChristian Poessinger
Streamline the CLI configuration where we try to use source-address when creating connections which are especially sourced from a discrete address.
2021-02-28tunnel: T3364: rename encapsulation mode "gre-bridge" to "gretap"Christian Poessinger
The following list shows the mapping of VyOS tunnel encapsulation modes to the corresponding Linux modes. VyOS Linux gre gre gre-bridge gretap ipip ipip ipip6 ipip6 ip6ip6 ip6ip6 ip6gre ip6gre sit sit Besides gre-bridge this is pretty consistent. As bridge interfaces are also called tap interfaces gre-bridge will be renamed to gretap to make the post-processing much easier. This means (in detail) that there are no more child classes of _Tunnel and there will be now one geneirc TunnelIf class handling all sorts of encapsulation.
2021-02-28vxlan: T1513: add additional EVPN related CLI optionsChristian Poessinger
A VXLAN tunnel may now get a TTL, TOS, Flowlabel option specified. It is also possible to disable learning of unknown addresses into the forwarding database.
2021-02-27smoketest: bgp: T2100: fix "simple" testcase for ebgp-requires-policyChristian 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-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-24xml: add missing constaint to source-interface includeChristian Poessinger
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-23Merge pull request #739 from sever-sever/T3211Christian Poessinger
routing: T3211: Add redistribute protocol IS-IS to bgp ospf rip
2021-02-23routing: T3211: Add redistribute protocol IS-IS to bgp ospf ripsever-sever
2021-02-22xml: tunnel: erspan: make individual parameter nodes reusableChristian Poessinger
VXLAN will get tos, ttl and flowlabel options thus make individual parameter settings reusable by splitting tunnel-parameters-ip.xml.i into individual files.
2021-02-22Merge branch 'current' of https://github.com/vyos/vyos-1x into currentDaniil Baturin
2021-02-19bgp: T3331: Fix set unsuppress-map for neighborsever-sever
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-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