@AsusMy, I'd like to suggest you and your team behind AsusWRT to consider supporting IPv6-only networks using your product(s). One of the reasons is, with many ISP's in Malaysia implementing CGNAT on WAN, it clearly shows that IPv4 is already exhausted and ISP's need to reserve as many IPv4 IP address as they can. This makes IPv4 scarce and rare and expensive to customers unlike before.
Welcome to IPv6. No NAT no nonsense just direct end-to-end communication as intended.
On your product(s), the key components to make this work are:-
1. NAT64
2. DNS64
3. CLAT (X464LAT)
#1 -- This is similar to IPv4 NAT44 but translate an IPv4 to IPv6 address using the given well-known or GUA /96 prefix.
#2 -- This resolves an IPv4-only domain to have a synthetic IPv6 address by translating it using the configured /96 prefix.
#3 -- This takes care of IPv4 literals in applications that still use legacy AF_INET.
All 3 components work hand in hand together for an IPv6-only network to work properly. With this in place, you can run IPv4-only applications on IPv6-only LAN.
If your team decides to take on this project/challenge, bare in mind you have to consider customer networks that have dynamic IPv6 Prefix Delegation assigned to them by their ISP.
Some references:
https://github.com/toreanderson/clatd
https://github.com/vitlabuda/tundra-nat64
http://www.litech.org/tayga/
https://sites.google.com/site/tmoipv6/464xlat
https://datatracker.ietf.org/doc/html/rfc6877
Cheers.
Home Networking ASUS Malaysia Networking User & Technical Support, Managed by ASUS Malaysia Representative
Jan 25 2023, 01:45 AM
Quote
0.0350sec
0.64
7 queries
GZIP Disabled