• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1322
  • Last Modified:

ipv6 6to4 and 6in4

I am a bit confused between 6to4 and 6in4. From my understanding 6in4 is encapsulated IPv6 inside IPv4 header. That can be done manually from the routers. A few questions:
- Is 6to4 and 6in4 the same thing?
- For the tunnel broker, like he.net for example, is it 6in4 or 6to4? The tunnel broker is considered as IPv6 automatic transition technique.
- what is the RFC for 6to4? I know that 6in4 is 4213.

Thanks
0
leblanc
Asked:
leblanc
  • 3
  • 2
3 Solutions
 
giltjrCommented:
Here is the wikipedia entry for 6to4

en.wikipedia.org/wiki/6to4

It talks about a various RFC's and has links/reference at the end.  One is 6343.

It looks different from 6in4.
0
 
leblancAccountingAuthor Commented:
So it looks like they both encapsulate ipv6 in ipv4 header and they both require the tunnel configuration on the routers. Except for 6in4, you have "tunnel mode ipv6ip" and "tunnel mode ipv6ip 6to4" for 6to4. Here is my confusion. it says that 6in4 is a manual process and 6to4 is an automatic process. I don't see it as you have to manually configure your network devices with both techniques.

Also, why 6to4 is disabled by default in Windows 7?
0
 
giltjrCommented:
I have no clue why 6to4 is disabled in Windows V7.  

The major difference between 6to4 and 6in4 is how the IP V4 addresses are  derived.

6in4 uses a static mapping, where as 6to4 uses a mapping where the IPV4 address is derived from the IPV6 address.  So static is considered "manual" and the derived is "automatic."
0
 
leblancAccountingAuthor Commented:
from my understanding, the difference is with 6to4, you do not need to specify the tunnel destination address. It is self discovered by the source host.
0
 
leblancAccountingAuthor Commented:
do not need to specify the tunnel destination address is the main difference between 6in4 and 6to4
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now