VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=mergify%2Fbp%2Fsagitta%2Fpr-3923 2024-02-09T08:05:14+00:00 2024-02-09T08:05:14+00:00 Christian Breunig christian@breunig.cc 2024-02-09T07:32:15+00:00 urn:sha1:32de8b3234f512d1555ad569d27ddecff6e18922 CLI source node is port and not listen-port. (cherry picked from commit 63d53a17274349fd68defdbf9f7ce16be63fc9b1) 2024-01-30T10:43:17+00:00 John Estabrook jestabro@vyos.io 2024-01-29T17:17:12+00:00 urn:sha1:1e97bee82294c2a63ff2c17ad9206aea99fe9061 (cherry picked from commit f057075409b024a18ea8a39b5e128fcde988c00e) 2024-01-10T07:11:39+00:00 Christian Breunig christian@breunig.cc 2024-01-06T09:55:42+00:00 urn:sha1:34eadcf2f74ae57342997bed77ce64bddd34219b We have not seen the adoption of the https virtual-host CLI option. What it did? * Create multiple webservers each listening on a different IP/port (but in the same VRF) * All webservers shared one common document root * All webservers shared the same SSL certificates * All webservers could have had individual allow-client configurations * API could be enabled for a particular virtual-host but was always enabled on the default host This configuration tried to provide a full webserver via the CLI but VyOS is a router and the Webserver is there for an API or to serve files for a local-ui. Changes Remove support for virtual-hosts as it's an incomplete and thus mostly useless "thing". Migrate all allow-client statements to one top-level allow statement. (cherry picked from commit d0d3071e99eb65edb888c26ef2fdc9e038438887) 2024-01-08T20:11:13+00:00 Christian Breunig christian@breunig.cc 2024-01-05T21:35:59+00:00 urn:sha1:1b85e7a9442aa71e2137df44747bd184c4a8b6de (cherry picked from commit 9ab6665c80c30bf446d94620fc9d85b052d48072)