Gennaro Cimmino
89b1b06094
A route can carry a lightweight tunnel - seg6 encapsulation, an MPLS label push - that the kernel applies to every packet it forwards. The FIB notifier never looked at it, so such a route through a gateway on a switch port was offloaded like any other, and the hardware forwarded its traffic to the gateway bare. OpenWrt enables seg6 lightweight tunnels by default on every target without small_flash, realtek included. Leave these routes out, on both families. An IPv6 one gets a trap row, as the other IPv6 routes the driver leaves out do. An IPv4 one takes the path of the routes without a device or through a nexthop object: a /32 is trapped in the host table and a shorter prefix gets no row, so an offloaded shorter prefix covering it would still forward its traffic. The delete handler takes the same path, so a trapped /32 does not outlive its route. Tested on a Hasivo S1100W-8XGT-SE (RTL9303) with L3 offload enabled, main against main with this change. Three routes with seg6 encapsulation through a gateway on a switch port - 10.99.80.0/24, 10.99.81.7/32 and fd00:9a::/48 - each took 5 echoes from another VLAN. - main: each gets a forwarding row, and the gateway receives all 5 echoes bare, none encapsulated. - this change: no row for the /24, a trap row for the /32 and the /48, and the gateway receives none bare and all 5 inside an IPv6 segment routing header. No row is left after the deletes. A build without the delete half leaves the trapped /32 in the host table once its route is gone. An IPv4 and an IPv6 prefix without a tunnel, through the same gateway, forward in hardware on both images, 5 of 5. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25560 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