summaryrefslogtreecommitdiff
path: root/interface-definitions/interfaces-wireguard.xml.in
AgeCommit message (Collapse)Author
2020-07-26wireguard: ifconfig: T2653: move to get_config_dict()Christian Poessinger
The current VyOS CLI parser code written in Python contains a ton of duplicates which I can also hold myself accountable for - or maybe mainly me - depends on the angle of judge.
2020-07-26wireguard: T2734: fwmark is a 32bit value - fix validatorChristian Poessinger
2020-05-19wireguard: T2481: support IPv6 based underlayChristian Poessinger
2020-04-08wireguard: T2244: split port configuration to XML include fileChristian Poessinger
2020-04-08wireguard: T2247: add VRF supportChristian Poessinger
2020-04-08wireguard: T2244: use xml include for mtuChristian Poessinger
2020-04-05wireguard: T2228: support ports less then 1024Christian Poessinger
2020-04-05wireguard: T2206: add valueHelp for listen portChristian Poessinger
2020-04-05wireguard: T2206: split endpoint node into address and portChristian Poessinger
WireGuard has been the only subsystem combining a remote ip address and a remote port number into a single node. This is bad as there is no possiblity for the XML based input validation for IP address and port numbers. That's the reason the peer endpoint node goets migrated into a peer address and a peer port node utilizing the embedded syntax node checking for IP addresses and port ranges.
2020-04-03interfaces: XML: constraint: add start of line ^ to regexChristian Poessinger
2020-01-26Interfaces: unify interface help textChristian Poessinger
2020-01-26WireGuard: rephrase constraint error messageChristian Poessinger
2019-12-26xml: remove leading carrot (^) from regex syntaxChristian Poessinger
... as the carrot is applied automatically when reading in the XML definition. Auto replaced by: $ find interface-definitions -type f | xargs sed -i 's/regex>^/regex>/'
2019-12-22wireguard: remove artifical limitation on interface numbersChristian Poessinger
Interface name hould be allowed to exceed wg9999 - there is no reason to limit this.
2019-12-22interfaces: fix tagNode regex constraint (remove ^)Christian Poessinger
2019-12-06T1843: use include files to disable interface (admin down)Christian Poessinger
2019-12-06T1843: use include files for interface descriptionChristian Poessinger
2019-12-06T1843: recursively include IP address definitions in VIF/VIF-S definitionsChristian Poessinger
2019-12-06T1843: use include files for IPv4/IPv6 interface address configurationChristian Poessinger
As 219779bc6151 ("T1843: run interface-definitions though GCC preprocessor") implemented the foundation of using the GCC preprocessor to make our XML definitions more lightweight this commit transforms the configuration of an IPv4/IPv6 address to this new style. It implementes it for the following interface types: * bond * bridge * dummy * ethernet * geneve * loopback * vxlan * wireguard * wireless
2019-12-06T1843: run interface-definitions though GCC preprocessorChristian Poessinger
A lot of XML code is duplicated (VLAN, interface address) for instance. Such XML definitions should be moved to feature.xml.i files and then just pulled in via GCC preprocessor #include definition in e.g. bond or ethernet definitions. This will give us the ability to single-source repeating node definitions as: * Interface Address * Interface Description * Interface Disable * VLAN (both vif-s and vif-c) The .in suffix of the interface-definitions is a marker that those files are input files to the GCC preprocessor. They will be rendered into proper XML files in the build directory. Some node definitions have been reworder to remove escaped double quote occurances which would have been warned about by the GCC preprocessor.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-01 11:35:58 +0000