Include IPv6 for no extra cost on every plan in every location to get delisted.
OSes have supported IPv6 for over two decades now (hell, I ran experimental IPv6 on Solaris 8 and NT 4). There's no reason to not support IPv6 these days, and my routing tends to be better to most datacenters over IPv6 so I do not consider any provider that won't even toss in a single address.
As a provider, you can get large swaths of IPv6 cheaply. Like swaths bigger than the entire number of addresses in IPv4 (including the huge amount that will never be allocated).
And surely you can find a way to get it routed even if your hosting facility isn't providing you the address space. There are a number of solutions out there that a clueful administrator should be able to figure out with a weekend of poking around.
So yeah. It's now effectively 2023. If a provider can't figure out how to do what I was doing in 1998, 25 years ago, I can't trust them to have any of the other knowledge I have picked up in that time. So I can't really trust them with any of my projects, basically.
(There are very special cases, of course. But those also tend to be "I don't want to be associated with this" anyhow...)
Include IPv6 for no extra cost on every plan in every location to get delisted.
OSes have supported IPv6 for over two decades now (hell, I ran experimental IPv6 on Solaris 8 and NT 4). There's no reason to not support IPv6 these days, and my routing tends to be better to most datacenters over IPv6 so I do not consider any provider that won't even toss in a single address.
As a provider, you can get large swaths of IPv6 cheaply. Like swaths bigger than the entire number of addresses in IPv4 (including the huge amount that will never be allocated).
And surely you can find a way to get it routed even if your hosting facility isn't providing you the address space. There are a number of solutions out there that a clueful administrator should be able to figure out with a weekend of poking around.
So yeah. It's now effectively 2023. If a provider can't figure out how to do what I was doing in 1998, 25 years ago, I can't trust them to have any of the other knowledge I have picked up in that time. So I can't really trust them with any of my projects, basically.
(There are very special cases, of course. But those also tend to be "I don't want to be associated with this" anyhow...)
You make it sound much easier than it really is. When your upstream provider who manages the network does not support this, there is not a whole lot you can do. The largest provider supported by LEB/LET doesn't even offer IPv6 in the same exact locations. They must be trash also?
@cloudserver said:
You make it sound much easier than it really is. When your upstream provider who manages the network does not support this, there is not a whole lot you can do.
Quit the crappy upstream and switch to a more reputable upstream.
I hear Clouvider and Nexril and DataIdeas are awesome.
The largest provider supported by LEB/LET doesn't even offer IPv6 in the same exact locations. They must be trash also?
Include IPv6 for no extra cost on every plan in every location to get delisted.
OSes have supported IPv6 for over two decades now (hell, I ran experimental IPv6 on Solaris 8 and NT 4). There's no reason to not support IPv6 these days, and my routing tends to be better to most datacenters over IPv6 so I do not consider any provider that won't even toss in a single address.
As a provider, you can get large swaths of IPv6 cheaply. Like swaths bigger than the entire number of addresses in IPv4 (including the huge amount that will never be allocated).
And surely you can find a way to get it routed even if your hosting facility isn't providing you the address space. There are a number of solutions out there that a clueful administrator should be able to figure out with a weekend of poking around.
So yeah. It's now effectively 2023. If a provider can't figure out how to do what I was doing in 1998, 25 years ago, I can't trust them to have any of the other knowledge I have picked up in that time. So I can't really trust them with any of my projects, basically.
(There are very special cases, of course. But those also tend to be "I don't want to be associated with this" anyhow...)
You make it sound much easier than it really is. When your upstream provider who manages the network does not support this, there is not a whole lot you can do. The largest provider supported by LEB/LET doesn't even offer IPv6 in the same exact locations. They must be trash also?
I have configured IPv6 routing for non-v6-native sites personally and professionally for the past 15-20 years. There are a good half dozen options, some easier than others.
It's not "easy", but at the same time it's something that someone with working knowledge of BGP and similar technologies should be able to get semi-production-ready within a few weeks of background tasks.
At a worst case, one can tunnel a /48 over a v4 point-to-point link from outside the datacenter to the inside and then distribute from that to customers (and then announce natively in the future with nothing more than a burp in the traffic). Surely your upstream provider doesn't run all your own network's routing equipment for you?
And if you speak of the largest provider I think you are, I tend to avoid them like plague. Just because they're big doesn't mean they're clueful.
I am not sure why you are here bashing the products we offer. I have never done anything to offend you, frankly I am not even sure who you are.
We work hard to offer what we offer and if you do not like what we offer you can just move on and not try it, we do not fit everyone's needs. You coming here to try and tell me how "bad" we are because we do not offer IPv6 is irrelevant and uncalled for and a waste of both our time.
Comments
OSes have supported IPv6 for over two decades now (hell, I ran experimental IPv6 on Solaris 8 and NT 4). There's no reason to not support IPv6 these days, and my routing tends to be better to most datacenters over IPv6 so I do not consider any provider that won't even toss in a single address.
As a provider, you can get large swaths of IPv6 cheaply. Like swaths bigger than the entire number of addresses in IPv4 (including the huge amount that will never be allocated).
And surely you can find a way to get it routed even if your hosting facility isn't providing you the address space. There are a number of solutions out there that a clueful administrator should be able to figure out with a weekend of poking around.
So yeah. It's now effectively 2023. If a provider can't figure out how to do what I was doing in 1998, 25 years ago, I can't trust them to have any of the other knowledge I have picked up in that time. So I can't really trust them with any of my projects, basically.
(There are very special cases, of course. But those also tend to be "I don't want to be associated with this" anyhow...)
Yes, please open a ticket if you still dont see it, we just did update our OS list.
You make it sound much easier than it really is. When your upstream provider who manages the network does not support this, there is not a whole lot you can do. The largest provider supported by LEB/LET doesn't even offer IPv6 in the same exact locations. They must be trash also?
Quit the crappy upstream and switch to a more reputable upstream.
I hear Clouvider and Nexril and DataIdeas are awesome.
Yes, the purple provider is trash.
CloudServerRocks!
invoice Number:4188
Order Number: 6954489235
I have configured IPv6 routing for non-v6-native sites personally and professionally for the past 15-20 years. There are a good half dozen options, some easier than others.
It's not "easy", but at the same time it's something that someone with working knowledge of BGP and similar technologies should be able to get semi-production-ready within a few weeks of background tasks.
At a worst case, one can tunnel a /48 over a v4 point-to-point link from outside the datacenter to the inside and then distribute from that to customers (and then announce natively in the future with nothing more than a burp in the traffic). Surely your upstream provider doesn't run all your own network's routing equipment for you?
And if you speak of the largest provider I think you are, I tend to avoid them like plague. Just because they're big doesn't mean they're clueful.
CloudServerRocks!
invoice Number:4188
Order Number: 6954489235
please add my credit.
Order Number: 3726175218
CloudServerRocks
CloudServerRocks
my Invoice #4230
Order Number: 1649180654
please add my credit
CloudServerRocks
Order Number 9681093275
Ticket #235232
Thank you! Fast and smooth!
is there any news about the 2g ram
Is 10$/year eligible to get 25$ free credit ?
@yoursunny @lewellyn
I am not sure why you are here bashing the products we offer. I have never done anything to offend you, frankly I am not even sure who you are.
We work hard to offer what we offer and if you do not like what we offer you can just move on and not try it, we do not fit everyone's needs. You coming here to try and tell me how "bad" we are because we do not offer IPv6 is irrelevant and uncalled for and a waste of both our time.
The product you bought does not qualify for the credit, it has to be a product offered on this thread.
You have to make payment to receive a credit, also make sure its a product listed in this thread as OP
Thank you for the order, looks like Tyler added your credit, we appreciate your business!
It is not, only the products from the OP
In my case it looks like this ((

Order Number: 2076939582
Ticket:#283947