unixfox/readme.md

Last active October 21, 2025 19:56

Star (40) You must be signed in to star a gist
Fork (8) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/unixfox/bb299ce4f862fad66ee2e6d9024bef98.js"></script>
Save unixfox/bb299ce4f862fad66ee2e6d9024bef98 to your computer and use it in GitHub Desktop.

How to get IPv4 connectivity on an IPv6 only VPS

Raw

Some hosting providers like scaleway allows to remove the IPv4 from the VPS in order to save 1€/month but doing this will result in losing connectivity to the "IPv4 world". Here is how to gain your access back to the "IPv4 world".

Setup the nameserver(s)

Note: You may choose multiple nameservers.

Note²: You may deploy your own DNS64 & NAT64 server on a separate server by following this tutorial (untested): https://packetpushers.net/nat64-setup-using-tayga/.

Choose a DNS64 public server that has its own NAT64 public service from this list:

Nameserver	Provider	Location	Quality of internet connectivity
2001:67c:2b0::4 & 2001:67c:2b0::6	trex.fi	Finland (Europe)	Good
2001:67c:27e4::64	go6lab.si	Slovenia (Europe)	Good
2001:67c:27e4::60	go6lab.si	Slovenia (Europe)	Medium

Add the nameserver(s) to your /etc/resolv.conf file or in the configuration file of your network manager. Search on your prefered search engine a tutorial on how to change the DNS servers of your Linux distribution.
If you don't want to bother with configuring your network manager then you may deny any access to the /etc/resolv.conf by using chattr +i /etc/resolv.conf after modifying the file.

Install clatd for adding real IPv4 connectivity for applications that works only in IPv4 (optional)

Note: This tutorial only works on Linux distributions that has systemd or Upstart as a service manager.

Note²: If you are using ArchLinux you don't need to follow the tutorial because there is a clatd package on AUR: https://aur.archlinux.org/packages/clatd-git/.

Install make, git, cpan/perl, gcc and tayga from your package manager (Debian/Ubuntu : sudo apt-get install -y make git gcc tayga perl).
Clone the clatd Github repository using: git clone https://github.com/toreanderson/clatd.git
Change your current directory to the new directory called clatd: cd clatd.
Install clatd using sudo make install.
Install the required perl dependencies for clatd: cpan Net::IP Socket6 IO::Socket::INET6 Net::DNS.
Start clatd with sudo systemctl start clatd (systemd) or initctl start clatd (upstart).
Check if you have IPv4 connectivity using curl: curl -4 google.com.

Troubleshooting if case the curl command doesn't work

Execute systemctl status clatd and check if it say: This system already has IPv4 connectivity; no need for a CLAT.
If that's the case then add ExecStartPre=/bin/sh -c "sleep 30s && ip route del 0/0" after [Service] in the /etc/systemd/system/clatd.service file (this only works on systemd). If that's not the case then try to change the DNS64 nameserver with another one from the list above then restart clatd (sudo systemctl restart clatd) and if it still doesn't work then you are out of luck because your hosting provider doesn't support the NAT64 protocol.
Reload systemd and restart clatd: sudo systemctl daemon-reload && sudo systemctl restart clatd.
Check if you have IPv4 connectivity: curl -4 google.com.

tonywangcn commented Feb 24, 2023 •

edited

Loading

Here there,

Thanks for your great tutorial first. I did what you said above, but still failed to the ip4 connectivity. Any ideas how to debug it? Thanks !
A startdust instance from scaleway

[root@v6instance ~]# systemctl status clatd
● clatd.service - 464XLAT CLAT daemon
     Loaded: loaded (/usr/lib/systemd/system/clatd.service; enabled; preset: disabled)
     Active: active (running) since Fri 2023-02-24 12:36:14 UTC; 1min 39s ago
       Docs: man:clatd(8)
    Process: 474 ExecStartPre=/bin/sh -c sleep 30s && ip route del 0/0 (code=exited, status=0/SUCCESS)
   Main PID: 568 (clatd)
      Tasks: 2 (limit: 1138)
     Memory: 24.8M
        CPU: 306ms
     CGroup: /system.slice/clatd.service
             ├─568 /usr/bin/perl -w /usr/sbin/clatd
             └─588 tayga --config /tmp/dTaM6rZ2Rd --nodetach

