reply to ackistler
Re: AT&T IPv6 6to4 is broken BTW I thought it would be worthwhile to add that, for me:
I had 6to4 connectivity on Wednesday, May 30.
I didn't have 6to4 connectivity on Saturday, June 2.
I can't be certain about Thursday or Friday.
justbitsMore fiber than ATT can handlePremium
That matches my data. The 6to4 address (220.127.116.11) stopped responding to ping & traceroute on May 30th. IPv6 connectivity lost around the same timeframe.
There is no technical reason why they couldn't just enable a route for the closest BGP4 route. (he.net in Chicago!) I foresee this as a method of forcing IPv4 static IP customers to buy static IPv6 addresses (via 6rd) from AT&T.
[edit: corrected date]
said by justbits:I'm not in the midwest, but at work I have two AT&T business Internet connections. The primary Internet connection (fiber optic) routes 6to4 over the AT&T backbone from San Francisco to Los Angeles to Dallas where it is handed over to Hurricane Electric and their Dallas 6to4 relay (seems like a long way given that there are local HE.net gateways in San Jose and Fremont).
There is no technical reason why they couldn't just enable a route for the closest BGP4 route. (he.net in Chicago!)
Our backup Internet connection is DSL and it doesn't have a route to any 6to4 relay.
I do not know if 6to4 to an AT&T relay ever worked here. Whenever I speak to someone from AT&T (rarely) I always bring up the subject of IPv6 and the answer is always something evasive along the lines of "we working on it, we don't have any details to share at this point, we don't know when it will be available". If any of those AT&T technicians and account representatives had ever mentioned that AT&T was operating a 6to4 relay I would have certainly tried it out.
Got some spare cpu cycles ? Join Team Helix or Team Starfire!