staging/jow/config, branch main

netfilter: add kmod-nfnetlink-ct{helper,timeout}

2024-12-23T22:37:57Z

Add kmod-nfnetlink-ct{helper,timeout} to allow handling firewall rules in userspace (together with conntrackd). The timeout module allows specifying custom expiration rules. Signed-off-by: Joel Low Link: https://github.com/openwrt/openwrt/pull/17267 Signed-off-by: Hauke Mehrtens

config: enable SECCOMP support for loongarch64

2024-12-23T22:02:11Z

Make USE_SECCOMP selectable for loongarch64 Signed-off-by: Weijie Gao Link: https://github.com/openwrt/openwrt/pull/17335 Signed-off-by: Hauke Mehrtens

config: build: remove experimental warning from USE_APK option

2024-11-28T18:36:06Z

apk package manager is default for some time, so lets remove the EXPERIMENTAL warning from the related option. Signed-off-by: Petr Štetiar

kernel: enable pressure interface

2024-11-24T23:15:41Z

PSI provides a canonical way to see resource pressure increases as they develop, with pressure metrics for three major resources: memory, CPU, and IO. PSI stats are like barometers that provide fair warning of impending resource shortages, enabling users to take more proactive, granular, and nuanced steps when resources start becoming scarce. References: * https://www.kernel.org/doc/html/latest/accounting/psi.html * https://lwn.net/Articles/759781/ Build system: x86/64 Build-tested: x86/64/AMD Cezanne, flogic/glinet_gl-mt6000 Run-tested: x86/64/AMD Cezanne, flogic/glinet_gl-mt6000 Signed-off-by: John Audia Link: https://github.com/openwrt/openwrt/pull/13819 Signed-off-by: Hauke Mehrtens

config: dont select procd-seccomp via USE_SECCOMP

2024-11-24T11:18:21Z

base-files is including procd-secccomp as a dependency when USE_SECCOMP is selected, so there is no point in selecting the package directly here as well. Link: https://github.com/openwrt/openwrt/pull/17048 Signed-off-by: Robert Marko

config: rename SECCOMP to USE_SECCOMP

2024-11-24T11:18:21Z

It seems that we have some kind of a symbol name conflict which causes CONFIG_SECCOMP to always be read as y. Unfortunatelly, I could not figure out what is causing this, but simply renaming SECCOMP to USE_SECCOMP seems to properly work and leaves the symbol unset unless arch dependencies are satisfied. This fixes qoriq and others that dont support seccomp from failing due to procd-seccomp package being selected to get included but it cannot be built for them: ERROR: unable to select packages: procd-seccomp (no such package): required by: base-files-1637~52b6c92479[procd-seccomp] Fixes: 4c65359af49b ("build: fix including busybox, procd and apk/opkg in imagebuilder") Link: https://github.com/openwrt/openwrt/pull/17048 Signed-off-by: Robert Marko

config: Use APK as package manager by default

2024-11-10T23:09:50Z

This commit comes after a long period of hard work, starting back in early 2021 as a proof of concept. Thanks to the Alpine Linux project for creating such a nice package manager. Thanks to everyone involved; this is going to be great! Signed-off-by: Paul Spooren

menuconfig: add help description for Stack Smashing Protection options

2024-11-10T01:14:23Z

Descriptions taken from: https://wiki.osdev.org/Stack_Smashing_Protector Signed-off-by: Marius Dinu Link: https://github.com/openwrt/openwrt/pull/16897 Signed-off-by: Christian Marangi

kernel: KERNEL_NET_L3_MASTER_DEV default to y if !SMALL_FLASH

2024-11-01T10:49:09Z

Follow-up for 45d541bb409355f090b971d96ebebd8610ef84a7 This change allows features such as kmod-vrf ``` KERNEL_NET_L3_MASTER_DEV=n x86_64 generic bzImage 6,927,360 bytes aarch64 coretex-a53 kernel 4,268,836 bytes KERNEL_NET_L3_MASTER_DEV=y x86_64 generic bzImage 6,931,456 bytes aarch64 coretex-a53 kernel 4,273,042 bytes Delta: x86_64 generic +4096 bytes aarch64 coretex-a53 +4206 bytes x86_64 generic vrf.ko - 258,792 bytes aarch64 coretex-a53 vrf.ko - 263,632 bytes ``` See: https://forum.openwrt.org/t/vrf-support-testing-out-evpn-at-home/181108 https://forum.openwrt.org/t/please-enable-net-l3-master-dev-in-kernel-build-by-default/201825 Signed-off-by: Paul Donald Link: https://github.com/openwrt/openwrt/pull/16819 Signed-off-by: Robert Marko

kernel: enable Multi-Path TCP for !SMALL_FLASH targets

2024-10-26T14:21:03Z

Expose Kernel's CONFIG_MPTCP option and enable it by default for !SMALL_FLASH targets. The idea behind enabling it by default is to allow users of the binary distribution to make use of MPTCP tunneling for link aggregation. Using MPTCP for link aggregation is an often discussed topic in the forum and there is even a whole OpenWrt fork (MPTCPRouter) just for that. Enabling the kernel-side of the story by default will allow using MPTCP on vanilla OpenWrt without having to build anything from source. See also https://openwrt.org/docs/guide-user/network/mptcp Signed-off-by: Daniel Golle