Gennaro Cimmino
5bcc08cdd5
The router MAC this driver installs matches on any port and any VLAN, so from the first offloaded route every IP frame addressed to the switch is pulled into the route lookup. A destination the driver did not program misses that lookup, and a miss is a drop: not a trap, not a punt to the CPU, a drop in silicon before anything upstream can see the packet. A route with no gateway to resolve is never offloaded, so every on-link prefix is such a destination. Measured on an RTL9303 with two bridge VLANs, one port each, an address of the switch on both, routing on and the firewall stopped: from VLAN 10 to the switch, same VLAN 20/20 from VLAN 10 to the switch, in VLAN 20 20/20 from VLAN 10 to a host on-link in VLAN 20 0/20 The middle line is the control: crossing VLANs works, and it works because that destination has a row. The third has none, and the drop counter follows the packets: against an idle span of the same length that read four, the twenty-packet arm read twenty-four IPUC_ROUTING_LOOKUP_MISS, while a deliberate VLAN violation over the same two ports raises VLAN_IGR_FILTER and leaves that counter at zero. The arms are IPv4 because the miss does not depend on the family: the router MAC is matched before the lookup and the lookup is what fails. So the offload makes the switch worse at forwarding than it is with the offload off, which is a regression and not a missing feature. The miss itself cannot be steered. The Realtek GPL SDK carries a lookup miss action in the multicast route controls and in neither of the unicast ones - rtk_longan_regField_list.c gives L3_IPMC_ROUTE_CTRL and L3_IP6MC_ROUTE_CTRL a LU_MIS_ACT field and gives the two unicast registers none. What a unicast row can carry is an action of its own, and trapping is one of them. Write that row. One entry, prefix length zero, the trap action and no next hop, at the end of the block: the rows are ordered longest prefix first and the hardware answers with the lowest matching row, so every destination that has a row of its own is answered by it and only what nothing matches arrives here. What arrives is handed to the CPU, which is where it would have gone with the offload off. It costs one of the 127 entries the table holds for IPv6 and it costs that traffic the hardware path, which it never had. The row is written where the tables are set up, before the notifiers are registered, so there is no window in which the tables are live and a destination is dropped for want of a route that has not arrived yet. Only a switch whose L3 tables carry the destination writes it, which is an RTL930x built with the offload symbol, and no subtarget config sets that. The RTL839x reaches none of this. This commit writes the IPv6 row only, so the IPv4 arms above are still answered the same way at this point in the series: the row that answers them is in the commit after this one. Assisted-by: Claude:claude-opus-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25313 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