Openwrt Router Firmware

X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
More info about Xiaomi AX3000T stock firmware -- you can not use opkg to install software as it is not configured to do that. It is not based on official OpenWRT but probably based on MediaTek SDK.

Bash: 
root@XiaoQiang:/etc/config# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='18.06-SNAPSHOT'
DISTRIB_REVISION='unknown'
DISTRIB_TARGET='mediatek/mt7981'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt 18.06-SNAPSHOT unknown'
DISTRIB_TAINTS='no-all busybox'

root@XiaoQiang:/etc/config# opkg update
Downloading http://downloads.openwrt.org/releases/18.06-SNAPSHOT/targets/mediatek/mt7981/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/mediatek/mt7981/packages/Packages.gz

Downloading http://downloads.openwrt.org/releases/18.06-SNAPSHOT/packages/aarch64_cortex-a53/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/aarch64_cortex-a53/base/Packages.gz

Collected errors:
 * opkg_download: Failed to download http://downloads.openwrt.org/releases/18.06-SNAPSHOT/targets/mediatek/mt7981/packages/Packages.gz, wget returned 1.
 * opkg_download: Failed to download http://downloads.openwrt.org/releases/18.06-SNAPSHOT/packages/aarch64_cortex-a53/base/Packages.gz, wget returned 1.

root@XiaoQiang:~#  iperf3 -s -D && iperf3 -c 127.0.0.1
Connecting to host 127.0.0.1, port 5201
[  5] local 127.0.0.1 port 25061 connected to 127.0.0.1 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   513 MBytes  4.30 Gbits/sec    0   1.94 MBytes
[  5]   1.00-2.00   sec   518 MBytes  4.35 Gbits/sec    0   1.94 MBytes
[  5]   2.00-3.00   sec   482 MBytes  4.04 Gbits/sec    0   1.94 MBytes
[  5]   3.00-4.00   sec   498 MBytes  4.17 Gbits/sec    0   1.94 MBytes
[  5]   4.00-5.00   sec   509 MBytes  4.29 Gbits/sec    0   1.94 MBytes
[  5]   5.00-6.00   sec   502 MBytes  4.21 Gbits/sec    0   1.94 MBytes
[  5]   6.00-7.00   sec   499 MBytes  4.18 Gbits/sec    0   1.94 MBytes
[  5]   7.00-8.00   sec   508 MBytes  4.26 Gbits/sec    0   1.94 MBytes
[  5]   8.00-9.00   sec   474 MBytes  3.97 Gbits/sec    0   1.94 MBytes
[  5]   9.00-10.00  sec   527 MBytes  4.43 Gbits/sec    0   1.94 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  4.91 GBytes  4.22 Gbits/sec    0             sender
[  5]   0.00-10.00  sec  4.91 GBytes  4.22 Gbits/sec                  receiver

iperf Done.

root@XiaoQiang:~#  time sh -c 'dd if=/dev/zero bs=1M count=100 | md5sum'
100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 2f282b84e7e608d5852449ed940bfc51  -
0.936391 seconds, 106.8MB/s
real    0m 0.94s
user    0m 0.81s
sys     0m 0.30s

root@XiaoQiang:~# iwinfo | grep 'Hardware:\|PHY name'
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: apcli0
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: apclix0
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl0
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl1
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl13
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl14
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl15
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl5
          Hardware: unknown [Generic WEXT]
          Supports VAPs: no  PHY name: wl9
root@XiaoQiang:~# iwlist apclix0 channel
apclix0   13 channels in total; available frequencies :
          Channel 36 : 5.18 GHz
          Channel 40 : 5.2 GHz
          Channel 44 : 5.22 GHz
          Channel 48 : 5.24 GHz
          Channel 52 : 5.26 GHz
          Channel 56 : 5.28 GHz
          Channel 60 : 5.3 GHz
          Channel 64 : 5.32 GHz
          Channel 149 : 5.745 GHz
          Channel 153 : 5.765 GHz
          Channel 157 : 5.785 GHz
          Channel 161 : 5.805 GHz
          Channel 165 : 5.825 GHz
          Current Channel:44

root@XiaoQiang:~# iwlist apcli0 channel
apcli0    13 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz
          Current Channel:4
 
Last edited:
B

BradenHeat

