Thank you for sharing; we have a number of SoftLayer servers running CentOS 5.

We also work with small hosting providers (some of which are on SoftLayer); and the automation systems they use don’t work with IPv6.

My fear is that small businesses who cannot financially afford what is necessary to be on IPv6 will be forced to it when they are not ready… and then be forced out of business.

While I do believe IPv6 is the end goal; I hope those carrying the ball don’t squash the small businesses who are not in a position to keep up.

Of note, while I and our clients — like you — knew about IPv6… for hosting providers, there currently is no complete solution that I’m aware that supports IPv6.

So even having advance notice isn’t enough if the tools and systems used by the small business providers et all aren’t up to speed.

Thank you.

Not just that. CentOS 5 has issues with SPI on IPv6, rendering the firewall pretty much useless.
I really recommend everybody who has IPv6 but hasn’t given it a second thought to go through their scripts and configs and ensure they work when the default route changes to IPv6.

I’ve been battling my firewall over outgoing TCP connections to google for the past few days. Finally ripping it out and stepping up the process of moving up to RHEL 6

And yes, I’m paying the price for having IPv6 and not taking enough action before it “went life” learn from my miss-fortune

A number of those hosting automation systems are not (I repeat are not) IPv6 ready or capable.