You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/partials/networking-services/routing/configure-routes.mdx
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,10 @@ Refer to <a href={props.trafficSteeringPage}>Traffic Steering</a> for more infor
31
31
4. Enter a descriptive name for your route in **Description**.
32
32
5. In **Prefix**, enter your range of IP addresses. For example, `10.10.10.100/24`.
33
33
6. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in <ahref={props.tunnelEndpoints}>Configure tunnel endpoints</a>.
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 <ahref={props.routePrioritization}>Route prioritization</a> for more information
34
+
7. Choose the **Priority** for your route. Lower numbers have higher priorities.
35
+
:::note
36
+
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 <ahref={props.routePrioritization}>Route prioritization</a> for more information.
37
+
:::
35
38
8. (Optional) Choose a **Weight** for your route. Refer to <ahref={props.chooseWeights}>Set priority and weights for static routes</a> for examples.
36
39
9. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**.
37
40
10. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**.
0 commit comments