Feb 24 12:36:25 v6instance clatd[568]: Enabling Proxy-ND for 2001:bc8:1820:92:acfc:3c60:6378:0 on eth0
Feb 24 12:36:25 v6instance clatd[568]: Creating and configuring up CLAT device 'clat'
Feb 24 12:36:25 v6instance clatd[579]: Created persistent tun device clat
Feb 24 12:36:25 v6instance clatd[568]: Adding IPv4 default route via the CLAT
Feb 24 12:36:25 v6instance clatd[568]: Starting up TAYGA, using config file '/tmp/dTaM6rZ2Rd'
Feb 24 12:36:25 v6instance tayga[588]: starting TAYGA 0.9.2
Feb 24 12:36:25 v6instance tayga[588]: Using tun device clat with MTU 1500
Feb 24 12:36:25 v6instance tayga[588]: TAYGA's IPv4 address: 192.0.0.2
Feb 24 12:36:25 v6instance tayga[588]: TAYGA's IPv6 address: 2001:67c:2b0:db32:0:1:c000:2
Feb 24 12:36:25 v6instance tayga[588]: NAT64 prefix: 2001:67c:2b0:db32:0:1::/96
[root@v6instance ~]# curl -v -4 google.com
*   Trying 142.251.39.110:80...
^C
[root@v6instance ~]# curl -v google.com
*   Trying [2a00:1450:400e:802::200e]:80...
* Connected to google.com (2a00:1450:400e:802::200e) port 80 (#0)
> GET / HTTP/1.1
> Host: google.com
> User-Agent: curl/7.88.1
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Location: http://www.google.com/
< Content-Type: text/html; charset=UTF-8
< Date: Fri, 24 Feb 2023 12:38:16 GMT
< Expires: Sun, 26 Mar 2023 12:38:16 GMT
< Cache-Control: public, max-age=2592000
< Server: gws
< Content-Length: 219
< X-XSS-Protection: 0
< X-Frame-Options: SAMEORIGIN
< 
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
* Connection #0 to host google.com left intact
[root@v6instance ~]# cat /etc/resolv.conf
nameserver 2001:67c:2b0::4
nameserver 2001:67c:2b0::6
nameserver 2001:67c:27e4::64
nameserver 2001:67c:27e4::60
[root@v6instance ~]#

dokicro commented May 11, 2023

May I ask Why Google Public DNS64 is not on the list? https://developers.google.com/speed/public-dns/docs/dns64

Author

unixfox commented May 11, 2023

May I ask Why Google Public DNS64 is not on the list? https://developers.google.com/speed/public-dns/docs/dns64

Because it doesn't provide NAT64 connectivity, only the DNS resolution: https://en.wikipedia.org/wiki/NAT64

eenturk commented Aug 13, 2023

Thanks i was looking for something like this!

mla157 commented Jan 8, 2024

@tonywangcn - Do you figured it out?
I have the same issue ⌛

MizunaRei commented Jun 6, 2025

The NAT64 server functions as a proxy server, but we can also use another proxy server. For example, we can set up a WireGuard client to connect to an IPv4/IPv6 dual-stack WireGuard server on a VPS in the same data center. For a budget-friendly solution, Cloudflare WARP is an option. A free WARP account provides up to 20 Mbit/s. Since WARP can act as a SOCKS5 proxy server, it can be integrated into a proxy chain, which is particularly useful in restricted regions such as Iran and Russia. To do so, set up a sing-box server on an IPv6-only VPS and configure its outbound connection to use the listening port of the WARP SOCKS5 server on the local machine.