vyos-1x.git - VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)

Age	Commit message (Collapse)	Author
2020-12-22	wireguard: T2206: improve help strings	Christian Poessinger

2020-12-04	wireguard: T2653: add interface "ip" configuration node	Christian Poessinger

2020-11-20	wireguard: T3077: automatically create link-local IPv6 adresses	Christian Poessinger
	link-local addresses can still be disabled using: set interfaces wireguard wg0 ipv6 address no-default-link-local
2020-10-28	mtu: T2630: add support for ethernet MTU up to 16000 bytes	Christian Poessinger
	There is a Myricom 10G card with 16k MTU available.
2020-07-26	wireguard: 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-26	wireguard: T2734: fwmark is a 32bit value - fix validator	Christian Poessinger

2020-05-19	wireguard: T2481: support IPv6 based underlay	Christian Poessinger

2020-04-08	wireguard: T2244: split port configuration to XML include file	Christian Poessinger

2020-04-08	wireguard: T2247: add VRF support	Christian Poessinger

2020-04-08	wireguard: T2244: use xml include for mtu	Christian Poessinger

2020-04-05	wireguard: T2228: support ports less then 1024	Christian Poessinger

2020-04-05	wireguard: T2206: add valueHelp for listen port	Christian Poessinger

2020-04-05	wireguard: T2206: split endpoint node into address and port	Christian 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-03	interfaces: XML: constraint: add start of line ^ to regex	Christian Poessinger

2020-01-26	Interfaces: unify interface help text	Christian Poessinger

2020-01-26	WireGuard: rephrase constraint error message	Christian Poessinger

2019-12-26	xml: remove leading carrot (^) from regex syntax	Christian 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-22	wireguard: remove artifical limitation on interface numbers	Christian Poessinger
	Interface name hould be allowed to exceed wg9999 - there is no reason to limit this.
2019-12-22	interfaces: fix tagNode regex constraint (remove ^)	Christian Poessinger

2019-12-06	T1843: use include files to disable interface (admin down)	Christian Poessinger

2019-12-06	T1843: use include files for interface description	Christian Poessinger

2019-12-06	T1843: recursively include IP address definitions in VIF/VIF-S definitions	Christian Poessinger

2019-12-06	T1843: use include files for IPv4/IPv6 interface address configuration	Christian 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-06	T1843: run interface-definitions though GCC preprocessor	Christian 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.