Gennaro Cimmino
0ef832f34e
With more than one IPv6 table, the kernel also looks the local table up
before main, so a local IPv6 prefix (AnyIP: ip -6 route add local ...
table local) takes the destinations of a longer main route inside it.
The switch matches the longest prefix and forwards them. Commit
bf54d898c7 ("realtek: l3: trap main routes inside a local prefix") made
such a route trap for IPv4 only.
otto_l3_local_covers() now looks at local prefixes of both families. So
that a local prefix that comes or goes is seen for IPv6 too,
otto_l3_route_inside(), otto_l3_gw_seen() and
otto_l3_local_prefix_check() take the struct fib_notifier_info both
notifier infos start with, and tell the family from it. The IPv6 FIB
work calls otto_l3_local_prefix_check() after an add or a delete, and
the check no longer skips a prefix of length zero: otto_l3_fib_trap_v6()
gives a local ::/0 a row, which otto_l3_local_covers() counts as
covering every main route. An IPv4 local default route gets no row from
otto_l3_fib_trap_v4(), so for it the check only resolves the gateways
again and every route stays as it was. Without IPV6_MULTIPLE_TABLES the
local routes are in main, where the kernel matches the longest prefix
as the switch does, and they are not taken for local ones. Otherwise
IPv4 behaves as before.
Tested on a Hasivo S1100W-8XGT-SE (RTL9303), with 2001:db8:1:0:1::/80
via a gateway on switch.3 and echo requests to eight addresses inside
it captured at the gateway. With ip -6 route add local 2001:db8:1::/64
dev lo table local, main kept the row forwarding and all 8/8 reached the
gateway, whether the local prefix came before or after the route. With
this change the row traps and 0/8 reach it, in both orders. Without the
local prefix both forward 8/8. The same run of the IPv4 case traps on
both, as before. That run predates the zero-length part. In a run of
the final change, a local ::/0 made the row trap with 0/8 reaching the
gateway, and once it went the row forwarded 8/8 again.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net>
Link: https://github.com/openwrt/openwrt/pull/25753
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