All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Is possible (how) to setup IPv6-only accessible Windows RDP VPS when my ISP do not support IPv6?
Hello,
it may be funny question, but i will try to explain it.
i have server with Kimsufi/OVH. Such server has one IPv4 and IPv6 subnet. It would be good if i can setup virtualization and virtual servers (KVM maybe) with Windows Server on them. There are tutorials for this.
But problem is if/how i can setup them (Windows VPSs) without having IPv4s. To setup them so they have their own IPv6 and i can access them (via RDP) even my home ISP does not support IPv6 yet. I can buy an IPv6 Linux server to serve as a proxy (openVPN?), but found no simple tutorial where i will achieve that when i request IPv6 connection on my home computer, it will go to the proxy and proxy will connect IPv6 on my behalf and translate reply back to me via IPv4. Is there noob friendly tutorial?
Comments
Adding a VPN or IPv4/v6 gateway is only going to add latency to your desktop experience if you don't have native IPv6 yourself.
You mention KVM so assume the host will be Linux. If you only need to access RDP remotely, a far simpler approach might be to use iptables and nat a range of non standard RDP ports on the host system to 3389 on the internal IP addresses of your virtual servers. e.g.:
Then specify the external port in your RDP connections to the public IPv4 address.
One solution to this scenario is to use a free IPv6 tunnel broker service (see https://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers). You configure the tunnel from your computer to the remote service and they handle the IPv4 <--> IPv6 conversion.
I haven't personally configured a tunnel broker service on a VPS but I imagine it's feasible to configure your own tunnel on a VPS if you prefer that option.
NAT. You don't need ipv6 in this scenario - you just need to assign blocks of ports to each VPS and setup NAT rules.
Thx for nice advices, i assume Proxmox and such control panels does not include script that can setup NAT so i need to do it manually. I found interesting tutorial here https://www.ameir.net/blog/archives/55-running-proxmox-behind-a-single-ip-address.html . It is mentioning few iptables rules that will "forward" dedicated server IPv4 requests at certain port to the VPS being accessible via local non-public IP.
Though i am unsure if Windows RDP will work with just single port (RDP port) being "forwarded" from host to guest using NAT. If not work and anyone knows list of required Windows (2012) ports that have to be NAT"ed" please kindly share.
regarding IPv6, here are some interesting articles:
https://feeding.cloud.geek.nz/posts/ipv6-and-openvpn-on-linode/
https://www.lowendtalk.com/discussion/28237/ipv6-tunnel-broker-with-openvpn-on-openvz
My personal recommendation would be using a tunnel broker service like Hurricane Electric. They have guides for just about every OS and router under the sun. https://tunnelbroker.net/
RDP works with just a single port.
And there is always an option to use ssh port forwarding, just connect to host and forward rdp port to VM ip.