Configuring RIP in Gaia Portal

Important - In a ClusterClosed Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing., you must configure all the Cluster Members in the same way.

  1. From the left navigation tree, click the Advanced Routing > RIP.

  2. Optional: In the RIP Global Settings section, configure the applicable settings and click Apply Global Settings.

    Parameter

    Description

    Update Interval

    The amount of time between regularly scheduled RIP updates.

    To prevent synchronization of periodic updates, RIP updates are actually sent at a time from the uniform distribution on the interval (0.5*"Update Interval value", 1.5*"Update Interval value").

    Important - Be careful when you set this parameter, because RIP has no protocol mechanism to detect misconfiguration.

    Range: 1-65535 seconds

    Default: 30 seconds

    Expire Interval

    The amount of time that must pass with no update for a given route before the route is considered to have timed out.

    Note - This value must be 6 times the Update Interval before the network drops packets, which contain an update.

    Range: 1-65535 seconds

    Default: 180 seconds

    Auto Summarization

    Applies only to RIP v1.

    Controls whether to aggregate and redistribute automatically the non-classful RIP v1 into RIP v2.

    Important:

    • If you do not select this option, you must use route aggregation and route redistribution and configure the aggregation and redistribution manually.

    • Be careful when you configure this option, because RIP protocol has no mechanism to detect misconfiguration.

    Range: Selected, or Cleared

    Default: Selected

  3. In the RIP Interfaces section, add the applicable interfaces.

    1. Click Add.

    2. In the Interface field, select the applicable interface.

    3. In the Version field, select the RIP version.

      If you select v2, the default is to send full RIP v2 packets on the RIP multicast address.

      • Range: v1, or v2

      • Default: v1

    4. In the Metric field, enter the RIP metric.

      The RIP metric to add to routes that are sent with the specified interface(s).

      This is used to make other routers prefer other sources of RIP routes over this router.

      A higher metric means routes appear more expensive.

      Setting the metric to 0 or default removes the stored value.

      • Range: None, or 1-16

      • Default: None (to configure the default value, delete the current value 1-16)

    5. Select the Accept updates option.

      Controls if RIP packets from other routers, which use the interface, are accepted or ignored.

      Ignoring an update may result in suboptimal routing.

      Range: Selected, or Cleared

      Default: Selected

    6. Select the Send updates option.

      Controls if RIP packets are sent through the interface.

      If you do not select this option, the interface becomes a passive RIP listener.

      Range: Selected, or Cleared

      Default: Selected

    7. Select the Virtual Address option.

      Applies only to VRRP Cluster.

      Makes RIP run only on the VRRP Virtual IP address related to this interface.

      If this router is not a VRRP Master, then RIP does not run, if this option is selected. It only runs on the VRRP Master.

      Make sure that VRRP is configured to accept connections to VRRP IP addresses.

      Note - You must use VRRP Monitored Circuit mode, when you configure VRRP to work with Virtual IP addresses, and when you configure Virtual IP support for a dynamic routing protocol, including RIP.

      Range: Selected, or Cleared

      Default: Cleared

    8. In the Transport field, select how to send the RIP packets.

      In the Multicast mode, RIP v2 packets are sent as multicast on this interface.

      • Range: Multicast, or Broadcast

      • Default: Multicast

    9. In the Authentication Type field, select the authentication type.

      Applies only to RIP v2.

      The type of authentication scheme to use for the link.

      In general, routers on a given link must agree on the authentication configuration in order to form neighbor adjacencies.

      This is used to guarantee that routing information is accepted only from trusted routers.

      • None: There is no authentication scheme for the interface to accept routing information from neighboring routers.

      • Simple: Implements a simple authentication scheme for the interface to accept routing information from neighboring routers.

        In the Simple Password field, enter a password that contains from 1 to 16 characters.

        These characters are supported:

        • a-z

        • A-Z

        • 0-9

      • MD5: Implements an authentication scheme that uses an MD5 algorithm for the interface to accept routing information from neighboring routers.

        In the MD5 Key field, enter a password that contains from 1 to 16 characters.

        These characters are supported:

        • a-z

        • A-Z

        • 0-9

        • ` ~ ! @ # % ^ & * ( ) { } [ ] : ; , . _ - + =

        Select the Cisco Compatibility option to ensure interoperability with Cisco routers running RIP MD5 authentication.

        By default, RIP MD5 is set to conform to the Check Point standard, and not for Cisco compatibility.

      • Range: None, Simple, or MD5

      • Default: None

    10. Click Save.