Skip to content
AdminKit

Teredo and 6to4

What is Teredo and 6to4?

Teredo (RFC 4380) and 6to4 (RFC 3056) are legacy IPv6 transition mechanisms that tunnel IPv6 packets inside IPv4 traffic, which can reach a device despite a firewall written with only IPv4 rules in mind. AdminKit's IPv6 firewall guide explains why a device needs its own IPv6-aware rules regardless.

By AdminKit team, Netbase JSC · Updated

Teredo (tracked on the IETF Datatracker as a Proposed Standard) and 6to4 are IPv6 transition mechanisms that tunnel IPv6 packets inside IPv4 traffic, letting a device reach the IPv6 internet even when its own network only provides IPv4 — Teredo encapsulates packets in UDP specifically so the tunnel can traverse most NAT devices, while 6to4 wraps them directly in IPv4 protocol 41 and expects a public IPv4 address at the tunnel endpoint. Both predate today’s widespread native dual-stack deployment of IPv6 alongside IPv4 and are now considered legacy: Microsoft disabled Teredo by default starting with Windows 10 — Microsoft’s own Windows Server networking documentation confirms “ISATAP and Teredo are disabled by default in Windows” — and RFC 7526 formally deprecated 6to4’s anycast relay infrastructure. The public Teredo service itself is gone: the Miredo project, an open-source Teredo implementation for Linux and BSD, notes that public Teredo servers were shut down without notice in June 2021, effectively ending the Teredo tunneling service. The practical risk is that a tunnel operating inside otherwise-allowed UDP or protocol-41 traffic can give a device an IPv6 address a firewall configured only with IPv4 rules in mind was never written to cover.

AdminKit groups teredo and 6to4 under its IP & network cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What do Teredo and 6to4 do?

Tunnel IPv6 packets inside IPv4 traffic, letting a device reach the IPv6 internet even when its own network only provides IPv4.

How does Teredo differ from 6to4 mechanically?

Teredo encapsulates packets in UDP specifically so the tunnel can traverse most NAT devices, while 6to4 wraps them directly in IPv4 protocol 41 and expects a public IPv4 address at the endpoint.

Are Teredo and 6to4 still recommended for new deployments?

No -- both are considered legacy; Microsoft disabled Teredo by default starting with Windows 10 (confirmed in Microsoft's own Windows Server IPv6 configuration documentation), and RFC 7526 formally deprecated 6to4's anycast relay infrastructure.

What is the security risk of these tunnels?

A tunnel operating inside otherwise-allowed UDP or protocol-41 traffic can give a device an IPv6 address that a firewall configured only with IPv4 rules was never written to cover.