Skip to content

Clarifying anycast on egress #18702

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 2 commits into from
Dec 12, 2024
Merged

Clarifying anycast on egress #18702

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
68bc044
Clarifying anycast on egress
ricardomacas Dec 11, 2024
935db54
Update src/content/docs/magic-transit/reference/egress.mdx
marciocloudflare Dec 12, 2024
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
1 change: 1 addition & 0 deletions src/content/docs/magic-transit/reference/egress.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,4 @@ If you have implemented Magic Transit with egress traffic, below is a list of te
- You may need to configure multiple GRE/IPsec tunnels as a way to load-share traffic sent to the Internet via Cloudflare. You can achieve this by applying two different PBR. Thus, traffic sourced from one IP/subnet is routed via one tunnel, and traffic from another IP/subnet is sent out via a different tunnel.
- Your Magic Firewall rules will apply in both directions. Ensure that your Magic Firewall rules are set up for your intended traffic flows, both in and out.
- If using Magic Transit egress then we recommend you set your GRE or IPSEC tunnel health check configuration to [bidirectional](/magic-transit/how-to/configure-tunnels/#add-tunnels), so that Cloudflare health checks are in-sync with the [data plane](https://en.wikipedia.org/wiki/Forwarding_plane) traffic flow.
- Once your traffic is configured to egress through the GRE/IPsec tunnel, it is encapsulated and sent to a Cloudflare anycast endpoint. Your ISP then routes the encapsulated traffic to the nearest available Cloudflare point of presence (PoP), where it exits to the Internet via Cloudflare's connectivity options at that location.
Loading