Skip to content

[Magic] BGP Magic routing table info vs PNI peering #19548

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 4 commits into from
Jan 30, 2025
Merged

[Magic] BGP Magic routing table info vs PNI peering #19548

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ff63bc3
added routing table info
marciocloudflare Jan 30, 2025
cb20ecd
refined text
marciocloudflare Jan 30, 2025
4f9fc67
added links
marciocloudflare Jan 30, 2025
581f53e
Update src/content/partials/network-interconnect/bgp-peering.mdx
marciocloudflare Jan 30, 2025
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
18 changes: 18 additions & 0 deletions src/content/partials/network-interconnect/bgp-peering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,24 @@ With this functionality, customers can:
- Secure the session by MD5 authentication to prevent misconfigurations.
- Exchange routes dynamically between their devices and their Magic routing table.

## Peering with the Magic routing table

For both Magic WAN and Magic Transit use cases, BGP peering is with the Magic networking routing table (as opposed to peering with the Cloudflare Internet global network).

The Magic networking routing table is a virtual network overlay, private to your account, that spans all Cloudflare data centers globally. This overlay network provides:

- Magic Transit packet delivery for [DoS](/ddos-protection/) and [Magic Firewall](/magic-firewall/) filtered Internet traffic, from the entry data center where the traffic ingressed, to your publicly addressed edge/border network via tunnels (GRE/IPsec) or interconnect (CNI).
- Magic WAN packet transport between Magic tunnels, interconnects, [Cloudflare Load Balancer](/load-balancing/), and [Zero Trust](/cloudflare-one/) connections such as [WARP Client](/cloudflare-one/connections/connect-devices/warp/), [Remote Browser Isolation](/cloudflare-one/policies/browser-isolation/), [Access](/cloudflare-one/policies/access/), and [Gateway](/cloudflare-one/policies/gateway/).

The Magic routing table supports IPv4 routes to:

- [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) address space
- [BYOIP](/byoip/) public address space which you have onboarded to Cloudflare Magic Transit

BGP peers configured by following this guide will receive advertisements for all prefixes in the Magic routing table plus any additional prefixes configured in the per-interconnect [Advertised prefix list](#how-to-set-up-bgp-peering).

If instead you are seeking to do public peering with the Cloudflare ASN 13335 at one of the Cloudflare data centers, refer to [PNI and peering setup](/network-interconnect/pni-and-peering/). Note that it is not currently possible to share Magic network BGP peering and PNI on the same physical interconnect port.

## Route distribution and convergence

Routes received from the customer device will be redistributed into the Magic routing table, which is used by both Magic WAN and Magic Transit.
Expand Down
Loading