Gennaro Cimmino
e4c5f850ee
Every port is a member of VID 0, so that the frames the CPU sends with its PVID 0 reach the ports with untagged VLANs. A port without PVID keeps PVID 0 too, so in a VLAN-filtering bridge its untagged and priority tagged frames land in VID 0 and are flooded to the other ports of the bridge, tagged VID 0, where the bridge would drop them. The acceptable frame type of a port tells the two apart (one bit each for inner and outer, tagged and untagged frames; vendor SDK). While a port without PVID is in a VLAN-filtering bridge, it accepts only tagged frames, outer tagged ones as an 802.1ad port; standalone ports, which can have VLAN filtering on, and every other state accept all. The driver tracks the bridge membership itself, since DSA rolls back a failed join through port_bridge_leave() before it clears dp->bridge. VID 0 and the CPU path stay as they are. The register has this layout on all four families; only RTL839x sets its address here, the others keep their behaviour until tested. HPE 1920-48G (RTL8393), lan48 a UCI trunk with VLAN 3 and 7 tagged, lan47 an access port in VLAN 1: untagged and priority tagged ARP from the host behind lan48 left lan47 tagged VID 0, 3 of 3 each; now none does. STP, LLDP, LACP and EAPOL frames on lan48 still reach the CPU, 5 of 5 each, and VLAN 3 tagged frames pass. With a PVID on lan48 again, and in a bridge without VLAN filtering, the ARP leaves lan47 untagged; as standalone ports both accept all frames again. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/25992 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