VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git) https://git.amelek.net/marekm72/vyos-1x.git/atom?h=equuleus 2024-02-07T08:57:24+00:00 2024-02-07T08:57:24+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2024-02-07T08:57:24+00:00 urn:sha1:fc1be4c2b49f2237e8eeadccf32fd517d97b3b97 The custom systemd unit is not required as we generate 10-override which was implemented in https://github.com/vyos/vyos-1x/pull/2310/commits/5a6938a2e14373dfaa72211fe18deeb257d3ba12 2023-05-04T19:41:40+00:00 zsdc taras@vyos.io 2023-05-04T19:41:40+00:00 urn:sha1:748199b10df112cba0821703001c0307e325bd90 Added a new service that starts before Cloud-init, waits for all network interfaces initialization, and if requested by config, checks which interfaces can get configuration via DHCP server and creates a corresponding Cloud-init network configuration. This protects from two situations: * when Cloud-init tries to get meta-data via eth0 (default and fallback variant for any data source which depends on network), but the real network is connected to another interface * when Cloud-init starts simultaneously with udev and initializes the first interface to get meta-data before it is renamed to eth0 by udev 2023-03-15T14:54:04+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2023-03-15T14:54:04+00:00 urn:sha1:f992b2bd230dd2f095258cfa70f1e14796f86b3b Event-handler allows executing a custom script when detects some configured "pattern regex" set service event-handler event first filter pattern '.*ssh2.*' set service event-handler event first script arguments '192.0.2.5' set service event-handler event first script environment interface value 'eth0' set service event-handler event first script path '/config/scripts/hello.sh' It is the backport from 1.4 2022-08-15T16:00:56+00:00 Christian Poessinger christian@poessinger.com 2022-08-01T19:10:19+00:00 urn:sha1:dc41d55eba5e47a105d295e27fd30a0e6d62c711 (cherry picked from commit fa25d349aebc86e43957f37db765787fb7e431db) 2022-08-15T16:00:56+00:00 Christian Poessinger christian@poessinger.com 2022-08-01T18:53:47+00:00 urn:sha1:52b4b47f9e2484af7d493b72ebf0999c0047bf7b (cherry picked from commit 5e919d3f91bccaf64878a94756c21766896db132) 2022-08-15T16:00:56+00:00 Christian Poessinger christian@poessinger.com 2022-08-01T17:46:17+00:00 urn:sha1:fdc7814f12bc0bd1a6442284a5dbac8adeb57f54 (cherry picked from commit b2ff1407330e383a9fff688376377efc534bcfbc) 2022-08-15T16:00:56+00:00 Christian Poessinger christian@poessinger.com 2022-07-22T21:17:42+00:00 urn:sha1:66c1fbe7665fab4a51cbf1d626925d27e339f118 (cherry picked from commit bc70c1f502bc587627b1bd15f6803c6c09d20a66) 2022-01-09T19:55:40+00:00 Christian Poessinger christian@poessinger.com 2022-01-03T19:30:49+00:00 urn:sha1:5931d2530e9ab1b0fa0360602144d745b415ca42 (cherry picked from commit 5a73c946000902f6e445b0803ca090f7fc6e0954) 2021-12-30T16:02:26+00:00 zsdc taras@vyos.io 2021-12-29T22:41:31+00:00 urn:sha1:1a9c1479044040c64ca6be91835d8cea7004ddff In case if a CLI configuration is not available, dhclient cannot add nameservers to a `resolv.conf` file, because `vyos-hostsd` requires that an interface be listed in the `set system name-server` option. This commit introduces two changes: * `vyos-hostsd` service will not be started before Cloud-Init fetch all remote data. This is required because all meta-data should be available for Cloud-Init before any of VyOS-related services start since it is used for configuration generation. * the `vyos-hostsd-client` in the `dhclient-script` will be used only if the `vyos-hostsd` is running. In other words - if VyOS services already started, dhclient changes `resolv.conf` using `vyos-hostsd`; in other cases - does this directly. These changes should protect us from problems with DHCP during system boot if DHCP is required by third-party utils. 2021-12-25T23:10:41+00:00 Christian Poessinger christian@poessinger.com 2021-12-25T23:10:07+00:00 urn:sha1:acf90165456e87cff19f45053261667803255c8e (cherry picked from commit 4aaf0ba69139d84f89e5c3feee6edd845af8d1e5)