Blog

Banana Pi BPI-R4 with Official OpenWrt 25 Firmware – 10GbE and WiFi 7 MLO Performance Testing
The Banana Pi BPI-R4 is one of the most interesting networking platforms currently supported by OpenWrt. Powered by the MediaTek MT7988A quad-core Cortex-A73 processor, dual 10GbE SFP+ ports, and optional WiFi 7 expansion modules, it offers impressive hardware specifications at a relatively affordable price.

In this article, I installed the latest official OpenWrt 25 release on the BPI-R4 and evaluated its wired and wireless performance. The goal was to compare the experience with the stock firmware and identify any issues that users may encounter when deploying OpenWrt on this platform.

Test Setup

For this evaluation, I used the following hardware:

Router
- Banana Pi BPI-R4
- BPI-R4-NIC-BE14 WiFi 7 module
Client Device
- Windows 11 PC
- Intel BE200 WiFi 7 adapter
- Mellanox ConnectX-3 10GbE network card
Network Infrastructure
- 10 Gigabit Ethernet Switch
- Linux server running OpenSpeedTest and iperf3
The router was flashed with the latest official OpenWrt 25 image using Rufus and booted directly from a microSD card.

After the initial boot, I configured a root password, disabled automatic firmware checking, and assigned the WAN interface to the SFP-WAN port while keeping the SFP-LAN port connected to the LAN network.

For all routing tests, Packet Steering was enabled with 128 steering flows and Software Offloading remained disabled.

WAN-to-LAN Performance Testing

One of the most important capabilities of the BPI-R4 is its dual 10GbE connectivity. Naturally, this was the first area I wanted to test.

The test setup was straightforward:

Linux Server → 10GbE Switch → SFP-WAN → BPI-R4 → SFP-LAN → PC

CPU utilization was monitored using btop while throughput measurements were performed with iperf3.

First Test: 4 Parallel Streams

Running iperf3 with four parallel streams resulted in approximately 3.48 Gbps throughput.

While this result is not terrible, what immediately caught my attention was CPU utilization. Almost all traffic processing was handled by Core 0, while the remaining three cores remained mostly idle.

Considering Packet Steering was enabled, I expected the workload to be distributed more evenly across all CPU cores.

Second Test: 16 Parallel Streams

Increasing the number of streams to sixteen surprisingly reduced performance.

Throughput dropped to approximately 2.74 Gbps, while Core 0 remained fully loaded.

The remaining CPU cores showed only minimal activity, typically between 10% and 15%.

Alternative LAN Configuration

I also tested a simplified LAN setup by assigning the LAN network directly to the SFP-LAN interface instead of using the default bridge configuration.

Unfortunately, the results remained largely unchanged, fluctuating between 2.5 and 2.75 Gbps.

Comparison with Stock Firmware

These numbers became even more interesting when compared with my previous testing using the factory firmware supplied by Banana Pi.

Using the same hardware setup, the stock firmware achieved approximately 9.16 Gbps WAN-to-LAN throughput.

This suggests that either OpenWrt 25 is currently missing some optimizations, or there may be an issue with packet steering, driver behavior, or hardware acceleration.

At this stage, I do not have a definitive answer, but it is certainly an area worth further investigation.

WiFi 7 Testing

For wireless testing, I installed the BPI-R4-NIC-BE14 module and connected using an Intel BE200 WiFi 7 adapter running the latest available driver.

The client PC was positioned approximately one meter away from the access point with direct line of sight.

Initial Problem: WiFi Not Working

After installing OpenWrt 25, the MT7966E chipset was detected correctly and all three radios appeared in LuCI.

However, I quickly discovered that none of the configured SSIDs would start.

I tested multiple configurations:
- WiFi 7 (BE)
- WiFi 6 (AX)
- WiFi 5 (AC)
- WPA2 and WPA3 security
- Different channels and bandwidth settings
Nothing worked.

The maximum transmit power was limited to only 7 dBm, which immediately suggested something was wrong.

Fortunately, this issue is already known within the OpenWrt community.

After applying the recommended Device Tree Overlay workaround and rebooting the router, transmit power returned to normal levels and wireless functionality was restored.

WiFi 7 Performance on 6 GHz

160 MHz Channel Width

The first test used:
- 6 GHz band
- Channel 37
- 160 MHz bandwidth
- WPA3-SAE security
Windows reported a link speed of approximately 2882 Mbps.

