Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
25% Recurring Discount on NVMe VPS
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
Shells Virtual Desktop

Categories

In this Discussion

Home › Help
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

How to setup IPv6 properly on Virtualizor and create Windows KVM iPv6 only VPS

SherlockSherlock Member
in Help

That's the question. I'm not sure if that's even possible. If there's something better than virtualizor for this, I'm all ears.

Comments

  • JgalaJgala Member

    You will require to manually assign ipv6 in Windows from VNC/RDP .

  • seriesnseriesn Member

    @Sherlock said:
    That's the question. I'm not sure if that's even possible.

    Hi. What makes you say that?

  • SherlockSherlock Member

    @Jgala said:
    You will require to manually assign ipv6 in Windows from VNC/RDP .

    @seriesn said:

    @Sherlock said:
    That's the question. I'm not sure if that's even possible.

    Hi. What makes you say that?

    I was able to do it, plus did a lot of testing of NAT64 and DNS64. Had to use Hyper-V. It made it really easy. Virtualizor had me all lost.

  • seriesnseriesn Member

    @Sherlock said:

    @Jgala said:
    You will require to manually assign ipv6 in Windows from VNC/RDP .

    @seriesn said:

    @Sherlock said:
    That's the question. I'm not sure if that's even possible.

    Hi. What makes you say that?

    I was able to do it, plus did a lot of testing of NAT64 and DNS64. Had to use Hyper-V. It made it really easy. Virtualizor had me all lost.

    Were you doing ipv6 only?

  • SherlockSherlock Member

    @seriesn said:

    @Sherlock said:

    @Jgala said:
    You will require to manually assign ipv6 in Windows from VNC/RDP .

    @seriesn said:

    @Sherlock said:
    That's the question. I'm not sure if that's even possible.

    Hi. What makes you say that?

    I was able to do it, plus did a lot of testing of NAT64 and DNS64. Had to use Hyper-V. It made it really easy. Virtualizor had me all lost.

    Were you doing ipv6 only?

    Yeah, it was fun. From XP generation to 2019, tested on all.

  • seriesnseriesn Member

    @Sherlock said:

    @seriesn said:

    @Sherlock said:

    @Jgala said:
    You will require to manually assign ipv6 in Windows from VNC/RDP .

    @seriesn said:

    @Sherlock said:
    That's the question. I'm not sure if that's even possible.

    Hi. What makes you say that?

    I was able to do it, plus did a lot of testing of NAT64 and DNS64. Had to use Hyper-V. It made it really easy. Virtualizor had me all lost.

    Were you doing ipv6 only?

    Yeah, it was fun. From XP generation to 2019, tested on all.

    Virtualizor handles ipv6 a bit differently. You will essentially need to manually assign atleast 1 ipv6 via the panel. Maybe NAT ?

  • JgalaJgala Member

    Hi,

    @Sherlock

    After assinging ipv6 from panel , did you require to configure anything special anywhere to get it working on your vps ?
    Except adding it manually from vnc .

  • SherlockSherlock Member

    @Jgala said:
    Hi,

    @Sherlock

    After assinging ipv6 from panel , did you require to configure anything special anywhere to get it working on your vps ?
    Except adding it manually from vnc .

    I guess so because when I did it with virtualizor, it didn't straight away work after adding it to the vm from vnc.

    With hyper-v, it worked as soon as the vm booted, no other work needed.

Sign In or Register to comment.