Supremacy Member
Joined
Apr 4, 2005
Messages
7,252
Reaction score
1,584
xiaofan said:
I decided not to change Xiaomi AX3000T to OpenWRT this time, but rather to stick with Xiaomi stock FW, since I already installed Linux on the H3X NX30 Pro which has the same MTK Filogic 820 chipset and same 256MB RAM configuration.

But before I upgraded to latest MiWiFi 稳定版 1.0.64 which does not have the SSH exploit, I tried the SSH exploit from the original installed 1.0.47 version and the SSH exploit seems to work fine.
https://openwrt.org/inbox/toh/xiaomi/ax3000t

After upgrading to 1.0.64, no more SSH access.

Bash: 
PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> ssh root@192.168.31.1
root@192.168.31.1's password:


BusyBox v1.25.1 (2023-07-30 07:05:14 UTC) built-in shell (ash)

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


root@[B]XiaoQiang[/B]:~# ls

root@[B]XiaoQiang[/B]:/etc/config# ls

[/QUOTE]


welcome to xiao Qiang ????? :confused::spin::s22::s11::s11::s11:

In China, the cockroach is often called “xiao qiang,” meaning “[B]little mighty[/B],” said Sheng Li, an entomology professor at South China Normal University in Guangzhou and lead author of the paper. “It's a tiny pest, but has very strong vitality.”
Click to expand...
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
welcome to xiao Qiang ????? :confused::spin::s22::s11::s11::s11:

In China, the cockroach is often called “xiao qiang,” meaning “little mighty,” said Sheng Li, an entomology professor at South China Normal University in Guangzhou and lead author of the paper. “It's a tiny pest, but has very strong vitality.”
Click to expand...

Bash: 
PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> ssh root@192.168.31.1
root@192.168.31.1's password:


BusyBox v1.25.1 (2023-07-30 07:05:14 UTC) built-in shell (ash)

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


root@[B]XiaoQiang[/B]:~# ls

root@[B]XiaoQiang[/B]:/etc/config# ls

That is indeed special for Xiaomi.

Probably the development team wanted to show that Xiaomi routers were strong.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
xiaofan said:
I decided not to change Xiaomi AX3000T to OpenWRT this time, but rather to stick with Xiaomi stock FW, since I already installed Linux on the H3X NX30 Pro which has the same MTK Filogic 820 chipset and same 256MB RAM configuration.

But before I upgraded to latest MiWiFi 稳定版 1.0.64 which does not have the SSH exploit, I tried the SSH exploit from the original installed 1.0.47 version and the SSH exploit seems to work fine.
https://openwrt.org/inbox/toh/xiaomi/ax3000t

After upgrading to 1.0.64, no more SSH access.

As per OpenWRT forum, Xiaomi AX3000T will get official OpenWRT 23.05.4 release.
https://forum.openwrt.org/t/openwrt-support-for-xiaomi-ax3000t/180490/493

As per the post, the internation version (RD03 model) is also working with OpenWRT.
Click to expand...

There is a way to keep SSH access even after upgrading to 1.0.64 FW.
https://www.right.com.cn/forum/thread-8321180-1-1.html

I need to downgrade to 1.0.47 first, then enable SSH, then follow the above link to make SSH present even after the firmware upgrade.

u0GdNmB.png


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


BusyBox v1.25.1 (2023-11-21 07:25:22 UTC) built-in shell (ash)

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


root@XiaoQiang:~# uname -a
Linux XiaoQiang 5.4.171 #0 SMP Tue Nov 21 06:41:54 2023 aarch64 GNU/Linux
root@XiaoQiang:~# cat /etc/openwrt
openwrt.config   openwrt_release  openwrt_version
root@XiaoQiang:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='18.06-SNAPSHOT'
DISTRIB_REVISION='unknown'
DISTRIB_TARGET='mediatek/mt7981'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt 18.06-SNAPSHOT unknown'
DISTRIB_TAINTS='no-all busybox'

FW download method.


SSH enable method
https://openwrt.org/inbox/toh/xiaomi/ax3000t
https://www.kjfx.cc/266.html


+++++ the following are just for references, YMMV ++++++
Alternative Uboot bootloader
https://github.com/hanwckf/bl-mt798x

Alternative OpenWRT firmware with MediaTek vendor wireless driver (but older OpenWRT version)
https://github.com/hanwckf/immortalwrt-mt798x
https://github.com/aj782/ImmortalWrt-mt798x-builder-0000

Alternative OpenWRT firmware with more up-to-date OpenWRT version
https://github.com/immortalwrt/immortalwrt

