|
|
|
|
|
by agsamek
1370 days ago
|
|
My story about ipv6 is from a travel. I connected to a friend's wifi. It worked for some time and then a strange thing happened. I was able to google but I was not able to connect to my company's services. I debugged the cause and it looked like the router received ipv6 address but not an ipv4. There was some tornado going around that might something to it. This was the first time I felt like being on the ipv6 network. I also wonder why I was not able to access to ipv4 servers, I assume that in India people have no problem accessing ipv4 only networks. Anyway - this was the first time I had to deal with ipv6 :) On the business side. One ipv4 costs us $3/mo. We never had any problem with this, didn't feel any business reason to upgrade and in particular we (as most of the companies) do not have any permanent test of ipv6 connectivity going on. So even if this had been setup at some point, we would never notice a regression here. So - unless our customers started asking for ipv6, government pushed some regulation or the address' prise would go up - I do not think we will do anything about ipv6, like most other companies. |
|
The $3 are an early warning signal. You can start upgrading slowly on the cheap when you have all the time in the world, or you can do it for much more money and higher risks come crunch time, when you "see a business reason."
I don't have an axe to grind with IPv6 in particular, but I wish managers who consistently make short-sighted management decisions when the writing is so obviously on the wall, would face unemployment.