Openwrt Router Firmware

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
Indeed lower memory can be a big problem for consumer routers if you need to run OpenWRT and use extra features like Adguard Home and Tailscale.

Both RAM and Storage can be an issue with Adguard Home.
https://openwrt.org/docs/guide-user/services/dns/adguard-home

Newer chipsets for WiFi 6 and especially WiFi 7 already require more RAM for the chipsets. That is why you see many WiFi 7 routers are with 1GB RAM or even 2GB RAM.

I dislike WiFi 6/7 routers with only 256MB RAM myself.

Personally I use Mini PC based OpenWRT implementation, so no need to worry about RAM and Flash Storage (2GB RAM and 4GB Storage are more than enough). Then I use consumer wireless routers as AP: Asus RT-AX86U as AP for one setup, Asus TUF-BE6500 or TP-Link Archer BE805 for another setup.

And I do not use OpenWRT's Adguard Home package, rather I run it as a separate LxC container or Docker Container.
 

grynove

Senior Member
Joined
Feb 7, 2006
Messages
1,532
Reaction score
43
is 2gb ram sbc good enough to run openwrt with some container? need to run some controller app
 

hwzlite

Master Member
Joined
Jan 27, 2007
Messages
3,012
Reaction score
3,112
Personally I use Mini PC based OpenWRT implementation, so no need to worry about RAM and Flash Storage (2GB RAM and 4GB Storage are more than enough). Then I use consumer wireless routers as AP: Asus RT-AX86U as AP for one setup, Asus TUF-BE6500 or TP-Link Archer BE805 for another setup.

And I do not use OpenWRT's Adguard Home package, rather I run it as a separate LxC container or Docker Container.

For me I'm prepping for my N100 build a full sw reflash into the latest shining Proxmox VE 9.0 and Kasm v1.17.0

Now standing-by Xiaomi AX3600 stress-testing running essential services such as SQM: fq-codel+tbf, AdguardHome, Tailscale(Subnet routers), ACME-LetsEncrypt , DDNS - duckdns.org , zram-swap ...etc, before making the move (still in ever-procrastination mode ) 🤪
 
Last edited:

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
1. Banana Pi BPI-R4 Lite is a mid-range 2.5GbE router board based on MediaTek Filogic 850 (MT7987AV) quad-core Cortex-A53 network processor, coupled with 2GB DDR4 and 8GB eMMC flash, and equipped with four gigabit Ethernet ports, a 2.5GbE RJ45 WAN port, and a 2.5GbE SFP cable.

https://www.cnx-software.com/2025/0...5gbe-router-board-with-wifi-7-and-5g-support/

2. Reference for the existing big brother.
https://www.cnx-software.com/2023/1...-router-board-mediatek-filogic-880-processor/

Banana Pi BPI-R4 is a WiFi 7 router board powered by the MediaTek MT7988A (Filogic 880) quad-core Arm Corex-A73 processor with 4GB DDR4 RAM, 8GB eMMC flash, and 128MB SPI-NAND flash.

The board also comes with two 10GbE SFP cages, four Gigabit Ethernet RJ45 ports, a USB 3.2 port, as well as an M.2 socket for a 4G/5G modem or an NVMe SSD, and two mini PCIe slots with PCIe 3.0 to support WiFi 7.
 

GlassDoor

Member
Joined
Mar 29, 2021
Messages
305
Reaction score
499
1. Banana Pi BPI-R4 Lite is a mid-range 2.5GbE router board based on MediaTek Filogic 850 (MT7987AV) quad-core Cortex-A53 network processor, coupled with 2GB DDR4 and 8GB eMMC flash, and equipped with four gigabit Ethernet ports, a 2.5GbE RJ45 WAN port, and a 2.5GbE SFP cable.

https://www.cnx-software.com/2025/0...5gbe-router-board-with-wifi-7-and-5g-support/

2. Reference for the existing big brother.
https://www.cnx-software.com/2023/1...-router-board-mediatek-filogic-880-processor/

