Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Dashboard Users Guide > Manage > Network Manager > Actions > Networks > View a Network > View a Route Table > Create a New Route for a Route Table

Create a New Route for a Route Table

Table of Contents

Table of Contents

Prerequisites

  • You need the 'security_manager' role in your RightScale account.
  • Currently, route tables can only be created in AWS VPCs.

Overview

By default, a route table is created for a network and traffic is directed to the CIDR block address of the network. The default route cannot be modified. If you would like traffic routed outside of the network, such as to an Internet gateway or another network, you will need to create a new route from within a route table. You can create a route in either the default route table or another route table. When you create a route, you will need to specify where the traffic is coming from (the destination CIDR) and where it will be going to (the next hop). 

Steps

  1. Go to Manage > Network > select network > Route Tables and select your route table. 
  2. Click New Route

screen_CreateNewRouteforRouteTable.png

 

  1. Enter or select the following:
  • Destination CIDR: The CIDR address block of the incoming traffic. 
  • Next Hop: The location where the network traffic will be directed. It can either be an internet gateway attached to the network or a NAT instance in a VPC. For example, traffic coming from a CIDR address block of 172.0.0.0/24 will be directed to one of the Next Hop options. You can select one of the following:
    • Local - The default route of the network. When instances are launched within the network, the local route covers those instances by default. The local route cannot be modified.  
    • IP Address - Route to an individual IP address.
    • Instance - Route to an individual instance.
    • Network Gateway - Route to an internet gateway or a VPN gateway. 
  • Description: (Optional) The description of the route.
  1. Click Create.
Viewing 3 of 3 comments: view all
With Next Hop, you can control whether traffic is passed through an internet gateway attached to the network or a NAT instance in a VPC.

The location where the network traffic will be directed. It can either be an internet gateway attached to the network or a NAT instance in a VPC.


The routes target which can be either an internet gateway attached to the network or a NAT instances in the VPC.
Posted 09:56, 26 Dec 2013
<-- Isn't the destination CIDR a list of IP Addresses that can be coming to this route? Hop would be where the IP Address from the Destination CIDR is going? For example, traffic for a network gateway
Posted 09:54, 7 Jan 2014
When you create a subnet in a VPC, it's automatically associated to the route table rule created by default.

Since you can't modify the default route table, and if you would like to route traffic from outside the network, you will need to create a new route. Before you create a route, you must have



You must associate a subnet to a newly created route. If not, your subnet will automatically associate to the the default route table.

If you do not associate a subnet to a newly created route, your subnet will automatically associate to the default route table.

Example: When you create a subnet in a VPC, it's automatically associated to the route table rule created by default. This default route table can be configured to route traffic to the virtual private gateway.
Warning! But if your main route table is connected to an Internet Gateway, than any subnet you create will automatically connect to the default route table that will connect to an Internet gateway.
Posted 11:32, 7 Jan 2014
Viewing 3 of 3 comments: view all
You must to post a comment.
Last modified
11:41, 7 Jan 2014

Tags

This page has no custom tags.

Classifications

This page has no classifications.

Announcements

None


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.