Gennaro Cimmino
3797d2292b
Both notifiers allocate their work with GFP_ATOMIC and return NOTIFY_BAD when that fails. The kernel takes that as a veto only for a route or a rule being added; a route delete or a neighbour update goes ahead regardless, and the hardware keeps forwarding by what the lost event would have changed. On such a failure, queue a work item kept in the driver's control structure, which needs no allocation. It unregisters the FIB notifier, takes out every route the driver programmed and registers it again, so the kernel replays the FIB as it does at probe. The stale entry still forwards until that flush, which waits for the work already queued; from there until the replay is done, the catch-all rows trap what the routes no longer cover. A replay can fail too, short of memory the same way or on a route the notifier refuses that came in while it was away: it is flushed and tried again after a delay that doubles up to 64 seconds. An add the kernel refused schedules a replay as well, which finds nothing to correct. The work is enabled once probe has registered the notifier, and only where the L3 tables provide the catch-all rows; a family that routes through PIE rules keeps the old behaviour. Remove disables it before unregistering the notifiers. Tested on a Hasivo S1100W-8XGT-SE (RTL9303) with L3 offload enabled, through bench-only debugfs counters that make the next allocations of either notifier fail. A route deleted while its event is lost: without this change its row keeps forwarding and 5 of 5 echoes still reach the old gateway; with it the replay takes the row out and none do. A permanent neighbour moved to another host while its event is lost: without this change all 5 echoes still go to the old host, with it to the new one. With the replay's first allocation failing as well, the replay fails once and the retry converges the same way. An add whose event is lost is refused either way. The untouched IPv4 and IPv6 routes forward in hardware after every replay. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25603 Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.8+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0