nanog mailing list archives
Re: website in ipv6
From: Kenny Sallee <kenny.sallee () gmail com>
Date: Tue, 28 Jun 2011 11:09:04 -0700
I did this by creating a 6to4 tunnel to a relay provided by6in4, not 6to4. While HE do operate 6to4 relays, the brokered tunnel service is 6in4.
A very important distinction I didn't have clear in my head. To regurgitate some reading I just completed: both methods use v6 in v4 tunneling using ip proto 41 in the IPv4 protocol field. However, 6to4 derives the IPv4 tunnel destination of an IPv6 packet based on bits 17-48 of the IPv6 packet - which when converted, equals the 32 bit IPv4 destination. While 6in4 is statically configured IPv4 source and destination IP addresses on the Tunnel (gre) interface. In 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. Thanks for pointing out my mistake - it helped me learn some more! Later, Kenny
Current thread:
- website in ipv6 Deric Kwok (Jun 26)
- Re: website in ipv6 Justin M. Streiner (Jun 26)
- Re: website in ipv6 Mark Andrews (Jun 26)
- Re: website in ipv6 Mark Andrews (Jun 26)
- Re: website in ipv6 John Kemp (Jun 27)
- Re: website in ipv6 Mark Andrews (Jun 27)
- Re: website in ipv6 Mark Andrews (Jun 26)
- Re: website in ipv6 Kenny Sallee (Jun 27)
- Re: website in ipv6 Mark Andrews (Jun 27)
- Re: website in ipv6 Kenny Sallee (Jun 28)
- Re: website in ipv6 Deric Kwok (Jun 28)
- Re: website in ipv6 Mark Andrews (Jun 28)
- Re: website in ipv6 Jason Roysdon (Jun 28)
- Re: website in ipv6 Mark Andrews (Jun 27)