Skip to content

Commit f1f616e

Browse files
[BGP] Refined steps (#22016)
* refined name * refined step
1 parent 7601fdf commit f1f616e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/partials/networking-services/routing/configure-routes.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -299,7 +299,7 @@ You need to configure two ASNs:
299299
If you already have set up your Cloudflare account ASN, you can skip steps two and three below.
300300

301301
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
302-
2. Go to **{props.productName}** > **Configuration** > **BGP**.
302+
2. Go to **{props.productName}** > **Configuration** > **BGP configuration**.
303303
3. In **CF Account ASN**, enter Cloudflare's ASN.
304304
4. Go to **Interconnects**.
305305
5. Find the Direct CNI interconnect you want to configure with BGP > select the **three dots** next to it > **Configure BGP**.
@@ -308,4 +308,4 @@ If you already have set up your Cloudflare account ASN, you can skip steps two a
308308
8. (Optional) In **Advertised prefix list**, input the additional prefixes automatically assigned by Cloudflare during the creation of the CNI interconnect, to advertise alongside your existing routes. Leave blank if you do not want to advertise extra routes. <br /> Typical prefixes to configure here include:
309309
- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
310310
- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with WARP clients](/cloudflare-one/connections/connect-networks/private-net/warp-connector/user-to-site/#add-route-to-router).
311-
9. Select **Enable BGP**.
311+
9. Select **Save**.

0 commit comments

Comments
 (0)