|
| 1 | +# Static and Default Routing |
| 2 | + |
| 3 | +This guide explains how to configure **static** and **default routing** on routers using **Cisco Packet Tracer**. Both types of routing are important for controlling the flow of traffic within a network and ensuring that packets are routed correctly. |
| 4 | + |
| 5 | +## Table of Contents |
| 6 | +- [Introduction](#introduction) |
| 7 | +- [Static Routing](#static-routing) |
| 8 | + - [Step 1: Basic Static Route Configuration](#step-1-basic-static-route-configuration) |
| 9 | + - [Step 2: Verifying Static Route](#step-2-verifying-static-route) |
| 10 | +- [Default Routing](#default-routing) |
| 11 | + - [Step 1: Basic Default Route Configuration](#step-1-basic-default-route-configuration) |
| 12 | + - [Step 2: Verifying Default Route](#step-2-verifying-default-route) |
| 13 | +- [Troubleshooting Routing](#troubleshooting-routing) |
| 14 | +- [Conclusion](#conclusion) |
| 15 | +- [References](#references) |
| 16 | + |
| 17 | +--- |
| 18 | + |
| 19 | +## Introduction |
| 20 | + |
| 21 | +In networking, routers use **routing tables** to determine where to send packets. Routers can learn about routes dynamically or through manual configuration. **Static routing** requires manual configuration of routes, while **default routing** is a special type of static route that defines where to send traffic when no specific route exists in the routing table. |
| 22 | + |
| 23 | +--- |
| 24 | + |
| 25 | +## Static Routing |
| 26 | + |
| 27 | +### What is Static Routing? |
| 28 | + |
| 29 | +Static routing involves manually configuring routes on the router. It provides direct control over routing but requires manual intervention when there are network topology changes. |
| 30 | + |
| 31 | +### Step 1: Basic Static Route Configuration |
| 32 | + |
| 33 | +1. **Enter global configuration mode**: |
| 34 | + ```bash |
| 35 | + configure terminal |
| 36 | + ``` |
| 37 | +2. To create a static route, use the following syntax: |
| 38 | + ```bash |
| 39 | + ip route <destination_network> <subnet_mask> <next_hop_ip_address or exit_interface> |
| 40 | + ``` |
| 41 | + Example: |
| 42 | + ```bash |
| 43 | + ip route 192.168.2.0 255.255.255.0 192.168.1.2 |
| 44 | + ``` |
| 45 | + In this example, traffic destined for the `192.168.2.0` network will be sent to the next hop IP address `192.168.1.2`. |
| 46 | + |
| 47 | +3. Alternatively, you can specify the **exit interface** instead of the next hop IP address: |
| 48 | + ```bash |
| 49 | + ip route 192.168.2.0 255.255.255.0 gigabitEthernet 0/1 |
| 50 | + ``` |
| 51 | + |
| 52 | +### Step 2: Verifying Static Route |
| 53 | + |
| 54 | +After configuring the static route, use the following command to verify if the route has been added to the routing table: |
| 55 | +```bash |
| 56 | +show ip route |
0 commit comments