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

Age	Commit message (Collapse)	Author
2023-03-01	T4967: xml: provide re-usable constraint for CLI host-name definitions	Christian Breunig
	(cherry picked from commit d14a6814acb173cdc6df13212620f7da330434ed)
2023-01-21	validators: T4875: use file-path to replace validator 'interface-name'	Christian Breunig
	(cherry picked from commit f0bc6c62016d285f0645c4b3ba8b1451c40c637f)
2022-07-05	hosts: T2683: Allow multiple entries for static-host-mapping	Viacheslav
	(cherry picked from commit b1db3de80b8b5f4e2dcbc6d687d342986345c4b2)
2021-09-05	name-server: T3804: merge "system name-servers-dhcp" into "system name-server"	Christian Poessinger
	We have "set system name-server <ipv4\|ipv6>" to specify a name-server IP address we wan't to use. We also have "set system name-servers-dhcp <interface>" which does the same, but the name-server in question is retrieved via DHCP. Both CLI nodes are combined under "set system name-server <ipv4\|ipv6\|interface>" to keep things as they are in real life - we need a name-server.
2021-02-28	validators: fqdn: T3370: support "private" or "local" domain names	Christian Poessinger
	(cherry picked from commit 04724ed189553ce43f8504f68fef8024ef5796de)
2020-06-11	system: T2486: migrate disable-dhcp-nameservers to name-servers-dhcp	Jernej Jakob
	The previous implementation only supported disabling DHCP nameservers for all interfaces, and was implemented improperly so it didn't work anyway. This migrates it to name-servers-dhcp <interface>, which allows us to enable just the interfaces we want to use for system DNS, identical in syntax to 'service dns forwarding dhcp <interface>'. The migrator searches through all interfaces that have address 'dhcp(v6)?' and adds them to the name-servers-dhcp list if disable-dhcp-nameservers is not set, else it does nothing.
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-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.