Configuring IPv4 Static Routes in Gaia Clish

Description

Configure, show, and delete IPv4 static routes.

Syntax

Note - There are no "add" commands for the static route feature.

Important - After you add, configure, or delete features, run the "save config" command to save the settings permanently.

Parameters

CLI Parameters

Parameter

Description

default

Defines the default static IPv4 route.

<Destination IPv4 Address>

Specifies the IPv4 address of destination host or network using the CIDR notation (IPv4 Address / Mask Length).

Example: 192.168.2.0/24

You can use the default keyword instead of an IPv4 address when referring to the default route.

comment {"Text" | off}

Defines of removes the optional comment for the static route.

Write the text in double quotes.
Text must be up to 100 characters.
This comment appears in the Gaia Portal Web interface for the Check Point Gaia operating system. and in the output of the "show configuration" command.

nexthop

Defines the next hop path, which can be a gateway, blackhole, or reject.

gateway

Specifies that this next hop accepts and sends packets to the specified destination.

blackhole

Specifies that this next hop drops packets, but does not send ICMP unreachable packet to the traffic source.

reject

Specifies that this next hop drops packets and sends ICMP unreachable packet to the traffic source.

address <IPv4 Address of Next Hop Gateway>

Specifies the IPv4 address of the next hop gateway.

logical <Name of Local Interface>

Identifies the next hop gateway by the name of the local interface that connects to it.

Use this option only if the next hop gateway has an unnumbered interface.

monitored-ip <Monitored IP Address> {on | off}

Remote IPv4 address to monitor for the next hop gateway.

Monitors IP address(es) configured with the "ip-reachability-detection".

The next hop gateway becomes usable with respect to reachability of IP address(es) reported from the "ip-reachability-detection".

monitored-ip-option {fail-all | fail-any | force-if-symmetry {on | off}}

Set failure condition and flavor for the configured monitored IP address(es).

fail-all

Fails the next hop gateway when all monitored IP addresses become unreachable.

Restores the next hop gateway when one of the monitored IP addresses becomes reachable.

Default: off
fail-any

Fails the next hop gateway when one of the monitored IP addresses becomes unreachable.

Restores the next hop gateway when all monitored IP addresses become reachable.

Default: on
force-if-symmetry

Ignores IP reachability reports from IP addresses with asymmetric traffic.

Default: off

priority <Priority>

Defines which gateway to select as the next hop when multiple gateways are configured.

The lower the priority, the higher the preference - priority 1 means the highest preference, and priority 8 means the lowest preference.

You can define two or more paths with the same priority to specify a backup path with equal priority.

A next hop gateway with no priority configured is preferred over a next hop gateway with priority configured

nexthop ... on

Adds the specified next hop gateway.

nexthop ... off

Deletes the specified next hop gateway.

If you specify a next hop gateway, only the specified path is deleted.

If you do not specify a next hop gateway, the route and all related paths are deleted.

off

Removes the static route.

ping {on | off}

Enables (on) or disables (off) the ping of specified next hop gateways for IPv4 static routes.

The Ping feature sends ICMP Echo Requests to make sure the next hop gateway for a static route is working.

Gaia Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. includes in the kernel forwarding table only next hop gateways, which are verified as working.

When Ping is enabled, Gaia adds an IPv4 static route to the kernel forwarding table only after at least one next hop gateway is reachable.

To configure the ping behavior, run:

set ping count <value>

set ping interval <value>

rank <Rank>

Selects a route, if there are many routes to a destination that use different routing protocols.

The route with the lowest rank value is selected.

Use the rank keyword in place of the nexthop keyword with no other parameters.

Accepted values are: default (60), integer numbers from 0 to 255.

In addition, see this command: "set protocol-rank protocol <Rank>"

scopelocal {on | off}

Defines a static route with a link-local scope.

Use this setting on a Cluster Member Security Gateway that is part of a cluster., when the ClusterXL Virtual IPv4 address is in a different subnet than the IPv4 address of a physical interface.

This lets the Cluster Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing. Member accept static routes on the subnet of the Cluster Virtual IPv4 address.

To make sure that the scopelocal attribute is set correctly, run the "cat /etc/routed.conf" command.
For more information, see sk92799.