iKuai Soft Router Series - The Strongest Multi-Dialing Soft Router: iKuai
This article was last updated 969 days ago. The information in it may have developed or changed. If anything is no longer working, please leave a comment in the comment section.
Article Abstract
To address the demand for multi-dialing features, iKuai software router provides comprehensive support through a four-layer architecture. First, it offers two modes: single-line multi-dialing and multi-line multi-dialing, supporting hybrid configuration of physical network cards to flexibly adapt to different network environments. Second, supporting features such as port mapping, traffic splitting, and protocol/domain/uplink-downlink splitting are all compatible with multi-dialing scenarios, which, combined with intelligent flow control and dynamic DNS, meet complex network management needs. Third, it lowers the barrier to entry through an intuitive configuration interface, making it especially suitable for scenarios like home data centers. In practical applications, users can achieve bandwidth aggregation through multiple WAN ports, and simplify IPTV multi-device playback configuration with UDPXY technology, ultimately verifying iKuai's advantages in multi-dialing feature completeness and ease of use, making it a highly recommended solution for home network environments.
Qwen3-14B · 2026-06-18

Preface

If we are talking about the soft router with the best multi-dialing support, I think it is undoubtedly iKuai. What I mean by "the strongest" includes four aspects: first, it supports multi-dialing; second, the details of multi-dialing are well done; third, the multi-dialing support for supporting features is the best; and fourth, the configuration logic is simple. In fact, the last point, simple configuration logic, is extremely important, as it determines how quickly beginners can get started. Currently, the two systems I know of that have relatively good multi-dialing support are OpenWrt/LEDE and iKuai. While I still need to get used to the configuration logic of OpenWrt/LEDE, iKuai can be used directly without even looking at the help guide. Therefore, from this perspective, iKuai's configuration logic is the simplest.

Brief Description of iKuai Multi-Dialing Interface

Next, let's discuss iKuai's multi-dialing feature from the above four layers (combining the 1st and 2nd layers together).

The First and Second Layers

First, let's look at the current interface status of my iKuai router:

image.png

Currently, there are 3 WAN ports and 1 LAN port: WAN1 is single-line dual-dialing, connected to the data LAN port of the Telecom optical modem; WAN2 is a static IP, uplinked to the ASUS AC86U; WAN3 is DHCP, connected to the IPTV port of the Telecom optical modem, used to receive IPTV and convert it to HTTP via UDPXY for convenient simultaneous viewing on multiple clients (this topic is too broad, so I will cover it in a separate article and skip it here).

Let's first look at the single-line multi-dialing configuration of WAN1:

image.png

Since there are only 2 dials here, only adsl1 and adsl2 are shown at the bottom of the image above, and the status behind them is "Enabled", indicating successful dialing.

If you want single-line multi-dialing, you only need to select the hybrid mode based on physical network cards, and there is no limit on the number of multi-dials. If the ISP's central office has no restrictions, you can dial infinitely (wishful thinking). The reason to discuss this is that some routers can only do dual-dialing, such as ASUS routers, and their features are very limited:

image.png