Running OpenSpeedTest produced excellent results:
- Download: approximately 1782 Mbps
- Upload: approximately 1849 Mbps
Multiple test runs produced very similar results.

Interestingly, iperf3 throughput was slightly lower, reaching around 1.6 Gbps with eight parallel streams.

320 MHz Channel Width

Next, I increased the bandwidth to 320 MHz.

Windows immediately reported much higher link rates, reaching 5.1 Gbps receive and 3.6 Gbps transmit.

Unfortunately, real-world performance told a different story.

OpenSpeedTest results dropped dramatically:
- Download: approximately 774 Mbps
- Upload: approximately 897 Mbps
iperf3 results were similarly disappointing.

At least in my test environment, 320 MHz operation performed significantly worse than 160 MHz.

WiFi 7 Performance on 5 GHz

Moving to the 5 GHz band, I configured:
- Channel 60
- 160 MHz bandwidth
- WiFi 7 mode
The results were very impressive.

OpenSpeedTest consistently delivered:
- Download: approximately 1.6 Gbps
- Upload: approximately 1.7 Gbps
Compared to the 6 GHz results, the difference was only around 100 to 150 Mbps.

I also attempted to use 320 MHz bandwidth on 5 GHz, but the SSID completely disappeared from client devices. This may be related to regulatory limitations or DFS restrictions.

WiFi 7 Performance on 2.4 GHz

Testing the 2.4 GHz radio in WiFi 7 mode produced more modest but still respectable results.

Using a 40 MHz channel width, OpenSpeedTest achieved:
- Download: approximately 205 Mbps
- Upload: approximately 125 Mbps
Considering how crowded the 2.4 GHz spectrum typically is, these results are perfectly acceptable.

Testing Multi-Link Operation (MLO)

One of the headline features of WiFi 7 is Multi-Link Operation (MLO), which allows multiple radios to work together under a single connection.

OpenWrt 25 includes early support for this feature, so naturally I wanted to test it.

First Attempt

My initial configuration combined:
- 5 GHz @ 160 MHz
- 6 GHz @ 320 MHz
The MLO SSID was visible and clients could connect.

However, diagnostic information showed that only the 5 GHz radio was actually participating in the MLO group.

Second Attempt

After reducing the 6 GHz radio to 160 MHz, MLO started working correctly.

Both radios appeared active and Windows reported simultaneous connectivity on both frequency bands.

The reported link speed was approximately 2882 Mbps / 2882 Mbps.

MLO Performance Results

OpenSpeedTest produced:
- Download: approximately 1.8 Gbps
- Upload: approximately 2.0 Gbps
iperf3 achieved:
- Up to 1.87 Gbps in the forward direction
- Around 1.5 Gbps in reverse mode
These were the best wireless results recorded during all testing.

MLO Stability Issues

Although MLO was functional, I did encounter stability problems.

After approximately 10 to 15 minutes of operation, the client would lose connectivity to the router.

The WiFi connection remained associated, but traffic stopped flowing and the gateway could no longer be reached.

The only reliable solution was disabling and re-enabling WiFi on the client device.

Whether this issue originates from OpenWrt, the MediaTek driver, Intel’s BE200 driver, or my own configuration remains unclear.

Further testing will be required.

Final Thoughts

Based on my initial testing, OpenWrt 25 on the Banana Pi BPI-R4 is already very usable, but there are still several rough edges.

The WiFi 7 implementation is surprisingly capable, especially when operating at 160 MHz on both 5 GHz and 6 GHz bands. MLO support is also promising, although stability improvements are clearly needed.

The biggest concern at the moment is wired routing performance. Achieving only around 2.5–3.5 Gbps when the stock firmware can exceed 9 Gbps suggests there is still work to be done somewhere in the software stack.

Nevertheless, the BPI-R4 remains one of the most exciting OpenWrt platforms currently available, and I expect performance and stability to improve significantly as OpenWrt development continues.

If you are running OpenWrt 25 on a BPI-R4 and have achieved better results, feel free to share your configuration and findings. I would be very interested to compare notes and continue investigating these issues.
June 21, 2026
Orange Pi Plus 2E – Install Armbian 26.2.0 (Debian Trixie) in late 2025 / early 2026
Brief history of the Orange Pi Plus 2E

Orange Pi Plus 2E was released by Shenzhen Xunlong 2016. There is no solid information of the launch day, but it is around April. The SBC is powered by Allwinner H3 chip (1.3 GHz, 4 cores) with 2GB DDR3 RAM and 16GB eMMC.