X-WRT
https://downloads.x-wrt.com/rom/
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
A bit impatient and decided to install OpenWRT fork on the Xiaomi AX3000T.

I know in the end I will switch to official OpenWRT release version but I want to explore other options first. Take note as of now Xiaomi AX3000T only get snapshot release from official OpenWRT project.

Bootloader: https://github.com/hanwckf/bl-mt798x
OpenWRT fork: https://github.com/hanwckf/immortalwrt-mt798x
github action build of the above fork: https://github.com/mcuee/ImmortalWrt-mt798x-builder (my own git repo fork but not including any changes as of now).

Wired speedtest -- running from within the router -- this means Filogic 820 CPU is quite capable.
Bash: 
root@ImmortalWrt:~# ./speedtest

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     1.10 ms   (jitter: 0.09ms, low: 0.93ms, high: 1.18ms)
    Download:   922.25 Mbps (data used: 416.3 MB)
                  3.18 ms   (jitter: 0.56ms, low: 1.70ms, high: 4.02ms)
      Upload:   935.02 Mbps (data used: 1.2 GB)
                  4.00 ms   (jitter: 0.90ms, low: 1.51ms, high: 31.23ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/8ea0a5f0-f1d1-4d7c-9bf0-2e17f34a72e8

Wireless speedtest (CH44, 80MHz channel bandwidth, Intel AX201 WiFi 6 adater, Windows 11 laptop)
Bash: 
PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     2.91 ms   (jitter: 0.21ms, low: 2.83ms, high: 3.65ms)
    Download:   610.83 Mbps (data used: 510.2 MB)
                  8.29 ms   (jitter: 3.69ms, low: 2.63ms, high: 21.31ms)
      Upload:   529.44 Mbps (data used: 943.1 MB)
                 36.07 ms   (jitter: 12.26ms, low: 5.83ms, high: 120.17ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/bdccd849-f2ba-46f9-ab49-61523eb2dc55
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
xiaofan said:
A bit impatient and decided to install OpenWRT fork on the Xiaomi AX3000T.

I know in the end I will switch to official OpenWRT release version but I want to explore other options first. Take note as of now Xiaomi AX3000T only get snapshot release from official OpenWRT project.

Bootloader: https://github.com/hanwckf/bl-mt798x
OpenWRT fork: https://github.com/hanwckf/immortalwrt-mt798x
github action build of the above fork: https://github.com/mcuee/ImmortalWrt-mt798x-builder (my own git repo fork but not including any changes as of now).
Click to expand...

Now start to play with different OpenWRT or OpenWRT fork github action build for Xiaomi AX3000T.

1) No changes to the scipt yet -- tested the build as mentioned above
https://github.com/mcuee/ImmortalWrt-mt798x-builder

2) Minor changes to the script -- to be tested, for official OpenWRT build, lede andImmortalWRT fork build
https://github.com/mcuee/build-openwrt

3) Minor changes to the script -- to be tested, for lede and ImmortalWRT fork build
https://github.com/mcuee/AutoBuild-OpenWrt

4) no changes to the script -- to be tested
https://github.com/mcuee/openwrt-xiaomi-ax3000t
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
xiaofan said:
A bit impatient and decided to install OpenWRT fork on the Xiaomi AX3000T.

I know in the end I will switch to official OpenWRT release version but I want to explore other options first. Take note as of now Xiaomi AX3000T only get snapshot release from official OpenWRT project.

Bootloader: https://github.com/hanwckf/bl-mt798x
OpenWRT fork: https://github.com/hanwckf/immortalwrt-mt798x
github action build of the above fork: https://github.com/mcuee/ImmortalWrt-mt798x-builder (my own git repo fork but not including any changes as of now).

