summaryrefslogtreecommitdiff
path: root/interface-definitions
AgeCommit message (Collapse)Author
2021-04-12rip: T3328: route-map to zebra/kernel can not be removedChristian Poessinger
Removing the Zebra/Linux Kernel route-map added by "set protocols rip route-map" was not removed once applied. This was because the removal must happen within the zebra daemon and not ripd.
2021-04-09bgp: evpn: T1513: add support for ipv4/ipv6 prefix routes advertisementsChristian Poessinger
set vrf name red protocols bgp address-family l2vpn-evpn advertise ipv4 unicast
2021-04-09bgp: T1711: remove extra script completion helper on peer-groupsChristian Poessinger
After commit 73557d68 ("bgp: T1711: remove ASN tagNode and move to 'local-as'") when the BGP tag node was removed there is no need anymore for a script based completion helper, we can rather rely on the build in "path" variant.
2021-04-09tunnel: T3030: re-enable erspan version 2 supportChristian Poessinger
This was not possible due to a regression in iproute2 where the erspan_dir key did not have a value. See [1] for more information. [1]: https://lore.kernel.org/netdev/3ac544c09842410fb863b332917a03ad@poessinger.com/
2021-04-08isis: T2271: zebra route-map can only be set for default VRFChristian Poessinger
2021-04-08ospf: T2271: zebra route-map can only be set for default VRFChristian Poessinger
2021-04-08bgp: T2271: zebra route-map can only be set for default VRFChristian Poessinger
2021-04-08xml: route-map: add missing constraintsChristian Poessinger
Port over the regex used in the old node.def code-base and make this limitation also live on the new CLI interface.
2021-04-08isis: T1316: re-use common route-map XML building blockChristian Poessinger
2021-04-08static: T3280: re-use common route-map XML building blockChristian Poessinger
2021-04-07vrf: T3344: re-add virtual network identifierChristian Poessinger
Commit 548d9057e3e (vrf: T3344: move dynamic routing protocols under "vrf name <name> protocols") temporary removed the possibility to specify the VNI for a given VRF to to changing of the CLI configuration nodes. As VNI is set inside zebra, we can re-use the now widely deployed frr python library to configure and change the configuration without any interference to other FRR daemons.
2021-04-05tunnel: T3030: move erspan type into regular tunnel interfaceChristian Poessinger
Instead of having a dedicated ERSPAN interface type, rather move the specifics into "interface tunnel". A migrator is not needed as there is yet no LTS release with this feature and this is considered experimental.
2021-04-02interfaces: dhcp-client: T3454: add reject optionCharles Surett
Sometimes a modem might give a local IP before it retrieves a WAN IP. This can be an issue with failover routes, since the default route will get overridden.
2021-04-02Makefile: fix logic to detect empty "node.def" filesChristian Poessinger
Commit 5b22ebae ("T3170: check if any generated node.def files are empty") added an initial test to find empty node.def files created by build-command-templates or build-command-op-templates. The problem was that GNU find always returns 0, thus the condition to bail out on error was always met. This has been corrected to return false on hits only.
2021-04-02Makefile: T1579: do not remove interfaces "node.def" file anymoreChristian Poessinger
... this has been migrated to vyos-1x.
2021-04-02Revert "static: route: arp: T3170: prevent empty node.def from beeing generated"Christian Poessinger
This reverts commit d8c27642a3753513ae1d3c433fa46858a5ee946c.
2021-04-01static: route: arp: T3170: prevent empty node.def from beeing generatedChristian Poessinger
Currently if there are XML nodes defined in multiple places it can and will happen that one overrides the other. In this case, the "protocols static arp" definition file overwrites the node.def file in the "protocols static" folder that had a priority - the priority is essential for l2tpv3 to work.
2021-04-01Merge pull request #797 from erkin/currentDaniil Baturin
conf-mode: Add Dvorak layout
2021-04-01Add Dvorak layouterkin
2021-03-29bgp: 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-23vrf: T31: bump priority to 299 - still before any interface or serviceChristian Poessinger
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-21policy: xml: T2425: add missing priority tagsChristian Poessinger
2021-03-21xml: isis: ospf: re-arrange include blocksChristian Poessinger
2021-03-19bridge: T3415: add port isolation / private-vlan optionChristian Poessinger
Private VLAN, also known as port isolation, is a technique in computer networking where a VLAN contains switch ports that are restricted such that they can only communicate with a given "uplink". The restricted ports are called "private ports". Each private VLAN typically contains many private ports, and a single uplink. The uplink will typically be a port (or link aggregation group) connected to a router, firewall, server, provider network, or similar central resource. Q: https://en.wikipedia.org/wiki/Private_VLAN
2021-03-19isis: T2495: add missing priority nodeChristian Poessinger
2021-03-19ripng: T3281: add missing priority nodeChristian Poessinger
2021-03-19rip: T2547: add missing priority nodeChristian Poessinger
2021-03-17vrf: T3344: adjust routing protocol priorities to be +1 after default VRFChristian Poessinger
2021-03-17static: T3280: add missing and required priority xml node to avoid racesChristian Poessinger
2021-03-17ipv6: eui64: T3413: add custom validatorChristian Poessinger
VyOS 1.2 (crux) rejected prefixes other then of site /64. [ interfaces ethernet eth0 ipv6 address eui64 2006:ab00:abe1::2/127 ] Error: Prefix lenght is 127. It must be 64. Same should be done on VyOS 1.3 and newer
2021-03-17ipv6: eui64: T3413: improve valueHelp string for address assignmentChristian Poessinger
2021-03-14xml: accel-ppp: move building blocks to subfolderChristian Poessinger
As the amount of include files now has reached a certain amount, it is getting more and more crowsded, thuse introducing "per topic" subdirectories on the filesystem to keep a clean structure makes sense.
2021-03-14static: T3280: move building blocks to subfolderChristian Poessinger
As the amount of include files now has reached a certain amount, it is getting more and more crowsded, thuse introducing "per topic" subdirectories on the filesystem to keep a clean structure makes sense.
2021-03-14rip: xml: T2547: move building blocks to subfolderChristian Poessinger
As the amount of include files now has reached a certain amount, it is getting more and more crowsded, thuse introducing "per topic" subdirectories on the filesystem to keep a clean structure makes sense.
2021-03-14xml: T1579: re-arrange xml interface include building blocksChristian Poessinger
As the amount of include files now has reached a certain amount, it is getting more and more crowsded, thuse introducing "per topic" subdirectories on the filesystem to keep a clean structure makes sense.
2021-03-14Merge pull request #733 from sever-sever/T2425Christian Poessinger
conf-mode: T2425: Add XML for policy-lists
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