staging/xback/package/base-files, branch master

base-files: derive DHCP DUID from device MAC address

2026-06-24T09:21:28Z

The DUID-UUID was generated from a random UUID, which is regenerated on every fresh flash and therefore does not survive reconfiguration events such as reflashing without keeping the configuration. RFC8415/RFC6355 prefer a DUID that remains stable across such events. Add a ucode helper that picks the first LAN port (falling back to WAN) from /etc/board.json, resolves its MAC address and derives a stable UUID from it, falling back to a random UUID only when that fails. Signed-off-by: Felix Fietkau

base-files: handle name collision between kernel UBI volume and MTD partition

2026-06-16T14:07:58Z

On the AP-325 (and variants), the bootloader enforces a particular UBI volume layout and naming, so unfortunately the kernel's UBI volume and MTD partition end up with the name, which confuses the current logic. Therefore, add an option to ignore the MTD partition. Signed-off-by: Lukas Stockner Link: https://github.com/openwrt/openwrt/pull/20738 Signed-off-by: Paul Spooren

base-files: support rootfs_data on its own partition

2026-06-16T14:07:48Z

The current code assumes that the rootfs_data UBI volume is on the same MTD partition as the rootfs. Unfortunately, this does not work on the Aruba AP-325 (and variants), since the bootloader enforces a particular UBI volume layout. Therefore, this adds a separate variable to set the rootfs_data partition, and updates all existing devices with a non-default rootfs partition to also specify the new variable. Signed-off-by: Lukas Stockner Link: https://github.com/openwrt/openwrt/pull/20738 Signed-off-by: Paul Spooren

Revert "base-files: support rootfs_data on its own partition"

2026-06-16T14:05:25Z

This reverts commit 13fc688f033895e0ba91c1d752ffd63a06760ef5. Wrong Signed-off-by line was used, reverting and re-applying. Signed-off-by: Paul Spooren

Revert "base-files: handle name collision between kernel UBI volume and MTD partition"

2026-06-16T14:05:23Z

This reverts commit eef8c718b474aff652b42c2e96b55b1b310f7f56. Wrong Signed-off-by line was used, reverting and re-applying. Signed-off-by: Paul Spooren

base-files: handle name collision between kernel UBI volume and MTD partition

2026-06-16T11:45:44Z

base-files: support rootfs_data on its own partition

2026-06-16T11:45:44Z

scripts: dhcp/dhcpv6: handling of invalid client ID values

2026-06-11T08:40:57Z

Verify and clean up client ID and global DUID config values before use, in order to prevent DHCP client malfunction and loss of IPv4 and/or IPv6 connectivity. - Accept common separators in the string (colon, dash, spaces/tabs, lf) - Ignore invalid values (non-hex or odd-numbered length) - Log a warning for invalid settings The fall back mechanism is as follows: If a (user-configured) network..clientid setting is found invalid, ignore and fall back to using network.globals.dhcp_default_duid. In case that's also invalid (e.g. has been tampered with), don't pass a client ID to updhc/odhcpc. In that case, udhcpc/odhcpc will use their defaults, which currently is the i/f MAC address resp. the i/f DUID-LL. Only error handling is introduced, no behavior change for valid settings. Signed-off-by: Shine <4c.fce2@proton.me> Link: https://github.com/openwrt/openwrt/pull/23662 Signed-off-by: Robert Marko

base-files: move config_generate to preinit

2026-06-05T18:53:18Z

The mutex file via '/tmp/.config_pending' should prevent the command '/sbin/wifi config' from being called in the ieee80211 hotplug when loading the kernel modules [1]. Since the file '/etc/board.json' does not yet exist and could be incomplete. The '/etc/board.json' file is modified in the '/sbin/wifi config' script. This is only generated during the first boot when '/bin/config_generate' is called. This whole handling is unclean. Therefore the creation of the default configuration '/etc/config/network', '/etc/config/system' and '/etc/board.json' via '/sbin/config_generate' is moved to the preinint after the rootfile system has been mounted The advantage now is that on an ieee80211 hotplug event, the '/etc/board.json' is already present which simplifies the whole thing. [1] https://github.com/openwrt/openwrt/blob/main/package/network/config/wifi-scripts/files/etc/hotplug.d/ieee80211/10-wifi-detect Fixes: b993a00b82b1 ("base-files: fix duplicate wifi radio sections when using phy renaming") Signed-off-by: Florian Eckert

base-files: add options to disable default button handling

2026-05-19T22:02:31Z

In case OpenWrt is used to build a custom distribution, the default button handling logic may be undesired. Add config options to disable default standard button handling code at build-time. Signed-off-by: David Bauer