Gennaro Cimmino
b5395bdc8d
On RTL930x, the L2 entry of a next hop names the DMAC entry from which routed frames take their destination MAC (the field that replaces the VID), and the driver wrote that DMAC entry per route, at the route's id. Routes through one gateway share its L2 entry, which keeps naming the id of the route that claimed it first. When that route goes, another one takes its id and writes its own gateway MAC there, and the routes still going through the shared entry leave with that MAC. Hold the DMAC entry per gateway MAC instead, refcounted by the routes through it as the Realtek GPL SDK does (dal_longan_l3.c, _dal_longan_l3_dmacEntry_alloc()), and have the L2 entry name it. An entry that is already a next hop is pointed at it again on every claim, as the SDK writes it on every add, so an entry that stayed a next hop while its DMAC entry was given up does not keep naming it. A route holds at most one DMAC entry, and the table has one for every route id; entry 0 stays unused, as before. An entry whose write fails is not taken, and the route is left as it was. RTL838x and RTL839x still put the route id in that field, as before, and allocate nothing. Tested on a Hasivo S1100W-8XGT-SE (RTL9303) with a kprobe on otto_table_write_bytes() logging the DMAC writes. 10.99.80.0/24 (A) and 10.99.81.0/24 (B) went through one gateway; A was deleted and 10.99.82.0/24 (C) added through another. On main, C took A's id and wrote its own gateway MAC into the DMAC entry that the shared L2 entry named, and echo requests routed through B fell from 8/8 to 0/8 at their gateway. With this change that gateway's MAC was written once, to entry 1, which the L2 entry named; C's gateway got entry 2, and B still delivered 8/8. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25736 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