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=feature%2FT9082-codeql-cpp 2022-11-14T03:04:05+00:00 2022-11-14T03:04:05+00:00 Yuxiang Zhu vfreex@gmail.com 2022-11-14T02:23:46+00:00 urn:sha1:00ec496877453cc37ceec0633821a47f128d9f4f 1. When a PPPoE session is connected, `pppd` will update `/etc/resolv.conf` regardless of `system name-server` option unless `no-peer-dns` is set. This is because `pppd` vendors scripts `/etc/ppp/ip-up.d/0000usepeerdns` and `/etc/ppp/ip-down.d/0000usepeerdns`, which updates `/etc/resolv.conf` on PPPoE connection and reverts the change on disconnection. This PR removes those scripts and adds custom scripts to update name server entries through `vyos-hostsd` instead. 2. There is a typo in `/etc/dhcp/dhclient-enter-hooks.d/04-vyos-resolvconf, which misspells variable name `new_dhcp6_name_servers` as `new_dhcpv6_name_servers`. This causes IPv6 name server entries in `vyos-hostsd` not updated when dhclient receives nameservers from DHCPv6. 3. Regular expressions in scripts under `/etc/dhcp/dhclient-enter-hooks.d` and `/etc/dhcp/dhclient-exit-hooks.d/` are not enclosed in `^$`, so those IPv4 related branches (like `BOUND`) could be mistakenly executed when an IPv6 reason (like `BOUND6`) is given. 2022-02-01T07:00:58+00:00 Christian Poessinger christian@poessinger.com 2022-02-01T07:00:58+00:00 urn:sha1:bf549b34e7daab7e843176bc1c8a8d03148f3840 This reverts commit 78b247b724f74bdabab0706aaa7f5b00e5809bc1. 2022-01-28T21:15:29+00:00 Christian Poessinger christian@poessinger.com 2022-01-28T21:15:29+00:00 urn:sha1:78b247b724f74bdabab0706aaa7f5b00e5809bc1 2021-12-29T22:41:31+00:00 zsdc taras@vyos.io 2021-12-29T22:41:31+00:00 urn:sha1:ce77935eeeabcbb8d3510d09d12e0d79e74ad045 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-10-21T18:07:14+00:00 Ross Dougherty ross@dougherty.id.au 2021-10-20T12:50:51+00:00 urn:sha1:927ff3abba7610f7e70a4672bfd28156ace2915d (cherry picked from commit 67b3dd6b4715fef266eb47e68623944f8be617e0) 2021-04-14T22:37:50+00:00 zsdc taras@vyos.io 2021-04-14T21:20:44+00:00 urn:sha1:9ec8e2b6dc8144d4d5a17e53b1c183e22497580f There were two problems with VRF support inside dhclient-script: - VRF check inside the `01-vyos-cleanup` hook was needless because it will be done inside the `03-vyos-ipwrapper` anyway; - VRF was ignored for in-kernel routes in `03-vyos-ipwrapper`. Theoretically, there must be no situation now when this can leads to a real problem, but better will be to keep both kernel and FRR backends in sync. Also, the way to get and use a VRF name was changed to an easier one. 2021-02-15T15:30:00+00:00 Brandon Stepler brandon@stepler.net 2021-02-15T15:30:00+00:00 urn:sha1:dd2eb5e5686655c996ae95285b8ad7eb73d63d0b 2020-08-16T12:33:16+00:00 Christian Poessinger christian@poessinger.com 2020-08-16T12:27:03+00:00 urn:sha1:b17b8a0129f42c757c1e9a740664406e8da3dd42 2020-06-11T20:10:47+00:00 Jernej Jakob jernej.jakob@gmail.com 2020-06-11T07:32:58+00:00 urn:sha1:0ccdf15c0acb0be128fa2346b72cfdd8ce16b694 - vyos-hostsd-client syntax changed - track changes in changes variable - call apply only once at the end if any changes were made - remove 'cli-shell-api existsEffective system disable-dhcp-nameservers' condition check as the functionality was moved into vyos-hostsd - remove comparison between old_ and new_ variables as it caused a bug as the nameservers didn't get updated on renew or system restart, the dhclient lease file persists across reboots, so on boot the old variables will contain the values from previous dhclient run so they will usually be equal to the new variables. 2020-04-26T10:23:58+00:00 Gabriel Skupien g.skupien@vyos.io 2020-04-26T10:23:58+00:00 urn:sha1:ed4a493b734cac1fbf73df4a067a12d52d3fea57 Several improvements in processing RFC3442 routes (support for route deletion, DHCP RENEW and link-local routes)