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

Age	Commit message (Collapse)	Author
2021-08-29	xml: add missing "u32:" value declarator on integer ranges	Christian Poessinger
	(cherry picked from commit 794f193d11c8c1b5fed78f4e40280480446ab593)
2021-01-02	ddclient: T2858: no need to add a discrete priority	Christian Poessinger

2021-01-02	ddclient: T3175: update supported protocol list	Christian Poessinger

2020-12-29	xml: use new valueHelp format identifier "filename"	Christian Poessinger

2020-09-13	ddclient: T2858: migrate to get_config_dict()	Christian Poessinger

2020-02-13	ddclient: T1908: CloudFlares zone option can now also be specified manually	Christian Poessinger
	If there is no zone option given it will be "guessed" as in the past. This means (hostname -> resulting zone entry) domain.com -> com foo.domain.com -> domain.com bar.foo.domain.com -> foo.domain.com I have zero experience in the CloudFlare zone option what it is and what it does. SO maybe we still have a chance to auto render this setting.
2020-01-09	dynamic DNS: T1953: Relaxed service name check	zsdc
	Internally, we can accept more than one server of each type for sending dynamic DNS updates, but due to a strong check in CLI, it is not possible to add more than one server with the same protocol (except "custom", but it allows to add only one more server). The patch relaxing this limitation by allowing adding as many servers with the same protocol, as needed.
2019-12-15	dynamic-dns: T1879: extend XML validators	Christian Poessinger

2019-12-15	dynamic-dns: T1879: extend valueHelp strings	Christian Poessinger

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.