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
@wych: I'm crossing my fingers, toes, arms, legs, eyes, and nostrils
If you expected honesty it is your eyes that are crossed
I am not sure where in colo crossing stack they do not support ipv6 but i would think it would be import to replace providers that are not upgrading firmware or devices that support standards. If ipv6 was fully used there would be lots of use cases where your servers or vm's will use ipv6 for cluster communicatin and only ipv4 when talking to the outside world. i dont host anything in datacenters that dont support ipv6 unless its a ping node to stalk network routers.
You will probably crossing your arms on your chest before they run out of IPv4 and consider IPv6.
As I said a few times, in US there are plenty of IPv4 and the population is not growing, so, while, maybe, the prices will go up a bit that will be way less than in Asia or Europe, so no real incentives to support ipv6 and it will also complicate surveillance a bit, giving people a lot of space to create meshes and gateways hard to track to underground encrypted traffic.
BuyVM's soon has already been solved. so maybe CC ipv6 will be next solved
BuyVM tweaked their own kernel and template to be able to serve IPv6 flawlessly.
Erm what do you mean by that?
Not their own, but they tweak it so that it wouldn't be any conflict within the container.
The only kernel related things we did was get ip6tables to work better in 2.6.18. With 2.6.32 there hasn't been a lot of reasons to dink with the kernel.
Francisco
@Maounique there Fran has it answered
Ah, I thought they did something in their panel something like own OS.
Almost no one at all connects to my servers using IPv6, neither my 3G nor home internet support IPv6, often the rDNS can't be set for IPv6 or no IPv6 glue records are supported. -> I stopped bothering with IPv6 for now.
You are wrong. A good chunk of data on my cdn is being pulled from IPv6 at this point. They are dual stacks of course but it is getting used more and more.
No need to attack him Mun, he said:
Lots of sample size / opinion text, not definitives
.
lol
Amazing that this post is still relevant over four years later. My home ISP, phone provider, and employer all have native IPv6, as do all my VPSes except the ones hosted in ColoCrossing facilities (VirMach). This post is #1 in Google for "ColoCrossing IPv6"
HAHA, this is my favorite necro, not even mad!
Every single mobile carrier and home ISP here deploys native IPv6 (/56 minimum for home) here.
Got IPv6 as well... Native.
CC if you wanna bump your sales, just deploy IPv6.
I usually don't bump old threads... I made an exception for this one though, since it's special and "we'll do this before 2017" is a fun thing to read in 2019.
So vote with your money, don't buy services without IPv6. Seems simple enough.
666Colo666Crossing666.com
VirMach is legitimately a good provider though. Been using them for nearly two years, no issues. It's just unfortunate that they use ColoCrossing.
Sure, but in the end it shows that you don't really care that it doesn't have IPv6. Since you will still buy and use it even without. In turn that lets ColoCrossing continue to sell the dedis or whatnot to VirMach. And everything goes on IPv4-only for another 5 years, and so on. As it does, from the point of view of CC management, what's the issue?
Yeah, I'm going to migrate away from VirMach once my term is up (paid for one year) if they still don't offer IPv6.
https://blog.colocrossing.com/is-time-start-using-ipv6-data-center
My trailer park even has IPv6
Is CC a shitnado?
Francisco
Well, lets see then.
Oh.
@jbiloh after "beating" the 2017 estimate:
Nice victory.
Perhaps it's 2020:
https://www.lowendtalk.com/discussion/comment/705222/#Comment_705222