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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Neither suits me, over.
@SpartanHost has proper IPv6 /64 subnet.
V.PS @xTom won't give /64 due to obscure reasons, so we classify them as an incompetent provider and do not use them.
???
https://lowendtalk.com/discussion/comment/3509986#Comment_3509986
https://lowendtalk.com/discussion/comment/3473908#Comment_3473908
It is also common practice for services to ban entire /64's on abuse, just saying... I'm not sure that's much of a valid justification, tbh. Yes, it's one of the side-effects of having too many IPs available, but has it been that bad in order to only offer one single address despite it being a bad practice?
Not that I wanna engage into arguments, but, huh?
So?
Assigning less than /64 means "we are clueless about IPv6".
Every good provider assigns IPv6 by /64 or /48, so that customers can use IPv6 services in the proper way.
Moreover, you cannot assume potential customers to be evil.
If you don't want to attract proxy services, you can disallow it in ToS, instead of breaking IPv6 for everyone.
So why do you say
do not use them?Any reason you must use a /64 IPv6 address? Where do you see we are
breaking IPv6 for everyone?Another reason we do not support /64 IPv6 is the control panel we use does not support that.
Customers can pay to get a /48 IPv6 for his VPS or dedicated servers, we already did that for some customers.
My apps are designed to require a separate IPv6 address in each container.
This is how IPv6 is designed to be used.
You are assigning less than /64, which breaks IPv6 for everyone.
I do not use any provider that assumes potential customers to be evil.
Switch to a different control panel that properly support routed IPv6.
Virtualizor works passably.
This is how IPv6 is designed to be used.
That makes sense, you can request to pay to get a dedicated /48 IPv6 and use it.
I'm afraid we can't change anything at this time.
Sorry to hear that babe.
There's no plan to switch to other control panel, but we are planning to build our own control panel and we will assign /64 IPv6 to each VPS.
When/if this happens, you would be taken off the incompetent list.
If you make it routed IPv6 subnet (every address can be used without NDP responder), you would be enlisted on the Hall of Fame.
Such a WHMCS move. This is not incompetence. This, my dear unit, this is impotence.
Control panel doesn't support /64.
/48 can be assigned to VPS, and the control panel suddenly supports it.
So, which control panel supports /48 but doesn't support /64?
Moreover, IPv6 PA space is practically free in RIPE region.
If your control panel truly only supports /48, you can just give a free /48 to each VPS.
It's manually assignment, which needs manual work.
The control panel doesn't support automatic assignment.
We do support BGP sessions in some regions, customers can bring his own IPv4 an IPv6 and use it in his VPS.
I've used three other providers that perform manual IPv6 assignments or filter adjustments: HostHatch, LevelOneServers, ServerFactory.
IPv6 assignment is free of charge despite the (little bit of) manual work.
We are not free, we have to pay our engineers salary.
Glad & Love my limewave vps
For only $7/month service They even give me /48 for free without complicated
V.PS is better than SpartanHost, V.PS uses CN2/AS9929 routing, Spartan only uses AS4837.
IPv6 is redundant and useless for Chinese users.
Not everyone needs /64, and not everyone runs Docker/Containers in a VPS.
I am very satisfied with the San Jose mini pro from V.PS.
IPv6 or GTFO
You should pay your developer salary to automate routed /64 assignment.
Then you don't need to pay engineers anymore.
LOL, China isn't what you THINK it is.