I personally don’t like the Allwinner chip due to poor performance. Suprisingly, this is my first-ever purchased SBC since it is very cheap.

Also, thanks to the poor stock firmware, I get to know Armbian and setup the Orange Pi Plus 2E as a home server with OpenVPN, Wireguard VPN, Pi-Hole and DDNS. It worked well for 2 and a half year (2019 – 2021), until I shut it down for new device upgrade.

Today, I take out the board for some tests before giving away. Unfortunately, the boot process interrupted halfway, so I decided to give it a fresh OS installation.

Install Armbian 26.2.0 (Debian Trixie)

The installation procedure for Allwinner chip is simple (for those who knows):
1. Boot up Armbian from the microSD card
2. Go to the OS and run the installation script to copy the OS to the internal eMMC
Step1: Download Debian 13 (Trixie) Minimal/IOT images with Armbian Linux v6.6
Once you downloaded the image, burn it to the microSD using Rufus.

Now, insert the microSD card to the Orange Pi Plus 2E, press and hold the SW2 button (sdcard boot) and connect the power supply. Armbian should be up and running from the microSD in few minutes.

Follow the console message to create the root password, and create a normal account/username. Once it is done, you can playaround with the OS. Some useful command:

armbian-config

armbian-upgrade

Step 2. Install Armbian to the internal eMMC

With root access, run the below command
```
armbian-install
```
Select 2. Boot from eMMC2 – System on eMMC and follow the guide to complete the installation

During this process, the eMMC will be formated. In my case, I choose ext4 for filesystem. It will take around 5 minutes to complete.

Once you see this message, just press Enter, disconnect the power supply, remove the microSD card and power the SBC back on. You are ready to go!

Some Tests with the Orange Pi Plus 2E on Dec 2025

OS and Linux kernel information
```
root@orangepiplus2e:~# cat /etc/os-release
PRETTY_NAME="Armbian_community 26.2.0-trunk.44 trixie"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.2
ID=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
ARMBIAN_PRETTY_NAME="Armbian_community 26.2.0-trunk.44 trixie"
root@orangepiplus2e:~# uname -a
Linux orangepiplus2e 6.6.75-legacy-sunxi #1 SMP Sat Feb  1 17:37:57 UTC 2025 armv7l GNU/Linux
```
eMMC read sequential speed: 80.99 MB/s
```
root@orangepiplus2e:~# sudo hdparm -Tt /dev/mmcblk2
/dev/mmcblk2:
 Timing cached reads:   1168 MB in  2.00 seconds = 583.62 MB/sec
 Timing buffered disk reads: 244 MB in  3.01 seconds =  80.99 MB/sec
root@orangepiplus2e:~#
```
eMMC sequential write speed: 151 MB/s
```
root@orangepiplus2e:~# dd if=/dev/zero of=/tmp/testfile.img bs=1G count=1 oflag=dsync
dd: error writing '/tmp/testfile.img': No space left on device
1+0 records in
0+0 records out
1052647424 bytes (1.1 GB, 1004 MiB) copied, 6.95331 s, 151 MB/s
root@orangepiplus2e:~#
```
ipef3 throughput
- Normal, 4 streams (Upload): 849 Mbps
- Reversed, 4 streams (Download): 914 Mbps
That is all. Thanks for reading and long-live the Orange Pi Plus 2E.
December 10, 2025

Upgrading My PC’s Wireless Card from Intel AX210 to Intel BE200 (WiFi 7)

In preparation for upcoming WiFi 7 device reviews, I have upgraded my desktop’s wireless card from the Intel AX210 WiFi 6E to the Intel BE200 WiFi 7 module. For everyday usage, the differences are modest, but this upgrade is essential for accurate testing with next-generation wireless equipment.

	Wi-Fi 6E Intel AX210	Wi-Fi 7 Intel BE200
TX/RX Streams	2×2	2×2
Bands	2.4, 5, 6 GHz (160MHz)	2.4GHz, 5GHz and 6GHz
Max Speed	2.4 Gbps	5.8 Gbps (320MHz,4096QAM)
Real Life Speed (tested by me)	2.4Gbps (GL-MT6000)	2.9Gbps (BPI R4)
Stability	Good	Not really

Installation Overview

My system is powered by the MSI MAG B460M MORTAR motherboard, which does not include an M.2 Key-E slot for wireless modules. To accommodate the BE200, I used a PCIe-to-M.2 adapter.

