It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

How to Configure RIP Router Setup

  • Last updated on

 After enabling and configuring RIP, set up your RIP router. This article provides instructions on configuring global settings and network definitions that are used by RIP to advertise routes.

This tab only has to be configured when RIP has been activated in the Operational Setup tab through setting the Run RIP Router parameter to yes. Specification of global RIP settings such as version, timers and authentication, and definition of interfaces on which the RIP process is to run, is done in this place.

Configure RIP Router Setup

  1. Go to CONFIGURATION Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > OSPF-RIP-BGP-Service > OSPF/RIP/BGP Settings.
  2. Click Lock.
  3. In the left menu, select RIP Router Setup. In this section, the parameters can be specified as follows:

    RIP KeychainsKey/Key StringTo enable RIP authentication, so-called key chains must be introduced. A key chain can consist of several keys, where each key is identified by a number and a key string (password).
    RIP VersionThe Barracuda NextGen Firewall F-Series routing service allows usage of both standardized RIP versions RIPv1 or RIPv2. The following values are thus available for selection:
    • Version_1 (classful)
    • Version_2 (classless) 

    RIP Terminal Password

    Password to connect via telnet and query status information of the RIP router. The RIP router is reachable on TCP port 2604 (loopback only). This is mainly useful for debugging purposes. Note that remote connection to the RIP terminal is not possible.

    Privileged RIP Terminal PasswordPassword to connect via telnet and change configuration of the RIP router (not recommended since changes made via the terminal are not persistent). Note that remote connection to the RIP terminal is not possible.


    Route Update Filtering is used to provide Access Control Mechanisms and mechanisms to fine-tune RIP metrics.

    Metric Offsets
    Configuring Metric Offsets adds an offset to incoming and outgoing metrics to routes learned via RIP.

    • Update Direction
    • Enforced Metric
    • ACLs Devices

    Route In/Out Filters
    Route Filters are used to control the advertising and learning of routes in routing updates. Filters with the parameter Update Direction set to "in" apply to routes processed in incoming routing updates. The filter is matched against the content of the update, not against the source or destination of the routing update packets.
    • Update Direction
    • Object Type
    • ACLs
    • IP Prefix List
    • Devices

  4. In the RIP Preferences section, accessible from the Configuration menu, the settings can be specified as follows:


    Log Level

    Specifies the verbosity of the RIP routing service. Available values are:

    • critical
    • debugging
    • emergencies
    • errors
    • informational (default)
    • notifications
    • warnings
    • alerts

    Use Special Routing Table

    By setting this parameter to yes and selecting a table name below, routes learned by the RIP service are introduced into an own routing table. Note that the routing table is not automatically introduced, but has to be configured manually by introducing .

    Table Names

    A list of policy routing names can be specified here. Routes learned by the routing daemon are introduced into each of the enlisted routing tables.

    Multipath Handling

    • ignore - multipath routes will be discarded.

    RIP summarizes routes to multipath routes automatically if more than one next hop to a prefix exists. Use setting ignore with caution.

    • assign-internal-preferences - multipath routes will be translated to several routes with different metrics (preferences).
    • accept-on-same-device - multipath routes will be introduced as multipath if all nexthops are reachable on the same interface.
    • accept-all (default) - multipath routes will be introduced.
  5. Click Send Changes and Activate.
Last updated on