Howdy, Stranger!

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


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
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
Shells Virtual Desktop
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.

IPV6 Addresse(s) /64

2»

Comments

  • farsighterfarsighter Member
    edited May 2025

    @Motion3549 said:

    @unsafetypin said:

    @tentor said:

    @lirrr said:
    the gold medal for me is the provider with routed ipv6

    Routed /56 IPv6 provided is even better

    Routed /48 IPv6 provided is even better better...looking at you @Clouvider and @Francisco you're real ones for that

    Why do providers still offer /64 prefixes but not route them?

    Lowend providers don’t like giving it because it adds complexity such as bloating their routing table with additional entries (which can strain their network infrastructure when accumulated) and increasing support requests from users who don’t fully understand how to implement routing correctly and end up complaining..

    While it’s not technically difficult for them to provide, the added burden often isn’t justified by the (sometimes very) low price you’re paying. However some providers may still give it upon a polite request.

    Thanked by 2Motion3549 Alyx
  • yoursunnyyoursunny Member, IPv6 Advocate

    We just lost IPv4 connectivity in the house.
    Something is wrong with the ISP.

    Google, Facebook, and the green forums seem to be fully working on IPv6 only.
    Twitter, Reddit, and Discord are unreachable.

    Thanked by 2nghialele xms
  • @yoursunny said:
    We just lost IPv4 connectivity in the house.
    Something is wrong with the ISP.

    Google, Facebook, and the green forums seem to be fully working on IPv6 only.
    Twitter, Reddit, and Discord are unreachable.

    Dang, i had the opposite situation.

    I've just changed the ISP provided router to my new Grandstream one, now I lose my ipv6 connections :/

    Not to mention 3 days ago a strong wind break their fiber optic cable to my home .....

  • @juniorrrrr said:

    Does this mean if I were to virtualize this vps, I would have 64 ipv6 addresses assigned or available? Would they be free?

    The /64 IPv6 block means you’re being assigned a full IPv6 subnet with 2^64 (18 quintillion) addresses — not just 64 individual IPs.

    I'm looking at virtualizor to create VPSs. Will I be able to add the /64 as a IPV6 pool and they will then be assigned to the VPS where SSH into it would work?

  • @Carlin0 said:
    @russromei and would you work for a hosting provider ? :lol:

    yeah, me

  • @russromei said:
    I see a vps that says:
    IPV4 Addresse 1
    IPV6 Addresse(s) /64

    Does this mean if I were to virtualize this vps, I would have 64 ipv6 addresses assigned or available? Would they be free?

    It means you get a full /64 IPv6 subnet, so you can assign as many IPv6 addresses as you want. And yes, they're usually free.

  • @farsighter said:

    @Motion3549 said:

    @unsafetypin said:

    @tentor said:

    @lirrr said:
    the gold medal for me is the provider with routed ipv6

    Routed /56 IPv6 provided is even better

    Routed /48 IPv6 provided is even better better...looking at you @Clouvider and @Francisco you're real ones for that

    Why do providers still offer /64 prefixes but not route them?

    Lowend providers don’t like giving it because it adds complexity such as bloating their routing table with additional entries (which can strain their network infrastructure when accumulated) and increasing support requests from users who don’t fully understand how to implement routing correctly and end up complaining..

    While it’s not technically difficult for them to provide, the added burden often isn’t justified by the (sometimes very) low price you’re paying. However some providers may still give it upon a polite request.

    I once consulted some physical server providers whether they could route large ipv6 subnets such as /32 to a smaller /64 or /126 subnet on their upper-level routers, and then I could implement the ipv6 route block function mentioned in virtfusion. Thus, vm products with route ipv6 are provided for customers. However, if the number of VMS is very large, it will obviously increase the structural complexity of the upstream routers of the provider, and I cannot adjust these routes at any time by myself. So is it possible to set up a router virtual machine (using vyos/pfsense,ros) on the physical server when there is a large subnet (/32) and a small subnet (/64) on the physical server, and let this virtual router take over the ipv6 allocation and routing of other VMS? In this way, I can achieve the same requirement without relying on suppliers to adjust their upstream routers

  • @greenhost_cloud said:

    @russromei said:
    I see a vps that says:
    IPV4 Addresse 1
    IPV6 Addresse(s) /64

    Does this mean if I were to virtualize this vps, I would have 64 ipv6 addresses assigned or available? Would they be free?

    It means you get a full /64 IPv6 subnet, so you can assign as many IPv6 addresses as you want. And yes, they're usually free.

    thank you for the definitive an succinct response

Sign In or Register to comment.