One-click forwarding to migrate your IPV6 segments.
Similar to https://tunnelbroker.net/ to build your own "Hurricane Electric Free IPv6 Tunnel Broker".
- Self-built IPv6 tunnel for sit/gre/ipip protocols
- Support to customize the IPV6 subnet size to be cut out, and the appropriate IPV6 subnet information in CIDR format will be calculated automatically.
- Automatically recognizes the IPV6 subnet size of the server side
- Will automatically set up the tunnel server and print the commands that the client needs to execute
- Setting up the IPV6 tunnel is easy to understand and easy to remove
| VPS(A) | VPS(B) |
|---|---|
| one IPV4 address (server_ipv4) | one IPV4 address (clinet_ipv4) |
| one IPV6 subnet | no IPV6 address |
| Hereafter referred to as server | Hereafter referred to as client |
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
Execute it
./6in4.sh <client_ipv4> <mode_type> <subnet_size>
Repeatable, split into multiple subnets, corresponding to different clients (servers), client_ipv4 is required, others are optional
Remember to replace client_ipv4 with the IPV4 address of the machine you want to attach IPV6 to, and the command you need to execute on the client side will be sent back to you after execution, see the instructions after execution for details.
| Options | Optional Option 1 | Optional Option 2 | Optional Option 3 |
|---|---|---|---|
| <mode_type> | gre | sit | ipip |
| Options | Optional Option 1 | Optional Option 2 | Optional Option 3 |
|---|---|---|---|
| <subnet_size> | 64 | 80 | 112 |
<mode_type> only support those three protocols for now, the more advanced the more recommended, no fill in the default is sit protocol
<subnet_size> As long as it is larger than the original system subnet mask, and is a multiple of 8, if the difference between the cut subnet and the original subnet size is greater than 2 to the 16th power, it will be automatically adjusted, if you do not fill in the default is 80.
During script execution, the execution path is automatically switched to /root.
To prevent forgetting to copy commands, the commands to be executed by the client itself will be written to the 6in4_client.log file under the current path, and the commands to be executed by the client can be queried using cat 6in4_client.log.
To prevent forgetting that the server tunnel disappears after reboot, the commands to be executed by the server itself will be written to the 6in4_server.log file under the current path, you can use cat 6in4_server.log to query the commands that need to be executed by the server to redeploy the tunnel after reboot.
Because some servers have default intranet IPV6 routes that conflict with the tunnel, you can use the following command to remove the default IPV6 routes.(The following commands should only be executed if you get an error when attaching and the attachment fails, otherwise do not execute the following commands lightly.)
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
This assumes that your client's server's default NIC is eth0, and you can use ip -6 route to see the default route and replace it, the default route starts with default via and uses dev to specify the default NIC, you just need to find it by following this rule.
The script is not compatible with multiple network interfaces by default, in case of no output after ipv6_gateway: appears in the execution log, you need to execute ip -6 route show to check the gateway address of ipv6 and then write it to the file /usr/local/bin/6in4_ipv6_gateway by yourself and then run the script again.
A practical example: oneclickvirt#2
systemctl status ndpresponder
ip addr show
ip addr show
curl ipv6.ip.sb
server
exclude
cat /root/6in4_server.log
You can view the name of the tunnel used, starting with server-ipv6-.
ip link set <name> down
ip tunnel del <name>
Just replace the <name> above with the name you looked up.
client
ip link set user-ipv6 down
ip tunnel del user-ipv6
See https://www.spiritlhl.net/en/guide/incus/incus_custom.html and https://ipv6tunnel.spiritlhl.top/ for more details