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=1.4.0-rc2 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) 2023-11-07T19:38:18+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2023-11-04T10:56:55+00:00 urn:sha1:529aa5e6f36e0c3bece7801a9dd281107e646cef - Allow to configure only required interface prefixes set service snmp mib interface 'eth' set service snmp mib interface 'bond' include_ifmib_iface_prefix eth bond Sets the interface name prefixes to include in the IF-MIB data collection. For servers with a large number of interfaces (ppp, dummy, bridge, etc) the IF-MIB processing will take a large chunk of CPU for ioctl calls. A set of space separated interface name prefixes will reduce the CPU load for IF-MIB processing. For example, configuring "include_ifmib_iface_prefix eth dummy lo" will include only interfaces with these prefixes and ignore all others for IF-MIB processing. - Allow to configure maximum interface number set service snmp mib interface-max '100' ifmib_max_num_ifaces NUM Sets the maximum number of interfaces included in IF-MIB data collection. For servers with a large number of interfaces (ppp, dummy, bridge, etc) the IF-MIB processing will take a large chunk of CPU for ioctl calls (on Linux). Setting a reasonable maximum for the CPU used will reduce the CPU load for IF-MIB processing. For example, configuring "ifmib_max_num_ifaces 500" will include only the first 500 interfaces based on ifindex and ignore all others for IF-MIB processing. (cherry picked from commit 30a05ee1d447c6f92627162a506225f833a80f8c) 2023-05-17T04:10:36+00:00 Indrajit Raychaudhuri irc@indrajit.com 2023-05-17T01:49:59+00:00 urn:sha1:96d846d27ac818ee9a23bb7194bb58cfb7093387 Use a single ip-address validator to combine and replace ipv4-address and ipv6-address validators. 2023-05-08T20:45:53+00:00 Christian Breunig christian@breunig.cc 2023-05-08T19:27:14+00:00 urn:sha1:1dc79cebc6d27a8f9d2f9ca9c2e0f2fd0809d940 2023-04-02T07:53:39+00:00 Christian Breunig christian@breunig.cc 2023-04-02T07:25:35+00:00 urn:sha1:809f28f2b95a788d23db006a041955e7167a285d Remove redundant XML CLI node definitions for the common description node by referencing the common building block. 2023-02-10T18:42:44+00:00 Christian Breunig christian@breunig.cc 2023-02-10T18:42:44+00:00 urn:sha1:011e6a2cdea8fca73f7c433de5e2d6bc22bd9c19 After the RESTRICTED view was introduced snmpd requires a network to be specified. Before adding the RESTRICTED view snmpd always assumed the default network 0.0.0.0/0. This commit re-adds the build in default networks for IPv4 and IPv6 and exposes it as a proper default to the CLI so the user is informed about it: vyos@vyos# set service snmp community foooo Possible completions: authorization Authorization type (default: ro) + client IP address of SNMP client allowed to contact system + network Subnet of SNMP client(s) allowed to contact system (default: 0.0.0.0/0, ::/0) 2023-01-18T18:14:09+00:00 Nicolas Fort nicolasfort1988@gmail.com 2023-01-18T16:17:17+00:00 urn:sha1:67fa5f55ac79838768b4b0a5f6d2c4b3b4c8e762 2023-01-18T15:16:05+00:00 Nicolas Fort nicolasfort1988@gmail.com 2023-01-18T15:09:32+00:00 urn:sha1:1ce8e672b57e03e144998cb0a56ad1622c667a1d 2022-10-30T11:50:36+00:00 Christian Poessinger christian@poessinger.com 2022-10-30T11:50:36+00:00 urn:sha1:3f91033927d80748b70e1ef58b2941643d1aca33 2022-10-29T18:58:37+00:00 Christian Poessinger christian@poessinger.com 2022-10-29T18:58:37+00:00 urn:sha1:dda62226353ebc198b4dbbd319412bb5d1d1ece2