| Age | Commit message (Collapse) | Author |
|---|
|
pki: T8877: Add ability to show private key in pem format
|
|
This cleanup enhances readability and aligns the output
with the actual data being displayed.
|
|
Add op-mode command having ability to show private
key in pem format as part of PKI configuration.
This is needed for users who want to render the
certificate and its private key.
|
|
|
|
|
|
|
|
T8445: T8335: Extend config activation system
|
|
op-mode: T8483: fix /show_sensors.py: No such file or directory
|
|
Maintainers agreed to remove the CPU-flag-based hypervisor check, as it is
arbitrary and can produce incorrect behavior. Sensors can be passed through to
virtual machines, so running in a VM should not be treated differently.
If no sensors are detected - whether on a hypervisor VM or on bare metal - the
command now reports: "No sensors found".
|
|
|
|
|
|
|
|
serial: T8375: use boot activation script to define a serial console on the CLI
|
|
config-sync: T7784: Add command to diff configuration with secondary node
|
|
After rewriting the op-mode handlind code and introducing virtualTagNodes for
op-mode, also all <command> statements will be executed by a runner. Executing
"bash -c ''" code within that runner lacks the proper environment.
This can be verified by adding "env" into the bash -c '' executions string.
Solve this issue by moving the hypervisor detection code to show_sensors.py.
|
|
Previously, VyOS hardcoded the kernel boot log console to either ttyS0 or
tty0, with no post-install CLI method to change it (manual GRUB edits
were required).
This commit adds a new CLI node:
system console device <name> kernel
When set, the selected serial console is used as the kernel boot console.
When removed, the kernel boot console falls back to tty0.
|
|
Required during first-boot of a system. We have images form amd64 and arm64
CPUs which also tend to have different serial interfaces (ttyS vs. ttyAMA).
The images which are installed have the correct serial setting for GRUB (ttyS0
or ttyAMA0) and the activation script will probe the Kernel command-line. If a
serial interface is defined, we will include it in the VyOS CLI configuration.
|
|
For the sake of nice grep lines and refactoring we have an unspoken - unwritten
rule considered as folklore to have imports one per line. This helped in the
past with refactorings.
|
|
Add a new operational command to compare configuration between
nodes participating in config synchronization.
New command:
- `show configuration secondary sync [commands] [running|candidate|saved] [config-node-path]`.
This allows operators to view configuration differences across secondary peer
before applying or syncing changes.
Supports:
- displaying using raw diff and 'commands' format;
- optional section filtering (subtree comparison);
- selectable config source (running, candidate, saved).
|
|
Fix typos and mistakes
No functional changes
|
|
Fix typos and mistakes in the commands and comments
No functional changes
|
|
When performing an image installation and the user chooses vyos as the default
password, a warning is emitted.
The combination vyos/vyos is used in brute force lists and have been seen
multiple times in the wild. When adding the user via:
set system login user vyos authentication plaintext-password vyos
a warning should be shown!
|
|
T8352: VPP add op-mode commands to show bonding interfaces
|
|
op-mode: T8400: remove calls to tshark binary for PCAP files
|
|
T8396: VPP op-mode "show interfaces vpp" missing ipv6 address
|
|
|
|
|
|
|
|
The tshark binary might not be installed in every image, thus this command is
not only gambling if it will work or not, it will also bloat the image if
installed.
PCAP files should be properly revisited on a workstation and not on a NOS
(Network Operating System).
|
|
|
|
|
|
opmode: T8343: implement common verify_cli_exists() helper
|
|
|
|
Instead of re-defining a per module helper which verifies that a given CLI path
exists during execution, rather create a generic representation which takes a
CLI path (list) as argument with an optional error message to display on the
CLI.
This is the initial implementation of the generic helper with some migrations
for VPP, WireGuard and Wireless interfaces. More opmode scripts should follow.
|
|
tech-support: T8215: Extend tech-support archive and report generation
|
|
vpp: T8339: Cleanup vpp interfaces and kernel-interfaces after migration
|
|
T7513: vyos-1x: CGNAT Exclude Rule CLI support
|
|
|
|
ipsec: T8136: IPSEC PPK support
|
|
|
|
|
|
- Exclude .iso files from `/config` and `/home/*` to avoid large images
- Exclude previous debug-archived from new archives
- Include `/run` directory contents
- Add kernel modules information (`lsmod`)
- Add PCI details (`lspci -knnv`)
- Include full `/config` directory
- Add FRR memory usage (`vtysh "show memory"`)
- Add VPP info (`vppctl`)
- Add NUMA details (`numactl --hardware`, `numastat -cm`)
Full list of commands here: https://vyos.dev/T8215
|
|
|
|
|
|
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
|
|
T8257: image install search previous needs to consider legacy bind mount
|
|
|
|
For those images created with the legacy bind mount, the resident
config.boot at {mounted_image}/opt/vyatta/etc/config is the baseline,
not the saved config (which is then restored at boot). Image install
needs to search the legacy path at {mounted_image}/config as well as the
normalized path.
|
|
|
