This article provides step-by-step information on how to install and configure dynamic routing protocols.
To configure OSPF/RIP/BGP settings, proceed with the following steps:
- Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > OSPF-RIP-BGP-Service.
- Click Lock.
- In the left menu, click Operational Setup. General parameters of the dynamic routing protocols, like enabling/disabling the protocol and handling of dynamic routes are configured.
If this parameter is set to yes, the OSPF/RIP/BGP wrapper gets started by the control daemon but does not start up the actual OSPF/RIP/BGP routing service.
Run OSPF Router
By setting this value the OSPF routing functionality can be enabled or disabled.
Run RIP Router
By setting this value the RIP routing functionality can be enabled or disabled.
|Run BGP Router||By setting this value the BGP routing functionality can be enabled or disabled.|
Allows overriding the propagated hostname, which by default is the box hostname.
The operation mode defines handling of route learning and propagation. The following settings are possible:
Every OSPF/BGP router is identified by its Router ID. This ID is defined by an IP address explicitly configured for this router.
Specifies the verbosity of the OSPF routing service:
|Use Special Routing Table||By setting this parameter to yes and selecting a table name below, routes learned by the OSPF 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 Policy Routes.|
|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 routes will be discarded.
|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.|
Multipath routes will be introduced.
|Ignore default route (Advanced Mode)||If enabled, the learned default route is not inserted into the routing table of the Barracuda NextGen Firewall F-Series, but at the same time is still propagated via OSPF. If you do not want the default route to be propagated, use an OSPF filter.|
For more detailed information on OSPF Router configuration, see How to Configure OSPF Routers and Areas.
This section, accessible via the link in the Configuration menu, can be specified the same way.
For more detailed information on RIP Router configuration, see How to Configure RIP Router Setup.
For a setup example including screenshots, see Example for OSPF and RIP Configuration.
BGP Router Setup
|AS Number||Number of the autonomous system this router belongs to.|
|Confederation Parent AS||Number of the autonomous system that internally includes multiple sub-autonomous systems (aka confederation).|
|Confederation Partners||Sub-autonomous system numbers belonging to same confederation.|
|Terminal Password||Password to connect to the BGP router through telnet. The system is reachable on loopback TCP port 2605.|
|Privileged Terminal Password||Password to enable configuration through a telnet connection.|
Enter all networks the BGP router should run on. When running a Exterior Gateway Protocol BGP router, enter your WAN network.
|Route Aggregations||Enter network addresses to perform route aggregation to decrease the size of routing tables.|
|Advanced settings||Configuration of advanced BGP Settings.|
|Log Level||Logging level of the BGP routing daemon.|
|Use Special Routing Table||Routes learned via BGP will not be introduced in main table, but in tables given below.|
|Table Names||Tables must exist in network configuration.|
For more detailed information on BGP Router configuration, see How to Configure BGP Router Setup.
GUI as Text
This parameter set is only available in Advanced View mode. The configuration done with the GUI is displayed here in quagga/Cisco commands.
- Show as Text – Set this to yes to show created OSPF syntax configuration after Send Changes.
- OSPF Text – Created OSPF syntax configuration. Shown, if Show as Text is set to yes.
- RIP Text – Created RIP syntax configuration. Shown, if Show as Text is set to yes.
- BGP Text – Created BGP syntax configuration. Shown, if Show as Text is set to yes.
Text Based Configuration
Configure dynamic routing here, if you do not want to configure it with the GUI. Already done GUI configuration will be replaced. Syntax as used for quagga or Cisco applies.
OSPF Configuration / Free Format RIP Configuration:
- Use Free Format – Set this to yes to use free OSPF/RIP syntax configuration.
- Free Format Text – OSPF/RIP/BGP syntax configuration. This field applies when parameter Use Free Format is set to yes.
Routing Configuration Example
- OSPF network prefix: 10.0.66.0/24
- Server IP: 10.0.66.98
- Box network route:10.0.66.0/24 via dev eth1
- Additional box network route: 10.0.0.0/8 via dev eth0
In this configuration example, the required box network route "10.0.66.0/24 via dev eth1" is completely included in the additional box network route (bold). This will lead to a mismatch in the OSPF configuration. OSPF will neither detect eth0 nor eth1 as OSPF enabled and therefore not work.
The OSPF/RIP service synchronizes externally learned routes with its HA partner. Routes cannot be introduced on the partner, while this is "passive" because network routes required to do so are missing. The external routes HA information is thus stored in a file and introduced on the HA system during startup of the OSPF/RIP service. Take over and startup of the OSPF/RIP service usually take a few seconds. The HA routes are introduced as protocol "extha" (number 245). These routes are then either replaced by newly learned external OSPF or RIP routes (protocols "ospfext" or "ripext") or removed with the HA garbage collection after five minutes.