summaryrefslogtreecommitdiff
path: root/interface-definitions/ssh.xml.in
AgeCommit message (Collapse)Author
2021-01-13ssh: T3212: do not make /run/sshd directory disappear on failureChristian Poessinger
2020-12-12xml: use "u32:" keyword when identifying port rangesChristian Poessinger
This will render the completion help more nicely.
2020-10-06xml: include: add common helper file for listen-addressChristian Poessinger
2020-07-07ssh: T2691: bugfix loglevel config migrationChristian Poessinger
When migrating the conf from VyOS 1.2 to 1.3 a configuration error could appear if the user specified "info" as loglevel instead of "INFO". There was no input validation done in 1.2 but this is now enforced in 1.3. In VyOS 1.3 loglevel will be always lowercase on the CLI and when migrating the config this is transformed. Also VyOS 1.2 accpeted any arbitrary loglevel. If an invalid loglevel is found it will be set to info.
2020-06-23ssh: T2635: migrate to get_config_dict()Christian Poessinger
Jinja template contains some workarounds like {% if port is string %}, this depends of the resolution of https://phabricator.vyos.net/T2636
2020-06-23ssh: T2635: remove ' in comment to avoid proprocessor warningsChristian Poessinger
2020-06-23ssh: T2635: migrate from a script base completion helper to a listChristian Poessinger
SSH mac, ciper and key exchange algorithms are not ynamically and only change on distro upgrades. Thus it is easier to have them in a list and use a regex based constraint. In the past users could have entered anything here!
2020-06-22xml: ssh: fix typo in service descriptionChristian Poessinger
2020-06-11ssh: T2321: add VRF supportChristian 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-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.