Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

IPv6 brokenness?


Here's an example that affected me just a few days ago:

http://www.datacenterknowledge.com/archives/2009/10/22/peeri...

Basically, Hurricane Electric and Cogent (two major transit providers) are refusing to exchange IPv6 traffic. That breaks stuff. For me the problem manifested as a user facing a 20 second delay whenever he ssh'd in (over IPv4). (I'm on Hurricane Electric. The reverse DNS for his IPv4 address is served by Cogent DNS servers. Reverse DNS lookups were trying to access the Cogent name server over IPv6 and had to time out before IPv4 was tried.)

Other than that though, I actually haven't encountered very much IPv6 breakage.


Peering disputes are nothing new though. I was a Level 3 and Cogent customer, and suddenly my two servers couldn't talk anymore ...

Peering disputes are problematic for both IPv4 and IPv6. This has nothing at all to do with the IP version!

(p.s. You do realise that the article you linked to is from 2009 ...)


Has any IPv4 peering dispute lasted this long? (Yes, the article is from 2009. They're still locked in a dispute in 2012.)


No, mainly because it would be business suicide for whoever is involved. Especially if neither party is willing to pay for transit to the other... IPv6 is still small enough that it doesn't yet force one providers hand over the other.

That being said, if you are single homed on HE only then I would suggest you purchase transit elsewhere as well, or find a datacenter that has multiple transit providers. Being single home is dangerous.

The real question is going to be how long can Cogent hold-out. HE is willing to provide them free IPv6 peering, why not accept it so that their customers can get a full IPv6 table...


Presumably the failure of some to jump onto the IPv6 bandwagon? I guess we can expect IPv4 to stick around like IE6 for a while.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: