1 Introduction
The main router of my home data center has always been iKuai. Its main advantage is supporting the multi-dialing feature (for a detailed concept of multi-dialing, see the article: ). Since my Telecom broadband supports up to 3 dials, I can obtain 3 public IPv4 addresses simultaneously, which is extremely practical for a user like me who has multi-line access needs. Coupled with iKuai's mature capabilities in multi-link load balancing and traffic management, it has indeed felt very stable and reliable to me for many years.
However, as ISP policies tighten day by day, the possibility of the multi-dialing feature being canceled or public IP addresses being significantly restricted in the future is increasing. By then, iKuai's core advantages at the network level will be greatly compromised. Although it has many built-in advanced features, its support for the most commonly used Docker is quite awkward—not only does installing plugins require binding an iKuai Cloud account, but the plugin features are also very limited, far from meeting my needs for flexible expansion and customization. Simply put, iKuai's Docker feature can only be described as ”not non-existent,” but in terms of practicality, it is far from enough (the virtual machine feature is similar).
For these reasons, I started to consider whether it is possible to find an alternative solution that, in the event of future IPv4 public address reclamation or multi-dialing restrictions, can guarantee stability and out-of-the-box usability while simultaneously offering good Docker support and a rich software ecosystem. Coincidentally, some time ago I acquired a mini x86 host equipped with an Intel N150 processor and 6 Gigabit Ethernet ports to upgrade my existing iKuai main router (after all, the original J2900 four-port machine was already stretched thin, with 1 LAN port and 3 WAN ports no longer being enough).
So how can the replaced J2900 be repurposed? Considering the performance and interface advantages of this hardware, I thought of the X-WRT project. As a customized system based on OpenWrt, it theoretically has the potential to become an ideal alternative in terms of routing stability, plugin richness, and container support. Next, based on this replaced host, I will deeply explore the installation and use of X-WRT to see if it can truly achieve the main router goal of “stable + flexible + rich”.

2 From OpenWrt to X-WRT: A Better Choice for the Main Router
As for what system to flash onto this retired J2900 four-port mini PC, I didn't actually struggle too much with the decision. It was basically certain to be in the OpenWrt camp, except that between the original OpenWrt and its modified version X-WRT, I made a careful comparison and finally chose the latter.
Let's briefly explain the relationship between the two:X-WRT is a deeply re-developed version based on OpenWrtIt inherits OpenWrt's underlying architecture and driver compatibility, but has made a lot of enhancements and optimizations in the Web interface, default features, plugin integration, and user experience. You can think of the original OpenWrt as a “minimalist basic version”—highly flexible, but you have to configure everything manually; whereas X-WRT is more like an “enhanced out-of-the-box version”—common features are pre-configured for you, and it works right after powering on.
If OpenWrt is “leaving blank space for experts to tinker with,” then X-WRT is more like “pre-setting 80% of scenarios for users.” Its target users are very clear:mainstream home users who want their devices to run stably, can complete configurations directly through the web backend, and want to avoid messing with the command line as much as possibleTherefore, it has made many compromises and optimizations in stability and ease of use: interface beautification, pre-installed plugins, and driver adaptation are relatively mature, making it especially suitable for “basic but critical” roles like the main router.
Of course, this design philosophy also means it makes trade-offs on certain advanced features. For example, X-WRT does not integrate proxy-related features by default, and no longer uses the opkg package manager. Although the new version has switched to the apk system, and mainstream proxy components like sing-box and v2ray can still be installed, overall the range of optional software is relatively limited,and proxying is not its main featureThis also reflects its usage philosophy:The main router focuses on stability, and it is highly recommended to leave proxy services to a bypass router—after all, once the proxy configuration goes wrong, it is highly likely to affect normal access for the entire intranet.
As for my mini host, which is prepared to take on the responsibility of the main router, what I truly value are three keywords:stability, complete features, and hassle-free deploymentI don't want to manually adjust network ports, fill in software sources myself, or build the Docker environment on my own as soon as I boot up. X-WRT gives me the feeling that “all of these have been prepared for you.”
Especially in the LuCI backend, core features of the main router such as network management, DHCP allocation, firewall rules, and port forwarding all have clear UI pages, requiring almost no terminal commands; and common plugins such as Aria2, KSmbd, DDNS, UPnP, and Docker are already built into the full-featured image, ready to use with just a click.
So in the end, I chose the full version image of X-WRT. After flashing, almost the entire configuration was completed in the Web backend, and the experience was even more comfortable than my previous AC86U.For me, X-WRT is not necessarily the “lightest,” but it is definitely one of the OpenWrt family branches currently “most suitable to be used directly as a main router”。
3 Creating X-WRT Boot Storage
1 Overview
Different from our usual way of using ISO images to make boot disks and guide system installation, X-WRT writes the img to the boot storage through disk writing software (such as Etcher, dd). This is actually completely cloning the X-WRT system to the boot storage. After that, you only need to plug the boot storage into the USB port of the target device and set it to boot from the boot storage to run X-WRT normally.
2 Downloading the Image
The official download address for the X-WRT image is:https://downloads.x-wrt.com/rom/If the motherboard of the target device you want to install is a legacy BIOS boot (MBR), choose ”x-wrt-25.04-b202506071033-x86-64-generic-ext4-combined.img.gz”; if the target device motherboard forces UEFI boot, or you specifically want to use a GPT partition table (including an EFI partition, suitable for newer UEFI motherboards), choose ”x-wrt-25.04-b202506071033-x86-64-generic-ext4-combined-efi.img.gz”. For ARM architectures like the R2S Plus, choose ”x-wrt-25.04-b202506151427-armsr-armv8-generic-ext4-combined-efi.img.gz”:

