netifd, branch master

bridge: skip present toggle in bridge_free_member() when device is active

2026-02-26T10:25:53Z

When moving a device between bridges during config reload, the present toggle in bridge_free_member() can disrupt a bridge that has already successfully claimed the device. During device_init_pending(), bridges are processed in alphabetical order. If the new bridge (e.g. br-lan) is processed before the old bridge (e.g. br-wan), it successfully claims the device. When the old bridge then flushes the device, the present toggle tears down and rebuilds the new bridge unnecessarily, causing interface setup failures. Only toggle the present state when the device has no active claims, which is the case when bridge_enable_member() failed (e.g. because the device was still in the old bridge at the time). Signed-off-by: Felix Fietkau

global: add support for PSE-PD control

2026-02-23T09:58:26Z

This commit adds basic support for modern PSE-PD/POE control. It requires linux 6.18 or a backport. The backports are in those PRs: https://github.com/openwrt/openwrt/pull/21810 https://github.com/openwrt/openwrt/pull/21926 Additionally the Makefile for netifd is adjusted: https://github.com/openwrt/openwrt/pull/21918 In Detail: * device.h - Added PSE device attributes & settings * device.c - Added UCI parsing for PSE options * system-linux.c - Added genetlink PSE get/set functions Signed-off-by: Carlo Szelinsky Link: https://github.com/openwrt/netifd/pull/65 Signed-off-by: Robert Marko

examples: sync wireless scripts with openwrt

2026-02-15T08:26:17Z

Signed-off-by: Felix Fietkau

proto-ucode: add ucode proto handler scripts

2026-02-15T08:25:47Z

Add the ucode script infrastructure for ucode-based protocol handlers: proto.uc: Handler management module loaded by main.uc. Scans proto/*.uc for handler scripts, registers proto_config_load callback on netifd.cb for UCI config reading and sorted JSON serialization. proto-ucode.uc: Subprocess wrapper spawned for setup/teardown. Receives handler script path, proto name, action, interface name, config JSON, and optional device name via ARGV. Creates proto object with notification methods mapping to ubus calls to network.interface..notify_proto. Loads handler module via include() with scope injection and dispatches the requested action. Signed-off-by: Felix Fietkau

proto-ucode: add ucode protocol handler infrastructure

2026-02-15T08:25:27Z

Add C infrastructure for ucode-based protocol handlers. Handlers are registered via netifd.add_proto() from ucode scripts loaded at startup. Signed-off-by: Felix Fietkau

proto: add config_load callback to proto_handler

2026-02-15T08:24:31Z

Allow protocol handlers to implement custom config loading by adding a config_load callback to struct proto_handler. When set, it replaces the default uci_to_blob() call in config_parse_interface(). This enables protocol handlers (such as ucode-based ones) to perform their own UCI reading and config serialization. Signed-off-by: Felix Fietkau

proto-ext: extract shared protocol handler code from proto-shell.c

2026-02-15T08:24:31Z

Move the generic protocol handler infrastructure (state machine, notification handling, dependency tracking, checkup mechanism) into proto-ext.c for reuse by other protocol handler backends. proto-shell.c now only contains shell-specific logic: script spawning, handler parsing and registration. It delegates to proto_ext_run() for state machine transitions and proto_ext_notify() for notifications. The handler field access pattern changes from state->handler->proto.X to state->proto.handler->X, using the handler pointer set by proto_init_interface() in proto.c. Internal handler dispatch calls (proto_shell_handler()) are replaced with state->proto.cb(), making the shared code independent of the concrete handler implementation. Signed-off-by: Felix Fietkau

interface-ip: fix fortify build error

2026-02-10T07:30:12Z

Use the correct struct member for INET6 addresses Signed-off-by: Felix Fietkau

system-linux: only parse device status for AF_UNSPEC link messages

2025-10-20T21:37:36Z

In bridge messages (family = AF_BRIDGE), the commands are the same, but the contents are different, and this can confuse netifd into thinking that devices are down, while they are actually up. Signed-off-by: Felix Fietkau

system-linux: handle RTM_DELLINK events for device state tracking

2025-10-20T17:46:54Z

Add RTM_DELLINK handling to properly track device lifecycle. When a device is deleted, update its state with flags=0 to mark it as not present. This improves synchronization compared to only relying on the hotplug handler. Signed-off-by: Felix Fietkau