Skip to content

Commit 4874b37

Browse files
marciocloudflareOxyjun
authored andcommitted
[Magic] BGP Magic routing table info vs PNI peering (#19548)
* added routing table info * refined text * added links * Update src/content/partials/network-interconnect/bgp-peering.mdx Co-authored-by: Jun Lee <[email protected]> --------- Co-authored-by: Jun Lee <[email protected]>
1 parent 838a447 commit 4874b37

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

src/content/partials/network-interconnect/bgp-peering.mdx

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,24 @@ With this functionality, customers can:
2121
- Secure the session by MD5 authentication to prevent misconfigurations.
2222
- Exchange routes dynamically between their devices and their Magic routing table.
2323

24+
## Peering with the Magic routing table
25+
26+
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).
27+
28+
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:
29+
30+
- 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).
31+
- 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/).
32+
33+
The Magic routing table supports IPv4 routes to:
34+
35+
- [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) address space
36+
- [BYOIP](/byoip/) public address space which you have onboarded to Cloudflare Magic Transit
37+
38+
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).
39+
40+
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.
41+
2442
## Route distribution and convergence
2543

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

0 commit comments

Comments
 (0)