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=circinus-public-unmaintained 2024-10-06T14:56:55+00:00 2024-10-06T14:56:55+00:00 Christian Breunig christian@breunig.cc 2024-10-05T18:34:43+00:00 urn:sha1:34850de90c0fbc0c51ab7b4f4aeb0a87a73369ef This fixes the error message: Can not use both blackhole and reject for prefix "{prefix}"! Added in commit bb78f3a9ad28 ("static: T4283: support "reject" routes - emit an ICMP unreachable when matched") (cherry picked from commit 490ee3ec5ba7ea28002890841eab8e46f775a129) 2024-04-02T22:15:43+00:00 Christian Breunig christian@breunig.cc 2024-04-02T22:15:43+00:00 urn:sha1:274b2da242acd1f1f64ff1dee471e34295137c5f found using "git ls-files *.py | xargs pylint | grep W0611" 2023-07-25T20:46:44+00:00 Jonathan Voss jvoss@onvox.net 2023-07-25T19:25:42+00:00 urn:sha1:20ac831df73aa89da4eb172bfb4d5f4256071983 2023-04-13T07:01:31+00:00 Christian Breunig christian@breunig.cc 2023-04-10T08:57:34+00:00 urn:sha1:b454ddc8c2cc0edbdc832bd60ef03a1819a6d8d6 2023-04-13T07:01:31+00:00 Christian Breunig christian@breunig.cc 2023-04-08T20:15:41+00:00 urn:sha1:f9aa4c6312a773c216e65400db7e66849d5a02c7 2023-04-13T07:01:31+00:00 Christian Breunig christian@breunig.cc 2023-04-08T20:09:04+00:00 urn:sha1:3f4de1390d6459cdd17dd1b6f22b1a3aec002671 It is possible to install a route-map which filters the routes between routing daemons and the OS kernel (zebra) As of now this can be done by e.g. * set protocols ospf route-map foo * set protocols ospfv3 route-map foo * set protocols bgp route-map foo Which in turn will install the following lines into FRR * ip protocol ospf route-map foo * ipv6 protocol ospf6 route-map foo * ip protocol bgp route-map foo The current state of the VyOS CLI is incomplete as there is no way to: * Install a filter for BGP IPv6 routes * Install a filter for static routes * Install a filter for connected routes Thus the CLI should be redesigned to close match what FRR does for both the default and any other VRF * set system ip protocol ospf route-map foo * set system ipv6 protocol ospfv3 route-map foo * set system ip protocol bgp route-map foo * set system ipv6 protocol bgp route-map foo The configuration can be migrated accordingly. This commit does not come with the migrator, it will be comitted later. 2023-01-06T07:14:44+00:00 Christian Poessinger christian@poessinger.com 2023-01-06T07:14:44+00:00 urn:sha1:e32ce63b52eff0255d602b475d90cd97d3b282c1 Commit dafb0da2 ("static: T4883: add a description field for routing tables") added an iproute2 description table but lacked checking if the key exists. This has been fixed and also converted to Jinja2 to keep the "common" style inside the routing protocols. It might feel overengineered indeed. 2022-12-26T18:24:08+00:00 Daniil Baturin daniil@vyos.io 2022-12-15T14:59:58+00:00 urn:sha1:dafb0da26d9c27e2a2e836fc56175af5da039479 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. 2022-04-14T19:29:44+00:00 Christian Poessinger christian@poessinger.com 2022-04-14T19:24:08+00:00 urn:sha1:df045eca2f6c7a9257de5d32723d9ccc799346e5