Banana Pi BPI-R4 is a WiFi 7 router board powered by the MediaTek MT7988A (Filogic 880) quad-core Arm Corex-A73 processor with 4GB DDR4 RAM, 8GB eMMC flash, and 128MB SPI-NAND flash.

The board also comes with two 10GbE SFP cages, four Gigabit Ethernet RJ45 ports, a USB 3.2 port, as well as an M.2 socket for a 4G/5G modem or an NVMe SSD, and two mini PCIe slots with PCIe 3.0 to support WiFi 7.
bpi-r4 i believe has been replaced by bpi-r4 pro. but maybe still available if u look hard enough. technically it does not come with wifi 7 hardware build in and is dependent on bpi add-on cards. But from what i read those cards are plagued with SNR issues.
generally mt7988 or mt7987 or mediatek chipsets per say has good support for openwrt if you are willing to tinger around. kernel 6.6 is well supported by mtk-sdk and their sources and patches are available for all.
personally bpi-r4 meets my performance expectations and is very cool and stable
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
bpi-r4 i believe has been replaced by bpi-r4 pro. but maybe still available if u look hard enough. technically it does not come with wifi 7 hardware build in and is dependent on bpi add-on cards. But from what i read those cards are plagued with SNR issues.
generally mt7988 or mt7987 or mediatek chipsets per say has good support for openwrt if you are willing to tinger around. kernel 6.6 is well supported by mtk-sdk and their sources and patches are available for all.
personally bpi-r4 meets my performance expectations and is very cool and stable

Interestingly the international site mentions both BPI-R4 Pro (more prominently mentioned) and BPI-R4.

But then I just searched Taobao shops and they all only mention BPI-R4 (4GB RAM version and 8GB RAM version).

Example: BPI-R4 board with casing, cooling fan and power supply at RMB878.

【淘宝】7天无理由退货 https://e.tb.cn/h.hxfOSGapgQTA5zq?tk=Bwq74nXcrXR CZ356 「香蕉派Banana Pi BPI-R4路由器开发板热卖套餐」
点击链接直接打开 或者 淘宝搜索直接打开

Add-on WiFi 7 Card is at RMB 544.

【淘宝】7天无理由退货 https://e.tb.cn/h.hDj5VNfo6XFnSM9?tk=Uohu4nXehIL CZ225 「香蕉派开发板Banana Pi BPI-R4 wifi7模块 BPI-R4-NIC-BE14」
点击链接直接打开 或者 淘宝搜索直接打开
 
Last edited:

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
The above shop also has the BPI-R4 Lite at RMB540.

【淘宝】7天无理由退货 https://e.tb.cn/h.hDr5JUVvrFWZMd6?tk=ygwp4nXdjpL HU926 「香蕉派BPI-R4 Lite Wifi7 开源智能路由器开发板联发科MT7987方案」
点击链接直接打开 或者 淘宝搜索直接打开

They also sell OpenWRT One at RMB 640.

【淘宝】7天无理由退货 https://e.tb.cn/h.hDL1G4UKa5blqMw?tk=JE444nXTtBh CZ028 「Banana Pi OpenWrtOne 路由器开发板 联发科MT7981B芯片方案WiFi6」
点击链接直接打开 或者 淘宝搜索直接打开
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
Upgraded My Xiaomi AX3000T from an old snapshot version to offcial 24.10.2 FW version.

More about old version:
https://forums.hardwarezone.com.sg/threads/openwrt-router-firmware.5967482/page-29

WiFi Speed seems to be better than last time. But it could be due to different client used.
Not using WED. No flow offloading.


Xiaomi AX3000T, CH36, 5GHz band, 160MHz channel bandwidth.
Acer Swift Go 14 2024 model, Intel BE200 WiFi 7 chipset, 3m distance to Xiaomi AX3000T.
PHY Speed 2402 Mbps.

System​

HostnameOpenWrt
ModelXiaomi Mi Router AX3000T (OpenWrt U-Boot layout)
ArchitectureARMv8 Processor rev 4
Target Platformmediatek/filogic
Firmware VersionOpenWrt 24.10.2 r28739-d9340319c6 / LuCI openwrt-24.10 branch 25.231.61534~b47fce0
Kernel Version6.6.93
Local Time2025-08-29 12:02:59
Uptime0h 41m 51s
Load Average0.00, 0.02, 0.04

