Protocol 41 denotes the IP protocol that carries an entire IPv6 packet inside an IPv4 packet header. Rather than using TCP or UDP, this encapsulation places the IPv6 datagram directly within the payload of an IPv4 packet so that two endpoints separated by an IPv4-only network can exchange native IPv6 traffic. In practice the mechanism is widely used to give hosts or routers IPv6 reachability when only IPv4 addressing is available on the physical network.

How it works

At each tunnel endpoint an encapsulation/decapsulation function wraps outbound IPv6 packets with an IPv4 header whose protocol field indicates the encapsulated payload is IPv6. The receiving endpoint removes the outer IPv4 header and forwards the original IPv6 packet into the IPv6 routing domain. Tunnels can be configured in several ways: manually configured static tunnels with a fixed peer address, or automatic modes that derive addressing or endpoints from the IPv4 configuration.

Typical uses and implementations

  • Providing IPv6 connectivity to individual hosts, home routers, or small networks when the ISP supplies only IPv4.
  • Supporting tunnel brokers and tunnel services offered by providers such as Hurricane Electric, which allow customers to use IPv6 over existing IPv4 links.
  • Underlying several named tunneling techniques and variants that reuse this encapsulation method (for example, the common ‘‘6in4’’ approach and automatic schemes).

Many tutorials and service descriptions refer to the protocol and setup details; one convenient reference is Protocol 41 reference.

Operational considerations and limitations

Because Protocol 41 is an IP protocol type rather than a TCP or UDP port, it does not traverse some network devices that only handle TCP/UDP sessions. In particular, NAT boxes and some firewalls may block or not properly translate protocol 41 traffic, preventing tunnels from being established across them. Another common operational issue is MTU: encapsulation adds header overhead, so tunnel endpoints often need to negotiate lower MTU values or use fragmentation strategies to avoid dropped packets.

  • Protocol 41 is a simple IP-in-IP encapsulation and should not be confused with GRE-based tunnels, which use a different protocol identifier and header format.
  • It is distinct from techniques that encapsulate IPv6 over UDP (used by NAT-friendly approaches) or from overlay or translation services that manipulate addresses instead of tunneling native IPv6 packets.

In summary, Protocol 41 provides a straightforward way to carry IPv6 packets across an IPv4 infrastructure. It remains a useful tool for transition and testing, but its reliance on non-TCP/UDP encapsulation and its sensitivity to NAT and MTU issues mean operators must plan endpoint configuration and network policies carefully.