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=sagitta 2024-09-26T13:23:35+00:00 2024-09-26T13:23:35+00:00 zsdc taras@vyos.io 2024-08-21T18:55:17+00:00 urn:sha1:dddc6a7ea25f3514faaa562af0f3cefed4b6048b To increase the chance for dhclient to configure routes in FRR, added a workaround. Now 10 attempts are performed with 1 second delay and only after this dhclient gives up. (cherry picked from commit da64a7246e9b12d5bd84287517cfbfa59e364c28) 2024-04-24T05:43:50+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2024-04-23T15:43:08+00:00 urn:sha1:9865cd931aa80eccb1052cbef9827740a5285488 This fix for bug when `sudo` commands were not send to the remote syslog server. They stop before the directive that includes all configurations `$IncludeConfig /etc/rsyslog.d/*.conf` (cherry picked from commit 7164ad40f5cc47f35c7903626d4d4da048a25113) 2024-04-12T18:31:03+00:00 Lucas Christian lucas@lucasec.com 2024-04-12T16:34:13+00:00 urn:sha1:8ac67c2fc03065b257e7f53e28a6153d6dfd371b (cherry picked from commit 840ab82e8821624aae589dec1ea86cefbcf866b7) 2024-04-02T16:33:59+00:00 Christian Breunig christian@breunig.cc 2024-04-01T18:40:16+00:00 urn:sha1:cc208d74567e44d6cffa4fc9fd58bd9bcf050930 Currently VyOS only supports binding a service to one individual VRF. It might become handy to have the services (initially it will be VRF, NTP and SNMP) be bound to multiple VRFs. Changed VRF from leafNode to multi leafNode with defaultValue: default - which is the name of the default VRF. (cherry picked from commit e5af1f0905991103b12302892e6f0070bbb7b770) 2024-04-01T14:33:35+00:00 Christian Breunig christian@breunig.cc 2024-04-01T12:04:50+00:00 urn:sha1:4e37494b9cb15f3c85b876de700babbaf1b38215 After migrating from ISC DHCLIENT for IPv6 to wide-dhcp-client the logic which was present to update /etc/resolv.conf with the DHCP specified nameservers and also the search domain list was no longer present. This commit adds a per interface rendered script to inform vyos-hostsd about the received IPv6 nameservers and search domains. (cherry picked from commit ece425f0191762638b7c967097accd8739e9103d) 2024-03-28T16:09:40+00:00 Lucas Christian lucas@lucasec.com 2024-03-10T18:39:19+00:00 urn:sha1:71fe258f6a4dfc0ead8f8ee46821f9dd965d141a (cherry picked from commit 679b78356cbda4de15f96a7f22d4a98037dbeea4) 2024-03-28T16:09:39+00:00 Lucas Christian lucas@lucasec.com 2024-02-10T19:26:47+00:00 urn:sha1:40b0986d66c3a0891dedbedc273b5485e5a8ca3a (cherry picked from commit 92012a0b3db8e93b10db4137414073f0371ed8cc) 2024-03-28T16:09:39+00:00 Lucas Christian lucas@lucasec.com 2024-02-09T06:04:16+00:00 urn:sha1:781807e732da80b967019649cd79d4721e19f26d (cherry picked from commit cd8ef21f280f726955f537132e3fab2bcb3c286f) 2024-03-21T09:23:10+00:00 Christian Breunig christian@breunig.cc 2024-03-20T19:53:47+00:00 urn:sha1:c104f9aea60416dbff3bf8de994921069ee6a928 When a VTI interface is just created, it is in ADMIN UP state by default, even if an IPSec peer is not connected. After the peer is disconnected the interface goes to DOWN state as expected. This breaks routing logic - for example, static routes through VTI interfaces will be active even if a peer is not connected. This changes to logic so ADMIN UP/DOWN state can only be changed by the vti-up-down helper script. Error was introduced during the Perl -> Python migration and move to the generic vyos.ifconfig abstraction during the 1.4 development cycle. (cherry picked from commit 9eb018c4935235d292d7c693ac15da5761be064a) 2024-02-07T20:54:41+00:00 Christian Breunig christian@breunig.cc 2024-02-07T16:40:11+00:00 urn:sha1:4e4c645b47e81ec54c8b02d2f4377664e5689a86 Always enable VRF strict_mode (cherry picked from commit 117fbcd6237b59f54f2c1c66986a8ce073808c84)