Bash:
PS C:\work\networking> ssh root@192.168.32.1
root@192.168.32.1's password:


BusyBox v1.36.1 (2025-06-23 20:40:36 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 24.10.2, r28739-d9340319c6
 -----------------------------------------------------
root@OpenWrt:~# free -h
              total        used        free      shared  buff/cache   available
Mem:         240304       81356      111492        1368       47456      109960
Swap:             0           0           0
root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 4.5M      4.5M         0 100% /rom
tmpfs                   117.3M      1.3M    116.0M   1% /tmp
/dev/ubi0_2              78.6M      4.1M     70.5M   6% /overlay
overlayfs:/overlay       78.6M      4.1M     70.5M   6% /
tmpfs                   512.0K         0    512.0K   0% /dev
root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='24.10.2'
DISTRIB_REVISION='r28739-d9340319c6'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt 24.10.2 r28739-d9340319c6'
DISTRIB_TAINTS=''

root@OpenWrt:~# ubus call system board | grep 'model\|description'
        "model": "Xiaomi Mi Router AX3000T (OpenWrt U-Boot layout)",
                "description": "OpenWrt 24.10.2 r28739-d9340319c6",

root@OpenWrt:~#  iwinfo | grep 'Hardware:\|PHY name'
          Hardware: embedded [MediaTek MT7981]
          Supports VAPs: yes  PHY name: phy0
          Hardware: embedded [MediaTek MT7981]
          Supports VAPs: yes  PHY name: phy1

root@OpenWrt:~#  iw list | grep 'Wiphy\|TXQS\|AIRTIME_FAIRNESS\|AQL'
Wiphy phy1
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
                * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
                * [ AQL ]: Airtime Queue Limits (AQL)
Wiphy phy0
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
                * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
                * [ AQL ]: Airtime Queue Limits (AQL)

root@OpenWrt:~# cat /etc/modules.conf
# examples:
# options mod1 option=val
# blacklist mod2

root@OpenWrt:~# dmesg | grep "WED"
root@OpenWrt:~#

Wireless Speedtest results:
Bash:
PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     2.86 ms   (jitter: 0.45ms, low: 2.52ms, high: 3.28ms)
    Download:   837.00 Mbps (data used: 699.6 MB)
                  9.56 ms   (jitter: 2.78ms, low: 4.13ms, high: 19.06ms)
      Upload:   876.82 Mbps (data used: 879.5 MB)
                  9.90 ms   (jitter: 3.38ms, low: 2.86ms, high: 34.86ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/5e85e1ef-8015-4b21-a988-195c4add0967

PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.42 ms   (jitter: 0.19ms, low: 3.11ms, high: 3.55ms)
    Download:   801.05 Mbps (data used: 446.0 MB)
                  8.72 ms   (jitter: 2.13ms, low: 3.11ms, high: 14.46ms)
      Upload:   886.20 Mbps (data used: 785.7 MB)
                  9.64 ms   (jitter: 3.35ms, low: 3.47ms, high: 27.83ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/6751b286-626f-4269-8a89-8db73e52e870
 
Last edited:

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
During the upgrade process, I made a serious mistake of flashing the wrong FW. I am using the OpenWRT urboot so I need to use a different image.

Then it keeps booting back to the old snapshot without LUCI and without options to install the packages as the snapshot is no longer compatible with the current snapshot. I have to use tftp to recover, similar to the image mentioned in the following OpenWRT Xiaomi AX3000T page. BTW, if you use stock bootloader, tftp is also useful to recover in case you flash the wrong file.

Lesson learned --
1) better not to flash the Snapshot version and then forget about the router.
2) make sure you read the OpenWRT flashing guide properly.


https://openwrt.org/inbox/toh/xiaomi/ax3000t

If you have installed OpenWrt with u-boot mode layout, you can still use above UART recovery procedure, but u-boot will also look for a file called openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb in a tftp server at IP address 192.168.1.254.

If you provide that file in a tftp server, it'll be automatically loaded and run, so system can be recovered without using a UART connection.
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
Upgrading H3C Magic NX30 Pro is easier.

System​

HostnameOpenWrt_H3C_NX30Pro
ModelH3C Magic NX30 Pro
ArchitectureARMv8 Processor rev 4
Target Platformmediatek/filogic
Firmware VersionOpenWrt 24.10.2 r28739-d9340319c6 / LuCI openwrt-24.10 branch 25.231.61534~b47fce0
Kernel Version6.6.93
Local Time2025-08-29 21:04:54
Uptime0h 22m 41s
Load Average0.32, 0.14, 0.06


WiFi Speed seems to be better than last time. But it could be due to different client used.
Not using WED. No flow offloading.


H3C Magic NX30 Pro, CH36, 5GHz band, 160MHz channel bandwidth.
Acer Swift Go 14 2024 model, Intel BE200 WiFi 7 chipset, 3m distance to the router.
PHY Speed 2402 Mbps.

WAN speed (wired speed) is close to gigabit -- so the CPU is powerful enough for gigabit without flow offloading.

Bash:
PS C:\work> ssh root@192.168.1.1
root@192.168.1.1's password:


BusyBox v1.36.1 (2025-06-23 20:40:36 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 24.10.2, r28739-d9340319c6
 -----------------------------------------------------

root@OpenWrt_H3C_NX30Pro:~# free -h
              total        used        free      shared  buff/cache   available
Mem:         240336       78528      114616        1332       47192      112972
Swap:             0           0           0

root@OpenWrt_H3C_NX30Pro:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 4.5M      4.5M         0 100% /rom
tmpfs                   117.4M      1.3M    116.1M   1% /tmp
/dev/ubi0_2              38.6M      2.9M     33.8M   8% /overlay
overlayfs:/overlay       38.6M      2.9M     33.8M   8% /
tmpfs                   512.0K         0    512.0K   0% /dev

root@OpenWrt_H3C_NX30Pro:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="24.10.2"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 24.10.2"
VERSION_ID="24.10.2"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r28739-d9340319c6"
OPENWRT_BOARD="mediatek/filogic"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 24.10.2

root@OpenWrt_H3C_NX30Pro:~# ubus call system board | grep 'model\|description'
        "model": "H3C Magic NX30 Pro",
                "description": "OpenWrt 24.10.2 r28739-d9340319c6",

root@OpenWrt_H3C_NX30Pro:~# iwinfo | grep 'Hardware:\|PHY name'
          Hardware: embedded [MediaTek MT7981]
          Supports VAPs: yes  PHY name: phy0
          Hardware: embedded [MediaTek MT7981]
          Supports VAPs: yes  PHY name: phy1

root@OpenWrt_H3C_NX30Pro:~# iw list | grep 'Wiphy\|TXQS\|AIRTIME_FAIRNESS\|AQL'
Wiphy phy1
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
                * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
                * [ AQL ]: Airtime Queue Limits (AQL)
Wiphy phy0
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
                * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
                * [ AQL ]: Airtime Queue Limits (AQL)

root@OpenWrt_H3C_NX30Pro:~# cat /etc/modules.conf
# examples:
# options mod1 option=val
# blacklist mod2

root@OpenWrt_H3C_NX30Pro:~# dmesg | grep "WED"
root@OpenWrt_H3C_NX30Pro:~#

root@OpenWrt_H3C_NX30Pro:~# ./speedtest -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     1.98 ms   (jitter: 0.15ms, low: 1.90ms, high: 2.47ms)
    Download:   939.84 Mbps (data used: 658.1 MB)
                  5.59 ms   (jitter: 0.54ms, low: 1.68ms, high: 6.43ms)
      Upload:   937.82 Mbps (data used: 423.0 MB)
                  5.17 ms   (jitter: 0.52ms, low: 1.92ms, high: 6.73ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/cc2f3930-ca13-4ea1-8c67-6ea99d3bef1d

Wireless Speedtest results:

Bash:
PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.00 ms   (jitter: 0.98ms, low: 2.39ms, high: 4.35ms)
    Download:   868.81 Mbps (data used: 1.5 GB)
                  8.71 ms   (jitter: 4.39ms, low: 4.07ms, high: 232.83ms)
      Upload:   812.23 Mbps (data used: 914.7 MB)
                 12.07 ms   (jitter: 4.82ms, low: 4.12ms, high: 33.92ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/ea7538c9-de00-417c-bdf2-fd594dc01554

PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     2.52 ms   (jitter: 0.24ms, low: 2.37ms, high: 2.89ms)
    Download:   839.69 Mbps (data used: 1.0 GB)
                  8.39 ms   (jitter: 2.45ms, low: 3.93ms, high: 21.06ms)
      Upload:   899.79 Mbps (data used: 1.6 GB)
                  9.78 ms   (jitter: 4.58ms, low: 4.34ms, high: 40.01ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/12fa495c-36e4-4669-9f10-480ebbc520be
 
Last edited:

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
Xiaomi Stock FW tend to use very old version of OpenWRT (Vendor SDK from Qualcomm or MediaTek).

No way to use opkg to install packages.

But some people may be able to compile extra packages from source codes.

The following is from Xiaomi BE5000 after gaining SSH access (with latest Xiaomi stock FW).

The flash layout is very bad...

Bash:
PS C:\work> ssh root@192.168.31.1 -p 23323
root@192.168.31.1's password:


BusyBox v1.36.1 (2024-04-03 08:52:57 UTC) built-in shell (ash)

 -----------------------------------------------------
       Welcome to XiaoQiang!
 -----------------------------------------------------
  $$$$$$\  $$$$$$$\  $$$$$$$$\      $$\      $$\        $$$$$$\  $$\   $$\
 $$  __$$\ $$  __$$\ $$  _____|     $$ |     $$ |      $$  __$$\ $$ | $$  |
 $$ /  $$ |$$ |  $$ |$$ |           $$ |     $$ |      $$ /  $$ |$$ |$$  /
 $$$$$$$$ |$$$$$$$  |$$$$$\         $$ |     $$ |      $$ |  $$ |$$$$$  /
 $$  __$$ |$$  __$$< $$  __|        $$ |     $$ |      $$ |  $$ |$$  $$<
 $$ |  $$ |$$ |  $$ |$$ |           $$ |     $$ |      $$ |  $$ |$$ |\$$\
 $$ |  $$ |$$ |  $$ |$$$$$$$$\       $$$$$$$$$  |       $$$$$$  |$$ | \$$\
 \__|  \__|\__|  \__|\________|      \_________/        \______/ \__|  \__|


root@XiaoQiang:~# date
Fri Aug 29 21:42:46 CST 2025

root@XiaoQiang:~# opkg update
Downloading http://downloads.openwrt.org/releases/18.06-SNAPSHOT/targets/airoha/en7563/packages/Packages.gz
wget: server returned error: HTTP/1.1 404 Not Found
*** Failed to download the package list from http://downloads.openwrt.org/releases/18.06-SNAPSHOT/targets/airoha/en7563/packages/Packages.gz
Downloading http://downloads.openwrt.org/releases/18.06-SNAPSHOT/packages/arm_cortex-a7/base/Packages.gz
wget: server returned error: HTTP/1.1 404 Not Found
*** Failed to download the package list from http://downloads.openwrt.org/releases/18.06-SNAPSHOT/packages/arm_cortex-a7/base/Packages.gz

Collected errors:
 * opkg_download: Failed to download http://downloads.openwrt.org/releases/18.06-SNAPSHOT/targets/airoha/en7563/packages/Packages.gz, wget returned 1.
 * opkg_download: Failed to download http://downloads.openwrt.org/releases/18.06-SNAPSHOT/packages/arm_cortex-a7/base/Packages.gz, wget returned 1.

root@XiaoQiang:~# free -h
              total        used        free      shared  buff/cache   available
Mem:         449000      187556      139476         920      121968      222264
Swap:             0           0           0

root@XiaoQiang:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                26.5M     26.5M         0 100% /
tmpfs                   219.2M    908.0K    218.4M   0% /tmp
ubi1:cfg                 24.4M      6.0M     17.2M  26% /data
ubi1:cfg                 24.4M      6.0M     17.2M  26% /userdisk
/dev/root                26.5M     26.5M         0 100% /userdisk/data
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/config
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/datacenterconfig
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/smartcontroller
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/parentalctl
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/smartvpn
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/ppp
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/crontabs
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/mipctl
ubi1:cfg                 24.4M      6.0M     17.2M  26% /etc/antiy
tmpfs                   512.0K         0    512.0K   0% /dev

root@XiaoQiang:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="18.06-SNAPSHOT"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 18.06-SNAPSHOT"
VERSION_ID="18.06-snapshot"
HOME_URL="http://openwrt.org/"
BUG_URL="http://bugs.openwrt.org/"
SUPPORT_URL="http://forum.lede-project.org/"
BUILD_ID="unknown"
LEDE_BOARD="airoha/en7563"
LEDE_ARCH="arm_cortex-a7"
LEDE_TAINTS="no-all busybox"
LEDE_DEVICE_MANUFACTURER="OpenWrt"
LEDE_DEVICE_MANUFACTURER_URL="http://openwrt.org/"
LEDE_DEVICE_PRODUCT="Generic"
LEDE_DEVICE_REVISION="v0"
LEDE_RELEASE="OpenWrt 18.06-SNAPSHOT unknown"

root@XiaoQiang:~# ubus call system board | grep 'model\|description'
        "model": "ECONET (Device Tree)",
                "description": "OpenWrt 18.06-SNAPSHOT unknown"

root@XiaoQiang:~# iwinfo | grep 'Hardware:\|PHY name'
          Hardware: 14C3:7992 14C3:7992 [Generic MAC80211]
          Supports VAPs: yes  PHY name: phy0
          Hardware: 14C3:7992 14C3:7992 [Generic MAC80211]
          Supports VAPs: yes  PHY name: phy1
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: lan_int2_if
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: lan_int3_if
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: lan_int4_if
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wan_int2_if
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wan_int3_if
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wan_int4_if
          Hardware: 14C3:7992 14C3:7992 [Generic MAC80211]
          Supports VAPs: yes  PHY name: phy1
          Hardware: 14C3:7992 14C3:7992 [Generic MAC80211]
          Supports VAPs: yes  PHY name: phy0
          Hardware: 14C3:7992 14C3:7992 [Generic MAC80211]
          Supports VAPs: yes  PHY name: phy0
          Hardware: 14C3:7992 14C3:7992 [Generic MAC80211]
          Supports VAPs: yes  PHY name: phy1

root@XiaoQiang:~# iw list | grep 'Wiphy\|TXQS\|AIRTIME_FAIRNESS\|AQL'
Wiphy phy1
Wiphy phy0

root@XiaoQiang:~#  cat /etc/modules.conf
cat: can't open '/etc/modules.conf': No such file or directory

root@XiaoQiang:~# dmesg | grep "WED"
root@XiaoQiang:~#
 
Last edited:

BBCWatcher

Arch-Supremacy Member
Joined
Jun 15, 2010
Messages
22,986
Reaction score
4,523
Interesting issue of OpenWRT with regard to Xiaomi AX3000T. Not so sure if it will further improve the performance or not.
https://github.com/openwrt/openwrt/issues/19323
I don’t think it would help with any 2x2 device in a single device speed test. It might help with multiple concurrent devices or with 4x2 (or 4x4) devices.

I’ve noticed that some wireless routers/access points can dedicate the additional stream (3rd in this case) to monitor DFS channels and facilitate fast switching to an alternate DFS channel when there’s a radar hit. However, if you’re trying to use 160 MHz wide channels on 5 GHz there are only 2 of them, and both are DFS channels. You have to be quite unlucky-lucky to get a radar hit on one and still be clear to switch to the other. (And then you ping pong?) Typically a DFS hit on a 160 MHz wide channel will just shut off your whole 5 GHz radio.🤷‍♂️

Those speed test results are basically saying, “1000BASE-T is 1000BASE-T.” There’s not much gas left in that tank, so to speak.

On edit: do you get comparable results with an 80 MHz wide channel?
 
Last edited:

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
Those speed test results are basically saying, “1000BASE-T is 1000BASE-T.” There’s not much gas left in that tank, so to speak.

On edit: do you get comparable results with an 80 MHz wide channel?

1) Actually the speedtest results are mainly to show the official OpenWRT wireless driver for MediaTek Filogic 820 has improved by a lot and now it is matching stock firmware (MediaTek SDK, older OpenWRT version with MediaTek wireless driver).

Keyword --> Not using WED. No flow offloading.
Basically the CPU is pretty okay and the wireless driver has improved.

Quite some vendor implementation is based on MediaTek SDK (with wireless acceleration) and not using Open Source driver.

It is still the case for Qualcomm side that the vendor wireless driver with NSS support is faster than the official OpenWRT wireless driver.

The following thread is very popular in OpenWRT forum for Qualcomm chipsets.
https://forum.openwrt.org/t/qualcommax-nss-build/148529

Personally I am involved in quite some Open Source projects so I tend to like to use official OpenWRT version.

2) But I get your point, I will post 80MHz channel bandwidth test results as well.
 
Last edited:

BBCWatcher

Arch-Supremacy Member
Joined
Jun 15, 2010
Messages
22,986
Reaction score
4,523
1) Actually the speedtest is to show the official OpenWRT wireless driver for MediaTek Filogic 820 has improved by a lot and now it is matching stock firmware (MediaTek SDK, older OpenWRT version with MediaTek wireless driver).
Yes, understood. It looks like you’re now gated by the 1000BASE-T port since you’re at least pretty close to that limit. (Or is there some port bonding option available to pair two Ethernet ports?) And that’s a good thing.

Some of the Qualcomm drivers in OpenWrt have also improved lately too, although MediaTek devices are generally better for the reasons you mention. But I haven’t really paid too much attention since it’s “good enough.”
2) But I get your point, I will post 80MHz channel bandwidth test results as well.
OK, just curious.
 

hwzlite

Master Member
Joined
Jan 27, 2007
Messages
3,012
Reaction score
3,112
I don’t think it would help with any 2x2 device in a single device speed test. It might help with multiple concurrent devices or with 4x2 (or 4x4) devices.

I’ve noticed that some wireless routers/access points can dedicate the additional stream (3rd in this case) to monitor DFS channels and facilitate fast switching to an alternate DFS channel when there’s a radar hit. However, if you’re trying to use 160 MHz wide channels on 5 GHz there are only 2 of them, and both are DFS channels. You have to be quite unlucky-lucky to get a radar hit on one and still be clear to switch to the other. (And then you ping pong?) Typically a DFS hit on a 160 MHz wide channel will just shut off your whole 5 GHz radio.🤷‍♂️

Hmmm....i do occasionally encounter radar hit DFS events (ch 112) in my Xiaomi AX3000T on 80MHz wide ch too. Yet to try out OpenWrt DFS Checker – Improved Script for Handling DFS Radar Events

Those speed test results are basically saying, “1000BASE-T is 1000BASE-T.” There’s not much gas left in that tank, so to speak.

On edit: do you get comparable results with an 80 MHz wide channel?

LOL , on the other hand, wait till we are OCD obsessed with Wi-Fi latency reduction TXQS/ATF/AQL features.
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,211
Reaction score
8,273
1. Test condition:
All wireless routers-- 5GHz band, 80MHz channel bandwidth.
Acer Swift Go 14 2024 model, Intel BE200 WiFi 7 chipset, 3m distance to the router.

The Asus RT-AX86U is always present (since the other family members need to use wireless, using CH149) and it is 1m away from the other three routers (one at a time, using CH60).

I am actually quite impressed with the test results from Xiaomi AX3000T.

2. Asus RT-AX86U Merlin FW, CH149, 5GHz band, 80 MHz channel bandwidth.
PHY Speed 1201 Mbps.
Bash:
PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     4.31 ms   (jitter: 2.54ms, low: 3.21ms, high: 7.65ms)
    Download:   796.69 Mbps (data used: 805.8 MB)
                 17.11 ms   (jitter: 5.86ms, low: 6.01ms, high: 32.93ms)
      Upload:   500.62 Mbps (data used: 868.9 MB)
                 24.88 ms   (jitter: 13.63ms, low: 2.95ms, high: 132.85ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/ddfecdb7-ad74-43bc-b16c-f85005bc2604

3. Xiaomi BE5000 dual band WiFi 7, Xiaomi Stock FW, CH60, 5GHz band, 80 MHz channel bandwidth. MLO disabled. PHY Speed 1441 Mbps.

Bash:
PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.27 ms   (jitter: 0.35ms, low: 2.79ms, high: 4.04ms)
    Download:   962.14 Mbps (data used: 1.7 GB)
                 14.97 ms   (jitter: 5.43ms, low: 5.40ms, high: 28.49ms)
      Upload:   864.95 Mbps (data used: 1.1 GB)
                 12.09 ms   (jitter: 6.49ms, low: 2.45ms, high: 70.64ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/6ef97871-a0e4-4034-acbc-08e12670e0cd

4. H3C Magic NX30 Pro OpenWRT 24.10.2, CH60, 5GHz band, 80 MHz channel bandwidth.
Not using WED. No flow offloading.
PHY Speed 1201 Mbps.

Bash:
PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.35 ms   (jitter: 0.25ms, low: 2.95ms, high: 3.47ms)
    Download:   757.42 Mbps (data used: 671.7 MB)
                 10.11 ms   (jitter: 3.06ms, low: 4.20ms, high: 18.17ms)
      Upload:   822.83 Mbps (data used: 412.2 MB)
                 11.87 ms   (jitter: 4.38ms, low: 2.49ms, high: 24.46ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/e22b43b6-18c8-4d9a-9e22-3a5191af0ece

5. Xiaomi AX3000T OpenWRT 24.10.2, CH60, 5GHz band, 80 MHz channel bandwidth.
Not using WED. No flow offloading.
PHY Speed 1201 Mbps.

Bash:
PS C:\work\networking\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.27 ms   (jitter: 0.41ms, low: 2.92ms, high: 3.57ms)
    Download:   753.94 Mbps (data used: 979.2 MB)
                 12.00 ms   (jitter: 3.83ms, low: 3.03ms, high: 25.78ms)
      Upload:   871.67 Mbps (data used: 682.7 MB)
                 13.34 ms   (jitter: 4.09ms, low: 4.20ms, high: 23.27ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/4eb574c8-9a8d-4e66-9e91-3b248285538e
 

tanchoo1

Master Member
Joined
Feb 12, 2008
Messages
3,135
Reaction score
687
Indeed the Xiaomi AX3000T is a lovely piece of hardware at around the SGD 45 mark. It works great as a dumb AP.

It will also work great as the main router as long as you don't plan to run too many memory intensive services as it only has 256MB RAM.

Only downside is that you have to make sure you don't get the CN V2 version as that isn't compatible with OpenWrt because it doesn't use MediaTek.
 

hwzlite

Master Member
Joined
Jan 27, 2007
Messages
3,012
Reaction score
3,112
Indeed the Xiaomi AX3000T is a lovely piece of hardware at around the SGD 45 mark. It works great as a dumb AP.

It will also work great as the main router as long as you don't plan to run too many memory intensive services as it only has 256MB RAM.

Only downside is that you have to make sure you don't get the CN V2 version as that isn't compatible with OpenWrt because it doesn't use MediaTek.

I got my Xiaomi AX3000T from a nice gentleman for $10 at Carousell. :)

Now saw a Redmi ax6000(512MB) selling for $60 a pop there, price not swee yet..
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Community Guidelines and Standards, Terms of Service and Member T&Cs for more information.
Top