Age | Commit message (Collapse) | Author |
|
`mokutil --sb-state` will output "This system doesn't support Secure Boot" to stderr.
and return error code 255 if the UEFI system doesn't support secure boot.
Signed-off-by: Date Huang <tjjh89017@hotmail.com>
|
|
- Resolved unhandled exception occurring with default round-robin policy config.
- Added default filter to ensure proper round-robin policy.
|
|
In "option-def" parameter "record-types" field is an array of uint8 in format "<netmask>, <network-byte1>, <network-byte2>, <network-byte3>, <router-byte1>, <router-byte2>, <router-byte3>" where <network-byte3> with the value 0 is omitted, so the minimal length of array is 7 (e.g. for routing 10.1.0.0/16 via 10.1.6.4 "record-types": "16,10,1,10,1,6,4")
|
|
Commit 042be39cc ("syslog: T5367: add format option to include timezone in
message") added an invalid, outer if-statement when rendering the rsyslog
configuration option for TCP.
Remote hosts only got added when the format option "octet-counting" was defined
in addition to the TCP protocol. This has been fix and now TCP transport is
decoupled from octet-counting mode.
|
|
|
|
T6695: Machine-readable operational mode support for traceroute
|
|
|
|
dhcp_server: T6852: Add op mode command "show dhcpv6 server statistics"
|
|
Not all NICs could provide ring-buffers info requested by ethtool
in JSON format
For example 'vif' Xen/XCP-NG interfaces
Fix it
|
|
|
|
system_login: T6807: allow a trailing slash character in system login
|
|
op_mode: T6808: Console server op mode commands throw errors when console server is not configured
|
|
login: T6712: honor 80x25 terminal size for nonproduction banner message
|
|
|
|
In the new iproute2 package the link to `ip` was changed
$ file /usr/sbin/ip
/usr/sbin/ip: symbolic link to ../bin/ip
Fix smoketest
|
|
server is not configured
|
|
Allow the use of a trailing slash `("/")` at the of the user's home directory path. For example `/home/test/`
|
|
T4583: Rewrite VRRP op-mode to vyos.opmode format
|
|
T6791: Extend fair-queue hash-interval
|
|
|
|
|
|
|
|
pki: T4914: Rewrite the PKI op mode in the new style
|
|
|
|
|
|
reformat file by linter rules
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 3abe7c72c95c3d9b825db08b092c555786e9fbcf)
Co-authored-by: Viacheslav Hletenko <v.gletenko@vyos.io>
|
|
pki: T6766: Add support for ECDSA private keys
|
|
haproxy: T6745: Rename reverse-proxy to haproxy
|
|
|
|
|
|
|
|
config-mgmt: T5976: add option for commit-confirm to use 'soft' rollback
|
|
|
|
vyos.configtree: T4318: Allow set tag flag to true or false
|
|
|
|
smoketest: T4576: add guard timeout for systemd in log level tests
|
|
|
|
cli: T6740: add a converter from set commands to config
|
|
Signed-off-by: Daniil Baturin <daniil@baturin.org>
|
|
pbr: T6430: Local IP rules targeting VRFs by name as well as route table IDs
|
|
|
|
* This is the `policy local-route*` part of T6430, manipulating ip rules,
another PR covers firewall-backed `policy route*` for similar functionality
* Local PBR (policy local-route*) can only target table IDs up to 200 and
the previous PR to extend the range was rejected
* PBR with this PR can now also target VRFs directly by name, working around
targeting problems for VRF table IDs outside the overlapping 100-200 range
* Validation ensures rules can't target both a table ID and a VRF name
(internally they are handled the same)
* Relocated TestPolicyRoute.verify_rules() into VyOSUnitTestSHIM.TestCase,
extended to allow lookups in other address families (IPv6 in the new tests).
verify_rules() is used by original pbr and new lpbr smoketests in this PR.
|
|
pki: T6481: auto import ACME certificate chain into CLI
|
|
GitHub: T6494: add parallel step to run interface based smoketests
|
|
When using an ACME based certificate with VyOS we provide the necessary PEM
files opaque in the background when using the internal tools. This however will
not properly work with the CA chain portion, as the system is based on the
"pki certificate <name> acme" CLI node of a certificate but CA chains reside
under "pki ca".
This adds support for importing the PEM data of a CA chain issued via ACME into
the "pki ca AUTOCHAIN_<name> certificate" subsystem so it can be queried by
other daemons. Importing the chain only happens, when the chain was not already
added manually by the user.
ACME certificate chains that are automatically added to the CLI are all prefixed
using AUTOCHAIN_certname so they can be consumed by any daemon. This also adds
a safeguard when the intermediate CA changes, the referenced name on the CLI
stays consitent for any pending daemon updates.
|