Configure WireGuard to connect via IPv6 in your subnet
Configure WireGuard to connect via IPv6 in your subnet
I received a /64 IPv6 network for my project, requiring unique IPv6 and IPv4 addresses for each user. Using a large IPv6 subnet will quickly become costly, especially since you have many IPs to manage. At your current rate, obtaining enough IPs will become expensive fast.
So I set up my own Discord community focused on tech, coding, games, and computers. We’re launching a side project named Oxygen—a free VPN service available upon request, using WireGuard to connect anyone who signs up. My COO will receive a dedicated IPv6 address, and each week we’ll host the server on an 8GB DDR4 VPS in Germany. There’s no concern about IP costs because IPv6 is inexpensive, and I’ve secured a massive subnet with 18 trillion possible addresses at no extra charge.
I’m here to help without sounding confrontational. It seems there’s some confusion about your goals regarding IPv6 and IPv4. Many internet services still depend on IPv4 addresses, and forcing IPv6 can create significant challenges. Most networks and ISPs require IPv4 connectivity, and many don’t offer IPv6 support. You’d need a workaround like tunneling, but that’s only feasible if your provider allows it. If you’re aiming for a cost-effective VPN, it’s unlikely to work as intended due to scaling issues. Let me know how you’d like to proceed.
Hello, I already have the answer. Since I don’t have an IPv6 address at home, I couldn’t connect to my VPN.