The adapter is very popular on marketplaces including Amazon, eBay, AliExpress, etc.

The installation process is straightforward:

Remove the adapter from the PC (make sure you disconnect the AC power before doing that)
Remove the Intel AX210 from the adapter.
Install the new BE200 module and tighten the mounting screw.
Carefully reconnect the antenna cables.
Insert the PCIe adapter into the PCIe x1 slot and secure it.
Connect the Bluetooth power header included on the adapter.

With the hardware completed, the PC was ready for testing.

Driver and System Setup

The Intel BE200 has limited functionality on Windows 10. To ensure proper operation, I upgraded the system to Windows 11 and installed Intel’s latest wireless driver (version 23.170.0.1, released October 28, 2025).
A quick check using netsh wlan show drivers confirmed support for 2.4GHz, 5GHz and 6GHz bands.

Performance Testing on Windows 11

Connected to a WiFi 7 SSID on 5GHz, the BE200 reported a link speed of up to 2882 Mbps. However, real-world throughput was lower than expected:

Speedtest: 595 Mbps Download / 929 Mbps Upload
iperf3: ~ 1Gbps

Testing with a WiFi 6 SSID produced similar results. On the AX210, I typically achieved around 1.2 Gbps Download and 900 Mbps Upload (with the OpenWrt One WiFi 6 router), but the BE200 underperformed with only 660 Mbps Download and 883 Mbps Upload.

Performance on Ubuntu 24

On Ubuntu 24, the BE200 worked immediately thanks to the pre-installed driver.
Connected to a 5GHz WiFi 7 SSID (MT7996):

Link Speed: 2161 Mbps (this number is not stable, sometime it is higher, sometime lower)
Security: WPA3
Signal Strength: Excellent
iperf3: ~1.15 Gbps upload (normal direction, 4 streams) and ~1.2 Gbps download (reversed, 4 streams)

6GHz Capability

