All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
How does IPv6 work?
Hello all,
I've raised a dispute with a provider regarding the IPv6 for a VPS. I'd like some opinion on this matter.
Background:
The VPS comes with a /64 block. I have been assigned 2406:3003:2001:1234::/64 (not actual address). The VPS has been automatically setup on 2406:3003:2001:1234::1
This is IPv6 setup in the /etc/network/interfaces file:
auto ens3
iface ens3 inet6 static
address 2406:3003:2001:1234::1/64
gateway fe80::1
dns-nameserver 2606:4700:4700::1111
dns-nameserver 2001:4860:4860::8888
All is well currently, then I setup the VPS on another address, which I am sure is included in the same subnet, 2406:3003:2001:1234::a
So I try setting the config like this:
auto ens3
iface ens3 inet6 static
address 2406:3003:2001:1234::a/64
gateway fe80::1
dns-nameserver 2606:4700:4700::1111
dns-nameserver 2001:4860:4860::8888
Didn't work. But the same practice worked for all my other servers.
The Support Ticket:
And so I opened a ticket with them stating;
Hello,
I believe that I have access to a /64 subnet, however, I can only use the address 2406:3003:2001:1234::1
Manually assigning any other address such as ::2 or ::a only results in the server being unreachable. On other providers, any address in the subnet given can be assigned. Is there any limitation here that I am not aware of?
Thank you.
To which they responded,
Hello,
This solution is largely stock, and uses Open vSwitch for this as designed at SolusVM 2. No other changes are done in this regard. It does make sense to me that you can't break a /64 into smaller subnets, as a /80 is not directly reachable from the outside Internet per international rules.
What international rules are they refering to? I understand that address blocks smaller than /64 are usually not allocated by providers, but I still don't understand why I am not able to use addresses that are evident to me as being present in the subnet I was given...
Comments
one of my servers didnt work ipv6 until i execute this as root:
sysctl -w net.ipv6.conf.all.disable_ipv6=0
then all the config done with tunnelbroker in a racknerd server worked, also added additional ipv6. maybe gateway is wrong? dont know, just wanted to share that command worked for me.
Maybe they use
2406:3003:2001:1234::1as nexthop? Also did you made traffic capture to analyse what happens on wire?I think @yoursunny is considered the IPv6 guru here (so I tagged him).
Our only experience with Solus 2 was a trial with unnamed provider in early 2021.
At that time, Solus 2 can only use the
xxxx::1address within a /64.It's impossible to utilize any other address in the subnet regardless of how you configure it.
If this is still the case today, our suggestion is to ask for a refund under "item not as described" reason code.
You can then switch to a provider that offers VirtFusion or Convoy control panel, which has good support for IPv6 subnets.
stick to good old ipv4.
I definitely agree with you.
Of course because you're too incompetent to know how to properly route an IPv6 subnet
What if you add as a second IP? Such as...
auto ens3
iface ens3 inet6 static
address 2406:3003:2001:1234::1/64
gateway fe80::1
dns-nameserver 2606:4700:4700::1111
dns-nameserver 2001:4860:4860::8888
iface ens3 inet6 static
address 2406:3003:2001:1234::a/64
I've tried adding another address like this, didn't work, still not reachable