[142501] in North American Network Operators' Group
Re: website in ipv6
daemon@ATHENA.MIT.EDU (Deric Kwok)
Tue Jun 28 21:16:27 2011
In-Reply-To: <BANLkTikt-7aRAXBYzUk0ao9V5DBeKz-0eg@mail.gmail.com>
Date: Tue, 28 Jun 2011 21:15:20 -0400
From: Deric Kwok <deric.kwok2000@gmail.com>
To: Kenny Sallee <kenny.sallee@gmail.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Thank you all
Two questions:
If I get the HE as upstream to advertsie our ipv6,
1/ Do we still have www.tunnelbroker.net as tunneling connection?
2/ All the internet users can access our ipv6 website?
Thank you
On Tue, Jun 28, 2011 at 2:09 PM, Kenny Sallee <kenny.sallee@gmail.com> wrot=
e:
>>
>> > >
>> > I did this by creating a 6to4 tunnel to a relay provided by
>>
>> 6in4, not 6to4. =A0While HE do operate 6to4 relays, the brokered tunnel
>> service is 6in4.
>>
>
> A very important distinction I didn't have clear in my head. =A0To regurg=
itate
> some reading I just completed: both methods use v6 in v4 tunneling using =
ip
> proto 41 in the IPv4 protocol field. =A0However, 6to4 derives the IPv4 tu=
nnel
> destination of an IPv6 packet based on bits 17-48 of the IPv6 packet - wh=
ich
> when converted, equals the 32 bit IPv4 destination. =A0While 6in4 is
> statically configured IPv4 source and destination IP addresses on the Tun=
nel
> (gre) interface. =A0In Cisco world the config comes down to 'tunnel mode
> ipv6ip' vs 'tunnel mode ipv6ip 6to4' and a few other lines of config.
> Of course there are a lot more details then that searchable via google.
> =A0Thanks for pointing out my mistake - it helped me learn some more! =A0=
Later,
> Kenny
