vyos-1x.git/smoketest/scripts/system, branch rollingVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling2026-10-11T07:43:36+00:00debian: T9455: drop exfat-fuse in favour of in-kernel exFAT driver2026-10-11T07:43:36+00:00Christian Breunigchristian@breunig.cc2026-10-11T07:43:36+00:00urn:sha1:e5568919ced157534e05374ae50822a4efd94517
The VyOS kernel ships the native exFAT driver (CONFIG_EXFAT_FS=m), so the
userspace FUSE implementation is no longer needed. The exfatprogs tools for
creating and checking filesystems are kept.
The kernel options smoketest now verifies CONFIG_EXFAT_FS is enabled.
Merge pull request #5433 from c-po/arch-arm64-smoketests2026-08-31T06:09:47+00:00Christian Breunigchristian@breunig.cc2026-08-31T06:09:47+00:00urn:sha1:2c269ef450f88690d03970fcafb1dbaa8b3b7f54
smoketest: T9014: guard architecture specific smoketestssmoketest: T9014: add CPU architecture decorator to guard tests2026-08-29T12:32:57+00:00Christian Breunigchristian@breunig.cc2026-08-29T12:32:57+00:00urn:sha1:cf018cdd38eb30830c55d54591238b85516e5c1a
VyOS supports both amd64 and arm64 CPU architectures, but not every smoketest
is applicable to both of them. Add a cpu_arch() decorator to vyos.utils.cpu
which takes a list of supported CPU architectures - if the test is run on any
other architecture it is skipped with a message naming both the supported and
the current architecture. Tests without the decorator run everywhere.
Use it to replace the ad-hoc IS_ARM64 checks in test_kernel_options.py and to
guard the x86 only intel and intel_qat module sets in test_module_load.py,
which so far failed on arm64.
vrf: T6097: add the nat anchor conntrack zoning needs2026-08-29T07:27:35+00:00Christian Breunigchristian@vyos.io2026-08-25T16:16:18+00:00urn:sha1:c1f2dd914185f6d22c359b9027c604e338ef94a1
VRF conntrack zoning assigns a zone to the original direction only, which
leaves every reply tuple in the default zone 0. That is deliberate and is
required by T3655: the reply of a flow that was leaked out of a VRF and
NATed in the default VRF arrives on an interface carrying no zone at all,
so it can only be matched when the reply tuple lives in zone 0 as well.
The side effect is that two flows differing only by their VRF end up with
identical reply tuples. The second conntrack entry can then not be
inserted and its packet is dropped, visible as insert_failed and drop in
"conntrack -S".
The kernel already resolves this, but only once nf_nat is registered for
the address family: a null binding is applied to every new conntrack entry
and get_unique_tuple() reallocates the clashing reply tuple. nf_nat is
registered as soon as any "type nat" chain exists in that family.
IPv4 always had one, because the startup ruleset created "table ip nat"
unconditionally. IPv6 never had an equivalent, so IPv6 was dropped while
IPv4 kept working by accident. That is the asymmetry reported here.
Create the chain from the VRF code instead, in the inet family so one
table covers both, and only while conntrack zoning is installed. A
registered nf_nat costs about 200ns per new connection, measured at +19%
for IPv4 and +11% for IPv6 in a connection setup benchmark, and is not
worth paying on systems without a VRF.
kdump: T8868: Implement kernel crash dump support2026-08-20T13:35:07+00:00Oleksandr Kuchmystyio.kuchmystyi@vyos.io2026-07-09T08:16:09+00:00urn:sha1:2054c3c53f8bc83733c8ef81c2cc57f4e6b27f5a
Add new CLI subtree 'system option kdump' with memory reservation and
local dump path configuration. Also add 'show system kdump' and
'show system kdump dumps' operation mode commands to get
status of the configuration and list of dumps.
Extend 'show tech-support report' and 'generate tech-support archive' with
kdump service status, active config files and the recently kernel dump file.
utils: T9008: migrate remaining cmd() callers to cmdl() and remove cmd()2026-07-17T16:10:08+00:00Christian Breunigchristian@breunig.cc2026-07-09T20:21:52+00:00urn:sha1:e0684c0c343835c7674a94424d847592511915b0
Complete the safer-subprocess migration started by the cmdl()/ifconfig
refactoring and convert every remaining vyos.utils.process.cmd() call site to
the list-based cmdl().
Drop the vyos.utils.process.cmd() implementation as it is no longer in use.
smoketest: T8940: HYPERV_VTL_MODE must not be enabled; require vPCI2026-07-05T10:04:37+00:00Alex Kudentsov43482574+alexk37@users.noreply.github.com2026-07-05T10:04:37+00:00urn:sha1:3995d5769fa2bf7661a065fbe020826e91687d05Smoketest: T8879: add missing Kernel config tests for hypervisor platforms (#5203)2026-05-18T10:05:24+00:00Christian Breunigchristian@breunig.cc2026-05-18T10:05:24+00:00urn:sha1:964a01697f3c2361ce4324fb8333f5fe4d2b0434
Add checks for common used Hypervisor platforms where we know VyOS runs on.
Check that Linux Kernel is build with proper drivers for Hyper-V, VirtIO
and VMware.smoketest: T6847: probe for Intel I40E and IAVF Out-Of-Tree drivers2026-05-11T19:27:16+00:00Christian Breunigchristian@breunig.cc2026-05-09T05:59:11+00:00urn:sha1:38e21db24b41c4f0ea7fbbbcfe478ae4bc7f8447
The Intel iavf driver (formerly i40evf) is the Linux virtual function driver
for modern Intel Ethernet adapters supporting SR-IOV, including the X700/E800
series.
Renamed to iavf to support future devices, it replaced i40evf entirely by 2019.
The driver facilitates high-performance networking in virtualized environments.
smoketest: T8147: add Kernel option tests for dummy interfaces2026-05-06T17:18:08+00:00Christian Breunigchristian@breunig.cc2026-05-03T17:39:21+00:00urn:sha1:136f677b7accfba4be0d3e5519a89958f0b51f32