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.4.0 2024-01-01T08:25:32+00:00 2024-01-01T08:25:32+00:00 Christian Breunig christian@breunig.cc 2023-12-30T22:25:20+00:00 urn:sha1:c9eaafd9f808aba8d29be73054e11d37577e539a We will use _ as CLI level divider. The XML definition filename and also the Python helper should match the CLI node. Example: set interfaces ethernet -> interfaces_ethernet.xml.in set interfaces bond -> interfaces_bond.xml.in set service dhcp-server -> service_dhcp-server-xml.in (cherry picked from commit 4ef110fd2c501b718344c72d495ad7e16d2bd465) 2022-12-11T19:27:40+00:00 Christian Poessinger christian@poessinger.com 2022-12-11T18:38:28+00:00 urn:sha1:ff56aeefddaad2d37d3ea32626e1adf3960eaf26 vyos@vyos# show interfaces sstpc sstpc sstpc10 { authentication { password vyos user vyos } server sstp.vyos.net ssl { ca-certificate VyOS-CA } } 2022-11-15T05:54:19+00:00 Yuxiang Zhu vfreex@gmail.com 2022-11-15T05:52:14+00:00 urn:sha1:b8a4442c898727eaf7def8c42ee850fbb9dd60be ip-up/down scripts added in https://github.com/vyos/vyos-1x/pull/1656 need the executable bit. 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-04-25T18:37:12+00:00 Christian Poessinger christian@poessinger.com 2022-04-25T18:35:55+00:00 urn:sha1:68ad8752a4a5b57addc7bd3d2db0f464acb79b50 When VyOS is booting and an interface is brought up (PPPoE) which requires a user callback script that is executed asynchronously when the interface is up we can not use Config(). The problem is, Config() is not available when the system starts and the initial commit is still processed. We need to move to ConfigTreeQuery() which was build for this exact same purpose. 2022-04-21T20:08:38+00:00 Christian Poessinger christian@poessinger.com 2022-04-21T20:03:36+00:00 urn:sha1:a2ab95ff68b709f7ca31006bdef6607ef4ce961d VyOS 1.4 still leverages PPPd internals on the CLI. pppd supports three options for a default route, none, auto, force. * none: No default route is installed on interface up * auto: Default route is only installed if there is yet no default route * force: overwrite any default route There are several drawbacks in this design for VyOS and the users. If auto is specified, this only counted for static default routes - but what about dynamic ones? Same for force, only a static default route got replaced but dynamic ones did not got taken into account. The CLI is changed and we now re-use already existing nodes from the DHCP interface configuration: * no-default-route: On link up no default route is installed, same as the previous default-route none * default-route-distance: We can now specify the distance of this route for the routing table on the system. This defaults to 210 as we have for DHCP interfaces. All this will be migrated using a CLI migration script. 2021-08-21T19:48:58+00:00 Christian Poessinger christian@poessinger.com 2021-08-20T15:13:32+00:00 urn:sha1:64c9fdef02323309e97b2bb682604ada52d651e8 Now that MSS clamping is done on the "per-interface" level the entire PPPoE stuff would have needed to get a full copy in GNU BASH for this or, participate in the common library. Add a new PPP ip-up script named 99-vyos-pppoe-callback which will call the vyos.ifconfig.PPPoEIf.update() function to configure everything as done with all other interfaces. This removes duplicated code for VRF assignment and route installation when a PPPoE interface is brought up or down. 2021-06-20T18:34:47+00:00 Christian Poessinger christian@poessinger.com 2021-06-20T18:31:00+00:00 urn:sha1:b16939e5bf245c3463ab663093e9a05a7c9aeb95 2020-04-04T09:40:08+00:00 Christian Poessinger christian@poessinger.com 2020-04-04T09:40:06+00:00 urn:sha1:fec5b40244520b8455abd2fdcd8ce347a27fd7f4 2020-03-29T13:28:21+00:00 Christian Poessinger christian@poessinger.com 2020-03-29T13:28:21+00:00 urn:sha1:552106b0fb27003e5e5be5494f2213f54a699b9e