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=1.3.2 2022-08-19T18:04:00+00:00 2022-08-19T18:04:00+00:00 Christian Poessinger christian@poessinger.com 2022-08-19T16:55:24+00:00 urn:sha1:33db81f8055fa471d3b0b6cdf78c2a057c11a0fc When MACsec was bound to an ethernet interface and the underlaying source-interface got changed (even description only) this terminated the MACsec session running on top of it. The root cause is when EAPoL was implemented in commit d59354e52a8a7f we re-used the same systemd unit which is responsible for MACsec. That indeed lead to the fact that wpa_supplicant was always stopped when anything happened on the underlaying source-interface that was not related to EAPoL. (cherry picked from commit f92a23ef9ab8be59681e5b7ba627e399d89bce53) 2022-05-05T05:41:45+00:00 Dmitri Toubelis dtoubelis@users.noreply.github.com 2022-05-05T05:41:45+00:00 urn:sha1:0c00e7bf8b6e68814607fde4ff0cd70ce9f4b486 - Default dhclient script only uses value of `$IF_MERIC` envvar for default route recived via `router` option. - This variable has no effect on rotes received via `rfc3442-classless-static-routes` option - Considering that Vyos overrrides `ip` command originating from `dhclient` this can be easily fixed in `iptovtysh()` function by using the `$IF_METRIC` envvar directly in the dhclient hook. 2022-04-03T07:19:18+00:00 Christian Poessinger christian@poessinger.com 2022-04-02T12:38:11+00:00 urn:sha1:7091d0b54f21caf85ea86d2542d9bec4b5fd1afb (cherry picked from commit 5faeacd1111a83e5859b98ccc4193cb6017cdba8) 2022-03-28T07:46:52+00:00 Daniil Baturin daniil@vyos.io 2022-03-28T07:46:52+00:00 urn:sha1:2a511dfaf8fcc633baf254a45224ff612d0d1202 This reverts commit 382d5aa16d81b745e522a14122b429750ee64789. 2022-03-24T17:37:17+00:00 Christian Poessinger christian@poessinger.com 2022-02-17T19:58:02+00:00 urn:sha1:382d5aa16d81b745e522a14122b429750ee64789 (cherry picked from commit 1cbcbf40b7721849f9696c05fac65db010a66b7c) 2022-03-05T19:53:02+00:00 Christian Poessinger christian@poessinger.com 2022-03-05T08:40:32+00:00 urn:sha1:36c46f5893fa1f4df1defcee851e44ca3ed1fd8f (cherry picked from commit 2c94c3ec72a559de405b29b4399250db3085717e) 2022-02-08T15:14:03+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2022-02-08T15:14:03+00:00 urn:sha1:10d67313d320c97b48fe4fa2236f25ada94ae98c 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) 2022-01-09T19:55:35+00:00 Christian Poessinger christian@poessinger.com 2022-01-03T17:43:35+00:00 urn:sha1:1bb6b4458aa639e7dbea9fc9d6f666bdc7ea9612 Without this option systemd startup will hit a timeout and the kill keepalived again. (cherry picked from commit 2a279f48e208b90c91eac5d6c5855e65cee39018) 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.