Skip to content

[MT] Added info on Magic firewall ipv6 #22997

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 11, 2025
Merged

[MT] Added info on Magic firewall ipv6 #22997

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/magic-transit/how-to/ipv6.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Cloudflare transports IPv6 traffic over an IPv6-over-IPv4 GRE tunnel. Here is ho

- The IPv6 beta is not available for accounts with CNI links configured.
- MTU is 1420 bytes for egress traffic (does not impact Direct Server Return).
- Magic Firewall currently does not support IPv6.
- Magic Firewall supports two matching fields for IPv6 traffic: source IP address and destination IP address.
- Cloudflare supports the advertisement of IPv6 prefixes ranging from `/48` to `/32`.
- Limited to IPv4-based [tunnel health checks](/magic-transit/reference/tunnel-health-checks/) only.
- Supports only IPv4-based endpoint health checks.
Expand Down