Although the BE200 technically supports 6GHz, I was unable to connect to any WiFi 7 SSID operating in the 6GHz band. Interestingly, the Windows 11 did report the colocated AP on 6GHz (when I am connected to 5GHz WiFi 7 SSID of the Banana Pi R4 (MT7996).

Conclusion

This upgrade marks an important step toward detailed testing of WiFi 7 hardware on the channel. While the Intel BE200 shows promising link rates, actual performance still requires further investigation.

In the next article and video, I will review the Banana Pi R4 with the MT7996 WiFi 7 module and explore its capabilities.

Thank you for reading.

December 6, 2025

Install OpenWrt 23 Snapshot Firmware on Banana Pi BPI R2 PRO
This is a quick guide to install OpenWrt 23 snapshot firmware on your BPI R2 Pro (to the internal eMMC). This firmware had been pre-installed with LuCI and some packages. Here is the screenshot on Sep 2, 2023.

LuCI homepage overview. Linux kernel is 6.1.50

Network Interfaces overview. PPPoE connection is up and running

Speedtest & CPU usage overview

Currently, OpenWrt 21 firmware built by Banana Pi is out of date and there are some problems with DSA (i.e VLAN is not working). Thus, I will use OpenWrt builds from mj22226
1. Download this bpi-r2-pro-sd-to-emmc-flash.img.gz and burn it to a 16GB microSD card, using Rufus or your preferred application.
2. Insert the microSD to the BPI R2 PRO, press & hold the MASKROOM button while connecting the Power cable. The BPI R2 PRO should boot up OpenWrt
3. Login to LuCI. Under System -> Custom Command, press Run button to to flash the firmware to the internal eMMC.
4. If you receive error message such as “no space left on /dev/emmc…”, you can try to boot up OpenWrt on the SD card again (step 2). If it still failed, try to install OpenWrt firmware to the eMMC using the USB cable & RockChip DevTool
5. Once OpenWrt was flashed to the eMMC, remove the power cable, remove the microSD and boot up the BPI R2 PRO.
6. Download openwrt-rockchip-armv8-rockchip_bpi-r2-pro-squashfs-sysupgrade.img.gz (or a newer release). Go to System – Backup & Flash firmware to update the BPI R2 PRO with the firmware you have downloaded.
Enjoy you BPI R2 PRO router!
September 2, 2023
Setup File Sharing (SMB) on OpenWrt with Samba4
Why I write this guide?

Well, there are 2 guides for Samba4 and Samba3 on the OpenWrt Wiki. Each of the guide is missing a “small” piece of information which makes beginner confused.

1.Storage

More information on how to setup the storage on OpenWrt available here.
- USB Disk (USB stick/ USB to SATA adapter)
```
opkg update
opkg install kmod-usb-storage
opkg install kmod-usb-storage-uas
opkg install usbutils
lsusb -t
```
- Native SATA/NVMe Disk
Usually there is no need to install driver

2. Check if device is detected
```
ls -l /dev/sd* => if using USB stick or HDD/SSD with SATA to USB adapter
ls -l /dev/nvm* => if using NVMe
```
```
opkg install block-mount
block info
```
3. Create a partition on the disk

For this video/tutorial, I use fdisk
```
opkg install fdisk
```
```
fdisk /dev/nvme0n1 (Replace by your NVMe SSD disk name)
fdisk /dev/sda1 (Replace by your USB/SSD/HDD disk name)
```
- d => Delete partition
- n => New partition
- w => Write change to disk
4. Create a file system in the partition

This guide is only for ext4 file system. If you wish to use a different file system, please see the document.
```
opkg install e2fsprogs
opkg install kmod-fs-ext4
mkfs.ext4 /dev/sda1      => if you are using USB Stick/HDD/SSD
mkfs.ext4 /dev/nvme0n1    => if you are using NVMe
```
5. Auto mount the partition

It is easier to mount the partition using LuCI. See my video for more information. If you wish to do it with CLI, here is the commands
```
block detect | uci import fstab

uci set fstab.@mount[-1].enabled='1'
uci commit fstab

uci set fstab.@global[0].check_fs='1'
uci commit fstab
```
6. Install Samba4
```
opkg update && opkg install luci-app-samba4
```
Afer that, configure it with the the Web-UI. The Samba4 service should be automatically restart. If it doesn’t work, you can use
```
/etc/init.d/samba restart
```
7. Configure Samba Users

The username is stored in /etc/passwd file. To modify it, use VI or Nano
```
vi /etc/passwd
```
After that, insert this example line to end of the file. It will create a new username with the below information:
```
vantc:*:1000:65534:vantc:/var:/bin/false
```
Hint: Using the same username for Samba4 (OpenWrt) and Windows will cause some problems where you need to change some setting on Local Security Policy. If possible, please use a different username for Samba4 & Windows.
- user in this example will be called ‘vantc’“ (this is the loginname you need to enter, when Windows pops up the authentication dialogue)
- with the unique system ID ‘1000’
- with the group id ‘65534’ (which is the group identifier for ‘nobody’= no special default group)
- ‘/var’ just means the user will not need a special home folder on the system
- ‘/bin/false’ means the user will not have a default shell program associated
```
smbpasswd -a vantc => Set password
```
```
service samba restart (Optional)
```
8.Troubleshoot – No Write Access
- Modifying the permissions and owner of the folder
If you are using USB stick/ HDD/ SSD
```
chmod -R 777 /mnt/sda1
chown -R nobody /mnt/sda1
```
If you are using NVMe
```
chmod -R 777 /mnt/nvme0n1
chown -R nobody /mnt/nvme0n1
```
More info: https://openwrt.org/docs/guide-user/services/nas/cifs.server#cannot_write_to_a_samba_share

9. Fine-Tune & others
- Since netfilter tracks every connection, it may improve throughput to disable conntrack for Samba connections if you use NAT.
  https://openwrt.org/docs/guide-user/services/nas/cifs.server#throughput
- Remote Access
  Doable, not recommended. You better setup Wireguard VPN to access the NAS locally.
- Apple Discovery & Network Discovery
10. Enjoy your OpenWrt NAS

Have fun with your OpenWrt NAS.

If you enjoy my content, feel free to give it a like, leave a comment, subscribe to the channel, give me a Super Thanks or support me on Patreon. I will be happy regardless of the action!
August 26, 2023
Install OpenWRT on the Aruba AP-175
OpenWRT support for the AP-175 was officially available on March 26, 2023. The PR to Add OpenWRT support for Aruba AP-175 was created by Hurricos (Martin) on September 2022. Special thanks to Hurricos and all developers involved to make it happen.

Specifications
- Device: Aruba AP-175
- SoC: Atheros AR7161 680 MHz MIPS
- RAM: 128MB – 2x Mira P3S12D40ETP
- Flash: 16MB SPI NOR. Chip is vary from MXIC MX25L12845EMI-10G to Spansion S25FL128P
- WiFi: 2 x DNMA-H92 Atheros AR9220-AC1A 802.11abgn
- ETH: IC+ IP1001 Gigabit + PoE PHY
- LED: 2x int., plus 12 ext. on TCA6416 GPIO expander
- Console: CP210X linking USB-A Port to CPU console @ 115200
- RTC: DS1374C, with internal battery
- Temp: LM75 temperature sensor
Firmware
- Aruba AP-175 OpenWrt upgrade (sysupgrade)
- Custom u-Boot for AP-175, or build it from here
Installation Procedure Brief

Since stock u-Boot only allows signed kernel to boot (Aruba OS), A U-Boot replacement is required to install OpenWrt on this device.
- Use the CH314A SPI-Flasher or Raspberry Pi 4 and a 16-pin Test Clip (SOP16) to dump the SPI NOR chip
- Apply custom u-Boot for AP-175 on the SPI NOR dump
- Write the modified image to the SPI NOR chip again
- Boot up OpenWrt sysupgrade image via TFTP
Install u-Boot

Note that the stock bootloader on this device does not allow for unsigned kernels to boot, so replacing the bootloader is required for OpenWrt support on this device. The only way to do this is via directly writing to the SPI Flash. The custom U-Boot for the Aruba AP-175 can be found here. Besides, you can compile it from https://github.com/Hurricos/u-boot-ap105/tree/ap175.

To flash the SPI NOR you will need a 16-pin Test Clip (SOP16). You can use CH314A SPI-Flasher or directly wire the Raspberry Pi SBC to the SPI NOR with the test clip.

In this guide, I am using a Raspberry Pi 4 Model B, a “DIY 16-pin test clip” and flashrom application (on Raspberry Pi OS) to dump the SPI NOR.

Here is the main steps:
1. Create a full dump of the SPI Flash, and store it in a safe place
2. Erase and Clear 0x0-0x3ffff on the SPI Flash
3. Flash U-Boot to 0x0
4. Proceed to the OpenWrt Install Procedure
Detail guide for using Raspberry Pi SBC with flashrom:
- Make sure that SPI interface is enabled on Raspberry Pi OS. You can do this in raspi-config
- Make sure the AP-175 is power-off (disconnect PoE Adapter) before proceed
1. Create a full dump of the SPI Flash, and store it in a safe place

WIP
April 5, 2023

Blog

Banana Pi BPI-R4 with Official OpenWrt 25 Firmware – 10GbE and WiFi 7 MLO Performance Testing

Test Setup

Router

Client Device

Network Infrastructure

WAN-to-LAN Performance Testing

First Test: 4 Parallel Streams

Second Test: 16 Parallel Streams

Alternative LAN Configuration

Comparison with Stock Firmware

WiFi 7 Testing

Initial Problem: WiFi Not Working

WiFi 7 Performance on 6 GHz

160 MHz Channel Width

320 MHz Channel Width

WiFi 7 Performance on 5 GHz

WiFi 7 Performance on 2.4 GHz

Testing Multi-Link Operation (MLO)

First Attempt

Second Attempt

MLO Performance Results

MLO Stability Issues

Final Thoughts

Orange Pi Plus 2E – Install Armbian 26.2.0 (Debian Trixie) in late 2025 / early 2026

Brief history of the Orange Pi Plus 2E

Install Armbian 26.2.0 (Debian Trixie)

Step1: Download Debian 13 (Trixie) Minimal/IOT images with Armbian Linux v6.6

Step 2. Install Armbian to the internal eMMC

Some Tests with the Orange Pi Plus 2E on Dec 2025

Upgrading My PC’s Wireless Card from Intel AX210 to Intel BE200 (WiFi 7)

Installation Overview

Driver and System Setup

Performance Testing on Windows 11

Performance on Ubuntu 24

6GHz Capability

Conclusion

Install OpenWrt 23 Snapshot Firmware on Banana Pi BPI R2 PRO

Enjoy you BPI R2 PRO router!

Setup File Sharing (SMB) on OpenWrt with Samba4

1.Storage

2. Check if device is detected

3. Create a partition on the disk

4. Create a file system in the partition

5. Auto mount the partition

6. Install Samba4

7. Configure Samba Users

8.Troubleshoot – No Write Access

9. Fine-Tune & others

10. Enjoy your OpenWrt NAS

Install OpenWRT on the Aruba AP-175

Specifications

Firmware

Installation Procedure Brief

Install u-Boot