Published Russian article on Habr · Install guide: English / Russian · Latest binary release
I wanted the useful parts of an expensive mesh kit without paying for three premium boxes or replacing an open router with a closed controller. So I selected the least expensive device I could find for each job:
- Xiaomi Redmi Router AX6S as an inexpensive, well-supported Wi-Fi 6 platform bought specifically for OpenWrt;
- Mercusys MR60X as the low-cost Wi-Fi 6 coverage node;
- Mercusys MR47BE v2 as an affordable route to Wi-Fi 7, a dedicated 6 GHz radio, WPA3-SAE and 320 MHz channels.
The result is a three-node network under one SSID. OpenWrt remains the only router and DHCP server, both Mercusys devices receive their network over Ethernet, and the farthest node provides tri-band Wi-Fi 7. A measured controller-to-MR60X path reached 904.32 Mbit/s in one direction and 893.84 Mbit/s in the other; a separate user-run Wi-Fi measurement reached about 900 Mbit/s on the tested client and topology.
OpenWrt was attractive for more than mesh. The same router also gives my network hot failover between two Internet providers and policy-routed VPN access through PAC rules and several exit nodes. Those are subjects for separate articles; here I keep the focus on building a useful mixed-vendor mesh for little money.
Because this build was purchased in Russia, the reproducible source listings below are Russian retailer pages. Prices were checked on 21 July 2026, converted to US dollars at the Bank of Russia official rate of USD 1 = RUB 78.3159, and rounded to the nearest USD 5. These figures are a snapshot, not an estimate of availability, import costs or taxes in another country.
| Device | Why I chose it | Approximate price |
|---|---|---|
| Xiaomi Redmi Router AX6S | Low-cost Wi-Fi 6 platform with good OpenWrt support | about USD 65. The exact Megamarket listing is sold out; IQMI provides a replacement-cost reference |
| Mercusys MR60X | Inexpensive Wi-Fi 6 coverage and Gigabit Ethernet | about USD 25 in the observed Ozon listing |
| Mercusys MR47BE | The lowest-cost option in my survey for tri-band Wi-Fi 7, 6 GHz and 320 MHz | about USD 130 in the observed Ozon listing |
That is roughly USD 220 for all three nodes at the recorded exchange rate. The AX6S is no longer a current retail model, but it remains the device around which this build was designed. Always confirm the hardware revision with the seller.
Mercusys specifies the MR60X v2.20 as an AX1500 dual-band device. The MR47BE v2 is a BE9300 tri-band model with 6 GHz and 320 MHz support. BE9300 is the aggregate radio class, not a promise of 9.3 Gbit/s to one client.
Internet
|
Xiaomi Redmi AX6S
OpenWrt: routing + DHCP + Wi-Fi + mesh control
|
| Ethernet
v
Mercusys MR60X: Wi-Fi 6
|
| Ethernet
v
Mercusys MR47BE: Wi-Fi 7, including 6 GHz
The AX6S is the only gateway and DHCP server. Both Mercusys units are part of the same LAN, so there is no second NAT layer, competing DHCP service or hidden subnet. The controller sees two distinct EasyMesh nodes and reports an Ethernet connection for each one.
This distinction matters. Giving three access points the same SSID and password can make the client list look tidy, but it does not prove that a controller knows about the nodes or that the wired path is being used. Here the controller topology, the IEEE 1905.1 exchange and the live traffic path agree with one another.
The Ethernet layout is deliberately expandable. The branch behind the MR60X can also carry computers, servers, switches and future access points. Everything remains in the main OpenWrt bridge, so adding an ordinary wired client does not require renumbering the network or creating another routing domain.
The AX6S runs OpenWrt 25.12.5 with Linux 6.12.94. I built the first public revision of prplmesh-stock 6.0.1 around the normal OpenWrt model: UCI remains the configuration layer, Linux bridge owns the LAN, and the existing hostapd/wpad installation keeps control of the radios. Installing a complete prplOS stack was unnecessary.
The interesting compatibility problem was the hostapd control socket. A plain upstream control client could send a command but could not reliably receive the reply inside OpenWrt's sandbox. The radio-management process then timed out and restarted, leaving the topology empty. The package fixes that at source level by applying the corresponding OpenWrt permission patch to the pinned hostapd control-client source before prplMesh is compiled.
The public build recipe therefore does four useful things:
- pins the prplMesh and hostapd inputs;
- verifies the unmodified control-client source before patching;
- applies a minimal, reviewable patch series;
- verifies that the package does not replace
wpad,hostapdorwpa_supplicant.
The build recipe and patches are kept next to the ready-to-install APK and SHA-256 file, so the binary can be checked against the documented inputs rather than treated as an opaque attachment.
The released APK was built and tested for OpenWrt 25.12.5 on the Xiaomi/Redmi AX6S (mediatek/mt7622, aarch64_cortex-a53). It is not a universal package for every router with the same CPU architecture. The English and Russian installation guides cover the compatibility gate, off-device backup, SHA-256 verification, placeholder mapping, controlled startup, acceptance checks, removal and rollback. The reproducible build recipe is the path for another target.
The package ships disabled and its public example contains no private SSID, password, address or hardware identifier. That is intentional: enabling a radio-control service with copied credentials would be a much worse default than requiring five minutes of local configuration.
The MR47BE's 6 GHz radio required a stricter check than simply searching for a familiar network name. Each band is read separately and the full SSID is compared, so a similarly named profile with a suffix cannot be mistaken for the target network.
The final read-back from the MR47BE confirmed:
- the expected shared SSID;
- the 6 GHz band;
- WPA3-SAE;
- 320 MHz channel width;
- the expected MR47BE hardware identity.
Some 6 GHz settings remain vendor-local in the Mercusys firmware, so a narrow convergence check watches that exact radio profile. It discovers the device's current management address, validates its identity, compares the complete band settings and touches only the allowlisted fields when drift is detected. After one correction, repeated checks at 12, 60 and 180 seconds required no further change.
| Check | Observed result |
|---|---|
| Two Mercusys nodes in the controller topology | Both active; Ethernet reported for both |
| MR47BE 6 GHz profile | Shared SSID, WPA3-SAE, 320 MHz |
| AX6S → MR60X wired path | 904.32 / 893.84 Mbit/s |
| Separate user-run Wi-Fi measurement | About 900 Mbit/s |
| Recovery after a hardware restart | 19/19 acceptance checks |
| Recovery after restarting mesh control | 19/19, no skipped checks |
The 904.32/893.84 Mbit/s result belongs to the first wired segment and is close to the practical limit of Gigabit Ethernet after protocol overhead. The separate Wi-Fi measurement reached about 900 Mbit/s on the tested client and topology; it is not the aggregate BE9300 radio rating. The second Ethernet segment has not yet been throughput-tested.
A separate read-only audit found that the client and the installed OpenWrt stack support 802.11r/FT, but FT is not enabled in the current OpenWrt profile: the association uses a non-FT AKM and the runtime has no mobility domain or FT parameters. The stock Mercusys interfaces did not provide proof of an active FT profile either. I therefore do not claim mesh-wide FT roaming. Closing that gap requires consistent configuration on every node and a walking test that records BSSID, AKM, latency and packet loss. Mesh-wide MLO is not achievable on this hardware: the Xiaomi AX6S and Mercusys MR60X are Wi-Fi 6 devices without EHT/MLO. Only local MLO on the MR47BE with a compatible client remains a separate candidate for measurement.
This is not a compromise assembled from leftover routers. Each device was bought for a particular price/performance role: an open Wi-Fi 6 router at the center, an inexpensive Wi-Fi 6 node for coverage, and an affordable Wi-Fi 7 node for 6 GHz and 320 MHz. The result keeps one expandable LAN, nearly fills the tested Gigabit path, reaches about 900 Mbit/s in the separate Wi-Fi measurement and automatically reconstructs the two-node topology after service restarts.
It also keeps control of the network where I want it. OpenWrt can grow with dual-provider failover, policy routing, VPN exits, monitoring and ordinary wired services without forcing every future feature into one vendor's controller.
I publish deeper engineering notes for developers, architects and team leads in Java && Management. My technical-audit work and other projects are collected at krot.name, while source code and reproducible artifacts live on GitHub.
- Telegram: Java && Management
- Website: krot.name
- GitHub profile: github.com/krotname
- This project: krotname/openwrt-prplmesh-easymesh
- Published article: Habr (Russian)
- Installation: English · Russian
- Binary release: latest APK and checksums
Prices and availability were checked in Russian retail listings on 21 July 2026, converted at USD 1 = RUB 78.3159 and rounded to the nearest USD 5. Article structure and illustrations were prepared with generative-AI assistance from the author's logs and measurements; technical claims were checked against the recorded acceptance evidence.