| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2019-11-03 |
secure, region, zone, subnet, routing, terminology, public gateway, floating IP, NAT, API |
vpc |
{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tip: .tip} {:note: .note} {:important: .important} {:download: .download} {:DomainName: data-hd-keyref="DomainName"}
{: #advanced-routing}
You can control the flow of network traffic in your VPC by configuring routes. Use routes to specify the next hop for packets, based on their destination addresses. {:shortdesc}
Separate route tables exist for each zone in your VPC. When a packet leaves a subnet, it is evaluated against the route table in the subnet's zone to determine where to send the packet next. Each route table has a default route, but you can add custom static routes to your routing tables.
A VPC route has three main components: the destination CIDR, the next hop to which to route packets, and the zone. Any traffic that originates in the specified zone of the VPC and has a destination address within the specified destination CIDR is routed to the next hop. If the destination address is within the destination CIDR for multiple VPC routes, the most specific route is used. If there are two or more equally specific routes, the traffic is round-robin distributed between each route.
{: #create-route}
{: #create-a-route-from-the-user-interface}
Go to the details page for a VPC and click Routes in the navigation.
{: #create-a-route-using-the-cli}
Use the ibmcloud is vpc-route-create command.
{: #create-a-route-using-the-api}
Use the routes API.
{: #routing-limitations}
- Currently, custom default static routes are not available. Only non-default static routes are supported.
- You can set the next hop to be an IP address only.