| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
smoketest: T9014: guard architecture specific smoketests
|
|
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 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.
|
|
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.
|
|
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.
|
|
|
|
(#5203)
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.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
The inotify support for overlayfs is no longer needed. Native upstream support
landed in kernel 4.16 (commit 31747eda41ef/764baba80168 in 2018, which made
overlayfs hash inodes by their lower inode so fsnotify works on overlay mounts),
and kernel 6.8 (commit bc2473c90fca in 2023) extended it so fsnotify generates
events for operations on the real underlying files of an overlay.
|
|
Move from the out-of-tree to an in-tree variant of the OpenVPN DCO module. As
this was not available in the previous used LTS 6.6 Kernel it now is available
while we upgrade to Linux 6.18.
|
|
Extend required kernel options in arm64 test to cover CN10308
platform features, including OCTEONTX2 networking, I2C, GPIO,
MMC, LED, and RTC drivers.
|
|
Check the Kernel `kexec` and additional arm64 modules
|
|
|
|
The legal team says years are not necessary so we can go ahead with it, since
it will simplify backporting.
Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \
's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors <maintainers@vyos.io>/g'
In addition we will error-out during "make" if someone re-adds a legacy
copyright notice
|
|
|
|
|
|
There is "set system option kernel amd-pstate-driver" which requires a Kernel
driver to operate. This adds a smoketest validating the Kernel configuration.
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
From Kernel commit e485f3a6eae0 ("ixgb: Remove ixgb driver")
There are likely no users of this driver as the hardware has been discontinued
since 2010. Remove the driver and all references to it in documentation.
|
|
|
|
|
|
* T5195: move run, cmd, call, rc_cmd helper to vyos.utils.process
* T5195: use read_file and write_file implementation from vyos.utils.file
Changed code automatically using:
find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import read_file$/from vyos.utils.file import read_file/g' {} +
find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import write_file$/from vyos.utils.file import write_file/g' {} +
* T5195: move chmod* helpers to vyos.utils.permission
* T5195: use colon_separated_to_dict from vyos.utils.dict
* T5195: move is_systemd_service_* to vyos.utils.process
* T5195: fix boot issues with missing imports
* T5195: move dict_search_* helpers to vyos.utils.dict
* T5195: move network helpers to vyos.utils.network
* T5195: move commit_* helpers to vyos.utils.commit
* T5195: move user I/O helpers to vyos.utils.io
|
|
|
|
|
|
As WireGuard is now part of the mainline Kernel, we no longer need to validate
it using the external module loader/tester.
|
|
|
|
|
|
|
|
This is for better readability during testruns
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vyos-smoketest-integration (T2832)
* 'master' of github.com:vyos/vyos-smoketest: (153 commits)
pppoe-server: test some more values
lcd: adjust to cli changes
lcd: adapt test to new CLI design
pppoe-server: initial smoketest with local and radius auth
pppoe: validate dhcpv6 client will be started
wireless: validate hostapd/wpa_supplicant is running
pppoe: sync to new dhcpv6-pd cli
anyconnect: T2812: add basic testing
ethernet: check interface disable state
router-advert: check 'infinity' option in script logic
ssh: config file is now volatile (moved to /run)
ipv6: link-local: test address assignment on interfaces
router-advert: add initial test
mdns-repeater: add basic test
pseudo-ethernet: extend smoketests with VIFs
l2tpv3: add initial interface test
wireless: use library function for loading kernel modules
ethernet: test "ip" subtree of interface for e.g. ARP settings
pppoe: use assertEqual()
service: bcast-relay: add initial tests
...
|
