[Cloudflare WAN, Magic Transit] Add IPv6 support row to Unified Routing beta limitations#30531
Draft
steve-cloudflare wants to merge 1 commit intocloudflare:productionfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new "IPv6 Support" row to the Unified Routing beta limitations table in the shared Traffic steering reference. The row clarifies that IPv6 is supported for IPsec and GRE under Unified Routing, but Network Firewall support for IPv6 is currently limited to source/destination IP filtering.
This partial is shared between Cloudflare WAN and Magic Transit, so the new row appears on both products' Traffic steering pages.
PCX-21814
Documentation checklist