Preface

As shown in the image above, with the deep implementation of the "Cyberpower" strategy, major domestic operators have been racking their brains over the past two years to reclaim public IPv4 addresses. Taking Chengdu Telecom as an example: as long as you change your plan, even if you are upgrading your plan, your original public IPv4 address may be gone. You should know that in the past, keeping the old configuration during an upgrade was an unwritten rule of the highest order, as well as selling public IPv4 address plans at high prices (Chengdu Telecom requires at least a 399 plan plus a 100 yuan service fee). Home broadband with public IPv4 will only become scarcer, though public IPv6 addresses are indeed becoming more and more common~.
However, IPv6 and IPv4 are different after all. Even if the operator issues an IPv6 address, if the router does not support it or is not configured correctly despite supporting it, you still cannot enjoy this hidden benefit. Therefore, I will take the iKuai soft router I use as an example to introduce the relevant configuration of IPv6. However, since different router brands support different IPv6 features, the specific configuration needs to be adjusted according to your actual equipment. I can only provide an example here.
In addition, the premise of the following text is that the broadband operator you use has successfully deployed IPv6 and correctly pushed the policy to the optical modem. This is actually quite easy to test. Just connect your computer directly to the optical modem for PPPoE dial-up, and then check if you obtain an IPv6 address. Additionally, you can also verify this with your operator. It cannot be ruled out that optical modem configuration issues prevent obtaining an IPv6 address. I won't go into too much detail here, otherwise there would be too many possibilities.
Prerequisites: Differences in public address allocation methods between IPv4 and IPv6
In essence, it is the difference between "one" and "a bunch":
IPv4
When operators allocate IPv4 public addresses, they only need to allocate one IPv4 public address to a user's optical modem (routing mode) or the router's WAN port (bridging mode), usually via PPPoE. Then, all data destined for this IPv4 public address is simply sent to the user's device.
IPv6
When operators allocate IPv6 public addresses, they allocate a relatively large network segment to the user. Well, saying "a relatively large network segment" is a bit conservative. Take my home Telecom IPv6 address allocation as an example:

As shown in the figure above, Telecom allocates a /60 prefix. However, because IPv6 requires that the subnet in all public addresses (Global Unicast Addresses) must have a /64 prefix, the IPv6 address segment of the LAN1 port is actually just one chosen from the 16 available /64 prefix network segments (usually the first one). Nevertheless, in an environment with multiple LAN ports, iKuai can further subdivide the /60 prefix network segment and assign them to different LAN ports:

This feature is actually DHCPv6-PD, which is very useful for environments that require hierarchical deployment of IPv6 public addresses.
Note 1: iKuai also supports multi-line IPv6 functionality:

However, this feature is paid. I specifically bought a 1-month dual-line subscription to play around with it, but found it wasn't very useful for me because it also requires a multi-LAN environment: that is, one IPv6 line can be bound to one LAN port. For home users, there is no such need for isolation, unless you are like I used to be, setting up multiple LAN segments and using a Huawei S5720-28P Layer 3 switch as a home core switch for over two years. But later, because I really couldn't stand the noise, I optimized it back to a single LAN segment and used TP-LINK's TL-SG2024D as the core switch, and the world instantly became quiet... The conclusion is that the physical topology of a home network should not be made too complex.
Note 2:
Without IPv4 public addresses, and with the popularization of 1000M downstream and IPv6 public addresses, multi-dialing technology, which previously aimed to expand upstream and downstream bandwidth and obtain multiple IPv4 public addresses, will completely exit the stage of history. Traditional port mapping is only suitable for scenarios like IPv4 public address -> IPv4 private address. Port forwarding technology will become a technology to replace traditional port mapping in certain special scenarios (such as in an intranet, router interface IPv6 public address -> other intranet device IPv6 public address, or router interface IPv6 public address -> other intranet device IPv4 private address). Unfortunately, iKuai does not currently support IPv6 port forwarding, and OpenWrt wins here: it can be indirectly achieved by installing software like socat or lucky, though this comparison is a bit unfair since it is not a built-in feature of OpenWrt either...
Note 3:
A network segment with a /60 prefix can be divided in the following ways: 1 /60 segment; 2 /61 segments; 4 /62 segments; 8 /63 segments; 16 /64 segments. This is because 64-60=4, and 2^4=16. It's enough to just have a general concept of this. The specifics of IPv6 are too complex and a pain to think about. Fortunately, when I was working on networking, it was just IPv4... However, when I was working on application delivery, I did not escape the wave of IPv6 transformation in the financial industry around 2020. All kinds of strange problems also gave me a real headache...
Returning to the question above, why did I say that allocating a "large network segment" is a conservative statement? How large is this network segment? Taking the /64 prefix as an example, what does 2^64 equal? I don't even know how to read that number. So the claim that IPv6 can assign a public address to every grain of sand in the world is really no joke. A /64 is just what is allocated to a household. Unfortunately, I don't even have 100 devices that can obtain an IPv6 public address, what a waste.
Enabling IPv6 on iKuai
The IPv6-related settings of iKuai are located under "Network Settings" - "IPv6":