Wired speedtest -- running from within the router -- this means Filogic 820 CPU is quite capable.
Bash: 
root@ImmortalWrt:~# ./speedtest

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     1.10 ms   (jitter: 0.09ms, low: 0.93ms, high: 1.18ms)
    Download:   922.25 Mbps (data used: 416.3 MB)
                  3.18 ms   (jitter: 0.56ms, low: 1.70ms, high: 4.02ms)
      Upload:   935.02 Mbps (data used: 1.2 GB)
                  4.00 ms   (jitter: 0.90ms, low: 1.51ms, high: 31.23ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/8ea0a5f0-f1d1-4d7c-9bf0-2e17f34a72e8

Wireless speedtest (CH44, 80MHz channel bandwidth, Intel AX201 WiFi 6 adater, Windows 11 laptop)
Bash: 
PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     2.91 ms   (jitter: 0.21ms, low: 2.83ms, high: 3.65ms)
    Download:   610.83 Mbps (data used: 510.2 MB)
                  8.29 ms   (jitter: 3.69ms, low: 2.63ms, high: 21.31ms)
      Upload:   529.44 Mbps (data used: 943.1 MB)
                 36.07 ms   (jitter: 12.26ms, low: 5.83ms, high: 120.17ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/bdccd849-f2ba-46f9-ab49-61523eb2dc55
Click to expand...

Similar tests for official OpenWRT snapshot release (open source MediaTek wireless drivers, Software flow offloading enabled, CH44, 80MHz channel bandwidth).

Wired speed is okay but wireless speed is not that consistent (especially upload speed)

Wired speed
Bash: 
root@OpenWrt:~# uname -a
Linux OpenWrt 6.6.32 #0 SMP Sat Jun  1 15:40:10 2024 aarch64 GNU/Linux

root@OpenWrt:~# cat /etc/openwrt_version
r26497-37ff0ea726

root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r26497-37ff0ea726'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r26497-37ff0ea726'
DISTRIB_TAINTS=''

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

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     2.23 ms   (jitter: 0.12ms, low: 2.02ms, high: 2.27ms)
    Download:   909.86 Mbps (data used: 456.7 MB)
                  3.68 ms   (jitter: 0.70ms, low: 2.22ms, high: 6.28ms)
      Upload:   929.57 Mbps (data used: 1.1 GB)
                  4.49 ms   (jitter: 0.71ms, low: 2.30ms, high: 15.51ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/d9668955-88e1-4b43-88d5-33b12b9ca042

Wireless speed (Intel AX201 WiFi 6 adapter, Acer year 2021 Windows 11 laptop)

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

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.60 ms   (jitter: 0.38ms, low: 3.06ms, high: 3.70ms)
    Download:   566.26 Mbps (data used: 598.2 MB)
                  9.16 ms   (jitter: 3.10ms, low: 4.30ms, high: 23.87ms)
      Upload:   540.69 Mbps (data used: 663.6 MB)
                 39.99 ms   (jitter: 11.24ms, low: 14.11ms, high: 150.07ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/ef39b122-44d1-4635-a44d-3fae7d8bda8f
PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     3.68 ms   (jitter: 0.28ms, low: 3.50ms, high: 4.37ms)
    Download:   539.22 Mbps (data used: 613.5 MB)
                  9.23 ms   (jitter: 5.15ms, low: 3.33ms, high: 92.19ms)
      Upload:   384.14 Mbps (data used: 573.5 MB)
                 45.91 ms   (jitter: 14.27ms, low: 13.43ms, high: 137.90ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/049d33ae-764e-417a-a5c8-8e1ff89d1b87
PS C:\work\speedtest\ookla-speedtest-1.2.0-win64> .\speedtest.exe -s 13623

   Speedtest by Ookla

      Server: Singtel - Singapore (id: 13623)
         ISP: Singtel Fibre
Idle Latency:     4.08 ms   (jitter: 0.24ms, low: 3.60ms, high: 4.42ms)
    Download:   531.93 Mbps (data used: 965.4 MB)
                  9.21 ms   (jitter: 5.25ms, low: 3.32ms, high: 68.91ms)
      Upload:   273.70 Mbps (data used: 505.6 MB)
                 75.60 ms   (jitter: 21.97ms, low: 9.64ms, high: 210.13ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/10dc79c3-38ff-470a-9d41-1300f81458e1
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
In the end, I decided to change to official OpenWRT Uboot as well.
https://openwrt.org/inbox/toh/xiaomi/ax3000t

The process is actually quite smooth. But you need to be careful during the process to avoid bricking the router.

But for typical users of Xiaomi AX3000T, probably it is better to use Xiaomi vendor firmware (including vendor bootloader) before official release of OpenWRT is available for Xiaomi AX3000T.
https://openwrt.org/releases/snapsh...uildbot_snapshots_vs_official_stable_releases

Code: 
root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r26536-c67d5189a4'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r26536-c67d5189a4'
DISTRIB_TAINTS=''

root@OpenWrt:~# ubus call system board | grep 'model\|description'
        "model": "Xiaomi Mi Router AX3000T (OpenWrt U-Boot layout)",
                "description": "OpenWrt SNAPSHOT r26536-c67d5189a4"
root@OpenWrt:~# iwinfo | grep 'Hardware:\|PHY name'
          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)
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
How to enable MediaTek WED ( Wireless Ethernet Dispatch) feature in mainline OpenWRT?
https://forum.openwrt.org/t/current-state-of-wireless-hardware-nat-in-mt76-driver/186838/2

It is supposed to be able to reduce CPU usage when carrying out wireless speedtest.
And indeed it is quite effective based on my testing (enable HW offloading along with SW offloading in OpenWRT FIrewall settings as well)

Bash: 
root@OpenWrt_Xiaomi_AX3000T:~# cat /etc/modules.conf
# examples:
# options mod1 option=val
# blacklist mod2
options mt7915e wed_enable=Y
root@OpenWrt_Xiaomi_AX3000T:~# dmesg | grep "mt798x-wmac"
[    6.663672] mt798x-wmac 18000000.wifi: attaching wed device 0 version 2
[    7.431526] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20221208201745a
[    7.605358] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20221208201806
[    7.699116] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20221208202048
[    7.791200] mt798x-wmac 18000000.wifi: registering led 'mt76-phy0'
[    7.799540] mt798x-wmac 18000000.wifi: registering led 'mt76-phy1'
[   15.697197] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
[   15.704429] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
root@OpenWrt_Xiaomi_AX3000T:~# dmesg | grep "WED"
[    6.871629] platform 15010000.wed: MTK WED WO Firmware Version: DEV_000000, Build Time: 20221208202138
[    6.881234] platform 15010000.wed: MTK WED WO Chip ID 00 Region 3
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
10Gbps routing with OpenWRT

1) Banana Pi BPi-R4 using MediaTek Filogic 880 CPU (with Snapshot support now).
https://openwrt.org/inbox/toh/sinovoip/bananapi_bpi-r4
https://forum.openwrt.org/t/a-new-dual-10g-router-based-on-filogic-880-banana-pi-bpi-r4/163861

2) Not any time soon -- RK3588, like Nano Pi R6S
https://github.com/openwrt/openwrt/pull/15607

3) Supported -- Intel low power CPU with dual SFP+ ports, example will be GoWin R86S-N series with Intel Core i3-N305.


Or even with Intel N305 CPU and 25 Gigabit Mellanox ConnectX-4 NIC


Of course you can build even higher end systems, for example, Minisforum MS-01.



4) Interesting discussions here
https://forum.openwrt.org/t/n100-vs-bpi-r4/199866/18
 
Last edited:
hwzlite

hwzlite

Master Member
Joined
Jan 27, 2007
Messages
3,000
Reaction score
3,095
xiaofan said:
How to enable MediaTek WED ( Wireless Ethernet Dispatch) feature in mainline OpenWRT?
https://forum.openwrt.org/t/current-state-of-wireless-hardware-nat-in-mt76-driver/186838/2

It is supposed to be able to reduce CPU usage when carrying out wireless speedtest.
And indeed it is quite effective based on my testing (enable HW offloading along with SW offloading in OpenWRT FIrewall settings as well)
Click to expand...

Unfortunately WED seems to negate AQL benefit when resulting in higher WiFi latency under load according to extensive tests done there....
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
hwzlite said:
Ah..... saw bro @GlassDoor ....having fun with bpi-r4 :cool:
Click to expand...

Haha, you can also get it if you like.

I am in the firm camp of using x86_64 mini PC as the main router (running OpenWRT/pfSense) plus wireless APs (no need to run OpenWRT). When time to upgrade to 10Gbps (say in 2026 to 2028), I will look for new 10G capable mini PCs to run Proxmox and virtual OpenWRT/pfSense.

For example, I am using ZTE BE7200 Pro+ now as an AP behind OpenWRT/pfSense virtual router and it will never have OpenWRT support because of the use of ZTE CPU. But it has very good wireless coverage. Filogic 820 based Xiaomi AX3000T and H3C NX30 Pro (I am running both of them with mainline OpenWRT now, including uboot from mainline OpenWRT) have no fight with ZTE BE7200 Pro+ in terms of wireless coverage. In fact, they have no fight with my Asus RT-AX86U either. After all, they are cheap low end WiFi rotuers compared to ZTE BE7200 Pro+ or Asus RT-AX86U.

That being said, I will be interested in future development of Filogic 880 platform and WiFi 7 in OpenWRT. WiFi 7 support will probably takes time though. It is said that there will be quite some cheaper Filogic 880 based China WiFi 7 routers to be launched in the near future. Filogic 860 based routers (BE7200 rated for dual band) have already hit the market, for example, Ruijie BE72 Pro, TP-Link TL-7DR7230 and TL-7DR7260.

As of now, I only know TP-Link Archer BE805 (bundled by MR 10Gbps plan) is using Filogic 880 platform.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
hwzlite said:
Unfortunately WED seems to negate AQL benefit when resulting in higher WiFi latency under load according to extensive tests done there....
Click to expand...

Nice to see that the user "_FailSafe" is also using Crusader for latency under load test. And it is nice that the OpenWRT wiki for GL.iNET MT-6000 includes such info. Probably it would be good to include that info for other Filogic 820/830 routers as well.
https://openwrt.org/toh/gl.inet/gl-mt6000

It is good that mt76 Linux wireless driver are getting more and more improvement, which should benefit Filogic 820/830 platform based WiFi 6 routers running OpenWRT.

Reference thread quoted by you.
https://forum.openwrt.org/t/mt6000-...and-some-optimization-kernel-6-6-x/185241/366
https://github.com/pesa1234/MT6000_cust_build

I am using OpenWRT mainline snapshot (Linux kernel 6.6.32 now) with Xiaomi AX3000T with WED ON and it seems to work well for my limited tests.

I am not so much worried about so-called higher WiFi latency under load situation myself, since usualy the router will not be under load for my use cases. The only higher load is probably OOkla SpeedTest I run occassionally. Haha.
 
Last edited:
G

GlassDoor

Member
Joined
Mar 29, 2021
Messages
281
Reaction score
440
xiaofan said:
Nice to see that the user "_FailSafe" is also using Crusader for latency under load test. And it is nice that the OpenWRT wiki for GL.iNET MT-6000 includes such info. Probably it would be good to include that info for other Filogic 820/830 routers as well.
https://openwrt.org/toh/gl.inet/gl-mt6000

It is good that mt76 Linux wireless driver are getting more and more improvement, which should benefit Filogic 820/830 platform based WiFi 6 routers running OpenWRT.

Reference thread quoted by you.
https://forum.openwrt.org/t/mt6000-...and-some-optimization-kernel-6-6-x/185241/366
https://github.com/pesa1234/MT6000_cust_build

I am using OpenWRT mainline snapshot (Linux kernel 6.6.32 now) with Xiaomi AX3000T with WED ON and it seems to work well for my limited tests.

I am not so much worried about so-called higher WiFi latency under load situation myself, since usualy the router will not be under load for my use cases. The only higher load is probably OOkla SpeedTest I run occassionally. Haha.
Click to expand...
when wed is enable, higher latency is evident even when cpu is at zero load. i tested on a mt6000. ironic that for the wireless, the best performance for me is without hardware flow offload and without WED running. meaning using raw cpu.
that being said, will probably sell or give away mt6000 current ipq807x still giving me better performance. i think i got mt6000 on tb at about 120sgd shipped. great value with plenty of development momentum (or any filogic 830 for that amtter)
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
29,548
Reaction score
7,899
For those who are looking at 10G capable mini PCs to run OpenWRT (including Proxmox PVE + virtual OpenWRT), other than R86S G/U/N seres (Intel N5005, N6005 and N100/N200/N305), or some Atom C3758/C3758R based solution), or the high end MinisForum MS-01 (Intel 12th/13th gen mobile CPU, there is a new option from MiniRoute: MiniRoute R1 N305.


 
Last edited:
G

GlassDoor

Member
Joined
Mar 29, 2021
Messages
281
Reaction score
440
hwzlite said:
Woowooo.....!
The Qualcommax NSS Build's guru has released "Add mac80211 based AQL support for ath11k" .
Time to whack my spare Xiaomi AX3600 for a spin :love:
Click to expand...
root@XXX:~# iw list | grep 'Wiphy\|TXQS\|AIRTIME_FAIRNESS\|AQL'
Wiphy phy1
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ AQL ]: Airtime Queue Limits (AQL)
Wiphy phy0
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ AQL ]: Airtime Queue Limits (AQL)

Throughput is noticeability lower with AQL. On defaults didn't tweak anything.
 
You must log in or register to reply here.
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