Gennaro Cimmino
255b53f9c9
A source-specific route matches only the packets from its source, and the hardware matches on the destination alone, so the driver traps the destination of every such route. All of them shared one trap row with one member count, which each add overwrote: deleting one of two source-specific routes to a prefix took the row from the other, and an add of the route without a source to that prefix replaced the trap with a forwarding row, which then sent the traffic of every source to its gateway. A source-specific route added over a forwarding row took that row out, and deleting it again left the destination without one. Keep the members of each source apart on the trap row, next to those of the route without a source, and take the row out only when none is left. The route without a source joins the trap while source-specific routes remain, and keeps it after they are gone until its next event, as a multipath route keeps its trap after a member leaves. The error that stood in for this goes. Tested on a Hasivo S1100W-8XGT-SE (RTL9303) with L3 offload enabled, main against main with this change. fd00:9e::/32 through one gateway in hardware, a /48 inside it, and 5 echoes into the /48 from a host in the source of the first route below, which the CPU routes back to it: - two source-specific routes, then one deleted: main took the row away and all 5 echoes reached the /32's gateway; now the row stays and none do. - a route without a source through the /32's gateway, added after a source-specific one: main forwarded all 5 to that gateway whatever their source; now the row stays a trap and none go there. Deleting that route left no row on main; the trap stays now. - a source-specific route added and deleted over a forwarding route without a source: main left no row and all 5 reached the /32's gateway; now a trap stays and none do. A default route with a source gets no row on either. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25583 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