Note: X-WRT is divided into a lite version and a full version based on system size and feature configuration. The most significant difference is whether Docker support is built-in. The full version pre-installs docker-ce and integrates the LuCI interface control panel, making it suitable for devices with certain storage and computing capabilities, such as small servers and x86 hosts. The lite version is more suitable for lightweight devices like R2S and MT7621, retaining only basic routing and management features, and does not include Docker.
Since I am installing on a machine with a J2900 CPU, I chose the full version suitable for x86 architecture UEFI boot: ”x-wrt-docker-25.04-b202506151427-x86-64-generic-ext4-combined-efi.img.gz”.
3 Extracting the Image
In the CLI interface, use the following command to decompress the image (decompression tools in the GUI interface also work):
gzip -d x-wrt-docker-25.04-b202506151427-x86-64-generic-ext4-combined-efi.img.gz
Obtain the ”x-wrt-docker-25.04-b202506151427-x86-64-generic-ext4-combined-efi.img” file.
4 UseEtcherto write the img to the boot storage (TF card or USB flash drive)
Download the corresponding installation package from the Etcher GitHub homepage according to your environment to install it (https://github.com/balena-io/etcher/releases):

Run it after installation, and follow the steps below:





4 Initializing X-WRT (Running from Boot Storage on x86 Devices)
After successfully booting X-WRT using the boot storage, connect the console terminal's network port directly to eth0 of X-WRT. The eth0 interface has the DHCP service enabled, so the terminal can obtain an address directly upon connection, and then directly accesshttp://192.168.15.1That's it (connecting directly to eth0 allows you to automatically obtain an address via DHCP; as for whether it is 192.168.15.1, that is uncertain, who knows which version might change it again, so ultimately the default gateway address of the obtained address shall prevail), the default username and password for the web GUI are both ”admin”:

After logging into the GUI, you can first change the interface language:


Then modify the administrator password:


Enable SSH access:

Once the SSH service is enabled, you can directly enter the CLI interface via SSH whenever needed in the future.
5 Cloning X-WRT from USB Flash Drive to Local Storage (Go ahead on x86, proceed with caution on ARM)
When many people mention “cloning the system into the local hard drive”, they might subconsciously think it is nothing more than a dd command—but this actually only applies to X86 devices, for most ARM routers or development boards, things are often not that simple.
The reason is:The X86 platform has unified BIOS/UEFI boot specifications and standardized local storage interfaces, so there are almost no adaptation issues with system booting, so you can even directly clone the entire X-WRT system from a USB flash drive to the hard drive, plug it in and run, which is very “foolproof”.
However, ARM platforms (especially devices like NanoPi R2S Plus) are different: their boot mechanisms often rely on specific bootloaders, device trees, and partition layouts, and sometimes even require the system to boot from a specific offset address of eMMC/TF,even if you successfully dd it in, it may not boot at all. Even between devices of the same series (such as R2S and R2S Plus), firmware may not be compatible due to hardware differences, and the probability of running into issues is much higher than with X86.
Therefore, in this section, I will mainly take X86 devices as an example to explain how to clone X-WRT booted from a USB flash drive to a local hard drive, which is a stable, simple, and recommended practice; if you are using an ARM device, it is recommended to refer to the manufacturer's documentation or community experience first,and do not easily believe the saying “just dd directly”, as you will likely be ruthlessly taught a lesson just like me.
For devices that are already running X-WRT using boot storage, if they have local storage themselves (such as the local hard drive of an idle host), you can use the ”dd” command to directly clone the X-WRT system from the USB flash drive to the local storage, so you can get rid of the unorthodox scenario of ”running X-WRT using a USB device (or TF card)”.
After booting normally using a USB flash drive and enabling the SSH service in the web UI, you can use SSH to log into X-WRT, using the default username and password ”root/admin” to log in:

Confirm the name and path of the local disk:
lsblk
Generally, for X-WRT, sda is the local disk and sdb is the USB flash drive. Taking my x86 host as an example:

Then run the dd command to clone the X-WRT system to the local storage
Clone the X-WRT system on the USB flash drive to the local storage (if specifies the input source, of specifies the output destination, bs specifies the read/write speed, and if the USB flash drive is good, it can be set to 4M). Run the following command in X-WRT:
dd if=/dev/sdb of=/dev/sda bs=4M

Cloning completed:

The last step, and the most important command:
sync
The purpose of this command is:Forcefully write cached data in memory to the disk (or other storage devices)。
Why run this command? Because when running commands like dd, cp, tar, etc., that write large amounts of data, the Linux kernel usually does notimmediatelywrite the data to the hard drive, but instead places it in the memory cache first (to improve performance). This data will later be slowly flushed to the hard drive asynchronously by the kernel. But if youimmediately reboot, power off, or unplug the USB flash drive, these “not yet fully written” data may be lost, causing: file system corruption, cloning failure, incomplete partition structure, inability to boot the system, black screen on startup, etc. By adding sync, the system will wait until all data is flushed into /dev/sda before returning the terminal prompt, ensuring that the data you wrote is complete.
Wait for the cloning to complete, then restart the device and unplug the USB flash drive. Booting from the local hard drive, you can now enter X-WRT normally. Running the lsblk command again, you can see that the contents of sda are completely identical to the previous sdb:

Note 1: If it is a newer version of GNU dd, it supports the progress bar parameter ”status=progress”, but for X-WRT, it uses BusyBox dd, which does not support this parameter, so you just have to wait patiently.
Note 2: If you have an extra USB flash drive, you can actually find a new USB flash drive (FAT32 format is best, NTFS format is also fine), copy the previous img file: ”x-wrt-docker-25.04-b202506151427-x86-64-generic-ext4-combined-efi.img” directly to the root directory of the USB flash drive, then plug it into the mini PC and mount it to the ”/mnt” directory, such as ”/mnt/d”, and then use the dd command:
dd if=/mnt/d/x-wrt-docker-25.04-b202506151427-x86-64-generic-ext4-combined-efi.img of=/dev/sda bs=4M
This way, you don't need to ”clone the entire disk” of the boot USB flash drive to sda, but only write the image file, which takes less than 1 minute.
6 Network Configuration
1 Overview
Under the “Network” tab of X-WRT, users can centrally manage various network functions related to the router, including interface assignment, bridge settings, DHCP services, static routing, firewall zone division, VLAN configuration, etc. This interface basically covers most network scenarios required in home or small-to-medium network environments, retaining the flexibility of OpenWrt while simplifying the configuration process through a graphical interface. Since there are too many functions and most of them are not needed by average users, I will briefly explain a few functions that I consider important.
2 Interfaces

Under the default configuration, the X-WRT system usually pre-configures at least three basic network interfaces: lan, wan, and wan6.
Among them, the lan interface corresponds to a bridge device named br-lan, which is a Layer 2 bridging interface used to aggregate multiple physical network ports (such as eth0, eth2, eth3, etc.) into a unified broadcast domain to achieve interconnection within the local area network. By default, br-lan usually only contains eth0, meaning only one physical port is in the LAN zone, used to provide management access (such as Web UI or SSH).
The wan and wan6 interfaces are used for IPv4 and IPv6 external network connections respectively, bound to the eth1 interface by default, and the system will configure them as DHCP clients to automatically obtain public IP addresses. This port allocation strategy is applicable to most dual-port devices (such as industrial PCs, soft routers, etc.), where eth0 is used for the internal network and eth1 is used for the external network.
In addition, for some devices with USB network card interfaces, or in cases where specific customized image versions are used, X-WRT may alsopreset additional usbwan and usbwan6 interfaces, used to be compatible with scenarios such as external USB network cards, 4G/5G dongles, etc. These interfaces are usually bound to usb0 (or a similar name). Even if the user has not actually connected a USB network card, the system may still retain these two logical interfaces as one of the default configurations for device adaptation.
The default interfaces on my x86 host are as follows:

Click Edit in the image above to configure protocols, IP addresses, etc., for each interface.
3 DHCP/DNS
The DHCP and DNS server functions provided by X-WRT are actually very powerful, supporting a series of advanced features such as custom address pools, static leases, DNS forwarding rules, intranet domain name resolution, ad filtering, etc., suitable for users with high network control requirements to configure in depth. But for most ordinary users, the system's default settings are already sufficient for daily use, stable and reliable, with almost no need for additional adjustments.:

4 Firewall
This part of the content is actually the concrete result of iptables rules. Explaining it clearly involves underlying packet processing logic and forwarding chains, which is indeed quite complex. Fortunately, for the vast majority of users, X-WRT's default firewall configuration has already covered common use cases for home or small-to-medium networks, and basic intranet isolation, NAT egress, and a certain level of security protection can be achieved without additional changes. Only when you need to set up a bypass router transparent proxy, special port mapping, or complex VLAN management is it necessary to study this part of the configuration in depth.

Note: Forthe most common bypass gateway transparent proxy scenario(i.e., the main router is responsible for dialing, and the bypass gateway only acts as a traffic transit device), **only checking ”IP Masquerading” for LAN → WAN in "Zone Settings" is usually sufficient.
IP Masquerading is actually the specific implementation of the commonly known NAT (Network Address Translation) function in iptables: its role is to masquerade the source IP address as the router's egress IP when data packets are forwarded from the intranet (such as LAN) to the extranet (such as WAN), thereby enabling multiple devices to share a single public IP address to access the Internet.
Related to NAT behavior, there are also two important system-level parameters located in the “System” - “Advanced Options” page of X-WRT:
- Full Cone NAT(Full Cone NAT): also known as NAT Type 1, which means that as long as an intranet host has initiated an outbound connection, any subsequent response packets from that external address and port can be successfully forwarded back. This mode is very friendly to applications like P2P, gaming, and remote connections, making connection establishment easier and penetration stronger, but it is relatively open and slightly less secure.
- Enable Forwarding Acceleration (NAT Flow): This feature is based on the kernel's fastpath/flowoffload acceleration mechanism. After a packet matches a rule for the first time, it speeds up the forwarding processing efficiency of subsequent identical traffic, significantly improving NAT performance and reducing CPU usage, making it especially suitable for software routers in high-traffic scenarios.
Simply put:
- Masquerading is the basic operational core of NAT;
- Full Cone NAT is a “relaxed policy” type of NAT, which is more open to the outside;
- NAT Flow is a performance optimization and acceleration mechanism, which is friendlier to high loads.
Using these three in combination can allow your bypass gateway or main router to achieve a more balanced state in terms of functionality and performance. If it is just for ordinary home use, you can choose to enable all of them to both enhance the experience and maintain good compatibility.


5 Other Features
As for the remaining ”Website Filtering”, ”QoS”, ”Multi-WAN dialing”, etc., I won't go into detail. Most people won't need them, and they are actually not complicated; those who need them can research them on their own.
However, regarding multi-WAN dialing (strictly speaking, it should be multi-link management), let me add one thing: compared to iKuai's multi-link management, other solutions really don't stand a chance. The free version of iKuai completely blows everything else out of the water, including the related features of various enterprise-grade products:

7 Services
As I mentioned in the preface, compared to native OpenWrt,a major feature of X-WRT is its out-of-the-box “enhanced firmware” philosophy. Not only does the system enable the Web interface LuCI by default,but it also built-in a large number of polished and well-adapted utility tools and service components, covering multiple typical home/SMB network requirement scenarios ranging from downloading, sharing, printing, to proxying:

Below is a brief list of several representative components:
Aria2 Download Tool
Hailed as an “embedded masterpiece,” this multi-threaded download tool supports mainstream protocols such as HTTP, FTP, BitTorrent, and magnet links. X-WRT is usually paired with web-aria2-ui to provide a visual management interface, allowing you to easily manage download tasks in your browser and build a lightweight offline download center:

Dynamic DNS
Including mainstream dynamic DNS service platforms such as Alibaba Cloud, Tencent Cloud (Dnspod), Cloudflare, Namecheap, and DuckDNS, all of which are configurable via Web pages without tedious manual installation or scripting, making it suitable for public IP users to set up remote access capabilities:


p910nd Print Server
A classic USB print sharing service, especially suitable for old but still usable printers. Through built-in support, X-WRT gives these traditional devices a “second spring” in modern networks:


Docker CE Container
The Docker CE (Community Edition) container engine pre-installed in the full version of X-WRT unlocks more possibilities of embedded systems for advanced users. Whether deploying intranet services (such as Home Assistant, AdGuard Home, Frp, etc.) or running specific tool images (such as Aria2, qBittorrent, OpenWrt helper plugins, etc.), they can be quickly started using familiar Docker commands. X-WRT also integrates luci-app-dockerman to provide a visual container management interface, suitable for beginners to try containerized deployment, while also meeting the automation needs of advanced users, making the router a lightweight service platform in the truest sense:

Network Sharing (Lightweight Samba Implementation)
An SMB implementation contributed by Samsung, South Korea, with obvious performance optimization and resource usage far lower than traditional Samba. It is very suitable for routers or embedded devices with limited storage performance, and is commonly used in USB drive/NAS file sharing scenarios:

natcap Smart Transparent Proxy Engine
This is a highly distinctive core component in X-WRT in recent years. Based on the Connection Capture mechanism, it provides smart traffic splitting capabilities, enabling precise proxying or direct connection operations by protocol, target domain name, or IP. It is suitable for bypass gateway proxy scenarios and supports multiple forwarding backends (such as Clash, Brook, Xray, etc.), offering flexible configuration while remaining friendly to system resources:

tinyproxy Lightweight Forward Proxy Service
With an extremely small memory footprint, it is used solely for HTTP forward proxy purposes, making it suitable for temporary proxying of intranet devices or as a local transparent gateway forwarding module:

UPnP IGD / PCP Protocol Support
X-WRT supports common automatic port mapping protocols, including UPnP IGD (Internet Gateway Device) and the more modern PCP (Port Control Protocol), which can dynamically open public ports for intranet devices (such as NAS, game consoles, download clients, etc.), eliminating the hassle of manual port forwarding configuration. Especially in home network environments, this “plug-and-play” automatic penetration capability significantly improves device connectivity and usability. X-WRT provides the luci-app-upnp page, where users can view in real-time which devices and applications are currently using port mapping, and supports custom policies to avoid abuse:

Note: If you do not need the ”Docker CE Container” feature, you do not need to install the full version of X-WRT; installing the slim version is sufficient.
In addition to the above components, X-WRT usually built-in according to the firmware type:
- Common diagnostic tools (such as iperf3, tcpdump, ethtool, etc.);
- Common Web management plugins (such as traffic statistics, port forwarding, ARP/neighbor table display);
- Customized optimizations for the network environment in Mainland China (such as automatic domestic/international traffic splitting, NAT acceleration, bypass transparent forwarding presets), etc.
From “downloading/sharing” to “printing/remote access,” and then to “transparent proxy,”X-WRT covers the core needs of most home and small-to-medium office network environments. It is not just a routing system, but more like a customized “small network operating system.”
8 Software Packages
In addition to these built-in services, as a modded version of OpenWrt, you can of course still install the software you need through ”System” - “Software”:


Commonly used software is still not lacking:



I won't introduce the others one by one; those in the OpenWrt family are basically much the same.
9 Afterword
In fact, there are many modded versions of OpenWrt,and X-WRT is just one representative that is relatively mainstream, balancing ease of use and stability.In addition to this, there are many other branch versions that are equally excellent but have their own characteristics, such as:
- LEDE: An early, very active modded version that later merged with
- ImmortalWrt: A derivative version based on the latest OpenWrt code, with an active community, integrating more plugins and architecture support by default, especially popular for proxying and multi-dialing;
- Community firmwares such as OpenWrt-Rockchip / R66S-Plus-OpenWrt: More focused on hardware adaptation and performance optimization, commonly found on devices like R4S, R5S, and x86;
- Highly integrated proxying firmwares (such as Flippy's firmware, P3TERX compiled version): Focusing on an out-of-the-box proxying experience, often integrating sing-box, Clash, Xray, etc., suitable for use as bypass gateways or proxy relay devices.
In general, every modified OpenWrt firmware has its own target users and design philosophy: you don't have to stick to X-WRT. The key is to see which devices you want to use it on, what features you need, and how much effort you are willing to spend on configuration and maintenance. Just like my choice of X-WRT this time, it's because it allows me to quickly deploy a stable main router system. But if you have higher pursuits for proxying, automation, and ultimate performance, then other customized firmwares might be the answer you truly need.
It is recommended that everyone clarify their actual needs before selecting a model, and then search targetedly for the version that suits them best.—Although this process may take more time, it will save you from many detours.
On my end, multi-dialing is possible but the speed does not stack, and no public IP is provided. It falls into the category of “multi-dialing is possible, but pointless.”
Multi-dialing without a public IP is indeed just for self-amusement.