Just follow these steps:
WAN Configuration
In "IPv6 Settings" -> "WAN Configuration", click "Add" in the red box on the right:

After selecting the "WAN Interface", keep the "Access Method" and "Request Prefix Length" at their default values, and then click "Save" in the red box below:

Normally (if the operator has already configured the relevant environment), the WAN interface should already be able to obtain an IPv6 public address:

LAN Configuration
In "IPv6 Settings" -> "LAN Configuration", click "Add" in the red box on the right:

Select the LAN port that needs an IPv6 address (in a normal environment, there is only one LAN port) and the WAN line to be bound (the WAN port I selected earlier was adsl3, so I select that here as well). Keep everything else at default, and finally click "Save" in the red box below:

Normally, the LAN interface should have already obtained an IPv6 public address:

At the same time, you can check on devices in the LAN that have IPv6 enabled to confirm whether they have successfully obtained a public address, such as my MacBook:

My Win11 virtual machine:

Other IPv6 features of iKuai
iKuai's IPv6 also supports separate statistics for IPv6 line data:

Static prefix allocation:

DHCPv6 blacklist and whitelist:

View DHCPv6 clients:

View neighbor list:

The statistical functions are still very powerful.
Built-in dynamic domain name client
Actually, even if you have an IPv6 public address, you might feel a bit embarrassed to share it directly with others for access. Why? Please imagine the following scenario (Note: the final 12345 is the port number):

The sight is simply too beautiful to behold. Therefore, an IPv6 public address must be combined with a dynamic domain name (DDNS) to be accessed normally. Of course, the premise is that the person accessing it also has an IPv6 address.
iKuai's built-in dynamic domain name client is very powerful. In addition to supporting multiple domain name providers:

It also supports the selection of multiple resolution methods:

WAN line means resolving to the IPv6 address of the WAN port; Client MAC means the IPv6 address of the device corresponding to a certain internal MAC address; Client DUID is the DHCP Unique Identifier in the previous DHCPv6 client interface:

The complete dynamic domain name interface is as follows, taking my Cloudflare domain as an example:

Let's look at some of my domain name resolutions:

To be honest, in my triple-dialing environment, I wouldn't know what to do without iKuai's dynamic domain name client. So iKuai is definitely one of the core components of my home data center.
In addition, iKuai's IPv6-related help is also easy to understand, with many examples. This is something I have always praised. It reminds me of the old NetScreen firewalls, whose help documentation was really well done; even someone who didn't understand could follow the help manual step-by-step.
P.S.: Actually, if you have a registered domain name (ICP filing), using a domestic CDN provider paired with an IPv6 public address to build a website is the most cost-effective way. I will write a dedicated article about this when I have the chance in the future.
Summary
In fact, iKuai's IPv6 configuration logic is very clear and easy to understand. Crucially, some of its peripheral features are also well done, especially the dynamic domain name section, which is absolutely my favorite. I rely on it to complete dynamic domain name resolution for Cloudflare, Tencent Cloud, and Alibaba Cloud. Crucially, the stability of the free version is also strong, and it has never crashed, even when running virtual machines in the past. Not to mention features like packet capture, port mirroring, UDPXY, authentication and billing, VPN, behavior management, traffic control, and so on. There are too many to list. Except for not supporting proxy-related features, I personally think it is already perfect.
There are also many other devices that now support IPv6 features, such as my ASUS AC86U:

It still has the features it should have, focusing on simplicity. Many years ago, I also used an ASUS router to run IPv6 for a period of time, because at that time, other routers did not support IPv6 well, and ASUS was the only one standing out (the concept of soft routers had not yet emerged back then).
In short, everyone should check based on their existing devices first. Reusing old equipment is always the priority, unless it really doesn't work, then consider replacing the device.