Aleksei Sviridkin
244d2f67a5
On the Keenetic MT7981 boards the LAN port takes its MAC from rf-eeprom
0x4, and mt76 reads the same slot for phy0. The 2.4 GHz radio and the
LAN port therefore share one address. Found on a Keenetic KN-1012 while
writing down its MAC map: eth0, br-lan and phy0 all read
d4:9c:53:xx:xx:a1.
This is the phy0 side of the collision fixed for phy1 in commit
cc96ed1e6d ("mediatek: filogic: fix Keenetic phy1 MAC collision"). Give
phy0 the slot with the LA bit set. The userspace VIF allocator keeps bit
7 of the first octet, so the extra phy0 VIFs stay apart from phy1 and
its VIFs, which have bit 7 flipped, and from the ethernet addresses,
which have the LA bit clear. With num_global_macaddr set, the allocator
adds to the base instead, and phy0 + 1 was the WAN address wherever the
0xa slot holds the base + 1, as on the KN-1012; that goes away too. The
2.4 GHz BSSID of these boards changes accordingly. On KAP-630 and
NAP-630 the ethernet port uses the 0xa slot instead, so there it only
changes the BSSID, and the family keeps one 2.4 GHz addressing
convention.
The Buddy 6 and Buddy 6 SE extenders (KN-3411, KN-4410, NC-3411,
NC-4410) have the same collision on their single port: on an NC-4410,
phy0-ap0 came up with d4:9c:53:xx:xx:23, the address its LAN has. They
only need the phy0 part. Their 0xa slot is empty (zeros on that unit),
so mt76 already derives phy1 as the family fixup does, 56:9c:53:xx:xx:23
there.
Tested on the KN-1012: phy0 comes up as d6:9c:53:xx:xx:a1 and phy1 stays
56:9c:53:xx:xx:a1. The VIF allocator hands phy0 d2/de/da and phy1
52/5e/5a in the first octet, none of them equal to the LAN or WAN
address. With two APs on phy0 and one on phy1, all bridged into br-lan,
every bridge port has its own local address.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Link: https://github.com/openwrt/openwrt/pull/25450
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.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