> Source: [sk183976](https://support.checkpoint.com/results/sk/sk183976)

# sk183976 - Static Route Missing from Kernel Routing Table after Adding New Entry

| Property | Value |
|----------|-------|
| Solution ID | sk183976 |
| Date Created | 2025-09-22 |
| Last Modified | 2026-01-31 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20, R81.10 (EOS) |
| OS | Gaia |

## Symptoms

- * After adding a static route, the system does not display the route in the kernel routing table.
* No error is reported during route addition, but network traffic is not routed as expected.

## Cause

The issue occurs due to a mismatch in network configuration. Specifically, the network mask of the relevant port or the next hop configuration does not meet the requirements to install the static route in the kernel routing table. As a result, although the route appears in configuration files, it is not activated in the kernel routing table, and traffic is not routed as expected.

## Solution

1. **Review Port and Next Hop Configuration:**

<!-- -->

1.
   * Verify the network mask of the port associated with the static route.
   * Confirm that the next hop address is reachable and correctly configured.
   * Verify that the interface you are working with is state "UP". If the interface is state "DOWN" the routing table (even in vsx) will only show the directly connected route to that interface. It will not show any routes attached to that interface. Even if they are in /config/active for Gaia. Any routes you add will not appear if an interface is state "DOWN"  

2. **Adjust Network Mask or Next Hop:**
   * Extend the network mask of the relevant port to match the requirements for the static route.
   * Alternatively, set a different next hop address that is valid for the route.  

3. **Apply Configuration Changes:**   
   After making the necessary adjustments, re-add the static route using Gaia Clish or the appropriate command.  

4. **Verify Route Installation:**
   * Check the kernel routing table to confirm the route is present.
   * Ensure network traffic is routed as intended.

   [](https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_Gaia_AdminGuide/Topics-GAG/IPv4-Static-Routes-Gaia-Clish.htm)
5. **Verify that the interface you are working on is state "UP"**
   * If the interface is down the routing table (even in vsx) will only show the directly connected route to that interface. It will not show any routes attached to that interface. Even if they are in /config/active for Gaia.

<br />

**Note:** For related commands, see the Gaia Administration Guide for your version:  
[R81.20](https://sc1.checkpoint.com/documents/R81.20/WebAdminGuides/EN/CP_R81.20_Gaia_AdminGuide/Content/Front-Matter/Important-Information-GAG.htm?tocpath=_____1) \| [R81.10](https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_Gaia_AdminGuide/Front-Matter/Important-Information-GAG.htm?tocpath=_____1)  

<br />

**Best Practice:** Always verify port and next hop configurations before adding static routes.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content