In addition to single-line multi-dialing, there is also a luxurious way to use multiple WAN ports: multi-line multi-dialing (previously, my iKuai had 6 network interfaces, so I luxuriously used 3 independent network ports as WAN1, WAN2, and WAN3, respectively connected to the Telecom optical modem's data ports, which was very aggressive). Each WAN port can dial independently. The advantage of this is that if the ISP's central office has no restrictions, you can have 3 Gbps downlink bandwidth (my home can only do 3 dials at most), like in my case (actually useless), which is useful for some guys who like to run speed tests just to see big numbers. However, the prerequisite for this is to have at least one 2.5G port or 10G port as the LAN port (or do link aggregation of 3 Gigabit ports between iKuai and the intranet core switch, which I used to do, but later found useless), and the core switch in the intranet must also have at least one 2.5G port or 10G port. Since my software router only has Gigabit ports, I previously used link aggregation to aggregate 3 Gigabit electrical ports with 3 electrical ports of the intranet Huawei Layer 3 switch S5720-28P-SI-AC (which was also actually useless).


Digression: I used to love tinkering too much. I divided the intranet into several VLANs, each with a 24-bit mask subnet. The secondary switches in each room supported 802.1Q and were manageable, connecting to the core Huawei switch via 802.1Q. At the same time, I used policy routing on the Huawei Layer 3 switch to manage traffic. A key requirement here was IPTV. A major reason for dividing VLANs before was to connect the Telecom optical modem IPTV on the sofa wall side (connected to a separate VLAN on the core Huawei switch) with the Telecom set-top box on the TV wall side (connected to a VLAN with the same ID on the TV wall's secondary switch) through VLANs. Therefore, the secondary switch on the TV wall side had to support VLAN and 802.1Q to connect with the core Huawei switch. Later, I got tired of it, and after an iKuai upgrade, it directly supported UDPXY, eliminating the need for VLAN isolation, allowing multi-device playback within a single VLAN.

Playback effect after installing APTV on the Apple TV in the living room:

image.png

image.png

With an Apple TV in both the living room and master bedroom running APTV, and APTV installed on iPhone, iPad, Mac mini, and MacBook, I can watch TV anytime (although I never actually watch it, but as a tech enthusiast, having it is one thing, watching it is another). For specific implementation steps, please refer to my other article:iKuai Soft Router Series: Achieving Telecom IPTV All-Media Playback

Digressing a bit, since the core demand for VLANs was gone, I optimized it later. I replaced the core switch with a TP-Link 24-port managed switch (the Huawei switch fan was too noisy), deleted the VLAN configurations of other secondary switches, and used them as unmanaged switches. This made the network environment much simpler all of a sudden.


The WAN2 port is uplinked to the ASUS AC86U router (a classic model with great software support, whether Merlin firmware or other special plugins) using a static IP, and dialed once more on the AC86U. At this point, all 3 dials are used up.

Compared to the multi-dialing settings of OpenWrt/LEDE, I think iKuai's is simpler, clearer, and has a simpler logic.

The Third Layer: Excellent Support for Multi-Dialing in Supporting Features

What does this mean? Actually, if you think about it, you will understand. After successful multi-dialing, many features need to support multi-dialing, such as:

Port Mapping

We definitely need to be able to specify port mapping on different egress lines, right?

image.png

iKuai can do this; you can choose to map all together or map one or several individually.

Traffic Splitting

Multi-Line Load Balancing

This most basic splitting method:

image.png

Protocol Splitting:

image.png

Port Splitting:

image.png

Domain Splitting:

image.png

Uplink/Downlink Splitting:

image.png

Intelligent Flow Control:

image.png

In terms of flow control, iKuai is extremely powerful. Unfortunately, these features are only useful in multi-dialing or multi-WAN environments. Generally, if there is only one egress link, these features are useless.

Dynamic Domain Name

This is indeed powerful:

image.png

iKuai's DDNS supports multiple domain providers:
image.png

Commonly used Alibaba Cloud, Tencent Cloud, Cloudflare, and PeanutHull are all supported. This feature is extremely useful for building a home data center, which we will discuss later.

Monitoring

image.png

Actually, there are other auxiliary features that support multi-line, but we won't discuss them one by one. The ones above are already enough for most users.

The Fourth Layer

In fact, from the configuration pages above, it can be seen that iKuai's configuration logic fits Chinese users” habits very well; it is basically self-explanatory, and if you don't understand the meaning of some options, you can just check the online help. So from the configuration level, it is indeed very simple. However, unfortunately, without a multi-line environment, many of iKuai's advantages cannot be fully utilized. Additionally, if users want to achieve more features on a single device, such as extending certain features through plugins, iKuai does not support it directly (why say not directly? iKuai supports virtual machines and Docker, which can indirectly achieve some features). Therefore, I only say that iKuai is the strongest “multi-dialing software router" (actually, OpenWrt's multi-dialing feature is also good, but I just feel its configuration logic is weird and awkward, not very pleasant to use).

It is very generous of iKuai to support so many features in the free version. Moreover, the online help documentation is very well written; anyone with a technical background can understand it at a glance. Finally, you can even open a support case when encountering problems, though the support might not be very timely. All in all, I have tried and switched between many systems, including DD-WRT, OpenWrt, and modified Merlin, and ultimately chose iKuai as the main egress router for my home data center.

iKuai has many other great features, which I will discuss separately in other articles.

View Related Categories · 3 Matches
📌 Content Structure Prompt:
This content is part of the following knowledge map, where you can view the complete content path: Blog Knowledge Map。
📎 Related Articles
Share this article
The blog content is original, please indicate the source when reposting! The RSS address of the blog is:https://blog.tangwudi.com/feed, welcome to subscribe; if needed, you can join theTelegram Groupto discuss questions together.
No Comments

Send Comment Edit Comment


				
|´・ω・)ノ
ヾ(≧∇≦*)ゝ
(☆ω☆)
(╯‵□′)╯︵┴─┴
 ̄﹃ ̄
(/ω\)
∠( ᐛ 」∠)_
(๑•̀ㅁ•́ฅ)
→_→
୧(๑•̀⌄•́๑)૭
٩(ˊᗜˋ*)و
(ノ°ο°)ノ
(´இ皿இ`)
⌇●﹏●⌇
(ฅ´ω`ฅ)
(╯°A°)╯︵○○○
φ( ̄∇ ̄o)
ヾ(´・ ・`。)ノ"
( ง ᵒ̌皿ᵒ̌)ง⁼³₌₃
(ó﹏ò。)
Σ(っ °Д °;)っ
( ,,´・ω・)ノ"(´っω・`。)
╮(╯▽╰)╭
o(*////▽////*)q
>﹏<
( ๑´•ω•) "(ㆆᴗ
😂
😀
😅
😊
🙂
🙃
😌
😍
😘
😜
😝
😏
😒
🙄
😳
😡
😔
😫
😱
😭
💩
👻
🙌
🖕
👍
👫
👬
👭
🌚
🌝
🙈
💊
😶
🙏
🍦
🍉
😣
Source: github.com/k4yt3x/flowerhd
Kaomoji
Emoji
Little Dinosaur
Flower!
Previous
Next
       

👋 Welcome to “Wudi's Personal Blog”

Here, long-term exploration is mainly carried out around the following directions:

🧱 Personal Digital Infrastructure and Blog System Construction
☁️ Cloudflare and Network Architecture Practice
🧠 AI and Knowledge System Exploration
🛡️ Network Security and Access Optimization
🎵 Music and Sound Cognition
👁️ Cognitive Perspectives and Worldviews