[aklug] Re: IPv6 via GCI

From: Shane R. Spencer <shane@bogomip.com>
Date: Fri Sep 09 2011 - 15:38:30 AKDT

Since I'm feeling generous about ATT and GCI peering.. I will also gladly procure a 6 to
50 foot cable of your choosing (Fiber SM/MM, Cat6, Coax, etc....) in place of my wireless
offer in order to plug router A into router Z at a shared facility.

- Shane

On 09/09/2011 03:35 PM, Shane R. Spencer wrote:
> I just got this going today. I've used Sixxs in the past and I'm happy to see they are
> still simple to work with.
>
> GCI is now routing my IPv6.. however.. I have to go to Seattle and back.
>
> I'd like to sarcastically thank whoever at ATT and/or GCI is keeping peering between them
> unavailable. It's the most sane thing anybody has ever done and the business reasons
> along prove that there is genius at play. I can see how this keeps people from..
> something.. I'm sure.. and capitalizes profit margins and reduces bottom lines and crap.
> Maybe somebody didn't win in a three legged race and now this is just tangled up in
> redonkulous bureaucracy. I dunno.. but I figured we could just make this happen.
>
> HOST: gw01 Loss% Snt Last Avg Best Wrst StDev
> 1. 12.17.188.001.Borealisbroadb 0.0% 10 4.6 8.5 2.8 29.7 8.5
> 2. wireless1.dtn.anc.borealisbr 0.0% 10 5.8 11.0 4.2 34.2 8.7
> 3. core.att.anc.borealisbroadba 0.0% 10 14.8 13.3 9.8 18.3 2.9
> 4. 12.119.146.61 0.0% 10 21.6 16.9 11.9 27.2 5.1
> 5. cr2.st6wa.ip.att.net 0.0% 10 40.4 43.8 39.9 47.8 3.1
> 6. 12.122.146.177 0.0% 10 73.2 46.3 38.1 73.2 10.9
> 7. 192.205.36.154 0.0% 10 44.4 46.3 37.8 65.9 8.1
> 8. ae-13-51.car3.Seattle1.Level 0.0% 10 70.8 49.3 39.0 70.8 9.8
> 9. GCI-COMMUNI.car3.Seattle1.Le 0.0% 10 51.4 48.8 42.9 59.7 6.1
> 10. 93-129-165-209.gci.net 0.0% 10 76.3 76.7 68.8 89.7 7.0
> 11. 144-129-165-209.gci.net 0.0% 10 82.9 79.7 69.1 96.4 9.6
> 12. 89-250-223-66.gci.net 0.0% 10 83.9 77.1 69.5 83.9 5.0
> 13. usanc01.sixxs.net 0.0% 10 73.0 75.0 70.3 83.9 4.1
>
> As for ACS/GCI. I will gladly donate a secure and reliable wireless backhaul that can
> operate at ~100mbps to you guys in order to make this happen. Hell.. I'll donate enough
> to make it 500mbps.
>
> Cheers,
>
> Shane
>
> On 09/01/2011 10:53 AM, Alan C. wrote:
>> No native support on the cable modem platform yet; if you set an Airport =
>> Express or some other device with automatic IPv6 configuration to tunnel =
>> mode it will build a tunnel to the tunnelbroker.net servers in Seattle.
>>
>> If you would like a tunnel in Anchorage there is a Sixxs tunnel server =
>> (http://www.sixxs.net) on GCI's network, which is how I'm currently =
>> accessing IPv6. Sixxs supports both network to network tunnels and =
>> dynamic tunnels.
>>
>> Another option you can us while waiting for your Sixxs account to be =
>> approved is http://www.tunnelbroker.net. Your tunnel will be terminated =
>> in Seattle but you can be online in minutes.
>>
>> -Alan
>>
>> On Sep 1, 2011, at 10:46 AM, Jim MacDonald wrote:
>>
>>> Anyone know if GCI is routing IPv6 yet? if so do you know what the =3D
>>> correct settings are to connect?
>>> =20
>>> Jim MacDonald
>>> jim@macdonald.org
>>> =20
>>> =20
>>> =20
>>> ---------
>>> To unsubscribe, send email to <aklug-request@aklug.org>
>>> with 'unsubscribe' in the message body.
>>> =20
>>
>> ---------
>> To unsubscribe, send email to <aklug-request@aklug.org>
>> with 'unsubscribe' in the message body.
>>
>

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Fri Sep 9 15:38:24 2011

This archive was generated by hypermail 2.1.8 : Fri Sep 09 2011 - 15:38:24 AKDT