Skip to content
Merged
Changes from 1 commit
Commits
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
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.
- After setting up your traffic to egress to your GRE/IPsec tunnel, it is sent encapsulated toward the Cloudflare anycast endpoint. Your ISP will route the encapsulated traffic to a nearby available Cloudflare point of presence where your traffic will exit to the Internet from our connectivity options at that location.
Loading