| Age | Commit message (Collapse) | Author |
|
This version includes a fix for
T8391: Bonding interface permission errors with custom Ethernet MTU
|
|
build: T9140: include version and flavor information in the boot menu
|
|
|
|
kernel: T9138: enable support for Microsoft MANA NIC driver
|
|
|
|
iproute2: T8926: add custom build which matches Kernel 6.18
|
|
T9124: Fix smoketest file check
|
|
|
|
The prior expect of 'No such file or directory' can prevent smoketests from completing if test fails with that same error
|
|
Testsuite: T9021: answer question during test for bash_history migration
|
|
|
|
T9099: improve test framework - add safeguards
|
|
Kernel: T9103: fix arm64 syscalltbl path breaking linux-perf package build
|
|
Building linux-perf-* on a native arm64 build host failed with "No rule to
make target '.../unistd_64.h'" because arch/arm64/kernel/Makefile.syscalls
overrides syscalltbl with a path relative to the kernel root, but
tools/lib/perf/Makefile invokes the header generator from tools/lib/perf/
instead. Make the override absolute, matching the srctree-prefixed default.
|
|
BOOTLOADERchooseSerialConsole() sent fixed DOWN/ENTER keystrokes with blind
sleeps to navigate the post-install GRUB "Boot options" and "Select console
type" submenus. Under host load, a dropped keystroke could land navigation one
level too deep (e.g. "Select boot mode" instead of "Select console type").
GRUB submenus never time out on their own, so the VM sat there until the
unrelated 600s login wait in loginVM() expired, producing a confusing
pexpect.TIMEOUT far from the real cause.
Add child.expect() checks after each submenu transition to confirm the expected
menu actually rendered before sending the next keypress, so a misnavigation now
fails fast and points at the right step.
|
|
Test targets forward extra CLI arguments to their scripts via
$(filter-out $@,$(MAKECMDGOALS)) (e.g. make test -- --match interfaces_bond)
Those extra words are also goals as far as make is concerned, so after the test
recipe succeeded, make went on to "build" --match and interfaces_bond too,
falling through to the generic `%:` flavor rule and running
build-vyos-image --match
which errored and masked the fact that the smoketest itself had already passed.
Declare the trailing goals as phony no-ops when the primary target is one of
the test targets, so they no longer reach the `%:` rule.
The existing MATCH=<value> form is unaffected.
|
|
sbom: T9098: syft should run un squashfs instead of unpacked chroot
|
|
Kernel: T8868: Enable crash dump (kdump) and debug info in config
|
|
lb (live-build) binary runs binary_rootfs first, then binary_grub-efi.
binary_grub-efi temporarily installs EFI tooling and then runs:
"apt remove --auto-remove --purge --allow-remove-essential"
That cleanup is safe for the already-generated squashfs, but it mutates
build/chroot and can remove vyos-1x, breaking subsequent work that expects
chroot to remain intact for SBOM generation.
But why unpacking the squashfs?
In an ideal world we could call syft on the compressed squashfs file which is
supported. In our world, we do use a BCJ pre-filter chained with LZMA2 for
compressing the squashfs, which will increase the compression ratio without a
decompression penalty.
Difference: ~14.3 MB, ~2.7% smaller
This is unsupported by fyft which means we do need to unpack the squashfs first
before checking the files and generating the SBOM file.
|
|
openssl: T9083: fix APT detected package downgrade despite identical versions
|
|
VyOS rolling APT repo (packages.vyos.net/repositories/rolling) publishing its
own openssl/libssl3 packages, pinned at priority 600 (higher than Debian's 500)
causes a "poisoning" of the APT cache policy inside the chroot:
openssl:
Installed: 3.0.20-1~deb12u2
Candidate: 3.0.20-1~deb12u2
Version table:
* 3.0.20-1~deb12u2 500 <- debian bookworm + bookworm-security
* 3.0.20-1~deb12u2 600 <- packages.vyos.net rolling (same version string, higher pin)
* 3.0.17-1~deb12u2 500 <- bookworm-updates
This results in APT seeing a version-string tie between Debian's build and the
VyOS repo build of the same package and, because of the pin-priority swap,
classifies switching to the VyOS repo copy as a "downgrade".
This is fixed by appending a clear VyOS related marked to the package version,
preventing any possible downgrade detection.
Signed-off-by: Date Huang <tjjh89017@hotmail.com>
Co-authored-by: Christian Breunig <christian@breunig.cc>
|
|
Kernel: T5641: enable module compression to save disk space
|
|
Enabling the following options allows us to use `kdump-tools`:
- `CONFIG_CRASH_DUMP`
- `CONFIG_DEBUG_INFO`
- `CONFIG_PROC_VMCORE`
|
|
Kernel: T9067: Update Linux Kernel to 6.18.38
|
|
Option useful during development to not automatically clean the Linux Kernel
source folder of all its intermediate files.
|
|
After signing the Linux Kernel modules with the ephemeral key, proceed
by compressing the Kernel modules with xz to reduce the final ISO image
size.
Initial tests have shown a size reduction by 60MiB.
|
|
|
|
|
|
build: T9058: add a script for building Squid from source
|
|
|
|
kernel: T8940: disable HYPERV_VTL_MODE and restore Hyper-V vPCI driver
|
|
|
|
ci: T9047: dispatch docker-image rebuild against production ref
|
|
|
|
The Docker image rebuild curl-dispatch was still pointed at
vyos-reusable-workflows main, which is frozen pre-App-token-migration and
still uses the retired secrets.PAT checkout pattern (empty token, immediate
"could not read Username" auth failure on every dispatched run since
2026-06-02). The fix already shipped and is live on production
(VyOS-Networks/vyos-reusable-workflows#123, merged 2026-05-31) — this
caller was simply never repointed.
🤖 Generated by [robots](https://vyos.io)
|
|
T9040: Build FIPS-provider OpenSSL version
|
|
Build FIPS-compatible OpenSSL binaries
The FIPS provider does not get built and installed automatically.
To enable it, you need to configure OpenSSL using the `enable-fips` option.
|
|
accel-ppp-ng: T9039: update the commit hash
|
|
for the fix for legacy hash algorithm loading
to make MS-CHAP work correctly again
|
|
podman: T9024: package upgrade from v4.9.5 to v5.8.4
|
|
T9028: add .claude folder to .gitignore
|
|
T9029: Switch default branch for CI workflows
|
|
This updates the used Podman version from 4.9.5 to 5.8.4 which is a major bump.
For this update to work on Vyos we also do need to switch from crun to runc, as
the Debian Bookworm provided version of crun is not working with podman 5.8.4.
Building crun from Debian trixie package sources does not work due to missing
build time dependencies.
|
|
Switch to "production" branch to call the package build workflow.
|
|
`icon_heigh` is a typo of the GRUB2 boot_menu property `icon_height`. Icons are
already disabled in this menu via `icon_width = 0` + `item_icon_space = 0`, so
correcting the property name is behaviour-neutral. Clears the lone typos-check
hit on this repo ahead of the T8490 ruleset pilot active flip.
🤖 Generated by [robots](https://vyos.io)
|
|
|
|
Kernel: T8914: add support for 2.5G pluggables on BCM57810S
|
|
Kernel: T8605: net/l2tp: allow unmanaged tunnel setup without route to peer
|
|
Kernel: T9010: update existing patches to remove "hunk off" notices
|
|
Add the well-known JAMESMTL kernel module patch for bnx2x to advertise 2.5Gbit/s
capabilities on Broadcom NetXtreme2-X cards with BCM57810S chipset.
This is useful for ISP GPON access networks that use 2.5Gbit/s pluggables and
need the NIC to negotiate beyond 1000baseT/Full, avoiding the 940Mbit/s
practical cap on overprovisioned 1G services.
References:
* https://hack-gpon.org/broadcom-57810s/
* https://github.com/JAMESMTL/snippets/blob/dceb2fee74d80c66d/bnx2x/patches/bnx2x_warpcore_8727_2_5g_sgmii_txfault.patch
|