<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"> ... and it seems it is in fact <i>intentional</i>.
<br>
I opened a ticket with SixXS and the response was "check the
news". On their news page I then found a post (new as of an hour
ago) with more than a dozen reasons why we should "call your ISP
for IPv6", which SixXS has been saying for several months. <br>
<br>
I <i>have</i> IPv6 from my ISP. What I <i>don't</i> have is IPv6
in certain other places: behind a corporate IT NAT firewall (which
otherwise does allow outbound AYIYA/AICCU), Starbucks, John Glenn
Airport, my sister's house. (Where her ISP probably gives them
IPv6 but their router doesn't grok.) <br>
<br>
SixXS is actually dead. The web site still works. Any tunnels
presently active should remain active. But you can no longer sign
up for new service. You cannot request new tunnels or subnets. And
as of this week you cannot re-establish a tunnel if it is
interrupted (e.g., because you had to reboot or experienced an
IPv4 hiccup). <br>
<br>
SixXS really intrigues me. What is/was their motivation? I've
never been fond of end-of-life of either systems or software, but
the SixXS guys have <u>had EOL in view</u> from the beginning.
(Once everyone has native IPv6, why would you need a tunnel?) And
it's a <u>hobby project</u>. I get that. (But who engages in a
hobby with an end date? Is there a day when a painter will
intentionally quit painting?) And it's a <u>freebe</u>. (But
they've won awards and garnered reputation.) <br>
<br>
Gotta wonder if they switched their info/init server to loopback
just to see who complained, to find out if anyone cared. <br>
I've been played. <br>
<br>
-- R; <><<br>
<br>
<br>
<br>
<br>
<br>
</div>
</body>
</html>