Skip to content

Commit 74884dd

Browse files
added route priority note
1 parent ec6bdc4 commit 74884dd

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ params:
55
- trafficSteeringPage
66
- productName
77
- tunnelEndpoints
8+
- routePrioritization
89
- chooseWeights
910
- productGatewayOrEgress
1011
---
@@ -30,7 +31,7 @@ Refer to <a href={props.trafficSteeringPage}>Traffic Steering</a> for more infor
3031
4. Enter a descriptive name for your route in **Description**.
3132
5. In **Prefix**, enter your range of IP addresses. For example, `10.10.10.100/24`.
3233
6. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in <a href={props.tunnelEndpoints}>Configure tunnel endpoints</a>.
33-
7. Choose the **Priority** for your route. Lower numbers have higher priorities.
34+
7. Choose the **Priority** for your route. Lower numbers have higher priorities. You should also be aware that Cloudflare routing applies longest-prefix match. This means more specific routes will always be preferred over less specific ones. Refer to <a href={props.routePrioritization}>Route prioritization</a> for more information
3435
8. (Optional) Choose a **Weight** for your route. Refer to <a href={props.chooseWeights}>Set priority and weights for static routes</a> for examples.
3536
9. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**.
3637
10. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**.

0 commit comments

Comments
 (0)