Gennaro Cimmino
c8f47df6fc
An L2 unicast entry can be wanted by the bridge and by a route at the same time, and neither knows about the other. A static FDB entry now records itself in the map, so taking a next hop down no longer takes the address away from the bridge that also asked for it. Such an entry stays where it is, as the next hop it already was, with no port of its own and not ageing - which is how the driver writes a next hop it created itself. The other direction is wired here and starts working with the last patch. The FDB delete asks the map before it invalidates an entry, but nothing counts the routes behind a gateway yet, so the branch that keeps such an entry is not reached until they are counted. Keeping it on the route's behalf rests on two things, not one: the map has to say a route wants it, and the entry itself has to still say it is a next hop. The map alone can be stale, because the switch drops rows by ageing and by the per-port flush a bridge asks for and nothing tells the driver; a stale count on its own would turn an ordinary FDB delete into a row that is valid, static, reachable through no port and never ageing. An entry nobody had claimed is zeroed before the bridge or a route takes it, for the same reason: the cell may still hold what its last owner left there, and a stale mark on a row a route has since taken would stop the removal from handing it back. CAM entries are left alone. The CAM is a table of its own with its own numbering, and this driver never places a next hop there, so nothing can be sharing one - the unconditional removal there is already right. No effect on RTL838x or RTL931x, although the handlers run there: nothing marks a next hop on those families, because neither config carries a setup op, which is what both notifiers gate on, so the entry is given back exactly as before. Not exercised on hardware: nothing in the test image puts an FDB entry and a route on one address. Compile-tested on realtek/rtl930x and realtek/rtl839x. Assisted-by: Claude:claude-opus-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25231 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