Configuring IPv4 Static Routes in Gaia Portal

You can configure IPv4 static routes one at a time, or many routes at once.

Step

Instructions

1

In the navigation tree, click Network Management > IPv4 Static Routes.

2

In the IPv4 Static Routes section, click Add.

The Add Destination Route window opens.

3

In the Destination field, enter the IPv4 address of destination host, or network.

4

In the Subnet mask field, enter the subnet mask.

5

In the Next Hop Type field, select one of these:

  • Normal - To accept and forward packets

  • Blackhole - To drop packets, and not send ICMP unreachable packet to the traffic source

  • Reject - To drop packets, and send ICMP unreachable packet to the traffic source

6

In the Rank field, leave the default value (60), or enter the relative rank of the IPv4 static route (an integer from 1 to 255).

This value specifies the rank for the configured route when there are overlapping routes from different protocols.

7

Select the Local Scope option, if needed.

Use this setting on a Cluster MemberClosed 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 ClusterClosed 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.

8

In the Comment field, enter the applicable comment text (up to 100 characters).

9

Click Add Gateway and select one of these options:

  • Option 1:

    1. Select IP Address to specify the next hop by its IPv4 address.

    2. In the IPv4 Address field, enter the IPv4 address of the next hop gateway.

    3. In the Priority field, either do not enter anything, or select an integer between 1 and 8.

    4. Add Monitored IPs.

    5. Click OK.

  • Option 2:

    1. Select Network Interface to specify the next hop by the name of the local interface name that connects to it.

    2. In the Local Interface field, select an interface that connects to the next hop gateway.

    3. In the Priority field, either do not enter anything, or select an integer between 1 and 8.

    4. Add Monitored IPs.

    5. Click OK.

Notes:

  • Priority defines which next hop gateway to select when multiple next hop 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.

  • Multihop ping in Static Routes uses ICMP Echo Request to monitor reachability of an IP address multiple hops away. Multihop ping in Static Routes updates the status of an associated next hop in accordance to the reachability status. The next hop status becomes "down", if that IP address is unreachable.

10

If you defined a next hop gateway by IP Address, you can select the Ping option, if you need to monitor next hops for the IPv4 static route with the ping.

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

GaiaClosed 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.

11

Click Save.

12

In the Advanced Options section, you can configure the Ping behavior.

If you changed the default settings, click Apply.

You can use the batch mode to configure multiple static routes in one step.

Note - This mode does not allow the configuration of static routes that use a logical interface as the next hop.

Step

Instructions

1

In the navigation tree, click Network Management > IPv4 Static Routes.

2

In the Batch Mode section, click Add Multiple Static Routes.

3

In the Add Multiple Routes window, select the Next Hop Type:

  • Normal - To accept and forward packets

  • Blackhole - To drop packets, and not send ICMP unreachable packet to the traffic source

  • Reject - To drop packets, and send ICMP unreachable packet to the traffic source

4

Add the routes in the text box, using this syntax:

<Destination IPv4 Address>/<Mask Length> <IPv4 Address of Next Hop Gateway> ["<Comment>"]

Where:

  • <Destination IPv4 Address>/<Mask Length> - 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.

  • <IPv4 Address of Next Hop Gateway> - Specifies the IPv4 address of the next hop gateway

  • "<Comment>" - Optional. Free text comment for the static route.

    Write the text in double quotes. Maximal length of the text string is 100 characters.

Example:

default 192.0.2.100 192.0.2.1 "Default Route"
192.0.2.200/24 192.0.2.18 "My Backup Route"

5

Click Apply.

The newly configured static routes show in the IPv4 Static Routes section.

Note - The text box shows entries that contain errors with messages at the top of the page.

6

Correct errors and reload the affected routes.

7

In the top right corner, click the Monitoring tab to make sure that the routes are configured correctly.